November 2009 - virt - Fedora Mailing-Lists

Re: [fedora-virt] release notes virt passage seems overly pessimistic

by Dale Bewley

----- "Robert P. J. Day" <rpjday(a)crashcourse.ca> wrote: > reading here: > > http://docs.fedoraproject.org/release-notes/f12/en-US/html/sect-Release_N... > > down at the bottom: > > "KVM requires hardware virtualization features in the host system. > > Systems lacking hardware virtualization do not support Xen guests at > this time." > > if one is new to virt, that could be read as, "without HW virt, > you're pretty much screwed." or could that be worded a bit > differently? This is the same text carried over from 10 and 11. http://docs.fedoraproject.org/release-notes/f10/en_US/What_Do_System_Admi... While Xen does not require hardware support, KVM still (always will?) does. Xen guests on Fedora still require KVM-based xenner. There has been success with Xen dom0 on experimental 3rd party kernels, but that may be beyond the scope of the release notes. We wouldn't want it to be inferred as a recommendation. Hopefully the F13 release notes will be able to describe native support for Xen dom0 hosts. http://fedoraproject.org/wiki/FWN/Issue202#No_Xen_dom0_in_Fedora_12_Hopef... If you have any suggestions for further improvement to the release notes, please keep them coming. -- Dale

14 years, 5 months

2
1
0 / 0

release notes virt passage seems overly pessimistic

by Robert P. J. Day

reading here: http://docs.fedoraproject.org/release-notes/f12/en-US/html/sect-Release_N... down at the bottom: "KVM requires hardware virtualization features in the host system. Systems lacking hardware virtualization do not support Xen guests at this time." if one is new to virt, that could be read as, "without HW virt, you're pretty much screwed." or could that be worded a bit differently? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ========================================================================

14 years, 5 months

2
1
0 / 0

Fedora virt status

by Mark McLoughlin

Fedora 12 Release ================= Yay! Fedora 12 was released on Tuesday: http://fedoraproject.org/wiki/Fedora_12_Announcement Thanks to all who help get this release out! There was a single response to my call for a "witty tagline" for Fedora 12, so I went with Avi's "Dirty Dozen" suggestion - it's Fedora *12* and we have *12* virt features listed so ... :-) https://fedoraproject.org/wiki/Virtualization/History#Fedora_12:_The_Dirt... Note also that the marketing folks have posted an interview with some of the Fedora virt developers here: https://fedoraproject.org/wiki/Virtualization_improvements_in_Fedora_12 Fedora 12 includes a number of improvements in the field of Virtualization. New tools enable system administrators to perform nearly impossible - until now - tasks easily. Imagine re-configuring a virtual machine off-line, add new hardware to VM with out restarting it, migrate to another host without restarting the VMs and many other exotic features. Let's hear what developers have to say about those wonderful new options. virt-preview ============ Justin Forbes announced the availability of a virt-preview repository for Fedora 12 users: http://www.redhat.com/archives/fedora-virt/2009-November/msg00041.html A couple of improvements have been made this time around. Namely packages are build with mock instead of koji so that new packages can be used a BuildRequires for other new packages. Also new builds are triggered by successful koji builds of tracked packages against dist-rawhide, so the process is a bit more automated. These improvements should make virt-preview a hell of a lot more useful and manageable. Kudos Justin! Release Blockers ================ As with any release, we went through a couple of fire-drills with last-minute serious blocker bugs: https://bugzilla.redhat.com/526549 rawhide/i386 kvm host corrupts data of guests https://bugzilla.redhat.com/533063 preadv()/pwritev() prototypes are broken on i386 with -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 KVM guests on 32 bit hosts were seeing data corruption in some circumstances. After huge efforts from Justin Forbes, James Laska and Milan Broz to get the issue narrowed down to qemu, yours truly bisected it to the introduction of preadv/pwritev support. I happened to be sitting around a table with Dan Berrange, Chris Wright, Stephen Tweedie, Herbert Xu and Dor Laor at the time and all chipped in helping to figure out the issue. Eventually, danpb found the issue with glibc's preadv()/pwritev() prototypes in its headers and a simple fix sorted the issue out just in time for the release. Now there's a team effort! Another saga was going on in parallel on the VT-d front: https://bugzilla.redhat.com/524808 swiotlb should be enabled when VT-d setup fails This got recognized as a critical issue very late in the release as it was realized that there are plenty of users who will have VT-d enabled in the BIOS, certain broken BIOSes and >4Gb memory (including swap). In the end dwmw2's patch was included and tested by multiple people, so intel_iommu=on is still the default in Fedora 12. https://bugzilla.redhat.com/533952 DMAR: kernel panic with 2.6.31.5-127.fc12.i686 But then this issue came to prominence post-release, and it turns out the fix for bug #524808 broke those machines with fault BIOSes and <4Gb of RAM. Sometimes you just can't win! Lots of folks have been battling away at these bugs including David Woodhouse, Chris Wright, Adam Williamson and a whole bunch of others. Mount guest filesystems in the host =================================== Rich Jones continues rocking with yet another cool feature: http://www.redhat.com/archives/fedora-virt/2009-November/msg00001.html We just built a package called 'libguestfs-mount' in Rawhide which lets you mount virtual machines' filesystems on the host, using FUSE. Rich may have announced this very quietly, but sit up and take note - this is damn useful! Bugs ==== DOOM-O-METER: 186 bugs open three weeks ago, only 173 now! == Ongoing == === kernel === https://bugzilla.redhat.com/532009 "kvm_run: failed entry, reason 7" when running guest with F11 LiveCD Looks like an issue starting a guest on a F11 AMD host. === qemu ==== https://bugzilla.redhat.com/539365 qemu's system_powerdown doesn't work with Windows XP Now that virtinst enables acpi for XP guests, we're noticing that 'virsh shutdown' has no effect on them. That may be just due to a lack of ACPI support in the guest. https://bugzilla.redhat.com/id=538047 Any use of QEMU's vvfat driver always abort()s the whole process Dan Berrange discovered this nasty hack which causes glibc to abort qemu. === libvirt === https://bugzilla.redhat.com/537938 restore fails with large files; libvirtd becomes unresponsive Charles Duffy reported this issue and proposed a fix. Apparently this isn't needed upstream anymore, but we may still need it for F-12. https://bugzilla.redhat.com/532654 virsh save hangs in Fedora12 rawhide SELinux related issues breaking save/restore. https://bugzilla.redhat.com/536760 SELinux is preventing /usr/bin/qemu-kvm "write" access on sr0 It looks like we're getting AVCs because qemu is trying to open read-only images for writing. === python-virtinst === https://bugzilla.redhat.com/492082 python-virtinst: add a label to newly created disks? This has come back full circle again. Now that the anaconda guys have refused to do anything about it, our only option is to figure out some way of labelling the disk before starting the guest. === virt-manager === https://bugzilla.redhat.com/532216 virt-manager should disable unimplemented reboot option for qemu/kvm libvirt doesn't implement reboot for KVM (#496537), yet the button is still available in virt-manager. https://bugzilla.redhat.com/537221 virt-manager: URL install should prompt to change scratchdir perms virt-manager is downloading kernel and initrds to the users home directory where qemu cannot read them. Proposal is that virt-manager should prompt to change the ACLs on this dir like it does for ISOs. == Resolved == === kernel === https://bugzilla.redhat.com/532215 KSM bad_page() issue preventing VM startup Justin Forbes has cherry-picked a fix from upsteam into the kernel in updates. === qemu === https://bugzilla.redhat.com/539583 qemu use-after-free crash in slirp/m_free() A couple of days after the F-12 release, we get a report of a very obvious crasher in qemu 0.11.0's slirp code. One really does wonder how these things get unnoticed until after the release :-) https://bugzilla.redhat.com/533573 qemu-img convert can't handle parallels images above 4GiB David Woodhouse sent a patch upstream to fix this. === xen === https://bugzilla.redhat.com/521800 kernel backtrace: possible recursive locking detected on Xen domU Apparently this problem just disappeared with a recent 2.6.31 kernel.

14 years, 5 months

1
0
0 / 0

Sound status on VM?

by Paul Lambert

Does sound now work with a VM? I am using rawhide x86_64 for the host and FE-11 x86 for the guest. I also have a Windows XP VM. The VM hardware shows es1370. The host sound plays mp3s using either Totem or Rhythmbox just fine but no sound from either VM. Thanks Paul

14 years, 5 months

3
2
0 / 0

f11 rawvirt to f12: problems?

by Gianluca Cecchi

Having F11 + fedora-virt-preview repo, with some Linux guests running without problems. Then updated to F12 After some pains with preupgrade and upgrade, finally I was on F12 Actually I probably have to prune the duplicates because: [root@ ~]# rpm -qa libvirt\* qemu\* virt-manager\* qemu-common-0.11.0-11.fc11.x86_64 virt-manager-0.8.0-7.fc12.noarch libvirt-client-0.7.1-15.fc12.x86_64 qemu-common-0.11.0-11.fc12.x86_64 qemu-img-0.11.0-11.fc11.x86_64 qemu-img-0.11.0-11.fc12.x86_64 qemu-kvm-0.11.0-11.fc12.x86_64 libvirt-python-0.7.1-15.fc12.x86_64 qemu-system-x86-0.11.0-11.fc12.x86_64 libvirt-0.7.1-15.fc12.x86_64 (in the mean time I disabled fedora-virt-preview repo) So on 18th of November I booted the server with Nov 18 17:30:12 virtfed kernel: Linux version 2.6.31.5-127.fc12.x86_64 (mockbuild(a)x86-4.fedora.phx.redhat.com) (gcc version 4.4.2 20091027 (Red Hat 4.4.2-7) (GCC) ) #1 SMP Sat Nov 7 21:11:14 EST 2009 . I found this trace at boot: Nov 18 17:30:12 virtfed kernel: ------------[ cut here ]------------ Nov 18 17:30:12 virtfed kernel: WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:456 generic_get_mtrr+0xcc/0x10a() (Not tainted) Nov 18 17:30:12 virtfed kernel: Hardware name: ProLiant BL480c G1 Nov 18 17:30:12 virtfed kernel: mtrr: your BIOS has set up an incorrect mask, fixing it up. Nov 18 17:30:12 virtfed kernel: Modules linked in: radeon(+) ttm drm_kms_helper drm i2c_algo_bit i2c_core Nov 18 17:30:12 virtfed kernel: Pid: 183, comm: work_for_cpu Not tainted 2.6.31.5-127.fc12.x86_64 #1 Nov 18 17:30:12 virtfed kernel: Call Trace: Nov 18 17:30:12 virtfed kernel: [<ffffffff81051694>] warn_slowpath_common+0x84/0x9c Nov 18 17:30:12 virtfed kernel: [<ffffffff81051703>] warn_slowpath_fmt+0x41/0x43 Nov 18 17:30:12 virtfed kernel: [<ffffffff812aab35>] ? bus_find_device+0x88/0x98 Nov 18 17:30:12 virtfed kernel: [<ffffffff810227a4>] generic_get_mtrr+0xcc/0x10a Nov 18 17:30:12 virtfed kernel: [<ffffffff8102170e>] mtrr_add_page+0x16c/0x34a Nov 18 17:30:12 virtfed kernel: [<ffffffff81021934>] mtrr_add+0x48/0x54 Nov 18 17:30:12 virtfed kernel: [<ffffffffa007782a>] radeon_object_init+0x2e/0x87 [radeon] Nov 18 17:30:12 virtfed kernel: [<ffffffffa0089b3b>] r100_init+0x19d/0x23c [radeon] Nov 18 17:30:12 virtfed kernel: [<ffffffff8129e035>] ? vga_client_register+0x72/0x7d Nov 18 17:30:12 virtfed kernel: [<ffffffffa006c107>] radeon_device_init+0x203/0x27d [radeon] Nov 18 17:30:12 virtfed kernel: [<ffffffffa006cb35>] radeon_driver_load_kms+0xff/0x13a [radeon] Nov 18 17:30:12 virtfed kernel: [<ffffffffa00183ba>] drm_get_dev+0x36e/0x46f [drm] Nov 18 17:30:12 virtfed kernel: [<ffffffff81063af6>] ? do_work_for_cpu+0x0/0x2a Nov 18 17:30:12 virtfed kernel: [<ffffffffa009f670>] radeon_pci_probe+0x15/0x269 [radeon] Nov 18 17:30:12 virtfed kernel: [<ffffffff812101e1>] local_pci_probe+0x17/0x1b Nov 18 17:30:12 virtfed kernel: [<ffffffff81063b0e>] do_work_for_cpu+0x18/0x2a Nov 18 17:30:12 virtfed kernel: [<ffffffff81067765>] kthread+0x91/0x99 Nov 18 17:30:12 virtfed kernel: [<ffffffff81012daa>] child_rip+0xa/0x20 Nov 18 17:30:12 virtfed kernel: [<ffffffff810676d4>] ? kthread+0x0/0x99 Nov 18 17:30:12 virtfed kernel: [<ffffffff81012da0>] ? child_rip+0x0/0x20 Nov 18 17:30:12 virtfed kernel: ---[ end trace 5173c14fe23b4391 ]--- the system is a standalone node of a cluster (based on cman/rgmanager as provided in F11, now F12) I started two CentOS 5.4 vms and started ksm and ksmtuned [root@virtfed ~]# cat /sys/kernel/mm/ksm/pages_shared 2000 This morning I found the two guests in shutdown mode and these messages: Nov 20 08:22:06 virtfed kernel: script.sh invoked oom-killer: gfp_mask=0x201da, order=0, oomkilladj=0 Nov 20 08:22:06 virtfed kernel: script.sh cpuset=/ mems_allowed=0 Nov 20 08:22:06 virtfed kernel: Pid: 14360, comm: script.sh Tainted: G W 2.6.31.5-127.fc12.x86_64 #1 Nov 20 08:22:06 virtfed kernel: Call Trace: Nov 20 08:22:06 virtfed kernel: [<ffffffff8108a7d7>] ? cpuset_print_task_mems_allowed+0x91/0x9d Nov 20 08:22:06 virtfed kernel: [<ffffffff810c38e9>] oom_kill_process+0x98/0x256 Nov 20 08:22:06 virtfed kernel: [<ffffffff810c3d6a>] ? select_bad_process+0xa3/0x102 Nov 20 08:22:06 virtfed kernel: [<ffffffff810c3e53>] __out_of_memory+0x8a/0x99 Nov 20 08:22:06 virtfed kernel: [<ffffffff810c3fc5>] out_of_memory+0x163/0x195 Nov 20 08:22:06 virtfed kernel: [<ffffffff810c75c1>] __alloc_pages_nodemask+0x491/0x584 Nov 20 08:22:06 virtfed kernel: [<ffffffff810eb1c4>] alloc_pages_current+0x95/0x9e Nov 20 08:22:06 virtfed kernel: [<ffffffff810c15c1>] __page_cache_alloc+0x5f/0x61 Nov 20 08:22:06 virtfed kernel: [<ffffffff810c9235>] __do_page_cache_readahead+0x98/0x176 Nov 20 08:22:06 virtfed kernel: [<ffffffff810c9334>] ra_submit+0x21/0x25 Nov 20 08:22:06 virtfed kernel: [<ffffffff810c1abd>] filemap_fault+0x193/0x317 Nov 20 08:22:06 virtfed kernel: [<ffffffff810d6641>] __do_fault+0x54/0x3c4 Nov 20 08:22:06 virtfed kernel: [<ffffffff810d881a>] handle_mm_fault+0x2f6/0x705 Nov 20 08:22:06 virtfed kernel: [<ffffffff810f185d>] ? virt_to_head_page+0xe/0x2f Nov 20 08:22:06 virtfed kernel: [<ffffffff811012ec>] ? free_bprm+0x44/0x49 Nov 20 08:22:06 virtfed kernel: [<ffffffff8141cfe1>] do_page_fault+0x281/0x299 Nov 20 08:22:06 virtfed kernel: [<ffffffff8141af75>] page_fault+0x25/0x30 Nov 20 08:22:06 virtfed kernel: Mem-Info: Nov 20 08:22:06 virtfed kernel: Node 0 DMA per-cpu: Nov 20 08:22:06 virtfed kernel: CPU 0: hi: 0, btch: 1 usd: 0 Nov 20 08:22:06 virtfed kernel: CPU 1: hi: 0, btch: 1 usd: 0 Nov 20 08:22:06 virtfed kernel: CPU 2: hi: 0, btch: 1 usd: 0 Nov 20 08:22:06 virtfed kernel: CPU 3: hi: 0, btch: 1 usd: 0 Nov 20 08:22:06 virtfed kernel: CPU 4: hi: 0, btch: 1 usd: 0 Nov 20 08:22:06 virtfed kernel: CPU 5: hi: 0, btch: 1 usd: 0 Nov 20 08:22:06 virtfed kernel: CPU 6: hi: 0, btch: 1 usd: 0 Nov 20 08:22:06 virtfed kernel: CPU 7: hi: 0, btch: 1 usd: 0 Nov 20 08:22:06 virtfed kernel: Node 0 DMA32 per-cpu: Nov 20 08:22:06 virtfed kernel: CPU 0: hi: 186, btch: 31 usd: 164 Nov 20 08:22:06 virtfed kernel: CPU 1: hi: 186, btch: 31 usd: 23 Nov 20 08:22:06 virtfed kernel: CPU 2: hi: 186, btch: 31 usd: 100 Nov 20 08:22:06 virtfed kernel: CPU 3: hi: 186, btch: 31 usd: 0 Nov 20 08:22:06 virtfed kernel: CPU 4: hi: 186, btch: 31 usd: 47 Nov 20 08:22:06 virtfed kernel: CPU 5: hi: 186, btch: 31 usd: 51 Nov 20 08:22:06 virtfed kernel: CPU 6: hi: 186, btch: 31 usd: 181 Nov 20 08:22:06 virtfed kernel: CPU 7: hi: 186, btch: 31 usd: 48 Nov 20 08:22:06 virtfed kernel: Node 0 Normal per-cpu: Nov 20 08:22:06 virtfed kernel: CPU 0: hi: 186, btch: 31 usd: 160 Nov 20 08:22:06 virtfed kernel: CPU 1: hi: 186, btch: 31 usd: 5 Nov 20 08:22:06 virtfed kernel: CPU 2: hi: 186, btch: 31 usd: 181 Nov 20 08:22:06 virtfed kernel: CPU 3: hi: 186, btch: 31 usd: 0 Nov 20 08:22:06 virtfed kernel: CPU 4: hi: 186, btch: 31 usd: 73 Nov 20 08:22:06 virtfed kernel: CPU 5: hi: 186, btch: 31 usd: 38 Nov 20 08:22:06 virtfed kernel: CPU 6: hi: 186, btch: 31 usd: 156 Nov 20 08:22:06 virtfed kernel: CPU 7: hi: 186, btch: 31 usd: 31 Nov 20 08:22:06 virtfed kernel: Active_anon:2563037 active_file:0 inactive_anon:368313 Nov 20 08:22:06 virtfed kernel: inactive_file:31 unevictable:12620 dirty:0 writeback:0 unstable:0 Nov 20 08:22:06 virtfed kernel: free:16269 slab:25512 mapped:7756 pagetables:10201 bounce:0 Nov 20 08:22:06 virtfed kernel: Node 0 DMA free:15824kB min:16kB low:20kB high:24kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB present:15320kB pages_scanned:0 all_unreclaimable? yes Nov 20 08:22:06 virtfed kernel: lowmem_reserve[]: 0 3254 12092 12092 Nov 20 08:22:06 virtfed kernel: Node 0 DMA32 free:39040kB min:3784kB low:4728kB high:5676kB active_anon:2557420kB inactive_anon:511296kB active_file:0kB inactive_file:0kB unevictable:804kB present:3332660kB pages_scanned:0 all_unreclaimable? no Nov 20 08:22:06 virtfed kernel: lowmem_reserve[]: 0 0 8837 8837 Nov 20 08:22:06 virtfed kernel: Node 0 Normal free:10212kB min:10280kB low:12848kB high:15420kB active_anon:7694728kB inactive_anon:961956kB active_file:0kB inactive_file:236kB unevictable:49676kB present:9049596kB pages_scanned:0 all_unreclaimable? no Nov 20 08:22:06 virtfed kernel: lowmem_reserve[]: 0 0 0 0 Nov 20 08:22:06 virtfed kernel: Node 0 DMA: 2*4kB 1*8kB 2*16kB 1*32kB 2*64kB 0*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096kB = 15824kB Nov 20 08:22:06 virtfed kernel: Node 0 DMA32: 1068*4kB 1263*8kB 511*16kB 161*32kB 25*64kB 2*128kB 1*256kB 6*512kB 0*1024kB 1*2048kB 1*4096kB = 39032kB Nov 20 08:22:06 virtfed kernel: Node 0 Normal: 1595*4kB 0*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 10460kB Nov 20 08:22:06 virtfed kernel: 25465 total pagecache pages Nov 20 08:22:06 virtfed kernel: 17663 pages in swap cache Nov 20 08:22:06 virtfed kernel: Swap cache stats: add 1210138, delete 1192475, find 119729/133852 Nov 20 08:22:06 virtfed kernel: Free swap = 0kB Nov 20 08:22:06 virtfed kernel: Total swap = 4194296kB Nov 20 08:22:06 virtfed kernel: 3145727 pages RAM Nov 20 08:22:06 virtfed kernel: 63020 pages reserved Nov 20 08:22:06 virtfed kernel: 32665 pages shared Nov 20 08:22:06 virtfed kernel: 3054335 pages non-shared Nov 20 08:22:06 virtfed kernel: Out of memory: kill process 14357 (qemu-kvm) score 994666 or a child Nov 20 08:22:06 virtfed kernel: Killed process 14357 (qemu-kvm) Nov 20 08:22:06 virtfed kernel: virbr0: port 2(vnet1) entering disabled state Nov 20 08:22:06 virtfed kernel: device vnet1 left promiscuous mode Nov 20 08:22:06 virtfed kernel: virbr0: port 2(vnet1) entering disabled state and then similar about 1h 20minutes after for the other one.... Now I have: [root@virtfed ~]# free total used free shared buffers cached Mem: 12330828 1866848 10463980 0 546088 158820 -/+ buffers/cache: 1161940 11168888 Swap: 4194296 30024 4164272 and [root@ ~]# cat /sys/kernel/mm/ksm/pages_shared 0 It seems script.sh is the one provided by cluster manager but following messages were about other processed Nov 20 09:45:25 virtfed kernel: ksmd invoked oom-killer: gfp_mask=0x200d2, order=0, oomkilladj=0 Nov 20 09:45:25 virtfed kernel: ksmd cpuset=/ mems_allowed=0 Nov 20 10:58:35 virtfed kernel: awk invoked oom-killer: gfp_mask=0x201da, order=0, oomkilladj=0 Nov 20 10:58:35 virtfed kernel: awk cpuset=/ mems_allowed=0 Nov 20 10:58:35 virtfed kernel: libvirtd invoked oom-killer: gfp_mask=0x201da, order=0, oomkilladj=0 Nov 20 10:58:35 virtfed kernel: libvirtd cpuset=/ mems_allowed=0 /etc/sysconfig/ksm is empty (apart comments) at this moment: [root@virtfed log]# service ksm status ksm is not running [root@virtfed log]# service ksmtuned status ksmtuned (pid 8672) is running... Any hints? Thanks, Gianluca

14 years, 5 months

1
0
0 / 0

Re: [fedora-virt] bridged guest networking in f12 with netcf

by Dale Bewley

----- "Cole Robinson" <crobinso(a)redhat.com> wrote: > On 11/15/2009 04:10 PM, Dale Bewley wrote: ... > > [root@tofu2 network-scripts]# virsh iface-define br0.xml > > error: Failed to define interface from br0.xml > > error: invalid argument in virGetInterface > > > > It did work however. ... > > But now eth0 is missing from iface-list > > > > [root@tofu2 network-scripts]# virsh iface-list > > Name State MAC Address > > -------------------------------------------- > > lo active 00:00:00:00:00:00 > > > > Presumably, that's because from the libvirt / netcf perspective > (which is just looking at the ifcfg files) I have replaced it with the > br0 interface. However, br0 is not started, so presumably that's why > it isn't listed either. After a 'service network restart' things look > sane again. > > > > [root@tofu2 network-scripts]# virsh iface-list > > Name State MAC Address > > -------------------------------------------- > > br0 active 00:24:e8:30:20:e7 > > lo active 00:00:00:00:00:00 > > Probably want to try iface-list --all here, should list inactive > interfaces. That's what I would expect, but I recreated the situation and tried that. With and without --all, only lo showed up until a network restart. > > = Network = > > And finally, after creating this bridge, it would be nice to create > a network which utilizes it as follows. That fails the way I attempted > to do it. > > > > [root@tofu2 ~]# cat net-bridged.xml > > <network> > > <name>bridged</name> > > <forward mode='route'/> > > <bridge name='br0' /> > > </network> > > > > Physical device bridges are referenced directly in the VM xml, not via > the > virtual network XML. Example interface device block to add to your > VM: > > <interface type='bridge'> > <source bridge='br0'/> > <mac address="11:22:33:44:55:66"/> > </interface> > > - Cole I understand that, but I did lose track of that in my mind. It doesn't make much sense to refer to it as a 'network'. I do see that br0 shows up in the network/interface selection dialog of the VM creation wizard. One thing I just noticed is that NetworkManager is taking ownership of eth0 and preventing the br0 from being created. One fix is to chkconfig NetworkManager off chkconfig network on service NetworkManager stop service network restart I suppose the other solution would be to educate NetworkManager about the new configuration, but I've never really used paid much attention to NM. I'd have to look into how to do that properly.

14 years, 5 months

3
3
0 / 0

bridged guest networking in f12 with netcf

by Dale Bewley

Hello all, I started a blog post about experimenting with netcf and configuring a guest to share the same subnet as the host. It turned into something a bit longer and more rambling of course. * http://tofu.org/drupal/node/86 At any rate I ran into a few issues while using: virt-manager-0.8.0-7.fc12.noarch netcf-0.1.4-1.fc12.x86_64 libvirt-0.7.1-15.fc12.x86_64 = Virt-manager = I mentioned this one on the virt-tools list already. Virt-manager describes a routed network as a NAT network. = Bridge = Another issue was an error while using virsh iface-define. Given br0.xml: <interface type='bridge' name='br0'> <start mode='onboot'/> <protocol family='ipv4'> <ip address='10.10.10.158' prefix='24'/> <route gateway='10.10.10.254'/> </protocol> <bridge> <interface type='ethernet' name='eth0'> <mac address='00:24:E8:30:20:E7'/> </interface> </bridge> </interface> [root@tofu2 network-scripts]# virsh iface-define br0.xml error: Failed to define interface from br0.xml error: invalid argument in virGetInterface It did work however. [root@tofu2 network-scripts]# cat ifcfg-eth0 DEVICE=eth0 HWADDR=00:24:E8:30:20:E7 ONBOOT=yes BRIDGE=br0 TYPE=Ethernet BOOTPROTO=dhcp PEERDNS=yes PEERROUTES=yes NAME="System eth0" UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 [root@tofu2 network-scripts]# cat ifcfg-br0 DEVICE=br0 ONBOOT=yes TYPE=Bridge BOOTPROTO=none IPADDR=10.10.10.158 NETMASK=255.255.255.0 GATEWAY=10.10.10.254 But now eth0 is missing from iface-list [root@tofu2 network-scripts]# virsh iface-list Name State MAC Address -------------------------------------------- lo active 00:00:00:00:00:00 Presumably, that's because from the libvirt / netcf perspective (which is just looking at the ifcfg files) I have replaced it with the br0 interface. However, br0 is not started, so presumably that's why it isn't listed either. After a 'service network restart' things look sane again. [root@tofu2 network-scripts]# virsh iface-list Name State MAC Address -------------------------------------------- br0 active 00:24:e8:30:20:e7 lo active 00:00:00:00:00:00 = Network = And finally, after creating this bridge, it would be nice to create a network which utilizes it as follows. That fails the way I attempted to do it. [root@tofu2 ~]# cat net-bridged.xml <network> <name>bridged</name> <forward mode='route'/> <bridge name='br0' /> </network> [root@tofu2 ~]# virsh net-define net-bridged.xml error: Failed to define network from net-bridged.xml error: internal error Forwarding requested, but no IPv4 address/netmask provided Presumably that's the goal of http://fedoraproject.org/wiki/Features/Shared_Network_Interface in F13. Thanks for any comments.

14 years, 5 months

2
1
0 / 0

disabling ksm by default

by Izik Eidus

Hi, I saw that Fedora 12 will have ksm tunning script that control the ksm speed / kernel pages allocation. The only problem that I have is - as far as I remember ksm is by default enabled and only with 2000 kernel pages... What I am worried about is that users wont use the ksm tunning script and would just run ksm with this 2000 kernel pages - the result would be that ksm will probably merge just the zero pages (that could be alot of memory) and the user might not know that much more memory can be saved... Is it possible to at least make ksm disabled by default? so the users will have to run the ksm tunning script when they want to start ksm? And if we set it to disabled by default, cant we set the initialized values into more realistic value? (like 1/4 of the memory in the mainline kernels? ) Thanks.

14 years, 5 months

8
19
0 / 0

ANNOUNCE: libguestfs 1.0.78 released

by Richard W.M. Jones

I'm pleased to announce the release of libguestfs 1.0.78. Libguestfs is a library for accessing and modifying virtual machine disk images. Home page: http://libguestfs.org/ Source: http://libguestfs.org/download/ Binaries: http://libguestfs.org/FAQ.html#binaries A Fedora build is available in Koji here: http://koji.fedoraproject.org/koji/packageinfo?packageID=8391 (These release notes cover all the significant changes since the last announcement which was for 1.0.67, 2 months ago). New features: - FUSE support so you can mount guest filesystems in the host: http://rwmj.wordpress.com/2009/11/03/browsing-guests-using-fuse/ - Support for btrfs, gfs, gfs2, hfs, hfs+, nilfs2, jfs, reiserfs, xfs: http://rwmj.wordpress.com/2009/11/08/filesystem-metadata-overhead/ - Support for huge (multi-exabyte) sparse virtual disks: http://rwmj.wordpress.com/2009/11/04/petabytes-exabytes-why-not/ http://git.et.redhat.com/?p=libguestfs.git;a=commit;h=5ce72e039ca332ba19b... - New partitioning API, supports GPT and more: http://libguestfs.org/guestfs.3.html#guestfs_part_add http://git.et.redhat.com/?p=libguestfs.git;a=commit;h=b1e1ca2f74a921b3f78... - New tool: virt-ls http://rwmj.wordpress.com/2009/10/19/new-tool-virt-ls/ - New tool: virt-tar http://rwmj.wordpress.com/2009/10/19/new-tool-virt-tar/ - New tool: virt-edit http://rwmj.wordpress.com/2009/09/23/virt-edit/ - New tool: virt-rescue http://rwmj.wordpress.com/2009/09/22/virt-rescue/ - Windows Registry support, tools and library: http://rwmj.wordpress.com/2009/10/29/virt-win-reg-get-at-the-windows-regi... http://rwmj.wordpress.com/2009/10/28/libhivex-windows-registry-hive-extra... - OCaml bindings for virt-inspector - RELAX NG schema for virt-inspector - New APIs: utimens, vfs_type, truncate, truncate_size, lchown, lstatlist, lxattrlist, readlinklist, case_sensitive_path, find0, mkfs_b, mke2journal, and more ... - New program: OCaml viewer http://rwmj.wordpress.com/2009/09/29/graphical-virt-df/ - Allow stdout to be redirected when running guestfish remotely (Matt Booth). - Remove requirement for vmchannel support in qemu (horray!) and the tricky main loop code. Bug fixes: (Too many to list here, see: http://git.et.redhat.com/?p=libguestfs.git;a=log) Thanks to: Jim Meyering, Matt Booth and Charles Duffy for lots of bugfixes, patches and testing. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://et.redhat.com/~rjones/libguestfs/ See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html

14 years, 5 months

1
0
0 / 0

ubuntu 9.10 KVM on fedora 11 question

by Tom Horsley

I have some very weird behavior with my new ubuntu 9.10 virtual machines running as KVMs under fedora 11. I run testbeds on lots of different linuxii in ssh sessions to virtual machines, and the ssh session just stops randomly when talking to ubuntu 9.10 (no problem with 9.04, or 8.10, no problem with various fedora versions or openSUSE versions). I can still ssh into the KVM with a new ssh connection, but the original connection is frozen up, it never even times out an disconnects, it acts like it is in the middle of talking and is just waiting for the next thing to happen. Does this strike a familiar note to anyone? I've tried both virtio and emulated NIC modes, and see the same results.

14 years, 5 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt November 2009