From fedora at leemhuis.info Sun Mar 1 20:01:47 2009 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Sun, 01 Mar 2009 21:01:47 +0100 Subject: [fedora-virt] FESCo F-11 Virt features meeting In-Reply-To: <20090228181422.GA19324@redhat.com> References: <1928197141.523051235842773584.JavaMail.root@zebra.lib.ucdavis.edu> <1310012804.523071235842778681.JavaMail.root@zebra.lib.ucdavis.edu> <20090228181422.GA19324@redhat.com> Message-ID: <49AAE9AB.9060603@leemhuis.info> On 28.02.2009 19:14, Daniel P. Berrange wrote: > On Sat, Feb 28, 2009 at 09:39:38AM -0800, Dale Bewley wrote: >> ----- "Chris Lalancette" wrote: >> Not addressed in the meeting was: >> * http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge > > FYI, we've decided that this is almost certainly F12 material. The QEMU > upstream release will be so close to the feature freeze, that we don't > want to risk causing KVM regressions by trying to then merge the two. Sorry, but I fail to understand why is that a problem. Take the kernel for example: It's often still a early rc by Feature Freeze (this time it's a bit closer to final, but that is pure luck). IOW: the feature freeze afaics mean that things only need to be in a testable state. They features don't have to be fully ready. And the Qemu release is not that far away, isn't it? Just wondering. CU knurd From berrange at redhat.com Mon Mar 2 10:58:13 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 2 Mar 2009 10:58:13 +0000 Subject: [fedora-virt] FYI: Improved virt-manager UI coming in Fedora 11 Message-ID: <20090302105813.GD15108@redhat.com> FYI, there's a significant redesign of virt-manager in progress, with the first stage impacting the 'New VM' wizard, being aimed for Fedora 11. Cole has a blog post giving an overview of the major changes here http://blog.wikichoon.com/2009/02/virt-manager-in-fedora-11-new-vm-wizard.html so if you have any feedback about these changes, leave a comment on the blog or post to the virt-manager mailing list in this thread http://www.redhat.com/archives/et-mgmt-tools/2009-February/msg00084.html Many more design improvements are targetted for the next few virt-manager releases, impacting nearly every area of the UI, so keep an eye out for more UI review postings during F12 timeframe too.... Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From crobinso at redhat.com Wed Mar 4 00:39:18 2009 From: crobinso at redhat.com (Cole Robinson) Date: Tue, 03 Mar 2009 19:39:18 -0500 Subject: [fedora-virt] [ANNOUNCE] New release virtinst 0.400.2 Message-ID: <49ADCDB6.3030204@redhat.com> I'm happy to announce a new virtinst release, version 0.400.2. The release can be downloaded from: http://virt-manager.org/download.html The direct download link is: http://virt-manager.org/download/sources/virtinst/virtinst-0.400.2.tar.gz This release includes: - New virt-clone option --original-xml, allows cloning a guest from an xml file, rather than require an existing, defined guest. - New virt-install option --import, allows creating a guest from an existing disk image, bypassing any OS install phase. - New virt-install option --host-device, for connecting a physical host device to the guest. - Allow specifying 'cache' value via virt-install's --disk options (Ben Kochie) - New virt-install option --nonetworks (John Levon) - Lots of backend cleanups and documentation improvements. Thanks to everyone who has contributed to this release through testing, bug reporting, submitting patches, and otherwise sending in feedback! Thanks, Cole From m.a.young at durham.ac.uk Fri Mar 6 01:21:05 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Fri, 6 Mar 2009 01:21:05 +0000 (GMT) Subject: [fedora-virt] Re: Dom0 kernels In-Reply-To: References: Message-ID: Here is another build (kernel-2.6.29-0.114.2.10.rc7.fc11) http://koji.fedoraproject.org/koji/taskinfo?taskID=1225129 I managed to get the previous build I posted to boot (non-graphically) and run a xen client with networking enabled on an x86_64 machine and this one also looks promising as IDE disks are now working, though I haven't tested it much. Rough instructions to start xen are; modprobe evtchn mount -t xenfs none /proc/xen setenforce 0 service xenstored start service xend start service xenconsoled start xm create -c guestname Michael Young From kraxel at redhat.com Fri Mar 6 09:27:24 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Fri, 06 Mar 2009 10:27:24 +0100 Subject: [fedora-virt] Re: Dom0 kernels In-Reply-To: References: Message-ID: <49B0EC7C.304@redhat.com> M A Young wrote: > Here is another build (kernel-2.6.29-0.114.2.10.rc7.fc11) > http://koji.fedoraproject.org/koji/taskinfo?taskID=1225129 > I managed to get the previous build I posted to boot (non-graphically) > and run a xen client with networking enabled on an x86_64 machine and > this one also looks promising as IDE disks are now working, though I > haven't tested it much. > Rough instructions to start xen are; > modprobe evtchn Next round of xen packages (-8, building right now) should to this automagically. > mount -t xenfs none /proc/xen That should happen already with current (-7) rawhide packages. > setenforce 0 no comment ;) > service xenstored start > service xend start > service xenconsoled start You can just "chkconfig $name on" these. They will detect when not running on xen and do nothing in that case. HTH Gerd From m.a.young at durham.ac.uk Fri Mar 6 09:34:32 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Fri, 6 Mar 2009 09:34:32 +0000 (GMT) Subject: [fedora-virt] Re: Dom0 kernels In-Reply-To: <49B0EC7C.304@redhat.com> References: <49B0EC7C.304@redhat.com> Message-ID: On Fri, 6 Mar 2009, Gerd Hoffmann wrote: >> service xenstored start >> service xend start >> service xenconsoled start > > You can just "chkconfig $name on" these. They will detect when not > running on xen and do nothing in that case. They are "chkconfig $name on", however they are dependent on some of the previous steps so need to be rerun with my current setup. Michael Young From kraxel at redhat.com Fri Mar 6 09:49:27 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Fri, 06 Mar 2009 10:49:27 +0100 Subject: [fedora-virt] Re: Dom0 kernels In-Reply-To: References: <49B0EC7C.304@redhat.com> Message-ID: <49B0F1A7.4080405@redhat.com> M A Young wrote: > On Fri, 6 Mar 2009, Gerd Hoffmann wrote: > >>> service xenstored start >>> service xend start >>> service xenconsoled start >> >> You can just "chkconfig $name on" these. They will detect when not >> running on xen and do nothing in that case. > > They are "chkconfig $name on", however they are dependent on some of the > previous steps so need to be rerun with my current setup. Ah, ok. Fresh builds where this shouldn't be needed any more are here now (and in rawhide soon): http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/8.fc11/ cheers, Gerd From kraxel at redhat.com Fri Mar 6 11:28:23 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Fri, 06 Mar 2009 12:28:23 +0100 Subject: [fedora-virt] Re: Dom0 kernels In-Reply-To: <49B0F1A7.4080405@redhat.com> References: <49B0EC7C.304@redhat.com> <49B0F1A7.4080405@redhat.com> Message-ID: <49B108D7.7040904@redhat.com> > Ah, ok. Fresh builds where this shouldn't be needed any more are here > now (and in rawhide soon): > http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/8.fc11/ Well it doesn't work, module loading has a tyops, new build (#9) is on the way. cheers, Gerd From pasik at iki.fi Fri Mar 6 17:41:09 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Fri, 6 Mar 2009 19:41:09 +0200 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels In-Reply-To: <49B108D7.7040904@redhat.com> References: <49B0EC7C.304@redhat.com> <49B0F1A7.4080405@redhat.com> <49B108D7.7040904@redhat.com> Message-ID: <20090306174109.GJ15052@edu.joroinen.fi> On Fri, Mar 06, 2009 at 12:28:23PM +0100, Gerd Hoffmann wrote: > > Ah, ok. Fresh builds where this shouldn't be needed any more are here > > now (and in rawhide soon): > > http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/8.fc11/ > > Well it doesn't work, module loading has a tyops, new build (#9) is on > the way. > I rebuilt 3.3.1-9 on fc10, and it seems to work. But virt-install (and virt-manager) seem to have problems.. # virt-install ERROR Unsupported virtualization type 'xen' Was xen support removed from virt-install, or does it just fail to detect xen is available when using pv_ops dom0? -- Pasi From pasik at iki.fi Sat Mar 7 13:19:20 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sat, 7 Mar 2009 15:19:20 +0200 Subject: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 Message-ID: <20090307131920.GK15052@edu.joroinen.fi> Hello! I'm using Fedora 10 on my Xen pv_ops testing box. I rebuilt Xen 3.3.1-9 packages from F11/rawhide for Fedora 10 and installed them. http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/9.fc11/src/xen-3.3.1-9.fc11.src.rpm xen-3.3.1-9.fc10.i386.rpm xen-debuginfo-3.3.1-9.fc10.i386.rpm xen-devel-3.3.1-9.fc10.i386.rpm xen-hypervisor-3.3.1-9.fc10.i386.rpm xen-libs-3.3.1-9.fc10.i386.rpm xen-runtime-3.3.1-9.fc10.i386.rpm I also built custom 2.6.29-rc7 pv_ops dom0 kernel, which seems to boot OK for me. xend starts OK, and I can run 'xm info', 'xm list' etc. But now I'm having problems using virt-install and/or virt-manager to install new domains. [root at dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" ERROR Unsupported virtualization type 'xen' Has Xen support been dropped from virt-install, or is this just some bug? -- Pasi From crobinso at redhat.com Sat Mar 7 17:33:46 2009 From: crobinso at redhat.com (Cole Robinson) Date: Sat, 07 Mar 2009 12:33:46 -0500 Subject: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090307131920.GK15052@edu.joroinen.fi> References: <20090307131920.GK15052@edu.joroinen.fi> Message-ID: <49B2AFFA.1080908@redhat.com> Pasi K?rkk?inen wrote: > Hello! > > I'm using Fedora 10 on my Xen pv_ops testing box. > > I rebuilt Xen 3.3.1-9 packages from F11/rawhide for Fedora 10 and installed them. > > http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/9.fc11/src/xen-3.3.1-9.fc11.src.rpm > > xen-3.3.1-9.fc10.i386.rpm > xen-debuginfo-3.3.1-9.fc10.i386.rpm > xen-devel-3.3.1-9.fc10.i386.rpm > xen-hypervisor-3.3.1-9.fc10.i386.rpm > xen-libs-3.3.1-9.fc10.i386.rpm > xen-runtime-3.3.1-9.fc10.i386.rpm > > I also built custom 2.6.29-rc7 pv_ops dom0 kernel, which seems to boot OK > for me. > > xend starts OK, and I can run 'xm info', 'xm list' etc. > > But now I'm having problems using virt-install and/or virt-manager to > install new domains. > > [root at dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > > ERROR Unsupported virtualization type 'xen' > > Has Xen support been dropped from virt-install, or is this just some bug? > Xen support hasn't been dropped, we are probably just failing to detect that xen is available. First, can you try 'virsh --connect xen:///' and see if it succeeds? If that works, you can manually pass the connection string to virt-install in the interim (virt-install --connect xen:/// ...) Can you also check if the following 3 locations exist: /var/lib/xend /dev/xen/evtchn /proc/xen That is what we check in virtinst to guess that xen is present, and we should use its connection by default. If one of those is missing, any recommendations on how to detect xen presence would be appreciated. Thanks, Cole From pasik at iki.fi Sat Mar 7 18:19:22 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sat, 7 Mar 2009 20:19:22 +0200 Subject: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <49B2AFFA.1080908@redhat.com> References: <20090307131920.GK15052@edu.joroinen.fi> <49B2AFFA.1080908@redhat.com> Message-ID: <20090307181922.GM15052@edu.joroinen.fi> On Sat, Mar 07, 2009 at 12:33:46PM -0500, Cole Robinson wrote: > Pasi K?rkk?inen wrote: > > Hello! > > > > I'm using Fedora 10 on my Xen pv_ops testing box. > > > > I rebuilt Xen 3.3.1-9 packages from F11/rawhide for Fedora 10 and installed them. > > > > http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/9.fc11/src/xen-3.3.1-9.fc11.src.rpm > > > > xen-3.3.1-9.fc10.i386.rpm > > xen-debuginfo-3.3.1-9.fc10.i386.rpm > > xen-devel-3.3.1-9.fc10.i386.rpm > > xen-hypervisor-3.3.1-9.fc10.i386.rpm > > xen-libs-3.3.1-9.fc10.i386.rpm > > xen-runtime-3.3.1-9.fc10.i386.rpm > > > > I also built custom 2.6.29-rc7 pv_ops dom0 kernel, which seems to boot OK > > for me. > > > > xend starts OK, and I can run 'xm info', 'xm list' etc. > > > > But now I'm having problems using virt-install and/or virt-manager to > > install new domains. > > > > [root at dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > > "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > > > > ERROR Unsupported virtualization type 'xen' > > > > Has Xen support been dropped from virt-install, or is this just some bug? > > > > Xen support hasn't been dropped, we are probably just failing to detect > that xen is available. > > First, can you try 'virsh --connect xen:///' and see if it succeeds? If > that works, you can manually pass the connection string to virt-install > in the interim (virt-install --connect xen:/// ...) > Yeah, that seems to work: [root at dom0test ~]# virsh --connect xen:/// Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # vcpuinfo 0 VCPU: 0 CPU: 0 State: running CPU time: 32.3s CPU Affinity: yy VCPU: 1 CPU: 1 State: idle CPU time: 18.9s CPU Affinity: yy virsh # version Compiled against library: libvir 0.5.1 Using library: libvir 0.5.1 Using API: Xen 3.0.1 Running hypervisor: Xen 3.3.0 virsh # quit [root at dom0test ~]# xm info host : dom0test.localdomain release : 2.6.29-rc7-tip version : #10 SMP Sat Mar 7 16:04:28 EET 2009 machine : i686 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 3000 hw_caps : bfebfbff:00000000:00000000:00000180:0000441d:00000000:00000000:00000000 virt_caps : total_memory : 2038 free_memory : 992 node_to_cpu : node0:0-1 node_to_memory : node0:992 xen_major : 3 xen_minor : 3 xen_extra : .1-9.fc10 xen_caps : xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable cc_compiler : gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC) cc_compile_by : root cc_compile_domain : localdomain cc_compile_date : Fri Mar 6 17:24:19 EET 2009 xend_config_format : 4 > Can you also check if the following 3 locations exist: > > /var/lib/xend > /dev/xen/evtchn > /proc/xen > Yep, all of those do exist. [root at dom0test ~]# ls /var/lib/xend domains relocation-socket state storage xend-socket [root at dom0test ~]# ls -la /dev/xen/evtchn crw-rw---- 1 root root 10, 63 2009-03-07 20:10 /dev/xen/evtchn [root at dom0test ~]# ls /proc/xen/ capabilities privcmd xenbus xsd_kva xsd_port > That is what we check in virtinst to guess that xen is present, and we > should use its connection by default. If one of those is missing, any > recommendations on how to detect xen presence would be appreciated. > [root at dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" ERROR Unsupported virtualization type 'xen' Hmm.. so that didn't help unfortunately.. Other ideas? And thanks! -- Pasi From crobinso at redhat.com Sat Mar 7 18:45:11 2009 From: crobinso at redhat.com (Cole Robinson) Date: Sat, 07 Mar 2009 13:45:11 -0500 Subject: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090307181922.GM15052@edu.joroinen.fi> References: <20090307131920.GK15052@edu.joroinen.fi> <49B2AFFA.1080908@redhat.com> <20090307181922.GM15052@edu.joroinen.fi> Message-ID: <49B2C0B7.5030007@redhat.com> Pasi K?rkk?inen wrote: > > [root at dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > > ERROR Unsupported virtualization type 'xen' > > Hmm.. so that didn't help unfortunately.. Other ideas? > Ah okay. Libvirt capabilities must be getting confused. Can you attach the output of virsh --connect xen:/// capabilities cat /sys/hypervisor/properties/capabilities Thanks, Cole From pasik at iki.fi Sat Mar 7 18:50:36 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sat, 7 Mar 2009 20:50:36 +0200 Subject: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <49B2C0B7.5030007@redhat.com> References: <20090307131920.GK15052@edu.joroinen.fi> <49B2AFFA.1080908@redhat.com> <20090307181922.GM15052@edu.joroinen.fi> <49B2C0B7.5030007@redhat.com> Message-ID: <20090307185036.GN15052@edu.joroinen.fi> On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote: > Pasi K?rkk?inen wrote: > > > > [root at dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > > "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > > > > ERROR Unsupported virtualization type 'xen' > > > > Hmm.. so that didn't help unfortunately.. Other ideas? > > > > Ah okay. Libvirt capabilities must be getting confused. Can you attach > the output of > > virsh --connect xen:/// capabilities > cat /sys/hypervisor/properties/capabilities > [root at dom0test ~]# virsh --connect xen:/// capabilities i686 xenmigr [root at dom0test ~]# cat /sys/hypervisor/properties/capabilities cat: /sys/hypervisor/properties/capabilities: No such file or directory -- Pasi From pasik at iki.fi Sat Mar 7 18:52:23 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sat, 7 Mar 2009 20:52:23 +0200 Subject: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090307185036.GN15052@edu.joroinen.fi> References: <20090307131920.GK15052@edu.joroinen.fi> <49B2AFFA.1080908@redhat.com> <20090307181922.GM15052@edu.joroinen.fi> <49B2C0B7.5030007@redhat.com> <20090307185036.GN15052@edu.joroinen.fi> Message-ID: <20090307185223.GO15052@edu.joroinen.fi> On Sat, Mar 07, 2009 at 08:50:36PM +0200, Pasi K?rkk?inen wrote: > On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote: > > Pasi K?rkk?inen wrote: > > > > > > [root at dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > > > "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > > > > > > ERROR Unsupported virtualization type 'xen' > > > > > > Hmm.. so that didn't help unfortunately.. Other ideas? > > > > > > > Ah okay. Libvirt capabilities must be getting confused. Can you attach > > the output of > > > > virsh --connect xen:/// capabilities > > cat /sys/hypervisor/properties/capabilities > > > > [root at dom0test ~]# virsh --connect xen:/// capabilities > > > > > i686 > > > > > > > > xenmigr > > > > > > > > > > > > > > > > > [root at dom0test ~]# cat /sys/hypervisor/properties/capabilities > cat: /sys/hypervisor/properties/capabilities: No such file or directory > [root at dom0test ~]# ls -la /sys/hypervisor ls: cannot access /sys/hypervisor: No such file or directory -- Pasi From crobinso at redhat.com Sat Mar 7 19:28:52 2009 From: crobinso at redhat.com (Cole Robinson) Date: Sat, 07 Mar 2009 14:28:52 -0500 Subject: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090307185223.GO15052@edu.joroinen.fi> References: <20090307131920.GK15052@edu.joroinen.fi> <49B2AFFA.1080908@redhat.com> <20090307181922.GM15052@edu.joroinen.fi> <49B2C0B7.5030007@redhat.com> <20090307185036.GN15052@edu.joroinen.fi> <20090307185223.GO15052@edu.joroinen.fi> Message-ID: <49B2CAF4.2080107@redhat.com> Pasi K?rkk?inen wrote: > On Sat, Mar 07, 2009 at 08:50:36PM +0200, Pasi K?rkk?inen wrote: >> On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote: >>> Pasi K?rkk?inen wrote: >>>> [root at dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l >>>> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" >>>> >>>> ERROR Unsupported virtualization type 'xen' >>>> >>>> Hmm.. so that didn't help unfortunately.. Other ideas? >>>> >>> Ah okay. Libvirt capabilities must be getting confused. Can you attach >>> the output of >>> >>> virsh --connect xen:/// capabilities >>> cat /sys/hypervisor/properties/capabilities >>> >> [root at dom0test ~]# virsh --connect xen:/// capabilities >> >> >> >> >> i686 >> >> >> >> >> >> >> >> xenmigr >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> [root at dom0test ~]# cat /sys/hypervisor/properties/capabilities >> cat: /sys/hypervisor/properties/capabilities: No such file or directory >> > > [root at dom0test ~]# ls -la /sys/hypervisor > ls: cannot access /sys/hypervisor: No such file or directory > > Hmm, well that will do it. Libvirt capabilities are what tell user apps what types of domains can be installed, and generating xen capabilities is largely dependent on the above paths. Not too sure what to do from here. - Cole From pasik at iki.fi Sat Mar 7 19:37:25 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sat, 7 Mar 2009 21:37:25 +0200 Subject: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <49B2CAF4.2080107@redhat.com> References: <20090307131920.GK15052@edu.joroinen.fi> <49B2AFFA.1080908@redhat.com> <20090307181922.GM15052@edu.joroinen.fi> <49B2C0B7.5030007@redhat.com> <20090307185036.GN15052@edu.joroinen.fi> <20090307185223.GO15052@edu.joroinen.fi> <49B2CAF4.2080107@redhat.com> Message-ID: <20090307193725.GP15052@edu.joroinen.fi> On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote: > Pasi K?rkk?inen wrote: > > On Sat, Mar 07, 2009 at 08:50:36PM +0200, Pasi K?rkk?inen wrote: > >> On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote: > >>> Pasi K?rkk?inen wrote: > >>>> [root at dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > >>>> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > >>>> > >>>> ERROR Unsupported virtualization type 'xen' > >>>> > >>>> Hmm.. so that didn't help unfortunately.. Other ideas? > >>>> > >>> Ah okay. Libvirt capabilities must be getting confused. Can you attach > >>> the output of > >>> > >>> virsh --connect xen:/// capabilities > >>> cat /sys/hypervisor/properties/capabilities > >>> > >> [root at dom0test ~]# virsh --connect xen:/// capabilities > >> > >> > >> > >> > >> i686 > >> > >> > >> > >> > >> > >> > >> > >> xenmigr > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> [root at dom0test ~]# cat /sys/hypervisor/properties/capabilities > >> cat: /sys/hypervisor/properties/capabilities: No such file or directory > >> > > > > [root at dom0test ~]# ls -la /sys/hypervisor > > ls: cannot access /sys/hypervisor: No such file or directory > > > > > > Hmm, well that will do it. Libvirt capabilities are what tell user apps > what types of domains can be installed, and generating xen capabilities > is largely dependent on the above paths. Not too sure what to do from here. > Ok. I'll try asking what's the thing with that.. if it's still missing, or is it deprecated or something.. -- Pasi From pasik at iki.fi Sun Mar 8 19:23:10 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 8 Mar 2009 21:23:10 +0200 Subject: [Fedora-xen] Re: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090307193725.GP15052@edu.joroinen.fi> References: <20090307131920.GK15052@edu.joroinen.fi> <49B2AFFA.1080908@redhat.com> <20090307181922.GM15052@edu.joroinen.fi> <49B2C0B7.5030007@redhat.com> <20090307185036.GN15052@edu.joroinen.fi> <20090307185223.GO15052@edu.joroinen.fi> <49B2CAF4.2080107@redhat.com> <20090307193725.GP15052@edu.joroinen.fi> Message-ID: <20090308192310.GT15052@edu.joroinen.fi> On Sat, Mar 07, 2009 at 09:37:25PM +0200, Pasi K?rkk?inen wrote: > On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote: > > Pasi K?rkk?inen wrote: > > > On Sat, Mar 07, 2009 at 08:50:36PM +0200, Pasi K?rkk?inen wrote: > > >> On Sat, Mar 07, 2009 at 01:45:11PM -0500, Cole Robinson wrote: > > >>> Pasi K?rkk?inen wrote: > > >>>> [root at dom0test ~]# virt-install --connect xen:/// -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > > >>>> "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > > >>>> > > >>>> ERROR Unsupported virtualization type 'xen' > > >>>> > > >>>> Hmm.. so that didn't help unfortunately.. Other ideas? > > >>>> > > >>> Ah okay. Libvirt capabilities must be getting confused. Can you attach > > >>> the output of > > >>> > > >>> virsh --connect xen:/// capabilities > > >>> cat /sys/hypervisor/properties/capabilities > > >>> > > >> [root at dom0test ~]# virsh --connect xen:/// capabilities > > >> > > >> > > >> > > >> > > >> i686 > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> xenmigr > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> [root at dom0test ~]# cat /sys/hypervisor/properties/capabilities > > >> cat: /sys/hypervisor/properties/capabilities: No such file or directory > > >> > > > > > > [root at dom0test ~]# ls -la /sys/hypervisor > > > ls: cannot access /sys/hypervisor: No such file or directory > > > > > > > > > > Hmm, well that will do it. Libvirt capabilities are what tell user apps > > what types of domains can be installed, and generating xen capabilities > > is largely dependent on the above paths. Not too sure what to do from here. > > > > Ok. > > I'll try asking what's the thing with that.. if it's still missing, or is it > deprecated or something.. > Ok, it seems that /sys/hypervisor feature is not yet implemented in pv_ops dom0 kernel. There's a patch somewhere in Redhat's old dom0 repository.. Jeremy is trying to find that. For reference discussion on xen-devel about this: http://lists.xensource.com/archives/html/xen-devel/2009-03/msg00472.html -- Pasi From kraxel at redhat.com Mon Mar 9 07:27:14 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Mon, 09 Mar 2009 08:27:14 +0100 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels In-Reply-To: <20090306174109.GJ15052@edu.joroinen.fi> References: <49B0EC7C.304@redhat.com> <49B0F1A7.4080405@redhat.com> <49B108D7.7040904@redhat.com> <20090306174109.GJ15052@edu.joroinen.fi> Message-ID: <49B4C4D2.6070202@redhat.com> Pasi K?rkk?inen wrote: > > I rebuilt 3.3.1-9 on fc10, and it seems to work. > > But virt-install (and virt-manager) seem to have problems.. > > # virt-install > > ERROR Unsupported virtualization type 'xen' > > Was xen support removed from virt-install, or does it just fail to detect > xen is available when using pv_ops dom0? Either that, or the xen is a bit out-of-date because Fedora had no dom0 kernel (thus no testing) since Fedora 8 ... I'd suggest to file bugs. Most likely the culprit is libvirt. cheers Gerd From pasik at iki.fi Mon Mar 9 09:20:26 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 9 Mar 2009 11:20:26 +0200 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels In-Reply-To: <49B4C4D2.6070202@redhat.com> References: <49B0EC7C.304@redhat.com> <49B0F1A7.4080405@redhat.com> <49B108D7.7040904@redhat.com> <20090306174109.GJ15052@edu.joroinen.fi> <49B4C4D2.6070202@redhat.com> Message-ID: <20090309092026.GU15052@edu.joroinen.fi> On Mon, Mar 09, 2009 at 08:27:14AM +0100, Gerd Hoffmann wrote: > Pasi K?rkk?inen wrote: > > > > I rebuilt 3.3.1-9 on fc10, and it seems to work. > > > > But virt-install (and virt-manager) seem to have problems.. > > > > # virt-install > > > > ERROR Unsupported virtualization type 'xen' > > > > Was xen support removed from virt-install, or does it just fail to detect > > xen is available when using pv_ops dom0? > > Either that, or the xen is a bit out-of-date because Fedora had no dom0 > kernel (thus no testing) since Fedora 8 ... > > I'd suggest to file bugs. Most likely the culprit is libvirt. > Actually we hunted this down with Cole Robinson and Jeremy.. The reason is pv_ops dom0 kernel is still missing /sys/hypervisor infos.. virt-install (or libvirt) needs that info to fetch the capabilities. Jeremy said there should be a kernel patch for that in the old RH dom0 tree.. -- Pasi From berrange at redhat.com Mon Mar 9 10:09:21 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 9 Mar 2009 10:09:21 +0000 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels In-Reply-To: <20090306174109.GJ15052@edu.joroinen.fi> References: <49B0EC7C.304@redhat.com> <49B0F1A7.4080405@redhat.com> <49B108D7.7040904@redhat.com> <20090306174109.GJ15052@edu.joroinen.fi> Message-ID: <20090309100921.GE4578@redhat.com> On Fri, Mar 06, 2009 at 07:41:09PM +0200, Pasi K?rkk?inen wrote: > On Fri, Mar 06, 2009 at 12:28:23PM +0100, Gerd Hoffmann wrote: > > > Ah, ok. Fresh builds where this shouldn't be needed any more are here > > > now (and in rawhide soon): > > > http://kojipkgs.fedoraproject.org/packages/xen/3.3.1/8.fc11/ > > > > Well it doesn't work, module loading has a tyops, new build (#9) is on > > the way. > > > > I rebuilt 3.3.1-9 on fc10, and it seems to work. > > But virt-install (and virt-manager) seem to have problems.. > > # virt-install > > ERROR Unsupported virtualization type 'xen' This will be a libvirt bug - check output of virsh --connect xen:/// capabilities If that is not what you expect, then /sys/hypervisor/properties/capabilities is probably missing/broken. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From berrange at redhat.com Mon Mar 9 10:09:55 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 9 Mar 2009 10:09:55 +0000 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels In-Reply-To: <20090309092026.GU15052@edu.joroinen.fi> References: <49B0EC7C.304@redhat.com> <49B0F1A7.4080405@redhat.com> <49B108D7.7040904@redhat.com> <20090306174109.GJ15052@edu.joroinen.fi> <49B4C4D2.6070202@redhat.com> <20090309092026.GU15052@edu.joroinen.fi> Message-ID: <20090309100955.GF4578@redhat.com> On Mon, Mar 09, 2009 at 11:20:26AM +0200, Pasi K?rkk?inen wrote: > On Mon, Mar 09, 2009 at 08:27:14AM +0100, Gerd Hoffmann wrote: > > Pasi K?rkk?inen wrote: > > > > > > I rebuilt 3.3.1-9 on fc10, and it seems to work. > > > > > > But virt-install (and virt-manager) seem to have problems.. > > > > > > # virt-install > > > > > > ERROR Unsupported virtualization type 'xen' > > > > > > Was xen support removed from virt-install, or does it just fail to detect > > > xen is available when using pv_ops dom0? > > > > Either that, or the xen is a bit out-of-date because Fedora had no dom0 > > kernel (thus no testing) since Fedora 8 ... > > > > I'd suggest to file bugs. Most likely the culprit is libvirt. > > > > Actually we hunted this down with Cole Robinson and Jeremy.. > > The reason is pv_ops dom0 kernel is still missing /sys/hypervisor infos.. > virt-install (or libvirt) needs that info to fetch the capabilities. We could probably switch over to making a hypercall to fetch that info if /sys/hypervisor/properties/capabilities isn't going to reappear in the near future ... Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From kraxel at redhat.com Mon Mar 9 10:13:41 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Mon, 09 Mar 2009 11:13:41 +0100 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels In-Reply-To: <20090309100955.GF4578@redhat.com> References: <49B0EC7C.304@redhat.com> <49B0F1A7.4080405@redhat.com> <49B108D7.7040904@redhat.com> <20090306174109.GJ15052@edu.joroinen.fi> <49B4C4D2.6070202@redhat.com> <20090309092026.GU15052@edu.joroinen.fi> <20090309100955.GF4578@redhat.com> Message-ID: <49B4EBD5.2080501@redhat.com> Daniel P. Berrange wrote: > We could probably switch over to making a hypercall to fetch that info > if /sys/hypervisor/properties/capabilities isn't going to reappear in > the near future ... Or fallback to /proc/xen/capabilities (isn't that there anyway)? cheers, Gerd From ondrejj at salstar.sk Mon Mar 9 10:15:30 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Mon, 9 Mar 2009 11:15:30 +0100 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels In-Reply-To: <49B4EBD5.2080501@redhat.com> References: <49B0EC7C.304@redhat.com> <49B0F1A7.4080405@redhat.com> <49B108D7.7040904@redhat.com> <20090306174109.GJ15052@edu.joroinen.fi> <49B4C4D2.6070202@redhat.com> <20090309092026.GU15052@edu.joroinen.fi> <20090309100955.GF4578@redhat.com> <49B4EBD5.2080501@redhat.com> Message-ID: <20090309101530.GI25933@salstar.sk> On Mon, Mar 09, 2009 at 11:13:41AM +0100, Gerd Hoffmann wrote: > Daniel P. Berrange wrote: > > We could probably switch over to making a hypercall to fetch that info > > if /sys/hypervisor/properties/capabilities isn't going to reappear in > > the near future ... > > Or fallback to /proc/xen/capabilities (isn't that there anyway)? It's too small: [root at note ~]# uname -a Linux note.salstar.sk 2.6.29-0.114.2.10.rc7.fc11.i686.PAE #1 SMP Thu Mar 5 18:04:27 EST 2009 i686 i686 i386 GNU/Linux [root at note ~]# cat /proc/xen/capabilities control_d [root at note ~]# SAL From berrange at redhat.com Mon Mar 9 10:39:29 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 9 Mar 2009 10:39:29 +0000 Subject: [Fedora-xen] Re: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090308192310.GT15052@edu.joroinen.fi> References: <20090307131920.GK15052@edu.joroinen.fi> <49B2AFFA.1080908@redhat.com> <20090307181922.GM15052@edu.joroinen.fi> <49B2C0B7.5030007@redhat.com> <20090307185036.GN15052@edu.joroinen.fi> <20090307185223.GO15052@edu.joroinen.fi> <49B2CAF4.2080107@redhat.com> <20090307193725.GP15052@edu.joroinen.fi> <20090308192310.GT15052@edu.joroinen.fi> Message-ID: <20090309103929.GO4578@redhat.com> On Sun, Mar 08, 2009 at 09:23:10PM +0200, Pasi K?rkk?inen wrote: > On Sat, Mar 07, 2009 at 09:37:25PM +0200, Pasi K?rkk?inen wrote: > > On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote: > > > >> [root at dom0test ~]# cat /sys/hypervisor/properties/capabilities > > > >> cat: /sys/hypervisor/properties/capabilities: No such file or directory > > > >> > > > > > > > > [root at dom0test ~]# ls -la /sys/hypervisor > > > > ls: cannot access /sys/hypervisor: No such file or directory > > > > > > > > > > > > > > Hmm, well that will do it. Libvirt capabilities are what tell user apps > > > what types of domains can be installed, and generating xen capabilities > > > is largely dependent on the above paths. Not too sure what to do from here. > > > > > > > Ok. > > > > I'll try asking what's the thing with that.. if it's still missing, or is it > > deprecated or something.. > > > > Ok, it seems that /sys/hypervisor feature is not yet implemented in pv_ops > dom0 kernel. > > There's a patch somewhere in Redhat's old dom0 repository.. Jeremy is trying > to find that. If this patch gets rejected for whatever reason, let me know, becasue we can possibly switch libvirt over to making a direct hypercall to fetch this information. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From pasik at iki.fi Mon Mar 9 12:43:54 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 9 Mar 2009 14:43:54 +0200 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels In-Reply-To: <20090309100955.GF4578@redhat.com> References: <49B0EC7C.304@redhat.com> <49B0F1A7.4080405@redhat.com> <49B108D7.7040904@redhat.com> <20090306174109.GJ15052@edu.joroinen.fi> <49B4C4D2.6070202@redhat.com> <20090309092026.GU15052@edu.joroinen.fi> <20090309100955.GF4578@redhat.com> Message-ID: <20090309124354.GY15052@edu.joroinen.fi> On Mon, Mar 09, 2009 at 10:09:55AM +0000, Daniel P. Berrange wrote: > On Mon, Mar 09, 2009 at 11:20:26AM +0200, Pasi K?rkk?inen wrote: > > On Mon, Mar 09, 2009 at 08:27:14AM +0100, Gerd Hoffmann wrote: > > > Pasi K?rkk?inen wrote: > > > > > > > > I rebuilt 3.3.1-9 on fc10, and it seems to work. > > > > > > > > But virt-install (and virt-manager) seem to have problems.. > > > > > > > > # virt-install > > > > > > > > ERROR Unsupported virtualization type 'xen' > > > > > > > > Was xen support removed from virt-install, or does it just fail to detect > > > > xen is available when using pv_ops dom0? > > > > > > Either that, or the xen is a bit out-of-date because Fedora had no dom0 > > > kernel (thus no testing) since Fedora 8 ... > > > > > > I'd suggest to file bugs. Most likely the culprit is libvirt. > > > > > > > Actually we hunted this down with Cole Robinson and Jeremy.. > > > > The reason is pv_ops dom0 kernel is still missing /sys/hypervisor infos.. > > virt-install (or libvirt) needs that info to fetch the capabilities. > > We could probably switch over to making a hypercall to fetch that info > if /sys/hypervisor/properties/capabilities isn't going to reappear in > the near future ... > Just a followup to this thread too.. The patch (from old Redhat dom0 tree) implementing /sys/hypervisor feature is here: http://git.et.redhat.com/?p=linux-2.6-dom0-pvops.git;a=commit;h=7aa79a5603bb604e8bf4fe7c31cc9c8b3d3b7ea2 Hopefully Jeremy will merge it to current pv_ops dom0 tree. Discussion about this on xen-devel: http://lists.xensource.com/archives/html/xen-devel/2009-03/msg00472.html And another (more recent) thread on fedora-xen/fedora-virt about this subject: https://www.redhat.com/archives/fedora-xen/2009-March/msg00017.html -- Pasi From pasik at iki.fi Mon Mar 9 12:24:04 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 9 Mar 2009 14:24:04 +0200 Subject: [Fedora-xen] Re: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090309103929.GO4578@redhat.com> References: <20090307131920.GK15052@edu.joroinen.fi> <49B2AFFA.1080908@redhat.com> <20090307181922.GM15052@edu.joroinen.fi> <49B2C0B7.5030007@redhat.com> <20090307185036.GN15052@edu.joroinen.fi> <20090307185223.GO15052@edu.joroinen.fi> <49B2CAF4.2080107@redhat.com> <20090307193725.GP15052@edu.joroinen.fi> <20090308192310.GT15052@edu.joroinen.fi> <20090309103929.GO4578@redhat.com> Message-ID: <20090309122404.GX15052@edu.joroinen.fi> On Mon, Mar 09, 2009 at 10:39:29AM +0000, Daniel P. Berrange wrote: > On Sun, Mar 08, 2009 at 09:23:10PM +0200, Pasi K?rkk?inen wrote: > > On Sat, Mar 07, 2009 at 09:37:25PM +0200, Pasi K?rkk?inen wrote: > > > On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote: > > > > >> [root at dom0test ~]# cat /sys/hypervisor/properties/capabilities > > > > >> cat: /sys/hypervisor/properties/capabilities: No such file or directory > > > > >> > > > > > > > > > > [root at dom0test ~]# ls -la /sys/hypervisor > > > > > ls: cannot access /sys/hypervisor: No such file or directory > > > > > > > > > > > > > > > > > > Hmm, well that will do it. Libvirt capabilities are what tell user apps > > > > what types of domains can be installed, and generating xen capabilities > > > > is largely dependent on the above paths. Not too sure what to do from here. > > > > > > > > > > Ok. > > > > > > I'll try asking what's the thing with that.. if it's still missing, or is it > > > deprecated or something.. > > > > > > > Ok, it seems that /sys/hypervisor feature is not yet implemented in pv_ops > > dom0 kernel. > > > > There's a patch somewhere in Redhat's old dom0 repository.. Jeremy is trying > > to find that. > > > If this patch gets rejected for whatever reason, let me know, becasue we > can possibly switch libvirt over to making a direct hypercall to fetch > this information. > Yep. I will. The patch seems to be here: http://git.et.redhat.com/?p=linux-2.6-dom0-pvops.git;a=commit;h=7aa79a5603bb604e8bf4fe7c31cc9c8b3d3b7ea2 -- Pasi From crobinso at redhat.com Tue Mar 10 03:47:58 2009 From: crobinso at redhat.com (Cole Robinson) Date: Mon, 09 Mar 2009 23:47:58 -0400 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 Message-ID: <49B5E2EE.90402@redhat.com> I'm happy to announce a new virt-manager release, version 0.7.0. The release can be downloaded from: http://virt-manager.org/download.html The direct download link is: http://virt-manager.org/download/sources/virt-manager/virt-manager-0.7.0.tar.gz This release includes: - Redesigned 'New Virtual Machine' wizard (Jeremy Perry, Tim Allen, Cole Robinson) - Option to remove storage when deleting a virtual machine. - File browser for libvirt storage pools and volumes, for use when attaching storage to a new or existing guest. - Physical device assignment (PCI, USB) for existing virtual machines. - Bug fixes and minor improvements. Thanks to everyone who has contributed to this release through testing, bug reporting, submitting patches, and otherwise sending in feedback! Thanks, Cole From ondrejj at salstar.sk Wed Mar 11 10:22:45 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 11 Mar 2009 11:22:45 +0100 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <49B6B1DE.2030604@redhat.com> References: <49B5E2EE.90402@redhat.com> <20090310070023.GR25933@salstar.sk> <49B6B1DE.2030604@redhat.com> Message-ID: <20090311102245.GU25933@salstar.sk> Hello, after rebuild for F10 works well, just root password is not required when started. I think this is a feature and I am happy, that I don't need always click to run without privileges, but there is one problem. Starting an domain starts my serial console owned by root and is not accesssible from virt-manager (virt-viewer). After changing ownership it's immediatelly available. Is it possible to change this in time of virtual machine creation? (in libvirt or where?) Another feature enhacement can be adding "Serial 0" tab automatically, when there is no Console available for guest. Message "Console not configured for guest" can be sometimes misinterpretated, because I can have serial console for my guest. I prefer to use serial consoles, because they do not need to install graphical environment on host. They have multiple advantages, like access from another machine using serial or ipmi console, viewing crash status, when host crashes, ... And last possible enhancement: when pressing F10 key in guest's serial console, is it possible to avoid opening of "File menu" and send this key to serial 0, as it is done in VGA console? Thank you. SAL From sgallagh at redhat.com Wed Mar 11 12:43:43 2009 From: sgallagh at redhat.com (Stephen Gallagher) Date: Wed, 11 Mar 2009 08:43:43 -0400 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <49B5E2EE.90402@redhat.com> References: <49B5E2EE.90402@redhat.com> Message-ID: <49B7B1FF.4050202@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cole Robinson wrote: > I'm happy to announce a new virt-manager release, version 0.7.0. The > release can be downloaded from: > > http://virt-manager.org/download.html > > The direct download link is: > > http://virt-manager.org/download/sources/virt-manager/virt-manager-0.7.0.tar.gz > > This release includes: > > - Redesigned 'New Virtual Machine' wizard > (Jeremy Perry, Tim Allen, Cole Robinson) > - Option to remove storage when deleting a virtual machine. > - File browser for libvirt storage pools and volumes, for use when > attaching storage to a new or existing guest. > - Physical device assignment (PCI, USB) for existing virtual machines. > - Bug fixes and minor improvements. > > Thanks to everyone who has contributed to this release through testing, > bug reporting, submitting patches, and otherwise sending in feedback! > > Thanks, > Cole > > _______________________________________________ > Fedora-virt mailing list > Fedora-virt at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-virt I just attempted to build an RPM for Fedora 10 using the tarball linked above. It failed at two separate points. First, it could not build the manpages, because no Makefile existed in man/en. Once I copied the Makefile from the repository, it also failed missing the python-virtinst.spec file. I subsequently abandoned my attempts to build from the tarball and did a mercurial clone of the entire repo and built from that, which worked successfully. I couldn't find a link on the virt-manager webpage to the appropriate bug tracker, either (hence why this is going to the list). - -- Stephen Gallagher RHCE 804006346421761 Looking to carve out IT costs? www.redhat.com/carveoutcosts/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkm3sf8ACgkQeiVVYja6o6NmOACeMXn9LOK+4iPtQF+7lorZEZQ/ pxAAn2LgE8XDYgjlrMMTWkPzvMfTggBz =xidZ -----END PGP SIGNATURE----- From ondrejj at salstar.sk Wed Mar 11 12:50:36 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 11 Mar 2009 13:50:36 +0100 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <49B7B1FF.4050202@redhat.com> References: <49B5E2EE.90402@redhat.com> <49B7B1FF.4050202@redhat.com> Message-ID: <20090311125036.GW25933@salstar.sk> Hello, On Wed, Mar 11, 2009 at 08:43:43AM -0400, Stephen Gallagher wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Cole Robinson wrote: > > - Redesigned 'New Virtual Machine' wizard > > (Jeremy Perry, Tim Allen, Cole Robinson) > > - Option to remove storage when deleting a virtual machine. > > - File browser for libvirt storage pools and volumes, for use when > > attaching storage to a new or existing guest. > > - Physical device assignment (PCI, USB) for existing virtual machines. > > - Bug fixes and minor improvements. Also new is ability to scale display only when fullscreen. Very good option and I am happy, that it's default. :) > I just attempted to build an RPM for Fedora 10 using the tarball linked > above. It failed at two separate points. First, it could not build the > manpages, because no Makefile existed in man/en. Once I copied the > Makefile from the repository, it also failed missing the > python-virtinst.spec file. Why you do not recompile fc11 rpm? It's here: http://koji.fedoraproject.org/koji/buildinfo?buildID=93615 Enogh to download it and run: rpm --rebuild virt-manager-0.7.0-1.fc11.src.rpm Or if you want, fc10 packages are on my buildsys until I build something else: http://builder.salstar.sk/fedora-10-i386/result/ Cole: can you at least start an build for fc10 in koji? May be it will be usefull for other people. SAL From sgallagh at redhat.com Wed Mar 11 13:01:20 2009 From: sgallagh at redhat.com (Stephen Gallagher) Date: Wed, 11 Mar 2009 09:01:20 -0400 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <20090311125036.GW25933@salstar.sk> References: <49B5E2EE.90402@redhat.com> <49B7B1FF.4050202@redhat.com> <20090311125036.GW25933@salstar.sk> Message-ID: <49B7B620.7080706@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jan ONDREJ (SAL) wrote: > Hello, > > On Wed, Mar 11, 2009 at 08:43:43AM -0400, Stephen Gallagher wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Cole Robinson wrote: >>> - Redesigned 'New Virtual Machine' wizard >>> (Jeremy Perry, Tim Allen, Cole Robinson) >>> - Option to remove storage when deleting a virtual machine. >>> - File browser for libvirt storage pools and volumes, for use when >>> attaching storage to a new or existing guest. >>> - Physical device assignment (PCI, USB) for existing virtual machines. >>> - Bug fixes and minor improvements. > > Also new is ability to scale display only when fullscreen. Very good option > and I am happy, that it's default. :) > >> I just attempted to build an RPM for Fedora 10 using the tarball linked >> above. It failed at two separate points. First, it could not build the >> manpages, because no Makefile existed in man/en. Once I copied the >> Makefile from the repository, it also failed missing the >> python-virtinst.spec file. > > Why you do not recompile fc11 rpm? It's here: > http://koji.fedoraproject.org/koji/buildinfo?buildID=93615 Just so we're clear, I was able to build and install it successfully once I checked out the code from mercurial. My issue here is that a tarball is being provided that does not build. (It also fails to run 'python setup.py build' successfully because of the Makefile issue). > Enogh to download it and run: > rpm --rebuild virt-manager-0.7.0-1.fc11.src.rpm > > Or if you want, fc10 packages are on my buildsys until I build something > else: > http://builder.salstar.sk/fedora-10-i386/result/ > > Cole: can you at least start an build for fc10 in koji? May be it will be > usefull for other people. > > SAL - -- Stephen Gallagher RHCE 804006346421761 Looking to carve out IT costs? www.redhat.com/carveoutcosts/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkm3tiAACgkQeiVVYja6o6MJjACfYjmy3sjvGRl4f2H1azCA3pA5 ahoAn3luDcR4/t+SA1+HHZnHzowOMTb7 =dvl9 -----END PGP SIGNATURE----- From pasik at iki.fi Wed Mar 11 17:56:10 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 11 Mar 2009 19:56:10 +0200 Subject: [Fedora-xen] Re: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090309122404.GX15052@edu.joroinen.fi> References: <49B2AFFA.1080908@redhat.com> <20090307181922.GM15052@edu.joroinen.fi> <49B2C0B7.5030007@redhat.com> <20090307185036.GN15052@edu.joroinen.fi> <20090307185223.GO15052@edu.joroinen.fi> <49B2CAF4.2080107@redhat.com> <20090307193725.GP15052@edu.joroinen.fi> <20090308192310.GT15052@edu.joroinen.fi> <20090309103929.GO4578@redhat.com> <20090309122404.GX15052@edu.joroinen.fi> Message-ID: <20090311175610.GH15052@edu.joroinen.fi> On Mon, Mar 09, 2009 at 02:24:04PM +0200, Pasi K?rkk?inen wrote: > On Mon, Mar 09, 2009 at 10:39:29AM +0000, Daniel P. Berrange wrote: > > On Sun, Mar 08, 2009 at 09:23:10PM +0200, Pasi K?rkk?inen wrote: > > > On Sat, Mar 07, 2009 at 09:37:25PM +0200, Pasi K?rkk?inen wrote: > > > > On Sat, Mar 07, 2009 at 02:28:52PM -0500, Cole Robinson wrote: > > > > > >> [root at dom0test ~]# cat /sys/hypervisor/properties/capabilities > > > > > >> cat: /sys/hypervisor/properties/capabilities: No such file or directory > > > > > >> > > > > > > > > > > > > [root at dom0test ~]# ls -la /sys/hypervisor > > > > > > ls: cannot access /sys/hypervisor: No such file or directory > > > > > > > > > > > > > > > > > > > > > > Hmm, well that will do it. Libvirt capabilities are what tell user apps > > > > > what types of domains can be installed, and generating xen capabilities > > > > > is largely dependent on the above paths. Not too sure what to do from here. > > > > > > > > > > > > > Ok. > > > > > > > > I'll try asking what's the thing with that.. if it's still missing, or is it > > > > deprecated or something.. > > > > > > > > > > Ok, it seems that /sys/hypervisor feature is not yet implemented in pv_ops > > > dom0 kernel. > > > > > > There's a patch somewhere in Redhat's old dom0 repository.. Jeremy is trying > > > to find that. > > > > > > If this patch gets rejected for whatever reason, let me know, becasue we > > can possibly switch libvirt over to making a direct hypercall to fetch > > this information. > > > > Yep. I will. > > The patch seems to be here: > http://git.et.redhat.com/?p=linux-2.6-dom0-pvops.git;a=commit;h=7aa79a5603bb604e8bf4fe7c31cc9c8b3d3b7ea2 > And now this feature is committed to pv_ops kernel git tree: http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=834bf23efcffbc3e2c0c18ad277b3751ed2ba180 ATM this fix is needed to compile the kernel with /sys/hypervisor support patch: http://lists.xensource.com/archives/html/xen-devel/2009-03/msg00699.html I compiled a custom kernel with the patch included, and now: [root at dom0test ~]# cat /sys/hypervisor/properties/capabilities xen-3.0-x86_32p But Fedora 10 domU installation still fails: [root at dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" Starting install... Retrieving file .treeinfo... | 1.1 kB 00:00 Retrieving file vmlinuz-PAE... | 2.5 MB 00:01 Retrieving file initrd-PAE.img... | 16 MB 00:10 XML description for failed to build sexpr is not well formed or invalid Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm01'; otherwise, please restart your installation. ERROR XML description for failed to build sexpr is not well formed or invalid Traceback (most recent call last): File "/usr/sbin/virt-install", line 692, in main() File "/usr/sbin/virt-install", line 632, in main dom = guest.start_install(conscb, progresscb, wait=(not wait)) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 732, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 767, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 915, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: XML description for failed to build sexpr is not well formed or invalid -- Pasi From berrange at redhat.com Wed Mar 11 17:59:01 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 11 Mar 2009 17:59:01 +0000 Subject: [Fedora-xen] Re: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090311175610.GH15052@edu.joroinen.fi> References: <20090307181922.GM15052@edu.joroinen.fi> <49B2C0B7.5030007@redhat.com> <20090307185036.GN15052@edu.joroinen.fi> <20090307185223.GO15052@edu.joroinen.fi> <49B2CAF4.2080107@redhat.com> <20090307193725.GP15052@edu.joroinen.fi> <20090308192310.GT15052@edu.joroinen.fi> <20090309103929.GO4578@redhat.com> <20090309122404.GX15052@edu.joroinen.fi> <20090311175610.GH15052@edu.joroinen.fi> Message-ID: <20090311175901.GO23995@redhat.com> On Wed, Mar 11, 2009 at 07:56:10PM +0200, Pasi K?rkk?inen wrote: > But Fedora 10 domU installation still fails: > > [root at dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > > > Starting install... > Retrieving file .treeinfo... | 1.1 kB 00:00 > Retrieving file vmlinuz-PAE... | 2.5 MB 00:01 > Retrieving file initrd-PAE.img... | 16 MB 00:10 > XML description for failed to build sexpr is not well formed or invalid > Domain installation may not have been > successful. If it was, you can restart your domain > by running 'virsh start vm01'; otherwise, please > restart your installation. > ERROR XML description for failed to build sexpr is not well formed or invalid Now this one sounds like a genuine libvirt or virt-install bug ! Can you re-run with --debug, and file a BZ with the information so we can track it formally. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From pasik at iki.fi Wed Mar 11 20:05:03 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 11 Mar 2009 22:05:03 +0200 Subject: [Fedora-xen] Re: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090311175901.GO23995@redhat.com> References: <49B2C0B7.5030007@redhat.com> <20090307185036.GN15052@edu.joroinen.fi> <20090307185223.GO15052@edu.joroinen.fi> <49B2CAF4.2080107@redhat.com> <20090307193725.GP15052@edu.joroinen.fi> <20090308192310.GT15052@edu.joroinen.fi> <20090309103929.GO4578@redhat.com> <20090309122404.GX15052@edu.joroinen.fi> <20090311175610.GH15052@edu.joroinen.fi> <20090311175901.GO23995@redhat.com> Message-ID: <20090311200503.GI15052@edu.joroinen.fi> On Wed, Mar 11, 2009 at 05:59:01PM +0000, Daniel P. Berrange wrote: > On Wed, Mar 11, 2009 at 07:56:10PM +0200, Pasi K?rkk?inen wrote: > > But Fedora 10 domU installation still fails: > > > > [root at dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > > "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > > > > > > Starting install... > > Retrieving file .treeinfo... | 1.1 kB 00:00 > > Retrieving file vmlinuz-PAE... | 2.5 MB 00:01 > > Retrieving file initrd-PAE.img... | 16 MB 00:10 > > XML description for failed to build sexpr is not well formed or invalid > > Domain installation may not have been > > successful. If it was, you can restart your domain > > by running 'virsh start vm01'; otherwise, please > > restart your installation. > > ERROR XML description for failed to build sexpr is not well formed or invalid > > > Now this one sounds like a genuine libvirt or virt-install bug ! > > Can you re-run with --debug, and file a BZ with the information so we can > track it formally. > Ok. Will do. Here's the --debug info aswell: [root at dom0test ~]# virt-install --debug -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" Wed, 11 Mar 2009 21:58:52 DEBUG Using libvirt URI connect 'xen' Wed, 11 Mar 2009 21:58:52 WARNING Non-error from libvirt: 'Failed to find the network: Is the daemon running ?' Wed, 11 Mar 2009 21:58:52 DEBUG Requesting virt method 'xen' Wed, 11 Mar 2009 21:58:52 DEBUG Received virt method 'xen' Wed, 11 Mar 2009 21:58:52 DEBUG Hypervisor type is 'xen' Wed, 11 Mar 2009 21:58:52 DEBUG Using self.path for VirtualDisk. Wed, 11 Mar 2009 21:58:52 DEBUG VirtualDisk storage exists. Wed, 11 Mar 2009 21:58:52 DEBUG Detected storage as type 'block' Wed, 11 Mar 2009 21:58:52 DEBUG DistroInstaller location is a network source. Starting install... Wed, 11 Mar 2009 21:58:53 DEBUG Attempting to detect distro: Wed, 11 Mar 2009 21:58:53 DEBUG Detected .treeinfo file Wed, 11 Mar 2009 21:58:53 DEBUG Fetching URI ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os/.treeinfo Wed, 11 Mar 2009 21:58:53 DEBUG Saved file to /var/lib/xen/virtinst-.treeinfo.rXElMi Retrieving file .treeinfo... | /1.1 kB 00:00 Wed, 11 Mar 2009 21:58:53 DEBUG Fetching URI ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os/images/pxeboot/vmlinuz-PAE Retrieving file vmlinuz-PAE... 1.2 MB/s | /2.0 MB 00:00 Wed, 11 Mar 2009 21:58:54 DEBUG Saved file to /var/lib/xen/virtinst-vmlinuz-PAE.OgMr10 Retrieving file vmlinuz-PAE... | 2.5 MB 00:01 Wed, 11 Mar 2009 21:58:54 DEBUG Fetching URI ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os/images/pxeboot/initrd-PAE.img Retrieving file initrd-PAE.img... 1.9 MB/s | 16 MB 00:07 Wed, 11 Mar 2009 21:59:02 DEBUG Saved file to /var/lib/xen/virtinst-initrd-PAE.img.aF3UYJ Retrieving file initrd-PAE.img... | 16 MB 00:07 Wed, 11 Mar 2009 21:59:02 DEBUG Using self.path for VirtualDisk. Wed, 11 Mar 2009 21:59:02 DEBUG VirtualDisk storage exists. Wed, 11 Mar 2009 21:59:02 DEBUG Detected storage as type 'block' Wed, 11 Mar 2009 21:59:02 DEBUG Creating guest from ' vm01 524288 524288 c2d3c368-245d-05bd-7772-e799f0e05194 linux /var/lib/xen/virtinst-vmlinuz-PAE.OgMr10 /var/lib/xen/virtinst-initrd-PAE.img.aF3UYJ method=ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os destroy destroy destroy 1 ' Wed, 11 Mar 2009 21:59:02 DEBUG Removing /var/lib/xen/virtinst-vmlinuz-PAE.OgMr10 Wed, 11 Mar 2009 21:59:02 DEBUG Removing /var/lib/xen/virtinst-initrd-PAE.img.aF3UYJ XML description for failed to build sexpr is not well formed or invalid Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm01'; otherwise, please restart your installation. Wed, 11 Mar 2009 21:59:02 ERROR XML description for failed to build sexpr is not well formed or invalid Traceback (most recent call last): File "/usr/sbin/virt-install", line 692, in main() File "/usr/sbin/virt-install", line 632, in main dom = guest.start_install(conscb, progresscb, wait=(not wait)) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 732, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 767, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 915, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: XML description for failed to build sexpr is not well formed or invalid -- Pasi From pasik at iki.fi Wed Mar 11 21:39:00 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 11 Mar 2009 23:39:00 +0200 Subject: [Fedora-xen] Re: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090311200503.GI15052@edu.joroinen.fi> References: <20090307185036.GN15052@edu.joroinen.fi> <20090307185223.GO15052@edu.joroinen.fi> <49B2CAF4.2080107@redhat.com> <20090307193725.GP15052@edu.joroinen.fi> <20090308192310.GT15052@edu.joroinen.fi> <20090309103929.GO4578@redhat.com> <20090309122404.GX15052@edu.joroinen.fi> <20090311175610.GH15052@edu.joroinen.fi> <20090311175901.GO23995@redhat.com> <20090311200503.GI15052@edu.joroinen.fi> Message-ID: <20090311213900.GL15052@edu.joroinen.fi> On Wed, Mar 11, 2009 at 10:05:03PM +0200, Pasi K?rkk?inen wrote: > On Wed, Mar 11, 2009 at 05:59:01PM +0000, Daniel P. Berrange wrote: > > On Wed, Mar 11, 2009 at 07:56:10PM +0200, Pasi K?rkk?inen wrote: > > > But Fedora 10 domU installation still fails: > > > > > > [root at dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > > > "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > > > > > > > > > Starting install... > > > Retrieving file .treeinfo... | 1.1 kB 00:00 > > > Retrieving file vmlinuz-PAE... | 2.5 MB 00:01 > > > Retrieving file initrd-PAE.img... | 16 MB 00:10 > > > XML description for failed to build sexpr is not well formed or invalid > > > Domain installation may not have been > > > successful. If it was, you can restart your domain > > > by running 'virsh start vm01'; otherwise, please > > > restart your installation. > > > ERROR XML description for failed to build sexpr is not well formed or invalid > > > > > > Now this one sounds like a genuine libvirt or virt-install bug ! > > > > Can you re-run with --debug, and file a BZ with the information so we can > > track it formally. > > > > Ok. Will do. > Now done: https://bugzilla.redhat.com/show_bug.cgi?id=489799 -- Pasi From crobinso at redhat.com Fri Mar 13 16:45:56 2009 From: crobinso at redhat.com (Cole Robinson) Date: Fri, 13 Mar 2009 12:45:56 -0400 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <20090311102245.GU25933@salstar.sk> References: <49B5E2EE.90402@redhat.com> <20090310070023.GR25933@salstar.sk> <49B6B1DE.2030604@redhat.com> <20090311102245.GU25933@salstar.sk> Message-ID: <49BA8DC4.2080705@redhat.com> Jan ONDREJ (SAL) wrote: > Hello, > > after rebuild for F10 works well, just root password is not required when > started. I think this is a feature and I am happy, that I don't need always > click to run without privileges, but there is one problem. > > Starting an domain starts my serial console owned by root and is not > accesssible from virt-manager (virt-viewer). After changing ownership it's > immediatelly available. Is it possible to change this in time of virtual > machine creation? (in libvirt or where?) > Yes, this is one of the drawbacks of not running virt-manager as root: since the qemu:///system libvirt connection will launch your guests as root, a regular user won't be able to access ptys. I don't know of a proper solution to it all, other then running the app as root or changing the the pty permissions as you did. > Another feature enhacement can be adding "Serial 0" tab automatically, > when there is no Console available for guest. Message "Console not > configured for guest" can be sometimes misinterpretated, because I can have > serial console for my guest. I see what you mean. The wording could certainly be better, and It would make sense to try to connect to the serial console if no graphics device is attached. Thanks for the idea. I prefer to use serial consoles, because they > do not need to install graphical environment on host. They have multiple > advantages, like access from another machine using serial or ipmi console, > viewing crash status, when host crashes, ... > > And last possible enhancement: when pressing F10 key in guest's serial > console, is it possible to avoid opening of "File menu" and send this key to > serial 0, as it is done in VGA console? > We would probably need some sort of keygrab process like we do for VNC to get this right. Not sure if that's even an option for the VTE widget though. Thanks, Cole From crobinso at redhat.com Fri Mar 13 16:53:50 2009 From: crobinso at redhat.com (Cole Robinson) Date: Fri, 13 Mar 2009 12:53:50 -0400 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <49B7B1FF.4050202@redhat.com> References: <49B5E2EE.90402@redhat.com> <49B7B1FF.4050202@redhat.com> Message-ID: <49BA8F9E.2030600@redhat.com> Stephen Gallagher wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Cole Robinson wrote: >> I'm happy to announce a new virt-manager release, version 0.7.0. The >> release can be downloaded from: >> >> http://virt-manager.org/download.html >> >> The direct download link is: >> >> http://virt-manager.org/download/sources/virt-manager/virt-manager-0.7.0.tar.gz >> >> This release includes: >> >> - Redesigned 'New Virtual Machine' wizard >> (Jeremy Perry, Tim Allen, Cole Robinson) >> - Option to remove storage when deleting a virtual machine. >> - File browser for libvirt storage pools and volumes, for use when >> attaching storage to a new or existing guest. >> - Physical device assignment (PCI, USB) for existing virtual machines. >> - Bug fixes and minor improvements. >> >> Thanks to everyone who has contributed to this release through testing, >> bug reporting, submitting patches, and otherwise sending in feedback! >> >> Thanks, >> Cole > > I just attempted to build an RPM for Fedora 10 using the tarball linked > above. It failed at two separate points. First, it could not build the > manpages, because no Makefile existed in man/en. Once I copied the > Makefile from the repository, it also failed missing the > python-virtinst.spec file. > Ah, yes building an rpm from the extracted tarball has some issues, I'll fix these upstream. For future reference, you can just do: rpmbuild -ta virtinst-0.400.3.tar.gz And it will build an rpm. To install without an rpm, 'cd' into the checkout and run: python setup.py build && python setup.py install Thanks, Cole From ondrejj at salstar.sk Fri Mar 13 17:55:11 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Fri, 13 Mar 2009 18:55:11 +0100 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <49BA8DC4.2080705@redhat.com> References: <49B5E2EE.90402@redhat.com> <20090310070023.GR25933@salstar.sk> <49B6B1DE.2030604@redhat.com> <20090311102245.GU25933@salstar.sk> <49BA8DC4.2080705@redhat.com> Message-ID: <20090313175511.GR25933@salstar.sk> Hello, thank you for positive reply. On Fri, Mar 13, 2009 at 12:45:56PM -0400, Cole Robinson wrote: > Jan ONDREJ (SAL) wrote: > > Starting an domain starts my serial console owned by root and is not > > accesssible from virt-manager (virt-viewer). After changing ownership it's > > immediatelly available. Is it possible to change this in time of virtual > > machine creation? (in libvirt or where?) > > > > Yes, this is one of the drawbacks of not running virt-manager as root: > since the qemu:///system libvirt connection will launch your guests as > root, a regular user won't be able to access ptys. > > I don't know of a proper solution to it all, other then running the app > as root or changing the the pty permissions as you did. Is it known to libvirt, who is user which is starting virtual machine? Can libvirt change ownership of this pty back to user? Root do not need to be owner of this file to access it, he can access any file, but user needs. Another solution can be to change permissions on pty to 660, leave group to tty or change it to a value defined in libvirtd.conf. Is it possible? SAL From crobinso at redhat.com Fri Mar 13 18:06:37 2009 From: crobinso at redhat.com (Cole Robinson) Date: Fri, 13 Mar 2009 14:06:37 -0400 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <20090313175511.GR25933@salstar.sk> References: <49B5E2EE.90402@redhat.com> <20090310070023.GR25933@salstar.sk> <49B6B1DE.2030604@redhat.com> <20090311102245.GU25933@salstar.sk> <49BA8DC4.2080705@redhat.com> <20090313175511.GR25933@salstar.sk> Message-ID: <49BAA0AD.4060103@redhat.com> Jan ONDREJ (SAL) wrote: > Hello, > > thank you for positive reply. > > On Fri, Mar 13, 2009 at 12:45:56PM -0400, Cole Robinson wrote: >> Jan ONDREJ (SAL) wrote: >>> Starting an domain starts my serial console owned by root and is not >>> accesssible from virt-manager (virt-viewer). After changing ownership it's >>> immediatelly available. Is it possible to change this in time of virtual >>> machine creation? (in libvirt or where?) >>> >> Yes, this is one of the drawbacks of not running virt-manager as root: >> since the qemu:///system libvirt connection will launch your guests as >> root, a regular user won't be able to access ptys. >> >> I don't know of a proper solution to it all, other then running the app >> as root or changing the the pty permissions as you did. > > Is it known to libvirt, who is user which is starting virtual machine? Can > libvirt change ownership of this pty back to user? Root do not need to be > owner of this file to access it, he can access any file, but user needs. > I'm pretty sure libvirt doesn't know the actual user who is connecting via PolicyKit: it all looks like root after the authentication. > Another solution can be to change permissions on pty to 660, leave group to > tty or change it to a value defined in libvirtd.conf. > This doesn't sound unreasonable, you'd probably want to bring it up on libvir-list or file a bug though. Thanks, Cole From m.a.young at durham.ac.uk Fri Mar 13 23:40:11 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Fri, 13 Mar 2009 23:40:11 +0000 (GMT) Subject: [fedora-virt] Re: Dom0 kernels In-Reply-To: References: Message-ID: Another update (2.6.29-0.114.2.11.rc7.git5), which includes /sys/hypervisor support, is at http://koji.fedoraproject.org/koji/taskinfo?taskID=1238587 Michael Young From itamar at ispbrasil.com.br Sat Mar 14 01:11:56 2009 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Fri, 13 Mar 2009 22:11:56 -0300 Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: Message-ID: any chance to get this in fedora kernels ? worked fine for me [root at localhost ~]# uname -a Linux localhost.localdomain 2.6.29-0.114.2.11.rc7.git5.fc11.x86_64 #1 SMP Thu Mar 12 16:50:15 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux [root at localhost ~]# xm list /usr/lib64/python2.6/site-packages/xen/util/acmpolicy.py:20: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha Name ID Mem VCPUs State Time(s) Domain-0 0 1815 2 r----- 127.0 [root at localhost ~]# On Fri, Mar 13, 2009 at 8:40 PM, M A Young wrote: > Another update (2.6.29-0.114.2.11.rc7.git5), which includes /sys/hypervisor > support, is at http://koji.fedoraproject.org/koji/taskinfo?taskID=1238587 > > ? ? ? ?Michael Young > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- ------------ Itamar Reis Peixoto e-mail/msn: itamar at ispbrasil.com.br sip: itamar at ispbrasil.com.br skype: itamarjp icq: 81053601 +55 11 4063 5033 +55 34 3221 8599 From m.a.young at durham.ac.uk Sat Mar 14 12:46:25 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sat, 14 Mar 2009 12:46:25 +0000 (GMT) Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: Message-ID: On Fri, 13 Mar 2009, Itamar Reis Peixoto wrote: > any chance to get this in fedora kernels ? > > > worked fine for me The current plan is to wait until basic dom0 support makes it into the vanilla kernel, which should happen for 2.6.30, and then decide if dom0 can be enabled and if the patches for full dom0 support can safely be added without affecting ordinary operation. At the moment there are still things that are broken such as X support in some cases, and there are also Fedora patches that have been omitted because they were tricky to merge, so it is too early to start adding dom0 support to official Fedora kernels. Michael Young From itamar at ispbrasil.com.br Sat Mar 14 18:31:59 2009 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Sat, 14 Mar 2009 15:31:59 -0300 Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: Message-ID: I am sending this mail using your dom0 kernel and it's working fine. On Sat, Mar 14, 2009 at 9:46 AM, M A Young wrote: > On Fri, 13 Mar 2009, Itamar Reis Peixoto wrote: > >> any chance to get this in fedora kernels ? >> >> >> worked fine for me > > The current plan is to wait until basic dom0 support makes it into the > vanilla kernel, which should happen for 2.6.30, and then decide if dom0 can > be enabled and if the patches for full dom0 support can safely be added > without affecting ordinary operation. > > At the moment there are still things that are broken such as X support in > some cases, and there are also Fedora patches that have been omitted because > they were tricky to merge, so it is too early to start adding dom0 support > to official Fedora kernels. > > ? ? ? ?Michael Young > -- ------------ Itamar Reis Peixoto e-mail/msn: itamar at ispbrasil.com.br sip: itamar at ispbrasil.com.br skype: itamarjp icq: 81053601 +55 11 4063 5033 +55 34 3221 8599 From m.a.young at durham.ac.uk Sun Mar 15 16:20:47 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sun, 15 Mar 2009 16:20:47 +0000 (GMT) Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: Message-ID: On Sat, 14 Mar 2009, Itamar Reis Peixoto wrote: > I am sending this mail using your dom0 kernel > > and it's working fine. I don't think you have tested it very thoroughly because networking to the guest seems to be broken in my latest kernel. Also the success you have with graphics will depend a lot on what graphics card you have. It is entirely possible that graphics will work in some cases, but they definitely don't in others. Michael Young From berrange at redhat.com Mon Mar 16 09:14:48 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 16 Mar 2009 09:14:48 +0000 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <49BA8DC4.2080705@redhat.com> References: <49B5E2EE.90402@redhat.com> <20090310070023.GR25933@salstar.sk> <49B6B1DE.2030604@redhat.com> <20090311102245.GU25933@salstar.sk> <49BA8DC4.2080705@redhat.com> Message-ID: <20090316091448.GA22285@redhat.com> On Fri, Mar 13, 2009 at 12:45:56PM -0400, Cole Robinson wrote: > Jan ONDREJ (SAL) wrote: > > Hello, > > > > after rebuild for F10 works well, just root password is not required when > > started. I think this is a feature and I am happy, that I don't need always > > click to run without privileges, but there is one problem. > > > > Starting an domain starts my serial console owned by root and is not > > accesssible from virt-manager (virt-viewer). After changing ownership it's > > immediatelly available. Is it possible to change this in time of virtual > > machine creation? (in libvirt or where?) > > > > Yes, this is one of the drawbacks of not running virt-manager as root: > since the qemu:///system libvirt connection will launch your guests as > root, a regular user won't be able to access ptys. > > I don't know of a proper solution to it all, other then running the app > as root or changing the the pty permissions as you did. It is not worth running root just to get access to the serial PTYs. If we want to kep accessing PTYs directly, then perhaps make them use a TCP socket on localhost, instead of a PTY. The real solution though is to get the serial datastream tunneled over the VNC connection. I want this to be a goal for F12 - most of the work for that will be in KVM /GTK-VNc space, then it'll mostly 'just work' for virt-manager. > > And last possible enhancement: when pressing F10 key in guest's serial > > console, is it possible to avoid opening of "File menu" and send this key to > > serial 0, as it is done in VGA console? > > > > We would probably need some sort of keygrab process like we do for VNC > to get this right. Not sure if that's even an option for the VTE widget > though. You don't need to have it directly supported in VTE - virt-manager itself can call the neccessary functions whenever the widget gets keyboard focus. To get a full solution there's basically three things you need todo, disable F10 accelerator, disable global accelerators, and disable menu bar shortcuts. In C code I do: /* This allows F10 activating menu bar */ g_object_set_property(G_OBJECT(settings), "gtk-menu-bar-accel", &viewer->accelSetting); /* This allows global accelerators like Ctrl+Q == Quit */ for (accels = viewer->accelList ; accels ; accels = accels->next) { gtk_window_add_accel_group(GTK_WINDOW(viewer->window), accels->data); } /* This allows menu bar shortcuts like Alt+F == File */ for (i = 0 ; i < LAST_MENU ; i++) { GtkWidget *menu = glade_xml_get_widget(viewer->glade, menuNames[i]); g_signal_handler_disconnect(GTK_OBJECT(menu), viewer->accelMenuSig[i]); } you can probably figure out the python equivalents Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From sgallagh at redhat.com Mon Mar 16 11:16:55 2009 From: sgallagh at redhat.com (Stephen Gallagher) Date: Mon, 16 Mar 2009 07:16:55 -0400 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <49BA8F9E.2030600@redhat.com> References: <49B5E2EE.90402@redhat.com> <49B7B1FF.4050202@redhat.com> <49BA8F9E.2030600@redhat.com> Message-ID: <49BE3527.30109@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cole Robinson wrote: > Stephen Gallagher wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Cole Robinson wrote: >>> I'm happy to announce a new virt-manager release, version 0.7.0. The >>> release can be downloaded from: >>> >>> http://virt-manager.org/download.html >>> >>> The direct download link is: >>> >>> http://virt-manager.org/download/sources/virt-manager/virt-manager-0.7.0.tar.gz >>> >>> This release includes: >>> >>> - Redesigned 'New Virtual Machine' wizard >>> (Jeremy Perry, Tim Allen, Cole Robinson) >>> - Option to remove storage when deleting a virtual machine. >>> - File browser for libvirt storage pools and volumes, for use when >>> attaching storage to a new or existing guest. >>> - Physical device assignment (PCI, USB) for existing virtual machines. >>> - Bug fixes and minor improvements. >>> >>> Thanks to everyone who has contributed to this release through testing, >>> bug reporting, submitting patches, and otherwise sending in feedback! >>> >>> Thanks, >>> Cole > >> I just attempted to build an RPM for Fedora 10 using the tarball linked >> above. It failed at two separate points. First, it could not build the >> manpages, because no Makefile existed in man/en. Once I copied the >> Makefile from the repository, it also failed missing the >> python-virtinst.spec file. >> > > Ah, yes building an rpm from the extracted tarball has some issues, I'll > fix these upstream. For future reference, you can just do: > > rpmbuild -ta virtinst-0.400.3.tar.gz > > And it will build an rpm. To install without an rpm, 'cd' into the > checkout and run: > > python setup.py build && python setup.py install > > Thanks, > Cole That's part of what I was trying to tell you: setup.py build does not work in that tarball. It's missing a makefile in man/en - -- Stephen Gallagher RHCE 804006346421761 Looking to carve out IT costs? www.redhat.com/carveoutcosts/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkm+NScACgkQeiVVYja6o6OG2gCeLgUtfB+GIFL5S9EfsxAmU8ay w14AoI5yr0GXbjD88PflMjpXoXc99UHM =4E+l -----END PGP SIGNATURE----- From crobinso at redhat.com Mon Mar 16 13:39:07 2009 From: crobinso at redhat.com (Cole Robinson) Date: Mon, 16 Mar 2009 09:39:07 -0400 Subject: [fedora-virt] [ANNOUNCE] New release virt-manager 0.7.0 In-Reply-To: <49BE3527.30109@redhat.com> References: <49B5E2EE.90402@redhat.com> <49B7B1FF.4050202@redhat.com> <49BA8F9E.2030600@redhat.com> <49BE3527.30109@redhat.com> Message-ID: <49BE567B.2070302@redhat.com> Stephen Gallagher wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Cole Robinson wrote: >> Stephen Gallagher wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Cole Robinson wrote: >>>> I'm happy to announce a new virt-manager release, version 0.7.0. The >>>> release can be downloaded from: >>>> >>>> http://virt-manager.org/download.html >>>> >>>> The direct download link is: >>>> >>>> http://virt-manager.org/download/sources/virt-manager/virt-manager-0.7.0.tar.gz >>>> >>>> This release includes: >>>> >>>> - Redesigned 'New Virtual Machine' wizard >>>> (Jeremy Perry, Tim Allen, Cole Robinson) >>>> - Option to remove storage when deleting a virtual machine. >>>> - File browser for libvirt storage pools and volumes, for use when >>>> attaching storage to a new or existing guest. >>>> - Physical device assignment (PCI, USB) for existing virtual machines. >>>> - Bug fixes and minor improvements. >>>> >>>> Thanks to everyone who has contributed to this release through testing, >>>> bug reporting, submitting patches, and otherwise sending in feedback! >>>> >>>> Thanks, >>>> Cole >>> I just attempted to build an RPM for Fedora 10 using the tarball linked >>> above. It failed at two separate points. First, it could not build the >>> manpages, because no Makefile existed in man/en. Once I copied the >>> Makefile from the repository, it also failed missing the >>> python-virtinst.spec file. >>> >> Ah, yes building an rpm from the extracted tarball has some issues, I'll >> fix these upstream. For future reference, you can just do: >> >> rpmbuild -ta virtinst-0.400.3.tar.gz >> >> And it will build an rpm. To install without an rpm, 'cd' into the >> checkout and run: >> >> python setup.py build && python setup.py install >> >> Thanks, >> Cole > > That's part of what I was trying to tell you: setup.py build does not > work in that tarball. It's missing a makefile in man/en > Yes the Makefile is missing, but it shouldn't affect 'python setup.py build', and indeed works fine for me with the release tarball. Can you post the output of a failing build command? Thanks, Cole From ondrejj at salstar.sk Tue Mar 17 11:18:19 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Tue, 17 Mar 2009 12:18:19 +0100 Subject: [fedora-virt] Disk in snapshot mode Message-ID: <20090317111819.GW25933@salstar.sk> Hello, can I set snapshot mode for KVM disk emulation using virsh or/and virt-manager? This is a great feature to test software using qemu/kvm, but I don't see, how to use this using withou direct running of qemu-kvm -snapshot. In snapshot mode qemu does not change original disk file, but changes are written to temporary files and after shutdown changes are lost. It's good to use when trying something on virtual machien. As an opensource software developer I often need to test my software and then forget all changes in system. Running kvm using commandline work well, just it's a bit hard to setup devides same way as they are done in libvirt. Snapshot mode can be set 2 ways, by adding "-snapshot" qemu parameter or adding ",snapshot=on" to -drive parameter. May be an universal option in XML definitions to add unknown parameters may be useful, for example: ,snapshot=on Regards SAL From m.a.young at durham.ac.uk Wed Mar 18 00:26:56 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Wed, 18 Mar 2009 00:26:56 +0000 (GMT) Subject: [fedora-virt] Re: Dom0 kernels In-Reply-To: References: Message-ID: My latest build (2.6.29-0.114.2.12.rc8.git2.fc11) is available at http://koji.fedoraproject.org/koji/taskinfo?taskID=1246980 . Networking to the guest is working again, and the X situation is better than I thought, because my problems on one machine were due to using a F11 based kernel on F10, and X works if I use it with F11. In addition I got X working on the other machine working by using the nomodeset boot parameter (with nomodeset I get no text characters during boot - only a cursor that moves as invisible characters are presumably printed to the screen - but X starts successfully, without nomodeset I can read the boot messages but X crashes), however there are X problems on this machine with regular Fedora kernels, so this may not be xen's fault. Michael Young From canturk at alumni.princeton.edu Wed Mar 18 05:46:03 2009 From: canturk at alumni.princeton.edu (Canturk Isci) Date: Wed, 18 Mar 2009 01:46:03 -0400 (Eastern Daylight Time) Subject: [fedora-virt] kvm live migration with libvirt In-Reply-To: References: Message-ID: Hello all, I hope this is the right forum to bring this up, my apologies otherwise. We have been experimenting with live migration using KVM+libvirt, and it seems using 'migrate' via virsh has some problems in our canonical FC10 build. In summary: virsh# migrate qemu+ssh:///system results in: "failed to start listening vm" We can do migration successfully if we disable libvirt and do the migration directly from qemu monitor. I am wondering whether this is a known issue and if there is a workaround or newer build that resolves this, as i would prefer to use to libvirt interfaces in our infrastructure. Thanks a lot. -canturk From b_whelan at mistral.co.uk Wed Mar 18 08:53:02 2009 From: b_whelan at mistral.co.uk (Brendan Whelan) Date: Wed, 18 Mar 2009 08:53:02 +0000 Subject: [fedora-virt] New to virtualizatoin Message-ID: <49C0B66E.5070509@mistral.co.uk> I am new to using virtualization and, after some effort, I have created and then cloned a virtual image on a laptop with an Intel P8400 processor using Fedora 10. Unfortunately, when I run the cloned image I don't have proper cursor control, even after pressing ctrl-alt. Any suggestions? Is there a straightforward guide to creating and managing virtual applications under Fedora 10? I know that KVM and VMWare use different mechanisms. My understanding is that KVM accesses the hardware directly whilst VMWare creates a base system through which all information, from the virtual systems, is routed. However, is it possible to migrate an image from Fedora to VMware? Many thanks, Brendan From kraxel at redhat.com Wed Mar 18 09:02:52 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Wed, 18 Mar 2009 10:02:52 +0100 Subject: [fedora-virt] Re: Dom0 kernels In-Reply-To: References: Message-ID: <49C0B8BC.1050301@redhat.com> M A Young wrote: > (with nomodeset I get no text characters during > boot - only a cursor that moves as invisible characters are presumably > printed to the screen known issue with vga text mode (32bit only, 64bit works ok). vga window at 0xc0000 isn't mapped correctly. Workaround: drive the card in gfx mode. Either kernel mode setting or vesafb (use something like vga=gfx-1024x768x16 on the *xen* kernel command line). HTH, Gerd From dlaor at redhat.com Wed Mar 18 09:12:11 2009 From: dlaor at redhat.com (Dor Laor) Date: Wed, 18 Mar 2009 11:12:11 +0200 Subject: [fedora-virt] New to virtualizatoin In-Reply-To: <49C0B66E.5070509@mistral.co.uk> References: <49C0B66E.5070509@mistral.co.uk> Message-ID: <49C0BAEB.4080305@redhat.com> Brendan Whelan wrote: > I am new to using virtualization and, after some effort, I have > created and then cloned a virtual image on a laptop with an Intel > P8400 processor using Fedora 10. > Unfortunately, when I run the cloned image I don't have proper cursor > control, even after pressing ctrl-alt. Any suggestions? > Is there a straightforward guide to creating and managing virtual > applications under Fedora 10? For the mouse issue you might look at http://www.redhat.com/archives/fedora-virt/2009-February/msg00083.html Virt-manager is used to run VMs on F10 > I know that KVM and VMWare use different mechanisms. My understanding > is that KVM accesses the hardware directly whilst VMWare creates a > base system through which all information, from the virtual systems, > is routed. However, is it possible to migrate an image from Fedora to > VMware? Many thanks, Brendan While I hate to explain this, here it is: you can convert the disk format to VMW vmdk format using qemu-img and just run it there. > > > > > _______________________________________________ > Fedora-virt mailing list > Fedora-virt at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-virt From berrange at redhat.com Wed Mar 18 11:07:48 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 18 Mar 2009 11:07:48 +0000 Subject: [fedora-virt] New to virtualizatoin In-Reply-To: <49C0B66E.5070509@mistral.co.uk> References: <49C0B66E.5070509@mistral.co.uk> Message-ID: <20090318110748.GA23690@redhat.com> On Wed, Mar 18, 2009 at 08:53:02AM +0000, Brendan Whelan wrote: > I am new to using virtualization and, after some effort, I have created > and then cloned a virtual image on a laptop with an Intel P8400 > processor using Fedora 10. > Unfortunately, when I run the cloned image I don't have proper cursor > control, even after pressing ctrl-alt. Any suggestions? There was a bug in GTK-VNC for mouse grab handling. I've hust pushed an update to the stable repos so it should show up in a couple of days You want gtk-vnc-0.3.8-2.fc10 As of Fedora 11, the mouse will work perfectly without any grab being needed https://fedoraproject.org/wiki/Features/VirtImprovedConsole Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From b_whelan at mistral.co.uk Wed Mar 18 20:44:01 2009 From: b_whelan at mistral.co.uk (Brendan Whelan) Date: Wed, 18 Mar 2009 20:44:01 +0000 Subject: [fedora-virt] New to virtualizatoin In-Reply-To: <20090318110748.GA23690@redhat.com> References: <49C0B66E.5070509@mistral.co.uk> <20090318110748.GA23690@redhat.com> Message-ID: <49C15D11.8080905@mistral.co.uk> Thanks to Daniel and Dor for your helpful reponses. I hope to get back to configuring the laptop in a day ot two. Brendan Daniel P. Berrange wrote: > On Wed, Mar 18, 2009 at 08:53:02AM +0000, Brendan Whelan wrote: > >> I am new to using virtualization and, after some effort, I have created >> and then cloned a virtual image on a laptop with an Intel P8400 >> processor using Fedora 10. >> Unfortunately, when I run the cloned image I don't have proper cursor >> control, even after pressing ctrl-alt. Any suggestions? >> > > There was a bug in GTK-VNC for mouse grab handling. I've hust pushed an > update to the stable repos so it should show up in a couple of days > You want > > gtk-vnc-0.3.8-2.fc10 > > As of Fedora 11, the mouse will work perfectly without any grab being > needed > > https://fedoraproject.org/wiki/Features/VirtImprovedConsole > > Daniel > From b_whelan at mistral.co.uk Fri Mar 20 11:29:54 2009 From: b_whelan at mistral.co.uk (Brendan Whelan) Date: Fri, 20 Mar 2009 11:29:54 +0000 Subject: [fedora-virt] Accessing USB pen from virtual server Message-ID: <49C37E32.2090204@mistral.co.uk> My laptop uses Fedora 10. How can I access a USB pen from a virtual server within the machine? Thanks, Brendan From pasik at iki.fi Sun Mar 22 11:54:32 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Mar 2009 13:54:32 +0200 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels In-Reply-To: <49C0B8BC.1050301@redhat.com> References: <49C0B8BC.1050301@redhat.com> Message-ID: <20090322115432.GX15052@edu.joroinen.fi> On Wed, Mar 18, 2009 at 10:02:52AM +0100, Gerd Hoffmann wrote: > M A Young wrote: > > (with nomodeset I get no text characters during > > boot - only a cursor that moves as invisible characters are presumably > > printed to the screen > > known issue with vga text mode (32bit only, 64bit works ok). vga window > at 0xc0000 isn't mapped correctly. Workaround: drive the card in gfx > mode. Either kernel mode setting or vesafb (use something like > vga=gfx-1024x768x16 on the *xen* kernel command line). > So the reason for this issue is known.. any patches available? -- Pasi From m.a.young at durham.ac.uk Sun Mar 22 12:37:48 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sun, 22 Mar 2009 12:37:48 +0000 (GMT) Subject: [fedora-virt] Re: Dom0 kernels In-Reply-To: <49C0B8BC.1050301@redhat.com> References: <49C0B8BC.1050301@redhat.com> Message-ID: On Wed, 18 Mar 2009, Gerd Hoffmann wrote: > M A Young wrote: >> (with nomodeset I get no text characters during >> boot - only a cursor that moves as invisible characters are presumably >> printed to the screen > > known issue with vga text mode (32bit only, 64bit works ok). vga window > at 0xc0000 isn't mapped correctly. Workaround: drive the card in gfx > mode. Either kernel mode setting or vesafb (use something like > vga=gfx-1024x768x16 on the *xen* kernel command line). Unfortunately, both the kernel mode setting and using vesafb cause the X session to crash on that particular machine. So it is useful to know, but not that helpful in this particular case. Michael Young From dlbewley at lib.ucdavis.edu Sun Mar 22 21:38:37 2009 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Sun, 22 Mar 2009 14:38:37 -0700 Subject: [fedora-virt] kvm and qemu merge feature for f11 Message-ID: <1237757917.18334.20.camel@seitan.home.bewley.net> This feature is not officially accepted, http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge but koji makes that seem to be a moot point. $ koji latest-pkg dist-rawhide kvm $ koji latest-pkg dist-rawhide qemu qemu-0.10-0.9.kvm20090310git.fc11 f11-beta glommer The most recent kvm build 84.3 http://koji.fedoraproject.org/koji/buildinfo?buildID=92557 says "don't do anything here and use qemu package." F11-alpha includes a kvm package. Is it likely for this merge to stick through the beta if not the final release? Or is this a temporary state that will reverted at some point? Just wondering if I should put it back in the release notes. From dlbewley at lib.ucdavis.edu Mon Mar 23 03:53:01 2009 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Sun, 22 Mar 2009 20:53:01 -0700 Subject: [fedora-virt] Accessing USB pen from virtual server In-Reply-To: <49C37E32.2090204@mistral.co.uk> References: <49C37E32.2090204@mistral.co.uk> Message-ID: <1237780381.18334.21.camel@seitan.home.bewley.net> On Fri, 2009-03-20 at 11:29 +0000, Brendan Whelan wrote: > My laptop uses Fedora 10. How can I access a USB pen from a virtual > server within the machine? Thanks, Brendan Try this http://www.redhat.com/archives/et-mgmt-tools/2009-February/msg00063.html From markmc at redhat.com Mon Mar 23 08:12:22 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Mon, 23 Mar 2009 08:12:22 +0000 Subject: [fedora-virt] kvm and qemu merge feature for f11 In-Reply-To: <1237757917.18334.20.camel@seitan.home.bewley.net> References: <1237757917.18334.20.camel@seitan.home.bewley.net> Message-ID: <1237795942.3711.9.camel@blaa> On Sun, 2009-03-22 at 14:38 -0700, Dale Bewley wrote: > This feature is not officially accepted, > http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge > but koji makes that seem to be a moot point. > > $ koji latest-pkg dist-rawhide kvm > > $ koji latest-pkg dist-rawhide qemu > qemu-0.10-0.9.kvm20090310git.fc11 f11-beta glommer > > The most recent kvm build 84.3 > http://koji.fedoraproject.org/koji/buildinfo?buildID=92557 > says "don't do anything here and use qemu package." > > F11-alpha includes a kvm package. Is it likely for this merge to stick > through the beta if not the final release? Or is this a temporary state > that will reverted at some point? It's here to stay. I'm not sure why the feature page stalled. We should mark the page as 100% complete, change the category to FeatureReadyForWrangler and ask FESCo to approve it as an exception. Cheers, Mark. From kraxel at redhat.com Mon Mar 23 08:23:12 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Mon, 23 Mar 2009 09:23:12 +0100 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels In-Reply-To: <20090322115432.GX15052@edu.joroinen.fi> References: <49C0B8BC.1050301@redhat.com> <20090322115432.GX15052@edu.joroinen.fi> Message-ID: <49C746F0.3050704@redhat.com> Pasi K?rkk?inen wrote: > On Wed, Mar 18, 2009 at 10:02:52AM +0100, Gerd Hoffmann wrote: >> M A Young wrote: >>> (with nomodeset I get no text characters during >>> boot - only a cursor that moves as invisible characters are presumably >>> printed to the screen >> known issue with vga text mode (32bit only, 64bit works ok). vga window >> at 0xc0000 isn't mapped correctly. Workaround: drive the card in gfx >> mode. Either kernel mode setting or vesafb (use something like >> vga=gfx-1024x768x16 on the *xen* kernel command line). > > So the reason for this issue is known.. any patches available? According to jeremy someone works on unifying 32bit and 64bit page table initalization, which should nicely fix this issue as a side effect. cheers, Gerd From berrange at redhat.com Mon Mar 23 09:38:12 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 23 Mar 2009 09:38:12 +0000 Subject: [fedora-virt] kvm and qemu merge feature for f11 In-Reply-To: <1237757917.18334.20.camel@seitan.home.bewley.net> References: <1237757917.18334.20.camel@seitan.home.bewley.net> Message-ID: <20090323093812.GD10388@redhat.com> On Sun, Mar 22, 2009 at 02:38:37PM -0700, Dale Bewley wrote: > This feature is not officially accepted, > http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge > but koji makes that seem to be a moot point. > > $ koji latest-pkg dist-rawhide kvm > > $ koji latest-pkg dist-rawhide qemu > qemu-0.10-0.9.kvm20090310git.fc11 f11-beta glommer > > The most recent kvm build 84.3 > http://koji.fedoraproject.org/koji/buildinfo?buildID=92557 > says "don't do anything here and use qemu package." > > F11-alpha includes a kvm package. Is it likely for this merge to stick > through the beta if not the final release? Or is this a temporary state > that will reverted at some point? Regardless of FESCO "approval", the feature is complete - F11 will ship with a unified qemu+kvm rpm, just called 'qemu'. > Just wondering if I should put it back in the release notes. Yes, sounds reasonable Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From pasik at iki.fi Mon Mar 23 20:45:06 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 23 Mar 2009 22:45:06 +0200 Subject: [Fedora-xen] Re: [fedora-virt] virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10 In-Reply-To: <20090311213900.GL15052@edu.joroinen.fi> References: <20090307185223.GO15052@edu.joroinen.fi> <49B2CAF4.2080107@redhat.com> <20090307193725.GP15052@edu.joroinen.fi> <20090308192310.GT15052@edu.joroinen.fi> <20090309103929.GO4578@redhat.com> <20090309122404.GX15052@edu.joroinen.fi> <20090311175610.GH15052@edu.joroinen.fi> <20090311175901.GO23995@redhat.com> <20090311200503.GI15052@edu.joroinen.fi> <20090311213900.GL15052@edu.joroinen.fi> Message-ID: <20090323204506.GJ5528@edu.joroinen.fi> On Wed, Mar 11, 2009 at 11:39:00PM +0200, Pasi K?rkk?inen wrote: > On Wed, Mar 11, 2009 at 10:05:03PM +0200, Pasi K?rkk?inen wrote: > > On Wed, Mar 11, 2009 at 05:59:01PM +0000, Daniel P. Berrange wrote: > > > On Wed, Mar 11, 2009 at 07:56:10PM +0200, Pasi K?rkk?inen wrote: > > > > But Fedora 10 domU installation still fails: > > > > > > > > [root at dom0test ~]# virt-install -n vm01 -r 512 --vcpus=1 -f /dev/vg00/vm01 --vnc -p -l > > > > "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/10/Fedora/i386/os" > > > > > > > > > > > > Starting install... > > > > Retrieving file .treeinfo... | 1.1 kB 00:00 > > > > Retrieving file vmlinuz-PAE... | 2.5 MB 00:01 > > > > Retrieving file initrd-PAE.img... | 16 MB 00:10 > > > > XML description for failed to build sexpr is not well formed or invalid > > > > Domain installation may not have been > > > > successful. If it was, you can restart your domain > > > > by running 'virsh start vm01'; otherwise, please > > > > restart your installation. > > > > ERROR XML description for failed to build sexpr is not well formed or invalid > > > > > > > > > Now this one sounds like a genuine libvirt or virt-install bug ! > > > > > > Can you re-run with --debug, and file a BZ with the information so we can > > > track it formally. > > > > > > > Ok. Will do. > > > > Now done: https://bugzilla.redhat.com/show_bug.cgi?id=489799 > Ok, this "XML description for failed to build sexpr" error was caused by libvirtd not being started before running virt-install. Now I got further but still some problems.. I'll open another thread about that :) Thanks for the help! -- Pasi From pasik at iki.fi Tue Mar 24 19:25:02 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 24 Mar 2009 21:25:02 +0200 Subject: [fedora-virt] Success with Fedora 10 Xen pv_ops 2.6.29-rc8 dom0 Message-ID: <20090324192502.GS5528@edu.joroinen.fi> Hello! I've used a lot of time trying to get my custom Xen pv_ops dom0 kernel working with virt-install and/or virt-manager on Fedora 10, and now it seems I got things working. If you want to play with this you need: 1) New enough pv_ops dom0 kernel (2.6.29-rc8 or newer) so it has /sys/hypervisor support included - Compile with CONFIG_HIGHPTE=n since it seems to be broken still 2) libvirt 0.6.1 and related packages from Fedora 10 updates-testing In addition to those I'm using Xen 3.3.1-9 packages from rawhide/F11 rebuilt for F10. With the older Fedora 10 libvirt packages libvirtd was crashing often for me, and I had some other issues with virt-install console window not opening but stalling etc.. Today I was able to run the following on Fedora 10 32bit PAE pv_ops dom0: - CentOS 5.3 32bit PAE PV domU - Fedora 10 32bit PAE PV domU - Use virt-install to install Fedora 10 32bit PAE PV domU (using custom kickstart to force PAE kernel installation to avoid the anaconda BUG which installs wrong non-PAE kernel as a default). Fedora 11 (rawhide) installation most probably works too. I'm using LVM volumes for domU disks (tap:aio is not yet supported by pv_ops dom0 kernel). Network seems to work after running "ifdown eth0 && ifup eth0" on the guest.. dunno why that's needed. That's something to figure out later:) Graphical domU console works with virt-viewer and virt-install during installation. Issues: - virt-manager complains about default network (virbr0) being inactive and asks if I want to start it. If I click Yes, then I get error: "libvirtError: cannot create bridge 'virbr0': File exists" virbr0 works just fine with virt-install. So dunno what's the problem with that.. have to look into that later. Thanks to everyone involved for helping me with this! -- Pasi From berrange at redhat.com Tue Mar 24 19:28:46 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 24 Mar 2009 19:28:46 +0000 Subject: [fedora-virt] Success with Fedora 10 Xen pv_ops 2.6.29-rc8 dom0 In-Reply-To: <20090324192502.GS5528@edu.joroinen.fi> References: <20090324192502.GS5528@edu.joroinen.fi> Message-ID: <20090324192846.GN19446@redhat.com> On Tue, Mar 24, 2009 at 09:25:02PM +0200, Pasi K?rkk?inen wrote: > Hello! > > I've used a lot of time trying to get my custom Xen pv_ops dom0 kernel working with > virt-install and/or virt-manager on Fedora 10, and now it seems I got things > working. > > If you want to play with this you need: > > 1) New enough pv_ops dom0 kernel (2.6.29-rc8 or newer) so it has /sys/hypervisor support included > - Compile with CONFIG_HIGHPTE=n since it seems to be broken still > 2) libvirt 0.6.1 and related packages from Fedora 10 updates-testing > > In addition to those I'm using Xen 3.3.1-9 packages from rawhide/F11 rebuilt for F10. > > With the older Fedora 10 libvirt packages libvirtd was crashing often for me, and > I had some other issues with virt-install console window not opening but stalling etc.. > > Today I was able to run the following on Fedora 10 32bit PAE pv_ops dom0: > > - CentOS 5.3 32bit PAE PV domU > - Fedora 10 32bit PAE PV domU > - Use virt-install to install Fedora 10 32bit PAE PV domU (using custom kickstart > to force PAE kernel installation to avoid the anaconda BUG which installs > wrong non-PAE kernel as a default). > > Fedora 11 (rawhide) installation most probably works too. FYI, I've just testing i686 and x86_64 Fedora 11 guest installs on a RHEL5 Xen host and they both work flawlessly out of the box - including a sane mouse pointer running in absolute, so no dual-cursor problems, and installing correect PAE kernels > Issues: > - virt-manager complains about default network (virbr0) being inactive and > asks if I want to start it. If I click Yes, then I get error: "libvirtError: cannot create bridge 'virbr0': File exists" Possibly due to old 0.5.x libvirtd having crashed & left the network running. Since you've now upgraded to 0.6.1 libvirt, it is capable of noticing that the network is already runniing upon startup. So future crashes will recover better. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From pasik at iki.fi Tue Mar 24 20:06:15 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 24 Mar 2009 22:06:15 +0200 Subject: [fedora-virt] Success with Fedora 10 Xen pv_ops 2.6.29-rc8 dom0 In-Reply-To: <20090324192846.GN19446@redhat.com> References: <20090324192502.GS5528@edu.joroinen.fi> <20090324192846.GN19446@redhat.com> Message-ID: <20090324200615.GT5528@edu.joroinen.fi> On Tue, Mar 24, 2009 at 07:28:46PM +0000, Daniel P. Berrange wrote: > On Tue, Mar 24, 2009 at 09:25:02PM +0200, Pasi K?rkk?inen wrote: > > Hello! > > > > I've used a lot of time trying to get my custom Xen pv_ops dom0 kernel working with > > virt-install and/or virt-manager on Fedora 10, and now it seems I got things > > working. > > > > If you want to play with this you need: > > > > 1) New enough pv_ops dom0 kernel (2.6.29-rc8 or newer) so it has /sys/hypervisor support included > > - Compile with CONFIG_HIGHPTE=n since it seems to be broken still > > 2) libvirt 0.6.1 and related packages from Fedora 10 updates-testing > > > > In addition to those I'm using Xen 3.3.1-9 packages from rawhide/F11 rebuilt for F10. > > > > With the older Fedora 10 libvirt packages libvirtd was crashing often for me, and > > I had some other issues with virt-install console window not opening but stalling etc.. > > > > Today I was able to run the following on Fedora 10 32bit PAE pv_ops dom0: > > > > - CentOS 5.3 32bit PAE PV domU > > - Fedora 10 32bit PAE PV domU > > - Use virt-install to install Fedora 10 32bit PAE PV domU (using custom kickstart > > to force PAE kernel installation to avoid the anaconda BUG which installs > > wrong non-PAE kernel as a default). > > > > Fedora 11 (rawhide) installation most probably works too. > > FYI, I've just testing i686 and x86_64 Fedora 11 guest installs on a > RHEL5 Xen host and they both work flawlessly out of the box - including > a sane mouse pointer running in absolute, so no dual-cursor problems, > and installing correect PAE kernels > And I just tested installing CentOS 5.3 PV domU with virt-manager on F10 dom0, and it was successful aswell! > > Issues: > > - virt-manager complains about default network (virbr0) being inactive and > > asks if I want to start it. If I click Yes, then I get error: "libvirtError: cannot create bridge 'virbr0': File exists" > > Possibly due to old 0.5.x libvirtd having crashed & left the network running. > Since you've now upgraded to 0.6.1 libvirt, it is capable of noticing that > the network is already runniing upon startup. So future crashes will recover > better. > Yeah, rebooting the box fixed the problem and virt-manager works now. Thanks! -- Pasi From markmc at redhat.com Thu Mar 26 16:41:53 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 26 Mar 2009 16:41:53 +0000 Subject: [fedora-virt] Fedora virt status report Message-ID: <1238085713.3695.50.camel@blaa> This is the first Fedora virt status report in a month now, and it's been a heck of busy month! - The F11 feature/beta freeze - Scrambling to complete the F11 virt features - Legendary work getting the qemu/kvm package merge in shape - A re-designed virt-manager UI - Various upstream releases - Progress on Xen Dom0 - A massive amount of bugzilla activity We're not there yet, though. The final important item on the F11 schedule is: 2009-04-14 Final freeze (20 days) There's a huge pile of bug-fixing and polish work to do in that time. If you're looking to help out, there's no better place to start than the F11VirtBlocker/F11VirtTarget tracker bugs: https://bugzilla.redhat.com/showdependencytree.cgi?id=F11VirtBlocker&hide_resolved=1 https://bugzilla.redhat.com/showdependencytree.cgi?id=F11VirtTarget&hide_resolved=1 Fedora 11 Beta ============== The Beta was due to be released at this point, but a 7 day slip was announced last week: http://www.redhat.com/archives/fedora-devel-list/2009-March/msg01163.html Jesse isn't pointing fingers, but I am ... it's anaconda's fault :-) It looks like today's rawhide may be the final Beta compose, as the blocker list is looking much healthier: https://bugzilla.redhat.com/showdependencytree.cgi?id=F11Beta&hide_resolved=1 Fedora Weekly News ================== With so much going on in the Fedora Virtualization space in the last number of weeks, it's great to see Dale Bewley continuing to contribute excellent virt sections to FWN: https://fedoraproject.org/wiki/FWN/Issue168#Virtualization https://fedoraproject.org/wiki/FWN/Issue167#Virtualization https://fedoraproject.org/wiki/FWN/Issue166#Virtualization https://fedoraproject.org/wiki/FWN/Issue165#Virtualization F11 Virt Features ================= Chris Lalance summarised a recent FECSo meeting where four virt features were discussed: http://www.redhat.com/archives/fedora-virt/2009-February/msg00097.html The upshot is that the Shared Network Interface is postponed until Fedora 12. Also, the KVM and QEMU Merge feature fell off the radar briefly, but will hopefully be approved as an exception by FESCo this week. So, the final list of F11 virt features is: https://fedoraproject.org/wiki/Category:F11_Virt_Features * KVM PCI Device Assignment * KVM and QEMU merge * SVirt Mandatory Access Control * VirtImprovedConsole * VirtVNCAuth Planning for Fedora 12 has already begun, and the current set of features proposed is: https://fedoraproject.org/wiki/Category:F12_Virt_Features * Shared Network Interface * VirtStorageManagement * XenPvopsDom0 KVM PCI Device Assignment ========================= This feature is now complete for F11: https://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment Just in time for feature freeze, the libvirt node device attach, re-attach and reset APIs were added (in 0.6.1). Cole also added the --host-device parameter to virt-install and host device support to virt-manager. Also, /sys/bus/pci/devices/pci-stub/remove_id (used by libvirt) was recently backported from 2.6.30 to rawhide: https://bugzilla.redhat.com/487103 http://www.redhat.com/archives/fedora-kernel-list/2009-March/msg00021.html KVM and QEMU Merge ================== Glauber continued his awesome work on merging the qemu and kvm packages. https://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge -- QEMU 0.10 -- Upstream QEMU did a 0.10.0 release, followed closely by a 0.10.1 release: http://www.archivum.info/qemu-devel at nongnu.org/2009-03/msg00188.html http://www.archivum.info/qemu-devel at nongnu.org/2009-03/msg01067.html This release will form the basis of the Fedora 11 version of QEMU. However, in order for that to happen, the KVM upstream maintainers need to release a version of kvm-userspace which is based on the qemu-0.10.x series. This is planned in the near future. In the meantime, rawhide will ship snapshots of latest kvm-userspace.git. QEMU upstream plan to do regular releases every three months. There will also be releases from the current stable branch (e.g. 0.10.x for now) as needed. This is great news for Fedora, as it means we can track QEMU development in Fedora while still being able to keep QEMU stable in Fedora releases. -- BIOS Packages -- Work continued on the gnarly issue of build BIOS images for QEMU. The vgabios and openbios packages were approved: https://bugzilla.redhat.com/485418 Review Request: vgabios - vga option rom for bochs/qemu https://bugzilla.redhat.com/485420 Review Request: openbios - Open Source implementation of IEEE 1275-1994 Also, the bochs-bios package was approved, but with koji's ability to build noarch sub-packages, it was no longer needed: https://bugzilla.redhat.com/485417 Review Request: bochs-bios - bios implementation from the bochs project Later, it was realized that a KVM specific version of bochs was needed, so Glauber added that to the bochs package: https://bugzilla.redhat.com/488759 Cannot run F10/F11 i386 guests without disabling ACPI https://bugzilla.redhat.com/490203 doesn't boot RHEL 5 kernel -- The Merge -- Glauber committed his merged package to rawhide and various folks jumped in helping with testing and cleaning up various packaging issues: https://bugzilla.redhat.com/488418 kvm : Conflicts with other packages https://bugzilla.redhat.com/488249 /usr/bin/qemu-nbd: conflict with qemu-common-1.0-0.4.svn6666.fc11.x86_64 https://bugzilla.redhat.com/489432 problems with qemu scripts https://bugzilla.redhat.com/490190 bochs-bios >= 2.3.8-0.5 is needed by qemu-system-x86-2:0.10-0.9.kvm20090310git.fc11.x86_64 https://bugzilla.redhat.com/488350 New qemu package breaks kvm virtualization https://bugzilla.redhat.com/489750 qemu missing some files for kvm support https://bugzilla.redhat.com/489710 qemu-kvm has wrong directory for keymaps The version included in the F11 Beta release seems in really good shape considering how significant a change this was. -- GCC Bug -- Another issue that arose was that latest gcc is breaking plain QEMU. A patch has been proposed upstream, but it's not in rawhide yet: https://bugzilla.redhat.com/490512 segfault in stw_kernel when qemu is run https://bugzilla.redhat.com/490509 GCC register allocation wrongly using ebp sVirt ===== The sVirt patch set was added to libvirt-0.6.1 and is in the Fedora 11 Beta release: https://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control Some issues remain, but things are looking in pretty good shape, all things considered. Some of the related issues include: https://bugzilla.redhat.com/491052 selinux: virt-manager downloaded kernel/initrd cannot be accessed by KVM guest Nasty issue where, because virt-manager no longer runs as root, kernel and initrd images are readable by qemu because of their SELinux label. Dan Walsh committed some policy changes to fix this, but virt-manager will need to call restorecon on downloaded images. Dan also suggested a patch from virt-manager using this interesting bit of SELinux functionality: $> python >>> import selinux >>> selinux.selinux_virtual_image_context_path() '/etc/selinux/targeted/contexts/virtual_image_context' $> cat /etc/selinux/targeted/contexts/virtual_image_context system_u:object_r:virt_image_t:s0 https://bugzilla.redhat.com/491245 SELinux prevented qemu-kvm from reading an LVM logical volume https://bugzilla.redhat.com/474182 LVs created in an existing VG have wrong SELinux label Issues around the appropriate labelling of logical volumes used for guest installs. Should work better in rawhide. https://bugzilla.redhat.com/491176 Sound card breaks new and existing vm's A pulseaudio error caused by sVirt restrictions on guests was causing VMs with sound hardware to fail to start. Fixed in libvirt by disabling sound hardware if sVirt is enabled. https://bugzilla.redhat.com/484555 AVC denied errors when starting KVM guest Another issue cropped up with the selinux changes for libvirt 0.6.0. Fix is in F10 now. Improved Graphical Console ========================== Dan Berrange added a feature page describing the changes made to have the graphical console be 1024x768 by default and use a USB tablet in absolute mode rather than a PS2 mouse. https://fedoraproject.org/wiki/Features/VirtImprovedConsole The relevant bugs for each of the improvements are listed on the wiki page. These changes will make a huge difference to the user experience with Fedora virtualization tools. No longer a crappy screen resolution and no longer schizophrenic mouse behaviour. One related problem that Dan had to fix was a particularly nasty 'invisible wall' bug in gtk-vnc to do with pointer grabs and relative mode: https://bugzilla.redhat.com/454938 Cursor Movement is Constrained A particularly nasty 'invisible wall' bug in gtk-vnc to do with pointer grabs and relative mode. VNC Authentication ================== Dan Berrange got his VNC SASL authentication patches for QEMU and backported them to rawhide. Testing is welcome for this feature, but you'll need to bug Dan about filling in the "How To Test" section of the feature page first :-) https://fedoraproject.org/wiki/Features/VirtVNCAuth One problem which has just become apparent is that, in rawhide currently, we are shipping a snapshot of kvm-userspace.git which includes the SASL patches. However, when upstream KVM release a version of kvm-userspace based on qemu-0.10.x, that will not include the SASL patches. This means the patches will have to be backported again. Three cheers for confusion! New virtinst and virt-manager Releases ====================================== Cole released a new version of virtinst: http://www.redhat.com/archives/fedora-virt/2009-March/msg00002.html This release includes: - New virt-clone option --original-xml, allows cloning a guest from an xml file, rather than require an existing, defined guest. - New virt-install option --import, allows creating a guest from an existing disk image, bypassing any OS install phase. - New virt-install option --host-device, for connecting a physical host device to the guest. - Allow specifying 'cache' value via virt-install's --disk options (Ben Kochie) - New virt-install option --nonetworks (John Levon) - Lots of backend cleanups and documentation improvements. and also a new virt-manager release: http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00058.html This release includes: - Redesigned 'New Virtual Machine' wizard (Jeremy Perry, Tim Allen, Cole Robinson) - Option to remove storage when deleting a virtual machine. - File browser for libvirt storage pools and volumes, for use when attaching storage to a new or existing guest. - Physical device assignment (PCI, USB) for existing virtual machines. - Bug fixes and minor improvements. Both releases resolve many Fedora bugs and add new and interesting features, but by far the most user-visible change is the re-designed 'New Virtual Machine' wizard. More details Cole's blog: http://blog.wikichoon.com/2009/02/virt-manager-in-fedora-11-new-vm-wizard.html I think everyone will agree that this is a huge improvement. I particularily like the "detect distro" feature where we now make every effort to try and figure out what OS is being installed rather than require the user to tell us. libvirt ======= libvirt-0.6.1 was released: http://www.redhat.com/archives/libvir-list/2009-March/msg00144.html + New features: - new APIs for Node device detach reattach and reset (Mark McLoughlin) - sVirt mandatory access control support (James Morris and Dan Walsh) ... This is available in rawhide, the F11 Beta and F10 updates-testing. Note, however, that rawhide and F11Beta has quite a number of fixes not yet in updates-testing. Tricky Time Troubles ==================== Hans De Goede tracked down a nasty problem with anaconda running under KVM: https://bugzilla.redhat.com/show_bug.cgi?id=491529 Unable to mount filesystem: device /dev/sda1 does not exist The problem turned out to be that anaconda was sleeping for a single second to give the kernel time to reload the partition table after committing changes to a disk. However, one cannot predict predict how many CPU cycles a virtual machine will execute in a fixed about of real time. If the host or other guests are busy, then the guest may be starved of CPU for a time. In this case, the kernel was sometimes not getting enough CPU cycles in the time that anaconda was sleeping and so the partition table wasn't reloaded. The fix was to use udev_settle so that we could know for certain when the devices nodes were visible. Xen Dom0 ======== Michael Young continued posting more Dom0 kernel builds. Gerd has helped out by builing new versions of the xen userspace package to work with these kernels. Upstream recently saw some lively debate on whether the patches should be include at all: http://lwn.net/Articles/321696/ http://article.gmane.org/gmane.comp.emulators.xen.devel/62079 It's hard to predict these things, but it seems likely the patches will end up being accepted. Pasi K?rkk?inen has spent a good deal of time working through various issues with getting a Dom0 install working. One problem identified is that /sys/hypervisor was missing upstream prompting Jeremy Fitzhardinge added a patch to enable that. Pasi also filed some bugs arising from his testing: https://bugzilla.redhat.com/489799 libvirt "missing source" error message overwritten by "failed to build sexpr" error Basically, libvirt is giving a useless error message when the bridge name for a given network can't be found. https://bugzilla.redhat.com/show_bug.cgi?id=491766 libvirtd fails to start if pid file exists but init script still says it started OK libvirt's handling of its PID file isn't quite correct; nasty little issue. Pasi later reported further success: http://www.redhat.com/archives/fedora-virt/2009-March/msg00065.html Today I was able to run the following on Fedora 10 32bit PAE pv_ops dom0: - CentOS 5.3 32bit PAE PV domU - Fedora 10 32bit PAE PV domU - Use virt-install to install Fedora 10 32bit PAE PV domU Bugs ==== DOOM-O-METER: 192 one month ago, 185 now. Not bad! The summary of bugzilla activity is seriously long, so I'll try and categorize things a little: -- Installer -- https://bugzilla.redhat.com/470905 anaconda installs the wrong kernel for i686 xen guests danpb confirms this is now fixed because anaconda will always install PAE kernels on systems which support it. https://bugzilla.redhat.com/491112 QEMU disks show up in anaconda as UNKNOWN Parted needed some smarts to return an appropriate model string for virtio disks. Joel Granados came up with a patch to look in /proc/devices for "virtblk". https://bugzilla.redhat.com/492082 anaconda "unitialized drive" warning is a little too terrifying When virtinst creates a blank disk, anaconda throws up a slightly terrifying warning - "YOU WILL LOSE ALL DATA". We should be able to make the user experience a tad better here. https://bugzilla.redhat.com/491132 installation of guest fails with encryption Looks like yet another anaconda storage-rewrite bug. https://bugzilla.redhat.com/484721 Anaconda eats CPU A report that anaconda was stuck in a loop in KVM. Turned out to be a simple "poll() on invalid fd" bug in anaconda itself. -- QEMU -- https://bugzilla.redhat.com/492075 qemu package missing debuginfo for qemu-img Glauber has a fix which he submitted upstream. Turns out the upstream makefile was using "install -s", causing the binary to be stripped before find-debuginfo got to it. https://bugzilla.redhat.com/491943 qemu-img crashes creating 5TB qcow2 file https://bugzilla.redhat.com/491981 Integer wraparound creating a large disk image in VPC format Dan Berrange reports some issues with qemu's handling of very large disks. https://bugzilla.redhat.com/454251 kvm: Build qemu with $RPM_OPT_FLAGS Glauber nicely fixed this long-standing issue. https://bugzilla.redhat.com/457979 Update QEMU to use gPXE roms for iSCSI boot support https://bugzilla.redhat.com/492181 Review Request: gpxe - A network boot loader Discussion around moving to gPXE option ROMs instead of etherboot so as to get iSCSI initiator support during PXE boot. The blocking issue here is modifying QEMU to allow more space for the large gPXE ROM images. https://bugzilla.redhat.com/484364 block-rw-range-check.patch breaks qcow2 https://bugzilla.redhat.com/485148 "Cannot open disk image" when using qcow1 Our only significant not-upstream qemu patch has finally been merged (and fixed) upstream. Yay! https://bugzilla.redhat.com/491582 Fedora11 qemu-kvm installation using qcow2 is not recognizing the hard drive Another bug filed by IBM folks testing the alpha. Almost certainly the same as the qcow2 issue caused by block-rw-range-check.patch. https://bugzilla.redhat.com/489804 no working networking in guests with qemu-kvm A transient networking issue reported by Jeremy Katz. Seems to have gone away of its own accord. https://bugzilla.redhat.com/491381 Can't use AES encryption in qcow2 F10 qemu seems to lock up with encrypted qcow2 disks before asking for the password. It works fine in rawhide - so long as you think of switching to the qemu monitor with Ctrl-Alt-2. https://bugzilla.redhat.com/487118 Need to add subsystem vendor ID for kvm/qemu cirrus card https://bugzilla.redhat.com/251264 xorg should use 1024x768 for kvm/qemu cirrus card Now with an F11 host and an F11 guest, xorg's cirrus driver will default to 1024x768 instead of 800x600. Woo! https://bugzilla.redhat.com/487720 qemu-kvm segfaults on startup in SDL_memcpyMMX/SSE Eduardo tracked down and fixed this nasty crasher in libSDL. https://bugzilla.redhat.com/469859 F10 kvm: network stall with qemu rtl8139 NIC emulation People continue to have issues with using RHEL5 and QEMU's rtl8139 emulation. https://bugzilla.redhat.com/478976 qemu-kvm not working with evdev giving wrong key mappings Finally fixed, it seems. Not clear on the details. https://bugzilla.redhat.com/481619 Adding ac97-module (from qemu-repo) ac97 emulation is enabled by default since kvm-84. -- KVM -- https://bugzilla.redhat.com/475598 recent fedora guests in KVM are unstable with kvm-clock and !constant_tsc This was fixed a while back by an F10 kernel update, but there was some confusion. It sounds like some people may be experiencing other KVM hangs which are unrelated to this issue. https://bugzilla.redhat.com/490479 error when hot-unplugging a file-backed virtio disk Device 'virtio2' does not have a release() function, it is broken and must be fixed. Reported against F10, but has since been fixed upstream/rawhide. https://bugzilla.redhat.com/490266 Network transfer from qemu guest machine stalls A reported of a virtio_net related hang. May be similar to one that was reported on kvm at vger previously. https://bugzilla.redhat.com/491625 Unable to run RHEL-5 Xen within KVM guest Dan Berrange reports that F11 has regressed in its ability to be able to run the Xen hypervisor inside a guest. It looks to be related to KVM's in-kernel IOAPIC emulation. https://bugzilla.redhat.com/491631 Fedora11 Kernel BUG while installing kvm guest os using qcow2 Some IBM folks testing the F11 Alpha hit this oops during installs. We had previously come to the conclusion that this was caused by the pvmmu bug reported in #480822. https://bugzilla.redhat.com/483648 kvm: Oops while installing rawhide/x86_64 guest on F-10/x86_64 host (__shrink_dcache_sb() https://bugzilla.redhat.com/455097 2.6.26-0.124.rc9.git5.fc10.x86_64 oops in new_slab in kvm guest More dups of the the pvmmu issue that Marcelo previously fixed (rh #480822) https://bugzilla.redhat.com/487444 windows server 2003 x64 guest does not poweroff https://bugzilla.redhat.com/484166 QEmu uses 100% of two assigned cores for XP guest clalance reports that this issue seems fixed in F11. https://bugzilla.redhat.com/436881 qemu-kvm: samba/smb causes "bad page state" and/or freeze F9 vintage KVM oops that seems to have gone away in F11. https://bugzilla.redhat.com/437028 KVM: Intel/VMX: host kernel should support DEBUGCTLMSR=0x1d9 KVM does not emulate last-branch-recording which causes PTRACE_SINGLEBLOCK. Looks like the option is either to implement LBR virtualization or have the guest kernel detect that it is running on KVM and that the MSR isn't supported. https://bugzilla.redhat.com/476521 Coredump on start when no kvm modules is loaded Looks like a bug which was fixed in kvm-80. -- libvirt -- https://bugzilla.redhat.com/491913 adding a new cd-rom device to a KVM guest fails in libvirt Looks like a bug with cd-rom hotplug in libvirt. https://bugzilla.redhat.com/477955 Sound under KVM requires exclusive access to the sound device Dan Berrange explains why sound has essentially been disabled for now in KVM guests. https://bugzilla.redhat.com/490191 Ownership of serial console allow only root access If you configure a serial console for a kvm guest in libvirt, the console is only accessible by root ... even if it was a user other than root that started it. https://bugzilla.redhat.com/489946 libvirt does not do safe replacement of guest/storage pool/network config files When libvirt writes configuration files to disk, it does not use the recommended write-to-tmpfile/flush/sync/close/rename method to ensure data safety. https://bugzilla.redhat.com/484552 libnuma: Warning: /sys not mounted or no numa system. Assuming one node: No such file or directory This annoying warning which I thought had long ago been removed had only been removed on F10, not rawhide. https://bugzilla.redhat.com/489481 Useless "domain didn't show up" error when starting a guest with too much RAM It seems that if you assign too much RAM to a QEMU guest, libvirt gives a very unhelpful error message. https://bugzilla.redhat.com/444047 F9 iozone w/ direct I/O performing higher than the raw device Resolved by the option to set the disk caching mode in libvirt. -- virt tools -- https://bugzilla.redhat.com/489885 virt-manager (libvirt?) 0.6.1 fails to manage RHEL-5.3 machines virt-manager was failing to properly handle old-style when remotely connecting to a RHEL5 Xen host. Fix in the latest version of virt-manager. https://bugzilla.redhat.com/491755 virt-viewer jumps workspaces on guest restart with virt-install Because virt-viewer is run multiple times by virt-install, it can mean that the window moves unexpectedly between workspaces. https://bugzilla.redhat.com/491683 virt-viewer no longer auto adjusts to guest screen size Sounds like we have a screen resizing issue during installs with rawhide virt-manager/virt-viewer. https://bugzilla.redhat.com/490466 virt-manager displays incorrect number of vcpus Strange virt-manager bug artificially limiting the number of vcpus allowed. May turn out to be a gtk bug? https://bugzilla.redhat.com/490207 Wrong Ok/Cancel button order in virt-manager cd-rom connect dialog Another minor virt-manager bug; easy fix. https://bugzilla.redhat.com/488878 GConf error when starting virt-manager-0.6.1-1.fc10 after "su" (works with "su -") A weird virt-manager startup failure turns out to be a known bug with GConf. https://bugzilla.redhat.com/show_bug.cgi?id=489344 ConsoleKit doesn't know about vncserver sessions Because virt-manager now uses PolicyKit instead of console helper, and because ConsoleKit doesn't see vncserver sessions, virt-manager only opens read-only libvirt connections when running under vncserver. https://bugzilla.redhat.com/487190 virt-manager has hardcoded Requires: PolicyKit-gnome Cole fixed in rawhide to require PolicyKit-authentication-agent. https://bugzilla.redhat.com/487735 virt-manager/virtinst should not set a keymap unless one is explicitly requested Sounds like keyboard mappings will work correctly because of gtk-vnc scancode extension, so long as virtinst doesn't explicitly set a keymap. -- Xen -- https://bugzilla.redhat.com/487324 kernel/lockdep.c warning in xen guest boot dmesg Fixed upstream in 2.6.29-rc6-git5 -- Misc -- https://bugzilla.redhat.com/479760 grub-install doesn't support virtio_blk devices What looks like a simple patch to grub-install to make it recognise /dev/vd* From berrange at redhat.com Fri Mar 27 10:30:50 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 27 Mar 2009 10:30:50 +0000 Subject: [fedora-virt] Fedora virt status report In-Reply-To: <1238085713.3695.50.camel@blaa> References: <1238085713.3695.50.camel@blaa> Message-ID: <20090327103050.GD6913@redhat.com> On Thu, Mar 26, 2009 at 04:41:53PM +0000, Mark McLoughlin wrote: > -- GCC Bug -- > > Another issue that arose was that latest gcc is breaking plain QEMU. A > patch has been proposed upstream, but it's not in rawhide yet: > > https://bugzilla.redhat.com/490512 > segfault in stw_kernel when qemu is run > https://bugzilla.redhat.com/490509 > GCC register allocation wrongly using ebp IMHO, we should apply the patch to Fedora regardless of whether upstream think its the right long term approach. We need to have i386 qemu binary functional for release, even if that means carrying a temporary hack of some kind. > VNC Authentication > ================== > > Dan Berrange got his VNC SASL authentication patches for QEMU and > backported them to rawhide. > > Testing is welcome for this feature, but you'll need to bug Dan about > filling in the "How To Test" section of the feature page first :-) I wrote extensive docs about configuration in the QEMU docs. Unfortunately they don't publish the docs from 'tip' SVN online, but they're in the RPM we build /usr/share/doc/qemu-0.10/qemu-doc.html > https://fedoraproject.org/wiki/Features/VirtVNCAuth > > One problem which has just become apparent is that, in rawhide > currently, we are shipping a snapshot of kvm-userspace.git which > includes the SASL patches. However, when upstream KVM release a > version of kvm-userspace based on qemu-0.10.x, that will not include > the SASL patches. This means the patches will have to be backported > again. Three cheers for confusion! That isn't hard. The patches were merged in upstream QEMU 'tip' immediately after 0.10.x branched, so they will trivially apply to 0.10.x branch. I'll be surprised if there's any failed patch hunks. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From m.a.young at durham.ac.uk Sat Mar 28 15:14:37 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sat, 28 Mar 2009 15:14:37 +0000 (GMT) Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: Message-ID: On Sat, 28 Mar 2009, Frank Van Damme wrote: > Sorry, I don't understand this Koji thing. If I click through to the > dependant task for x86_64, then buildroot, then "built rpms", there > are no rpms. How to actually download the kernel rpm?? It looks like it isn't there any more. That might be because I have tried to build more recent packages (which failed). I will attempt another build shortly, and post the results if it works. Michael Young From ondrejj at salstar.sk Sat Mar 28 16:35:45 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Sat, 28 Mar 2009 17:35:45 +0100 Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: Message-ID: <20090328163545.GM31725@salstar.sk> On Sat, Mar 28, 2009 at 03:14:37PM +0000, M A Young wrote: > On Sat, 28 Mar 2009, Frank Van Damme wrote: > >> Sorry, I don't understand this Koji thing. If I click through to the >> dependant task for x86_64, then buildroot, then "built rpms", there >> are no rpms. How to actually download the kernel rpm?? > > It looks like it isn't there any more. That might be because I have tried > to build more recent packages (which failed). I will attempt another > build shortly, and post the results if it works. Can I ask you to create an yum repository with these packages? I think scratch builds are cleaned after some days, so moving these files into another server to an repository may be helpful. If you need some help (disk space, etc.), just tell me. SAL From m.a.young at durham.ac.uk Sat Mar 28 19:14:43 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sat, 28 Mar 2009 19:14:43 +0000 (GMT) Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: <20090328163545.GM31725@salstar.sk> References: <20090328163545.GM31725@salstar.sk> Message-ID: On Sat, 28 Mar 2009, Jan ONDREJ (SAL) wrote: > Can I ask you to create an yum repository with these packages? > I think scratch builds are cleaned after some days, so moving these files > into another server to an repository may be helpful. Okay I have created a mini repository at http://fedorapeople.org/~myoung/dom0/ . I haven't done so before because I wasn't sure how much use it will be, since rawhide kernels will in general be more recent than mine so yum won't fetch them, but if koji is going to delete files then it is probably worth it after all. The repository contains packages from the kernel 2.6.29-1.2.15.fc11 build http://koji.fedoraproject.org/koji/taskinfo?taskID=1263156 without the debuginfo packages which would take up too much space. Those are available from koji until it decides to delete them. Michael Young From ondrejj at salstar.sk Sat Mar 28 20:19:42 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Sat, 28 Mar 2009 21:19:42 +0100 Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> Message-ID: <20090328201942.GO31725@salstar.sk> On Sat, Mar 28, 2009 at 07:14:43PM +0000, M A Young wrote: > On Sat, 28 Mar 2009, Jan ONDREJ (SAL) wrote: > >> Can I ask you to create an yum repository with these packages? >> I think scratch builds are cleaned after some days, so moving these files >> into another server to an repository may be helpful. > > Okay I have created a mini repository at > http://fedorapeople.org/~myoung/dom0/ . I haven't done so before because > I wasn't sure how much use it will be, since rawhide kernels will in > general be more recent than mine so yum won't fetch them, but if koji is > going to delete files then it is probably worth it after all. Thanks. You can avoid replacing your kernel by renaming name of your package. You can name it kernel-dom0 (can't be named kernel-xen, because this package was obsoleted) or something similar. > The repository contains packages from the kernel 2.6.29-1.2.15.fc11 build > http://koji.fedoraproject.org/koji/taskinfo?taskID=1263156 without the > debuginfo packages which would take up too much space. Those are > available from koji until it decides to delete them. May be an f10 repository will be useful too. With all packages needed to run dom0 on Fedora 10. SAL From m.a.young at durham.ac.uk Sun Mar 29 18:34:06 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sun, 29 Mar 2009 19:34:06 +0100 (BST) Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> Message-ID: On Sat, 28 Mar 2009, M A Young wrote: > Okay I have created a mini repository at > http://fedorapeople.org/~myoung/dom0/ . I haven't done so before because I > wasn't sure how much use it will be, since rawhide kernels will in general be > more recent than mine so yum won't fetch them, but if koji is going to delete > files then it is probably worth it after all. It now contains packages from the kernel 2.6.29-1.2.16.fc11 build http://koji.fedoraproject.org/koji/taskinfo?taskID=1264355 . This one should actually boot. Michael Young From m.a.young at durham.ac.uk Sun Mar 29 18:53:02 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sun, 29 Mar 2009 19:53:02 +0100 (BST) Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: <20090328201942.GO31725@salstar.sk> References: <20090328163545.GM31725@salstar.sk> <20090328201942.GO31725@salstar.sk> Message-ID: On Sat, 28 Mar 2009, Jan ONDREJ (SAL) wrote: > Thanks. > You can avoid replacing your kernel by renaming name of your package. > You can name it kernel-dom0 (can't be named kernel-xen, because this package > was obsoleted) or something similar. That might not be easy, given the way it is built. > May be an f10 repository will be useful too. With all packages needed to run > dom0 on Fedora 10. I don't know how many packages you would actually need. For example X doesn't work for me in Fedora 10 on one of my machines but does for F11. However, it looks like the F10 2.6.29 development kernel tree has squashfs 3 patches to compile alongside squashfs 4, so I could probably make the kernel a bit more F10 friendly. Michael Young From pasik at iki.fi Sun Mar 29 20:11:48 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 29 Mar 2009 23:11:48 +0300 Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> Message-ID: <20090329201148.GA24960@edu.joroinen.fi> On Sun, Mar 29, 2009 at 07:34:06PM +0100, M A Young wrote: > On Sat, 28 Mar 2009, M A Young wrote: > > >Okay I have created a mini repository at > >http://fedorapeople.org/~myoung/dom0/ . I haven't done so before because I > >wasn't sure how much use it will be, since rawhide kernels will in general > >be more recent than mine so yum won't fetch them, but if koji is going to > >delete files then it is probably worth it after all. > > It now contains packages from the kernel 2.6.29-1.2.16.fc11 build > http://koji.fedoraproject.org/koji/taskinfo?taskID=1264355 . This one > should actually boot. > Do you have CONFIG_HIGHPTE=y in these kernels? At least for me CONFIG_HIGHPTE=y crashes the dom0 kernel after a while.. CONFIG_HIGHPTE=n pv_ops dom0 kernel runs fine. I'm running 32 bit PAE. Jeremy has not yet had time to look at this bug.. -- Pasi From m.a.young at durham.ac.uk Sun Mar 29 21:04:01 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sun, 29 Mar 2009 22:04:01 +0100 (BST) Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: <20090329201148.GA24960@edu.joroinen.fi> References: <20090328163545.GM31725@salstar.sk> <20090329201148.GA24960@edu.joroinen.fi> Message-ID: On Sun, 29 Mar 2009, Pasi K?rkk?inen wrote: > Do you have CONFIG_HIGHPTE=y in these kernels? At least for me > CONFIG_HIGHPTE=y crashes the dom0 kernel after a while.. > > CONFIG_HIGHPTE=n pv_ops dom0 kernel runs fine. > I'm running 32 bit PAE. For the most recent i686 build, yes, but I will change it for future builds until the problem is fixed. Michael Young From frank.vandamme at gmail.com Sat Mar 28 14:31:30 2009 From: frank.vandamme at gmail.com (Frank Van Damme) Date: Sat, 28 Mar 2009 15:31:30 +0100 Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: Message-ID: On Wed, Mar 18, 2009 at 1:26 AM, M A Young wrote: > My latest build (2.6.29-0.114.2.12.rc8.git2.fc11) is available at > http://koji.fedoraproject.org/koji/taskinfo?taskID=1246980 . Networking to > the guest is working again, and the X situation is better than I thought, > because my problems on one machine were due to using a F11 based kernel on > F10, and X works if I use it with F11. > In addition I got X working on the other machine working by using the > nomodeset boot parameter (with nomodeset I get no text characters during > boot - only a cursor that moves as invisible characters are presumably > printed to the screen - but X starts successfully, without nomodeset I can > read the boot messages but X crashes), however there are X problems on this > machine with regular Fedora kernels, so this may not be xen's fault. > > ? ? ? ?Michael Young Hi all, Sorry, I don't understand this Koji thing. If I click through to the dependant task for x86_64, then buildroot, then "built rpms", there are no rpms. How to actually download the kernel rpm?? -- Frank Van Damme "Anyone can sit down and write some boring artistic song. Pop music is the hardest shit to write." - Britney Spears. From glommer at redhat.com Mon Mar 30 18:10:20 2009 From: glommer at redhat.com (Glauber Costa) Date: Mon, 30 Mar 2009 15:10:20 -0300 Subject: [fedora-virt] Fedora virt status report In-Reply-To: <20090327103050.GD6913@redhat.com> References: <1238085713.3695.50.camel@blaa> <20090327103050.GD6913@redhat.com> Message-ID: <20090330181020.GC14361@poweredge.glommer> On Fri, Mar 27, 2009 at 10:30:50AM +0000, Daniel P. Berrange wrote: > On Thu, Mar 26, 2009 at 04:41:53PM +0000, Mark McLoughlin wrote: > > -- GCC Bug -- > > > > Another issue that arose was that latest gcc is breaking plain QEMU. A > > patch has been proposed upstream, but it's not in rawhide yet: > > > > https://bugzilla.redhat.com/490512 > > segfault in stw_kernel when qemu is run > > https://bugzilla.redhat.com/490509 > > GCC register allocation wrongly using ebp > > IMHO, we should apply the patch to Fedora regardless of whether upstream > think its the right long term approach. We need to have i386 qemu binary > functional for release, even if that means carrying a temporary hack of > some kind. I agree. What does gcc folks think about that? From m.a.young at durham.ac.uk Mon Mar 30 22:06:57 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Mon, 30 Mar 2009 23:06:57 +0100 (BST) Subject: [fedora-virt] Re: Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> Message-ID: The repository http://fedorapeople.org/~myoung/dom0/ is up to kernel 2.6.29-1.2.18.fc11 . This one is based on push2/xen/dom0/master rather than xen/dom0/hackery which should be closer to what is proposed for the 2.6.30 merge. It also has CONFIG_HIGHPTE=n (for x86), but my attempts to add squashfs 3 in addition to squashfs 4 didn't work as it seems you can't build both. Michael Young From itamar at ispbrasil.com.br Tue Mar 31 18:53:03 2009 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Tue, 31 Mar 2009 15:53:03 -0300 Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> Message-ID: any chance to get dom0 in these kernels http://koji.fedoraproject.org/koji/packageinfo?packageID=8 2.6.30 On Mon, Mar 30, 2009 at 7:06 PM, M A Young wrote: > The repository http://fedorapeople.org/~myoung/dom0/is up to kernel 2.6.29-1.2.18.fc11 . This one is based on > push2/xen/dom0/master rather than xen/dom0/hackery which should be closer to > what is proposed for the 2.6.30 merge. It also has CONFIG_HIGHPTE=n (for > x86), but my attempts to add squashfs 3 in addition to squashfs 4 didn't > work as it seems you can't build both. > > > Michael Young > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- ------------ Itamar Reis Peixoto e-mail/msn: itamar at ispbrasil.com.br sip: itamar at ispbrasil.com.br skype: itamarjp icq: 81053601 +55 11 4063 5033 +55 34 3221 8599 -------------- next part -------------- An HTML attachment was scrubbed... URL: