June 2009 - virt - Fedora Mailing-Lists

by Tim Tassonis

Hi all Just came across libguestfs and, as a qemu user, this project really sound fantastic to me. However, when I tried to compile the latest tarball, I failed, mainly because of the inavalability of febootstrap, which obviously does not exist under ubuntu, and cannot be installed due to the lack of yum under ubuntu at least. Is debian support planned, or is libguestfs designed to be a fedora-only project? Bye Tim

14 years, 10 months

5
24
0 / 0

Error using Virtual Machine Manager to create new Windows XP VM

by Colin Coates

Dear All, I was previously successful in using KVM/Qemu to create and run a Windows XP virtual machine hosted on Fedora 10. I have now upgraded to Fedora 11 x86_64 (using Live distribution), but I get an error whilst using the Virtual Machine Manager to create a Windows XP virtual machine. The virtual machine is configured to install from a local CD (containing the Windows XP Pro install CD), OS type is "Windows", Version is "Microsoft Windows XP (x86)", memory is 1536MB, CPU set to 1, disk is 50GB (allocate entire disk now). My host PC is a Lenovo T60p (Intel Core 2 Duo with 4GB physical memory), and I have enable Intel Virtualization in the BIOS. The message displayed in the Error dialog is: "Unable to complete install: 'internal error unable to start guest: char device redirected to /dev/pts/0 char device redirected to /dev/pts/1" The details are: "Unable to complete install '<class 'libvirt.libvirtError'> internal error unable to start guest: char device redirected to /dev/pts/0 char device redirected to /dev/pts/1 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 1501, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0). File "/usr/lib64/python2.6/site-packages/libvirt.py", line 974, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error unable to start guest: char device redirected to /dev/pts/0 char device redirected to /dev/pts/1" Can anyone offer any suggestions about what I might be doing wrong? Kind Regards, Colin Coates

14 years, 11 months

2
1
0 / 0

Fedora 11 - Networking fails in KVM VMs

by Scott Dowdle

Greetings, I have used KVM in Fedora now since Fedora 9 and it has always done quite well and I've been very happy with it. Today I did a fresh Fedora 11 install (retaining my /home and /vm directories where my .img files were stored) and copied my Fedora 10 /etc/libvirt/qemu/*.xml from backup. My machines started fine. The one Windows VM I had noticed a lot of new hardware. Everything seems to work fine and be very fast... but networking does NOT work in any of my VMs. Thinking that perhaps something had changed in the .xml files, I deleted all of the VMs (but retained their storage) and created all new VMs using the existing storage. I don't have any fancy networking going on. My physical machine has a public IP address. It has NATing turned on and ip_foward = 1. The VMs are default ones with privates that are gotten via DHCP with the internal DHCP server and I have not messed with any of the DHCP settings in virt-manager. In the past, the VMs would get a 192.168.122.x address and they just worked. Now they can't seem to get an IP. I'm guessing it is something funky with my iptables settings but I can't seem to see anything out of the ordinary. Anyone else run into problems or have some suggestions for troubleshooting this? So far I haven't seen anything on the mailing list that applies. I've installed Fedora 11 on about 6 machines now and a few VMs for building remix images and it has been great. Good job. TYL, -- Scott Dowdle CS Department SysAdmin EPS 262 406-994-3931 [work] 406-388-0827 [home]

14 years, 11 months

2
2
0 / 0

Fedora 11 and Virtual Machine Manager

by Gerry Maddock

Hello all, I have been using qemu-kvm via the virtual machine manger on Fedora 10 and have had no problems (works great & love it!). I just downloaded and installed Fedora 11 64 bit on a new server and logged in as a normal user and started the virtual machine manager. I'm able to connect to the virtual machine manager, but cant setup any new VM's as I'm connected as Read-Only (This must be a new feature). How should I go about connecting to VMM READ-WRITE? Do I need to setup this user in /etc/sudoers to use VMM? Any help would be appreciated!

14 years, 11 months

2
1
0 / 0

Minimum Host for Virt-Manager?

by Frank Murphy

What is the Minimum Host I can install to rum Virt-Manager? AOS? XFCE? Frank

14 years, 11 months

2
2
0 / 0

Install Guest\HD Q?

by Frank Murphy

Is it possible to assign a full *physical drive* to each guest. If I need one for F11, F11, Rawide the first two being update in line with releases. Do I set this up while installing the host OS? Best Recommended? -- msn: frankly3d skype: frankly3d Mailing-List Reply to: Mailing-List Still Learning, Unicode where possible

14 years, 11 months

3
6
0 / 0

Some new features of virt-inspector

by Richard W.M. Jones

I've added a few extra features to virt-inspector (in libguestfs >= 1.0.42). First up is a new 'query mode', documented in the manpage: http://et.redhat.com/~rjones/libguestfs/virt-inspector.1.html#query_mode Just run: virt-inspector --query [some virtual machine] and it'll print out some useful facts about the virtual machine such as whether it's fully virtualized or needs a Xen hypervisor, and whether it has various paravirt drivers installed. Secondly (not covered in the manpage), virt-inspector will try to discover whether a VM contains the right initrd drivers and module configuration to boot under various hypervisors. So for example it can tell you whether a guest has the virtio drivers available at boot time to boot from a virtio disk. As usual, to find out more about virt-inspector, see the manual page or the libguestfs home page: http://et.redhat.com/~rjones/libguestfs/virt-inspector.1.html http://et.redhat.com/~rjones/libguestfs/ libguestfs and virt-inspector are available in Fedora 11 updates- testing, or Rawhide, or as RPMs from Koji here: http://koji.fedoraproject.org/koji/buildinfo?buildID=105088 Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 75 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora

14 years, 11 months

1
0
0 / 0

Too much ram for F10

by Thomas S Hatch

I already posted about this in the cobbler list and they sent me over here. It seems that whenever I try to install a new virtual machine(kvm) with koan, and the ram for the machine is higher than 2 gigs the machine fails to install. The domain and hard drive image are created, but they won't start up to do the install. My guess was that the arch was being set to i686 in the libvirt xml file, and that that was causing issues, but the vms with 2 gigs of ram and arch="i686" in the libvirt config install just fine with a 64 bit version of Fedora. I then decided to track down where the arch assignment was being made in the code, koan uses the default arch supplied by virtinst.FullVirtGuest. In that code the 2 lines that detect the host arch are commented out, I uncommented them, and tried again. The arch in the libvirt xml files became x86_64, but they still failled to install for vms with 4 gigs of ram! So I am stumpted! Anyone have any suggestions? Host machine: Fedora 10 64 bit, 8 3Ghz core, 32 Gigs of ram 1TB hdd It is also running on a node in a red hat cluster suite 2.99 Here is the log from one of my systems: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -S -M pc -m 4096 -smp 2 -name broker -uuid 60cec202-99dd-0f63-e198-f708c90a288b -monitor pty -no-reboot -boot c -kernel /var/lib/libvirt/boot/virtinst-vmlinuz.kmgRaG -initrd /var/lib/libvirt/boot/virtinst-initrd.img.W2X9jX -append ks= http://192.168.46.234/cblr/svc/op/ks/system/broker ksdevice=link kssendmac lang= text method=http://192.168.46.234:80/cblr/links/F10-x86_64/<http://192.168.46.234/cblr/links/F10-x86_64/>-drive file=/vm/images/broker-disk0,if=virtio,index=0,boot=on -net nic,macaddr=00:16:3e:38:81:65,vlan=0,model=virtio -net tap,fd=22,script=,vlan=0,ifname=vnet1 -serial pty -parallel none -usb -vnc 0.0.0.0:1 -k en-us char device redirected to /dev/pts/4 char device redirected to /dev/pts/5 i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo ^[[K^[[D^[[D^[[D^[[D^[[Dinfo c^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo cp^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo cpu^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo cpus^[[K^M * CPU #0: pc=0x00000000000ffff0 thread_id=17984^M CPU #1: pc=0x00000000000ffff0 thread_id=17985^Mc^[[K^[[Dco^[[K^[[D^[[Dcon^[[K^[[D^[[D^[[Dcont^[[K^Mqemu: loading initrd (0x10efde0 bytes) at 0x000000007ef10000 kvm_cpu_register_physical_memory: failed create_userspace_phys_mem: Invalid argument And here is some host system info: /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.18 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 1 siblings : 4 core id : 0 cpu cores : 4 apicid : 4 initial apicid : 4 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.31 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.29 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 0 siblings : 4 core id : 2 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.27 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 4 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 0 siblings : 4 core id : 3 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.26 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 5 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 1 siblings : 4 core id : 1 cpu cores : 4 apicid : 5 initial apicid : 5 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.31 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 6 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 1 siblings : 4 core id : 2 cpu cores : 4 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.32 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 1 siblings : 4 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.29 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: /proc/meminfo: MemTotal: 23452656 kB MemFree: 19856416 kB Buffers: 11308 kB Cached: 92944 kB SwapCached: 236 kB Active: 3073996 kB Inactive: 29244 kB SwapTotal: 10256376 kB SwapFree: 10256016 kB Dirty: 180 kB Writeback: 0 kB AnonPages: 2998556 kB Mapped: 16820 kB Slab: 189048 kB SReclaimable: 61812 kB SUnreclaim: 127236 kB PageTables: 10352 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 21982704 kB Committed_AS: 3661632 kB VmallocTotal: 34359738367 kB VmallocUsed: 150160 kB VmallocChunk: 34359587191 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 7920 kB DirectMap2M: 23846912 kB

14 years, 11 months

2
1
0 / 0

intel vt versus amd-v?

by Robert P. J. Day

a friend wants to buy a server (probably dell) with HW virt support, and is wondering if there are any current clear advantages of intel over amd. the only observation i had time to make was that, if one checks out entry-level servers from dell (ballpark $1000 cdn), the amd opteron systems appear to be somewhat less expensive than equivalent intel-based systems. further thoughts? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================

14 years, 11 months

5
7
0 / 0

Fedora virt status

by Mark McLoughlin

Okay, so F-11 is done and dusted. Onwards to F-12! Here's what the schedule looks like: 2009-07-28 Feature Freeze (53 days) 2009-08-04 Beta Freeze (60 days) 2009-09-22 Final Development Freeze (109 days) 2009-10-20 Compose & Stage Release Candidate (137 days) F11 Release =========== Another one week slip for the F11 release, this because of a late breaking anaconda storage problem: http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02159.html A late discovered and just potentially fixed anaconda storage bug[1] has necessitated another week slip of our schedule. The change is important but invasive enough to require re-validating our storage tests. We were already late in producing the Release Candidate and there is not enough time to produce another one and validate it in time for next Tuesday's release date. However, the release is now complete and being queued up on the mirrors. Expect the release early next week! F11 Virt Interview ================== Dan Berrange was interviewed about virtualization in Fedora 11. Read the full interview here: http://jaboutboul.blogspot.com/2009/05/fedora-11-virtualization-reality.html F11 Updates =========== A number of zero-day updates are available for F-11 users. The following are available in stable: https://admin.fedoraproject.org/updates/qemu-0.10.5-2.fc11 https://admin.fedoraproject.org/updates/libvirt-0.6.2-11.fc11 https://admin.fedoraproject.org/updates/virt-manager-0.7.0-5.fc11 https://admin.fedoraproject.org/updates/libguestfs-1.0.21-3.fc11 https://admin.fedoraproject.org/updates/openbios-1.0-1.fc11 and these are in updates-testing: https://admin.fedoraproject.org/updates/libvirt-0.6.2-12.fc11 https://admin.fedoraproject.org/updates/virt-viewer-0.0.3-5.fc11 https://admin.fedoraproject.org/updates/libguestfs-1.0.41-1.fc11 https://admin.fedoraproject.org/updates/etherboot-5.4.4-14.fc11 Please help out with testing these latest updates and report any issues. Virt Preview Repository ======================= Updates are being pushed regularily to the virt-preview repository: http://markmc.fedorapeople.org/virt-preview/README Below are the updates which have been pushed lately - obviously these are also available in rawhide: == qemu == * Fri Jun 5 2009 Mark McLoughlin <markmc(a)redhat.com> - 2:0.10.50-6.kvm86 - Fix 'kernel requires an x86-64 CPU' error - BuildRequires ncurses-devel to enable '-curses' option (#504226) * Wed Jun 3 2009 Mark McLoughlin <markmc(a)redhat.com> - 2:0.10.50-5.kvm86 - Prevent locked cdrom eject - fixes hang at end of anaconda installs (#501412) - Avoid harmless 'unhandled wrmsr' warnings (#499712) * Thu May 21 2009 Mark McLoughlin <markmc(a)redhat.com> - 2:0.10.50-4.kvm86 - Update to kvm-86 release - ChangeLog here: http://marc.info/?l=kvm&m=124282885729710 == libvirt == * Fri Jun 5 2009 Mark McLoughlin <markmc(a)redhat.com> - 0.6.4-2.fc12 - Remove the qemu BuildRequires * Fri May 29 2009 Daniel Veillard <veillard(a)redhat.com> - 0.6.4-1.fc12 - Upstream release of 0.6.4 - new APIs - fixes for latests QEmu/KVM versions - various assorted fixes * Mon May 25 2009 Mark McLoughlin <markmc(a)redhat.com> - 0.6.3-11.fc12 - Bring up the bridge, even if it doesn't have an IP address (bug #501912) * Thu May 21 2009 Mark McLoughlin <markmc(a)redhat.com> - 0.6.3-10.fc12 - Fix XML attribute escaping (bug #499791) - Fix serious event handling issues causing guests to be destroyed (bug #499698) * Thu May 21 2009 Mark McLoughlin <markmc(a)redhat.com> - 0.6.3-9.fc12 - Fix qemu argv detection with latest qemu (bug #501923) Some discussion has also begun on how to sign the packages in the preview repo: http://www.redhat.com/archives/fedora-virt/2009-June/msg00024.html Xen Dom0 ======== Jeremy Fitzhardinge's latest submission of the Xen Dom0 patches for 2.6.31 has caused the kernel community to get themselves into a bit of a flap. LWN has a nice article on the 'discussion': http://lwn.net/Articles/335812/ But the stronger voice looks to be the one saying that the problems need to be fixed first. The deciding factors seem to be (1) the user-space ABI, and (2) the intrusion into the core x86 code; those issues make Xen different from yet another driver or filesystem. That, in turn, suggests that the Dom0 code is not destined for the mainline anytime soon. Instead, the Xen developers will be expected to go back and fix a list of problems - a lot of work with an uncertain result at the end. Will we have Dom0 support in the F-12 kernel? It's looking increasingly unlikely, isn't it? On a positive note, reading LKML threads like this are a good way of putting the supposed dire state of fedora-devel-list in perspective ;-) In other news Michael Young continues to push out RPM builds of the latest Dom0 patch set: http://www.redhat.com/archives/fedora-virt/2009-June/msg00023.html Oh yes - Gerd Hoffman has pushed a xen-3.4.0 update to F-11: Bugs ==== DOOM-O-METER: 236 open bugs 3 weeks ago, 238 now. It looks like 103 of these are F-11/F-12 bugs which aren't fixed by pending updates. The "short" list of particularily interesting F-11 bugs is here: https://bugzilla.redhat.com/showdependencytree.cgi?id=F11VirtTarget&hide_... = New Bugs = == qemu == https://bugzilla.redhat.com/503236 qemu/tcg - boot hangs intermittently on cryptomgr_test at doublefault_fn Rich Jones discovered this TCG issue with libguestfs tests. There has been some discussion upstream analyzing the issue. https://bugzilla.redhat.com/503184 Add system_reboot to qemu Currently there is no way for libvirt to request qemu to reboot a guest. We really should get this done for F12. https://bugzilla.redhat.com/503156 qemu VNC :: xterm inside VM shows garbled text Looks like our vnc server has some issues with framebuffer updates. https://bugzilla.redhat.com/504273 qemu-system-ppc on ppc host fails with "no opcode defined" It looks like qemu-system-ppc on a ppc host is failing to initialize its opcode table. https://bugzilla.redhat.com/504294 qemu-system-ppc fails to boot ISO image Looks like qemu's ppc target can't currently boot from a cdrom. == libvirt == https://bugzilla.redhat.com/500968 virt-manager traceback on shutdown of qemu-kvm -no-acpi guest A guest with ACPI disabled will exit immediately when issued with the "system_powerdown" command and libvirt isn't handling this gracefully. == virtinst == https://bugzilla.redhat.com/502627 virtinst should always specify the disk image format in guest configuration This is a long standing known issue, which has been fixed upstream bu we should really pull the fix into F-11. == virt-manager == https://bugzilla.redhat.com/502110 virt-manager does not re-connect after libvirtd restart It seems that if you restart libvirtd while virt-manager is running, then virt-manager doesn't know how to re-connect to libvirtd. https://bugzilla.redhat.com/499547 virt-manager should restart linux guests after they have finished installing Discussion about the fact that virt-manager does not re-start a guest after it has been installed. https://bugzilla.redhat.com/502777 virt-manager does not recalculate free disk space on new VM creation In the 'New VM' wizard, we don't currently update the 'XXXGb available on the host' message if people go and delete files when they realize they don't have enough space. https://bugzilla.redhat.com/503001 RFE virt-manager: allow desktop switch with ctrl+alt+arrow_key Someone finally filed a bug on it :-) When you go to switch workspaces with Ctrl-Alt-Arrow, virt-manager grabs the keyboard, which is pretty annoying. https://bugzilla.redhat.com/503150 virt-manager window size bigger after returning from fullscreen It seems that going back and forth between fullscreen can cause the virt-manager window to be resized such that it is partially off-screen. https://bugzilla.redhat.com/503784 memory changes in virt-manager do not persist across libvirtd restart virt-manager is using a non-persistent libvirt API to adjust the guest memory configuration. https://bugzilla.redhat.com/503786 virt-manager refuses to increase guest memory until max memory change is first applied An annoying little problem where virt-manager appears to want to pick a fight with the user. == gnome-applet-vm == https://bugzilla.redhat.com/502748 gnome-applet-vm should use PolicyKit The applet currently uses consolehelper, it should use PolicyKit instead. = Resolved Bugs = == qemu == https://bugzilla.redhat.com/501412 f11 kvm guest install exits after package install completes qemu wasn't properly implementing cdrom door locking allowing anaconda to eject the cdrom while it was locked, killing the install. Fixed in qemu-0.10.5-2.fc11. https://bugzilla.redhat.com/501264 qemu segfaults for -net socket,listen=localhost:4567 Simple fix cherry-picked from upstream and included in qemu-0.10.5-2.fc11. https://bugzilla.redhat.com/499712 qemu-kvm: avoid harmless unhandled wrmsr 0xc0010117 messages These warnings were causing quite a bit of confusion so we've cherry-picked a fix from Marcelo to make them go away. Also in qemu-0.10.5-2.fc11. https://bugzilla.redhat.com/503575 LiveCD Installer hangs during guest VM install-to-virt-drive Apparently this has been fixed by the qemu-0.10.5 update. https://bugzilla.redhat.com/503807 kqemu is disabled in qemu Glauber lays down the law, we're not supporting kqemu. https://bugzilla.redhat.com/504226 qemu-kvm binary should support the '-curses' option A simple missing ncurses-devel BuildRequires was causing the '-curses' option to not be supported in qemu. Fixed in F-12. == libvirt == https://bugzilla.redhat.com/502862 libvirt runs qemu-system-ppc with wrong machine type - should be g3beige, not g3bw The ppc machine types have changed in upstream qemu; fixed in the libvirt-0.6.2-12.fc11 update. https://bugzilla.redhat.com/503066 libvirtd crashes on tls connection danpb fixed this upstream and the fix was included in libvirt-0.6.2-12.fc11. https://bugzilla.redhat.com/503406 F11: libvirt: cannot shutdown virtual machines booted to a console prompt It turns out that if acpid is not running in the guest, the qemu 'system_powerdown' command used by libvirt doesn't do anything. == virt-viewer == https://bugzilla.redhat.com/499362 virt-viewer prevents key combinations like alt-f from being sent to the guest https://bugzilla.redhat.com/499595 virt-viewer mixes up password and username credentials for VNC https://bugzilla.redhat.com/499594 virt-viewer doesn't know how to provide a username/password to libvirt connections danpb pushed a virt-viewer-0.0.3-5.fc11 update with fixes for all these issues. == libguestfs == https://bugzilla.redhat.com/503133 "mkdir-p" should not throw errors on preexisting directories https://bugzilla.redhat.com/503135 cramfs and squashfs modules should be available in libguestfs appliances https://bugzilla.redhat.com/503169 libguestfs /dev is too sparse for kernel installation/upgrade Rich Jones and Charles Duffy have been busily fixing libguestfs bugs. = Ongoing Bugs = == qemu == https://bugzilla.redhat.com/501935 qemu-kvm -kernel should parse "vga=" cmdline option Someone posted an implementation for this upstream. https://bugzilla.redhat.com/501131 qemu segfault when VNC client disconnects Enrico tried the test patch and it didn't help, but that could be down to the fact that there are many failure cases. A cleaner fix is required.

14 years, 11 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt June 2009