From dlbewley at lib.ucdavis.edu Sun Mar 1 19:03:01 2009 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Sun, 01 Mar 2009 11:03:01 -0800 Subject: [Fedora-xen] Xen to KVM Migration - How to resize LVM Partisions using KVM In-Reply-To: References: Message-ID: <1235934181.8734.42.camel@seitan.home.bewley.net> On Sat, 2009-02-28 at 14:23 +0000, MOHAMMAD MATEEN ASLAM wrote: > Hi, I am migrating from Xen to KVM. I have created a VM which is > based on LVM (/dev/VolGroupV00/vm). I have installed FC-10 on VM with > swap, / and /var partisions. > > Now i want to resize my / and /var partisions. I have resized LVM > (/dev/VolGroupV00/vm), how to resize inner partisions (/, /var) of > LVM ? > > Can anyone guide me how KVM deals with LVM and how to manage resizing > in a painless way. Apparently you are not using LVM inside the guest. I would do so for flexibility. If you want to resize the guest partitions from the host, you can make your guest's "hard drive" available in the host by using kpartx. You can then manipulate this device to resize the partitions on it. 'kpartx -av /dev/VolGroupV00/vm' will create /dev/mapper/VolGroupV00-vm. Resize it as you would any disk (see parted, resize2fs) then remove the device mapping with 'kpartx -dv /dev/VolGroupV00/vm' when done. See http://fedoraproject.org/wiki/Getting_started_with_virtualization#Accessing_data_on_guest_disk_images And I have some tangentially related but not directly applicable notes at http://tofu.org/drupal/node/55 http://tofu.org/drupal/node/60 Hopefully that was at least marginally helpful. From pasik at iki.fi Mon Mar 2 09:42:53 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 2 Mar 2009 11:42:53 +0200 Subject: [Fedora-xen] Adding qemu disable pci devices patch to Fedora Xen In-Reply-To: <20090226202714.GA8351@redhat.com> References: <20090226191235.GI15052@edu.joroinen.fi> <20090226202714.GA8351@redhat.com> Message-ID: <20090302094253.GK15052@edu.joroinen.fi> On Thu, Feb 26, 2009 at 08:27:14PM +0000, Daniel P. Berrange wrote: > On Thu, Feb 26, 2009 at 09:12:35PM +0200, Pasi K?rkk?inen wrote: > > Hello. > > > > Would it be possible to add Qemu "disable pci devices" patch to Fedora Xen > > packages? It allows HVM domains (or more specifically PV drivers running > > in HVM domains) to hide qemu emulated disk/network devices in a sane way to > > prevent possible corruption and other problems when both the PV devices and Qemu > > emulated devices are present at the same time.. > > > > It's mostly needed for Xen gplpv drivers by James Harper. The same > > code/feature is also being used by Citrix/Xensource commercial Windows PV > > drivers. > > > > The patch has been in xen-unstable (3.4) for a while already without > > problems. > > Since its merged in xen-unstable & feedback seems positive, I've no > objections to it being added to the xen RPM in F11. > Ok, good. Gerd: Could you apply that patch for the next Fedora Xen build? -- Pasi From kraxel at redhat.com Mon Mar 2 10:53:10 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Mon, 02 Mar 2009 11:53:10 +0100 Subject: [Fedora-xen] Adding qemu disable pci devices patch to Fedora Xen In-Reply-To: <20090302094253.GK15052@edu.joroinen.fi> References: <20090226191235.GI15052@edu.joroinen.fi> <20090226202714.GA8351@redhat.com> <20090302094253.GK15052@edu.joroinen.fi> Message-ID: <49ABBA96.1030002@redhat.com> Pasi K?rkk?inen wrote: > Gerd: Could you apply that patch for the next Fedora Xen build? Already done. Commit message well hidden in the mass rebuild email flood ;) cheers, Gerd From pasik at iki.fi Mon Mar 2 11:24:26 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 2 Mar 2009 13:24:26 +0200 Subject: [Fedora-xen] Adding qemu disable pci devices patch to Fedora Xen In-Reply-To: <49ABBA96.1030002@redhat.com> References: <20090226191235.GI15052@edu.joroinen.fi> <20090226202714.GA8351@redhat.com> <20090302094253.GK15052@edu.joroinen.fi> <49ABBA96.1030002@redhat.com> Message-ID: <20090302112426.GL15052@edu.joroinen.fi> On Mon, Mar 02, 2009 at 11:53:10AM +0100, Gerd Hoffmann wrote: > Pasi K?rkk?inen wrote: > > Gerd: Could you apply that patch for the next Fedora Xen build? > > Already done. > Commit message well hidden in the mass rebuild email flood ;) > Oh, nice, that was fast :) Thanks! -- Pasi From pasik at iki.fi Mon Mar 2 11:28:05 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 2 Mar 2009 13:28:05 +0200 Subject: [Fedora-xen] Adding qemu disable pci devices patch to Fedora Xen In-Reply-To: <20090302112426.GL15052@edu.joroinen.fi> References: <20090226191235.GI15052@edu.joroinen.fi> <20090226202714.GA8351@redhat.com> <20090302094253.GK15052@edu.joroinen.fi> <49ABBA96.1030002@redhat.com> <20090302112426.GL15052@edu.joroinen.fi> Message-ID: <20090302112805.GM15052@edu.joroinen.fi> On Mon, Mar 02, 2009 at 01:24:26PM +0200, Pasi K?rkk?inen wrote: > On Mon, Mar 02, 2009 at 11:53:10AM +0100, Gerd Hoffmann wrote: > > Pasi K?rkk?inen wrote: > > > Gerd: Could you apply that patch for the next Fedora Xen build? > > > > Already done. > > Commit message well hidden in the mass rebuild email flood ;) > > > > Oh, nice, that was fast :) > > Thanks! > * Sat Feb 28 2009 Gerd Hoffmann - 3.3.1-6 - fix xenstored crash. - backport qemu-unplug patch. So I guess it's that one.. -- Pasi From kraxel at redhat.com Mon Mar 2 11:53:41 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Mon, 02 Mar 2009 12:53:41 +0100 Subject: [Fedora-xen] Adding qemu disable pci devices patch to Fedora Xen In-Reply-To: <20090302112805.GM15052@edu.joroinen.fi> References: <20090226191235.GI15052@edu.joroinen.fi> <20090226202714.GA8351@redhat.com> <20090302094253.GK15052@edu.joroinen.fi> <49ABBA96.1030002@redhat.com> <20090302112426.GL15052@edu.joroinen.fi> <20090302112805.GM15052@edu.joroinen.fi> Message-ID: <49ABC8C5.2020205@redhat.com> Pasi K?rkk?inen wrote: > * Sat Feb 28 2009 Gerd Hoffmann - 3.3.1-6 > - fix xenstored crash. > - backport qemu-unplug patch. Yep. cheers, Gerd From mateenaslam at hotmail.com Tue Mar 3 12:05:52 2009 From: mateenaslam at hotmail.com (MOHAMMAD MATEEN ASLAM) Date: Tue, 3 Mar 2009 12:05:52 +0000 Subject: Subject: [Fedora-xen] Xen to KVM Migration - How to resize LVM Partisions using KVM Message-ID: Thanks for your valuable suggestions. >> Apparently you are not using LVM inside the guest. I would do so for flexibility. I have tried to create LVM while installing FC10 using Virt-install. When I select Disk Format as LVM, mount point got disable, which simply means we cant install / or /var or swap on LVM. we tried another way to use LVM. we created 3 lvm /dev/VolgroupVoo/vm2.root, /dev/VolgroupVoo/vm2.var,/dev/VolgroupVoo/vm2.swap and install fedora with following command virt-install -n kvm-vm -r 200 -w bridge:br0 -l /fc/Fedora-10-i386-DVD.iso --accelerate --os-type=linux -f /dev/VolgroupV00 /vm2.root -f /dev/VolgroupV00/vm2.var -f /dev/VolgroupV00/vm2.swap --force -x console=ttyS0 --nographics --hvm Installation got successfull but VM refused to start giving following error in log ---------------------------------------------------------------------------------- LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -S -M pc -m 200 -smp 1 -name kvm-vm -nographic -monitor pty -boot c -drive file=/dev/vmdata/vm2.root,if=ide,index=0,boot=on -drive file=/dev/vmdata/vm2.var,if=ide,index=1 -drive file=/home/mmaeasam/Fedora-10-i386-DVD.iso,if=ide,index=2 -drive file=/dev/vmdata/vm2.swap,if=ide,index=3 -net nic,macaddr=54:52:00:0a:12:4d,vlan=0 -net tap,fd=16,script=,vlan=0,ifname=vnet2 -serial pty -parallel none -usb char device redirected to /dev/pts/2 char device redirected to /dev/pts/5 info cpus exception 13 (0) rax 0000000000000000 rbx 0000000000000000 rcx 0000000000000000 rdx 0000000000000000 rsi 0000000000000000 rdi 0000000000000000 rsp 000000000000ffea rbp 000000000000ffee r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 000000000001fe05 rflags 00033086 cs 1020 (00010200/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ds 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) es 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ss 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) fs 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) gs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) tr 0000 (fffbd000/00002088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt fb562/30 idt 0/3ff cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 89 e5 50 51 --> 06 57 8b 4e 0a 85 c9 74 10 8b 46 04 8e c0 8b 46 06 89 c7 8a 46 08 fc f3 aa 5f 07 59 58] 5d ----------------------------------------------------------------------------------------- I am not installing any graphical console for VM. Any idea, whats going wrong ? or Any other way to use LVM for Files system ???? Regards, Mateen _________________________________________________________________ Hotmail? is up to 70% faster. Now good news travels really fast. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mateenaslam at hotmail.com Tue Mar 3 12:10:15 2009 From: mateenaslam at hotmail.com (MOHAMMAD MATEEN ASLAM) Date: Tue, 3 Mar 2009 12:10:15 +0000 Subject: [Fedora-xen] Xen to KVM Migration - How to resize LVM Partisions using KVM Message-ID: Thanks for your valuable suggestions. >> Apparently you are not using LVM inside the guest. I would do so for flexibility. I have tried to create LVM while installing FC10 using Virt-install. When I select Disk Format as LVM, mount point got disable, which simply means we cant install / or /var or swap on LVM. we tried another way to use LVM. we created 3 lvm /dev/VolgroupVoo/vm2.root, /dev/VolgroupVoo/vm2.var,/dev/VolgroupVoo/vm2.swap and install fedora with following command virt-install -n kvm-vm -r 200 -w bridge:br0 -l /fc/Fedora-10-i386-DVD.iso --accelerate --os-type=linux -f /dev/VolgroupV00 /vm2.root -f /dev/VolgroupV00/vm2.var -f /dev/VolgroupV00/vm2.swap --force -x console=ttyS0 --nographics --hvm Installation got successfull but VM refused to start giving following error in log ---------------------------------------------------------------------------------- LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -S -M pc -m 200 -smp 1 -name kvm-vm -nographic -monitor pty -boot c -drive file=/dev/vmdata/vm2.root,if=ide,index=0,boot=on -drive file=/dev/vmdata/vm2.var,if=ide,index=1 -drive file=/home/mmaeasam/Fedora-10-i386-DVD.iso,if=ide,index=2 -drive file=/dev/vmdata/vm2.swap,if=ide,index=3 -net nic,macaddr=54:52:00:0a:12:4d,vlan=0 -net tap,fd=16,script=,vlan=0,ifname=vnet2 -serial pty -parallel none -usb char device redirected to /dev/pts/2 char device redirected to /dev/pts/5 info cpus exception 13 (0) rax 0000000000000000 rbx 0000000000000000 rcx 0000000000000000 rdx 0000000000000000 rsi 0000000000000000 rdi 0000000000000000 rsp 000000000000ffea rbp 000000000000ffee r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 000000000001fe05 rflags 00033086 cs 1020 (00010200/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ds 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) es 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ss 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) fs 1000 (00010000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) gs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) tr 0000 (fffbd000/00002088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt fb562/30 idt 0/3ff cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 89 e5 50 51 --> 06 57 8b 4e 0a 85 c9 74 10 8b 46 04 8e c0 8b 46 06 89 c7 8a 46 08 fc f3 aa 5f 07 59 58] 5d ----------------------------------------------------------------------------------------- I am not installing any graphical console for VM. Any idea, whats going wrong ? or Any other way to use LVM for Files system ???? Regards, Mateen _________________________________________________________________ Express your personality in color! Preview and select themes for Hotmail?. http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=TXT_MSGTX_WL_HM_express_032009#colortheme -------------- next part -------------- An HTML attachment was scrubbed... URL: 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-xen] [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-xen] 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-xen] Re: [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-xen] Re: [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-xen] Re: [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-xen] Re: [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 stephen.johnston at talktalk.net Fri Mar 6 19:16:00 2009 From: stephen.johnston at talktalk.net (Stephen Johnston) Date: Fri, 06 Mar 2009 19:16:00 +0000 Subject: [Fedora-xen] Xen v's VMWare ESX Server Message-ID: <49B17670.8090504@talktalk.net> What is the general feeling about the type 1 true hypervisor from VMWare , their ESX Server, and Xen as a hypervisor ? Other than free v's pay for it of course. I originally was of the opinion the VMWare Workstation, their original offering wasnt great as it had the host o/s layer, however this type 1 seems quite nice. I do wish their naming convention was easier to understand - what component of an enterprise set up is what for example :) -- Stephen Johnston 8 Lime Grove Tel. +44 (0)1506 437766 Craigshill Mob. 07786 733 150 Livingston West Lothian www.fluffyrodent.co.uk EH54 5FB From rvandolson at esri.com Fri Mar 6 22:43:53 2009 From: rvandolson at esri.com (Ray Van Dolson) Date: Fri, 6 Mar 2009 14:43:53 -0800 Subject: [Fedora-xen] Xen adventures (updating domU's kernel from dom0) Message-ID: <20090306224353.GA10668@esri.com> Hello all; I have a RHEL 5.3 x86_64 dom0 and attempted to install Fedora 10 i386 as a domU. This of course failed initially due to some kernel bugs, but I was able to update to 2.6.18-133.el5virttest11xen from clalance's repo at RH. Now F10 i386 installs just fine, but of course I managed to neglect using kickstart to force the use of the PAE kernel. As a result, my domU won't boot. I could reinstall with KS but I thought now would be a good time to try to get my hands dirty and attempt to replace the kernel myself from the dom0. After some trials and tribulations with conflicting VolGroup names, I finally got my domU mounted under /mnt on dom0, copied in the PAE kernel RPM's, chroot'd to /mnt and ran rpm -Uvh. So far so good, but I then get the following error: # rpm -Uvh --force kernel-PAE-*.rpm warning: kernel-PAE-2.6.27.19-170.2.35.fc10.i686.rpm: Header V3 DSA signature: NOKEY, key ID 4ebfc273 Preparing... ########################################### [100%] 1:kernel-PAE ########################################### [ 50%] grubby fatal error: unable to find a suitable template 2:kernel-PAE-devel ########################################### [100%] Hmm, sure enough, /boot/grub/grub.conf wasn't updated! Now, I'm guessing I could add the new entry myself and all would be fine, but I'd like to understand why this isn't working... my theory is that grubby is confused by the chroot environment somehow and unable to properly locate my existing grub.conf file or templates? Any thoughts on this? A search hasn't yielded much in the way of answers... Thanks, Ray 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-xen] 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-xen] Re: [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-xen] Re: [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-xen] Re: [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-xen] Re: [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-xen] Re: [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-xen] Re: [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-xen] Re: [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 Dustin.Henning at prd-inc.com Mon Mar 9 12:33:01 2009 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Mon, 9 Mar 2009 08:33:01 -0400 Subject: [Fedora-xen] Xen adventures (updating domU's kernel from dom0) In-Reply-To: <20090306224353.GA10668@esri.com> References: <20090306224353.GA10668@esri.com> Message-ID: <007101c9a0b3$2f686250$8e3926f0$@Henning@prd-inc.com> While I can't say I know for sure, your guess sounds like a good one. I usually have trouble with grub when I boot to a CD for recovery, and I believe this is on account of the chroot. I think it is because the /dev/ information isn't available in the chrooted environment, so grub can't decide to use (for instance) hd(0,0). When I have trouble, I am typically installing grub, though, so I never see your error and can't be certain the situation is the same. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Ray Van Dolson Sent: Friday, March 06, 2009 17:44 To: fedora-xen at redhat.com Subject: [Fedora-xen] Xen adventures (updating domU's kernel from dom0) Hello all; I have a RHEL 5.3 x86_64 dom0 and attempted to install Fedora 10 i386 as a domU. This of course failed initially due to some kernel bugs, but I was able to update to 2.6.18-133.el5virttest11xen from clalance's repo at RH. Now F10 i386 installs just fine, but of course I managed to neglect using kickstart to force the use of the PAE kernel. As a result, my domU won't boot. I could reinstall with KS but I thought now would be a good time to try to get my hands dirty and attempt to replace the kernel myself from the dom0. After some trials and tribulations with conflicting VolGroup names, I finally got my domU mounted under /mnt on dom0, copied in the PAE kernel RPM's, chroot'd to /mnt and ran rpm -Uvh. So far so good, but I then get the following error: # rpm -Uvh --force kernel-PAE-*.rpm warning: kernel-PAE-2.6.27.19-170.2.35.fc10.i686.rpm: Header V3 DSA signature: NOKEY, key ID 4ebfc273 Preparing... ########################################### [100%] 1:kernel-PAE ########################################### [ 50%] grubby fatal error: unable to find a suitable template 2:kernel-PAE-devel ########################################### [100%] Hmm, sure enough, /boot/grub/grub.conf wasn't updated! Now, I'm guessing I could add the new entry myself and all would be fine, but I'd like to understand why this isn't working... my theory is that grubby is confused by the chroot environment somehow and unable to properly locate my existing grub.conf file or templates? Any thoughts on this? A search hasn't yielded much in the way of answers... Thanks, Ray -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen 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-xen] [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 bill.murray at stfc.ac.uk Tue Mar 10 19:58:16 2009 From: bill.murray at stfc.ac.uk (William Murray) Date: Tue, 10 Mar 2009 20:58:16 +0100 Subject: [Fedora-xen] kvm memory corruption? Message-ID: <49B6C658.5010708@stfc.ac.uk> Hello there, I have a VM installed in Fedora 10 with the virt-manager gui. Its great! I love the fact I can mount disks so guest and host can both see them. But..I created it with 1-2GB ram (from my total 4), and it defaults to 1GB. That works. If I increase it to 2 I start to see weird crashes in the host. How can I migrate this system to having always 2GB please? ---and safely! Thank you, Bill From rvandolson at esri.com Tue Mar 10 21:08:13 2009 From: rvandolson at esri.com (Ray Van Dolson) Date: Tue, 10 Mar 2009 14:08:13 -0700 Subject: [Fedora-xen] Xen adventures (updating domU's kernel from dom0) In-Reply-To: <007101c9a0b3$2f686250$8e3926f0$@Henning@prd-inc.com> References: <20090306224353.GA10668@esri.com> <007101c9a0b3$2f686250$8e3926f0$@Henning@prd-inc.com> Message-ID: <20090310210813.GA12046@esri.com> On Mon, Mar 09, 2009 at 05:33:01AM -0700, Dustin Henning wrote: > > While I can't say I know for sure, your guess sounds like a good > one. I usually have trouble with grub when I boot to a CD for recovery, and > I believe this is on account of the chroot. I think it is because the > /dev/ information isn't available in the chrooted environment, so grub > can't decide to use (for instance) hd(0,0). When I have trouble, I am > typically installing grub, though, so I never see your error and can't be > certain the situation is the same. > Dustin Thanks Dustin. I ended up editin the grub.conf file manually, but after bootup, I just got an error from GRUB saying it couldn't find my VolGroup. Oh well. Embarked on another reinstall, but the whole thing just locks up way too much. I think 32-bit Fedora on 64-bit RHEL5 dom0 is not quite ready to work yet. :-) Guess I'll go download 64-bit Fedora... Ray 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 urs.golla at gmail.com Fri Mar 13 09:27:16 2009 From: urs.golla at gmail.com (Urs Golla) Date: Fri, 13 Mar 2009 10:27:16 +0100 Subject: [Fedora-xen] configuration files Message-ID: <64e30f320903130227h78bca2c1q691fff39351dacd8@mail.gmail.com> Hi I am a bit confused about the configuration files for XEN user domains in Fedora. Regarding to the Users? Manual for Xen v3.3 from xensource the configuration files should still be in /etc/xen/ like they are on RHEL5. However, on F8 they are somewhere in /var/lib/xen and have a new format (not XML?). Could someone please provide a link to a changelog, release notes or any other "official" documentation which describes this change? I could not really find an answer on http://fedoraproject.org/wiki/Docs/Fedora8VirtQuickStart, and I see that many users ask this questions in other boards or mailing lists. Regards Urs From ondrejj at salstar.sk Fri Mar 13 11:30:40 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Fri, 13 Mar 2009 12:30:40 +0100 Subject: [Fedora-xen] configuration files In-Reply-To: <64e30f320903130227h78bca2c1q691fff39351dacd8@mail.gmail.com> References: <64e30f320903130227h78bca2c1q691fff39351dacd8@mail.gmail.com> Message-ID: <20090313113040.GQ25933@salstar.sk> Hi, On Fri, Mar 13, 2009 at 10:27:16AM +0100, Urs Golla wrote: > I am a bit confused about the configuration files for XEN user domains > in Fedora. Regarding to the Users? Manual > for Xen v3.3 from xensource the configuration files should still be in > /etc/xen/ like they are on RHEL5. However, on F8 they are somewhere in > /var/lib/xen and have a new format (not XML?). Could someone please > provide a link to a changelog, release notes or any other "official" > documentation which describes this change? I could not really find an > answer on http://fedoraproject.org/wiki/Docs/Fedora8VirtQuickStart, > and I see that many users ask this questions in other boards or > mailing lists. You can use both of them. Original xen commands (xm) uses mostly text configurations in /etc/xen, Fedora commands (virsh and command which use this) are using XML configs from /var/lib. SAL 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-xen] 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-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-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-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-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 urs.golla at gmail.com Mon Mar 16 04:52:34 2009 From: urs.golla at gmail.com (Urs Golla) Date: Mon, 16 Mar 2009 05:52:34 +0100 Subject: [Fedora-xen] configuration files In-Reply-To: <20090313113040.GQ25933@salstar.sk> References: <64e30f320903130227h78bca2c1q691fff39351dacd8@mail.gmail.com> <20090313113040.GQ25933@salstar.sk> Message-ID: <64e30f320903152152q65144db2j277592d14fdc06ce@mail.gmail.com> Hi, ok, but why does the file in /var/lib/xend/dom-uuid/config.sxp use such a strange syntax? I mean '()' instead of '<>' and an empty element should look like not (name value). if I dump the xml with virsh, it looks much more like a standard xml to me. Regards Urs On Fri, Mar 13, 2009 at 12:30 PM, Jan ONDREJ (SAL) wrote: > Hi, > > On Fri, Mar 13, 2009 at 10:27:16AM +0100, Urs Golla wrote: >> I am a bit confused about the configuration files for XEN user domains >> in Fedora. Regarding to the Users? Manual >> for Xen v3.3 from xensource the configuration files should still be in >> /etc/xen/ like they are on RHEL5. However, on F8 they are somewhere in >> /var/lib/xen and have a new format (not XML?). Could someone please >> provide a link to a changelog, release notes or any other "official" >> documentation which describes this change? I could not really find an >> answer on http://fedoraproject.org/wiki/Docs/Fedora8VirtQuickStart, >> and I see that many users ask this questions in other boards or >> mailing lists. > > You can use both of them. Original xen commands (xm) uses mostly text > configurations in /etc/xen, Fedora commands (virsh and command which use > this) are using XML configs from /var/lib. > > SAL > From armbru at redhat.com Mon Mar 16 07:48:32 2009 From: armbru at redhat.com (Markus Armbruster) Date: Mon, 16 Mar 2009 08:48:32 +0100 Subject: [Fedora-xen] configuration files In-Reply-To: <64e30f320903152152q65144db2j277592d14fdc06ce@mail.gmail.com> (Urs Golla's message of "Mon\, 16 Mar 2009 05\:52\:34 +0100") References: <64e30f320903130227h78bca2c1q691fff39351dacd8@mail.gmail.com> <20090313113040.GQ25933@salstar.sk> <64e30f320903152152q65144db2j277592d14fdc06ce@mail.gmail.com> Message-ID: <87hc1t6h7z.fsf@pike.pond.sub.org> Urs Golla writes: > Hi, > > ok, but why does the file in /var/lib/xend/dom-uuid/config.sxp use > such a strange syntax? I mean '()' instead of '<>' and an empty > element should look like not (name value). Because it's not XML. > if I dump the xml with virsh, it looks much more like a standard xml > to me. Because it's XML. The .sxp files use Xen's native syntax, which is from the sexp family[*]. libvirt uses XML. [*] http://en.wikipedia.org/wiki/S-expression From urs.golla at gmail.com Mon Mar 16 08:12:34 2009 From: urs.golla at gmail.com (Urs Golla) Date: Mon, 16 Mar 2009 09:12:34 +0100 Subject: [Fedora-xen] configuration files In-Reply-To: <87hc1t6h7z.fsf@pike.pond.sub.org> References: <64e30f320903130227h78bca2c1q691fff39351dacd8@mail.gmail.com> <20090313113040.GQ25933@salstar.sk> <64e30f320903152152q65144db2j277592d14fdc06ce@mail.gmail.com> <87hc1t6h7z.fsf@pike.pond.sub.org> Message-ID: <64e30f320903160112l3d0ca2dtb21c246134863fab@mail.gmail.com> Hi Markus Thanks for your reply! > Because it's not XML. That really explains a lot ;-) I always assumed the "legacy" format from /etc/xen/mydomainconfig (like in RHEL 5) is the native XEN syntax (I see this is not the case.). So, the xml format from libvirt is like a replacement for the configuration in /etc/xen/mydomainconfig? But if I use virt-install (e.g. in Fedora 8) to install a new machine, it does not create a file /etc/xen/ and also no xml. All It does is creating the s-expression file in /var/lib/. Is there a documentation about the relation between all this different XEN / libvirt configuration files? The architecture part of the documentation on libvirt.org does not answer this question. cheers On Mon, Mar 16, 2009 at 8:48 AM, Markus Armbruster wrote: > Urs Golla writes: > >> Hi, >> >> ok, but why does the file in /var/lib/xend/dom-uuid/config.sxp use >> such a strange syntax? I mean '()' instead of '<>' and an empty >> element should look like not (name value). > > Because it's not XML. > >> if I dump the xml with virsh, it looks much more like a standard xml >> to me. > > Because it's XML. > > The .sxp files use Xen's native syntax, which is from the sexp > family[*]. ?libvirt uses XML. > > > [*] http://en.wikipedia.org/wiki/S-expression > From armbru at redhat.com Mon Mar 16 10:42:41 2009 From: armbru at redhat.com (Markus Armbruster) Date: Mon, 16 Mar 2009 11:42:41 +0100 Subject: [Fedora-xen] configuration files In-Reply-To: <64e30f320903160112l3d0ca2dtb21c246134863fab@mail.gmail.com> (Urs Golla's message of "Mon\, 16 Mar 2009 09\:12\:34 +0100") References: <64e30f320903130227h78bca2c1q691fff39351dacd8@mail.gmail.com> <20090313113040.GQ25933@salstar.sk> <64e30f320903152152q65144db2j277592d14fdc06ce@mail.gmail.com> <87hc1t6h7z.fsf@pike.pond.sub.org> <64e30f320903160112l3d0ca2dtb21c246134863fab@mail.gmail.com> Message-ID: <87eiwx3g0u.fsf@pike.pond.sub.org> Urs Golla writes: > Hi Markus > > Thanks for your reply! > >> Because it's not XML. > > That really explains a lot ;-) ;) > I always assumed the "legacy" format from /etc/xen/mydomainconfig > (like in RHEL 5) is the native XEN syntax (I see this is not the > case.). So, the xml format from libvirt is like a replacement for the > configuration in /etc/xen/mydomainconfig? But if I use virt-install > (e.g. in Fedora 8) to install a new machine, it does not create a file > /etc/xen/ and also no xml. All It does is creating the s-expression > file in /var/lib/. > > Is there a documentation about the relation between all this different > XEN / libvirt configuration files? The architecture part of the > documentation on libvirt.org does not answer this question. > > cheers Xen uses *two* native configuration file formats: S-expressions and a Python-like syntax. The .sxp files you found below /var/lib/xend/ use the former syntax, the guest configuration in /etc/xen the latter. I'd recommend to stick to libvirt as much as possible. Check "man virsh", in particular the domain commands "dumpxml" and "define". From berrange at redhat.com Mon Mar 16 11:17:30 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 16 Mar 2009 11:17:30 +0000 Subject: [Fedora-xen] configuration files In-Reply-To: <87eiwx3g0u.fsf@pike.pond.sub.org> References: <64e30f320903130227h78bca2c1q691fff39351dacd8@mail.gmail.com> <20090313113040.GQ25933@salstar.sk> <64e30f320903152152q65144db2j277592d14fdc06ce@mail.gmail.com> <87hc1t6h7z.fsf@pike.pond.sub.org> <64e30f320903160112l3d0ca2dtb21c246134863fab@mail.gmail.com> <87eiwx3g0u.fsf@pike.pond.sub.org> Message-ID: <20090316111730.GL22285@redhat.com> On Mon, Mar 16, 2009 at 11:42:41AM +0100, Markus Armbruster wrote: > Urs Golla writes: > > > Hi Markus > > > > Thanks for your reply! > > > >> Because it's not XML. > > > > That really explains a lot ;-) > > ;) > > > I always assumed the "legacy" format from /etc/xen/mydomainconfig > > (like in RHEL 5) is the native XEN syntax (I see this is not the > > case.). So, the xml format from libvirt is like a replacement for the > > configuration in /etc/xen/mydomainconfig? But if I use virt-install > > (e.g. in Fedora 8) to install a new machine, it does not create a file > > /etc/xen/ and also no xml. All It does is creating the s-expression > > file in /var/lib/. > > > > Is there a documentation about the relation between all this different > > XEN / libvirt configuration files? The architecture part of the > > documentation on libvirt.org does not answer this question. > > > > cheers > > Xen uses *two* native configuration file formats: S-expressions and a > Python-like syntax. The .sxp files you found below /var/lib/xend/ use > the former syntax, the guest configuration in /etc/xen the latter. To be more specific 'xend' use /var/lib/xend for storing master config files in SXPR format. 'xm' abuses python as a config file format in /etc/xen. XenD itself has no knowledge of these files, so it can't manage them. They should not be used in Xen >= 3.0.4 If you have existing files in /etc/xen, then you can load them into XenD by doing 'xm new configname', at which point both Xend and libvirt will be able to manage them. For Xen < 3.0.4 libvirt has some limited support for reading /etc/xen files directly 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 Dustin.Henning at prd-inc.com Mon Mar 16 14:54:11 2009 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Mon, 16 Mar 2009 10:54:11 -0400 Subject: [Fedora-xen] configuration files In-Reply-To: <20090316111730.GL22285@redhat.com> References: <64e30f320903130227h78bca2c1q691fff39351dacd8@mail.gmail.com> <20090313113040.GQ25933@salstar.sk> <64e30f320903152152q65144db2j277592d14fdc06ce@mail.gmail.com> <87hc1t6h7z.fsf@pike.pond.sub.org> <64e30f320903160112l3d0ca2dtb21c246134863fab@mail.gmail.com> <87eiwx3g0u.fsf@pike.pond.sub.org> <20090316111730.GL22285@redhat.com> Message-ID: <007601c9a647$113cb5d0$33b62170$@Henning@prd-inc.com> Response below... -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Daniel P. Berrange Sent: Monday, March 16, 2009 07:18 To: Markus Armbruster Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] configuration files On Mon, Mar 16, 2009 at 11:42:41AM +0100, Markus Armbruster wrote: > Urs Golla writes: > > > Hi Markus > > > > Thanks for your reply! > > > >> Because it's not XML. > > > > That really explains a lot ;-) > > ;) > > > I always assumed the "legacy" format from /etc/xen/mydomainconfig > > (like in RHEL 5) is the native XEN syntax (I see this is not the > > case.). So, the xml format from libvirt is like a replacement for the > > configuration in /etc/xen/mydomainconfig? But if I use virt-install > > (e.g. in Fedora 8) to install a new machine, it does not create a file > > /etc/xen/ and also no xml. All It does is creating the s-expression > > file in /var/lib/. > > > > Is there a documentation about the relation between all this different > > XEN / libvirt configuration files? The architecture part of the > > documentation on libvirt.org does not answer this question. > > > > cheers > > Xen uses *two* native configuration file formats: S-expressions and a > Python-like syntax. The .sxp files you found below /var/lib/xend/ use > the former syntax, the guest configuration in /etc/xen the latter. To be more specific 'xend' use /var/lib/xend for storing master config files in SXPR format. 'xm' abuses python as a config file format in /etc/xen. XenD itself has no knowledge of these files, so it can't manage them. They should not be used in Xen >= 3.0.4 If you have existing files in /etc/xen, then you can load them into XenD by doing 'xm new configname', at which point both Xend and libvirt will be able to manage them. For Xen < 3.0.4 libvirt has some limited support for reading /etc/xen files directly Daniel -- I should hope this won't be considered a thread hijacking, but when you refer to using Xen >= 3.0.4, are you also referring specifically to within Fedora (and perhaps RH & clones), or are you actually referring to that version of Xen regardless? Moreover, assuming you are referring specifically to Fedora, is there any compelling reason to do this beyond the fact that virt-install and Xen both support it and can then play nice? I ask because I still use /etc/xen and xm python-like config files, primarily because I can then quickly and easily edit those config files, but also because I use the functionality in /etc/xen/auto (and related config files) for startup and shutdown (which incidentally does appear somewhat broken specifically in F8 [EOL, I know, but it has appeared broken since some number of updates ago, and that might be the compelling reason]). Dustin 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-xen] 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 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-xen] Re: [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 markmc at redhat.com Fri Mar 20 12:16:18 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 20 Mar 2009 12:16:18 +0000 Subject: [Fedora-xen] kvm memory corruption? In-Reply-To: <49B6C658.5010708@stfc.ac.uk> References: <49B6C658.5010708@stfc.ac.uk> Message-ID: <1237551378.4938.63.camel@blaa> Hi Bill, On Tue, 2009-03-10 at 20:58 +0100, William Murray wrote: > Hello there, > I have a VM installed in Fedora 10 with the virt-manager > gui. Its > great! I love the fact I can mount disks so guest and host can both see > them. > But..I created it with 1-2GB ram (from my total 4), and it defaults to 1GB. > That works. If I increase it to 2 I start to see weird crashes in the host. > > How can I migrate this system to having always 2GB please? > ---and safely! If this hasn't already been sorted out, please file a bug against the kvm package which as many details as possible. See: https://fedoraproject.org/wiki/Reporting_virtualization_bugs Also - the fedora-virt at redhat.com list would be more appropriate. Thanks, Mark. From shoom013 at gmail.com Tue Mar 17 18:44:19 2009 From: shoom013 at gmail.com (=?ISO-8859-2?Q?Zoran_Popovi=E6?=) Date: Tue, 17 Mar 2009 19:44:19 +0100 Subject: [Fedora-xen] ia64 HVM network problem !!! Message-ID: <96b40cab0903171144i598acb92w429e7b053a84f842@mail.gmail.com> I am having trouble with Realtek 8139 NIC on ia64 HVM guest with Windows 2003 SP1 - I can not install a valid ia64 driver (none available), and vif=[ ... model=ne2k_pci|pcnet|whatever ... ] does not seem tho change anything ... I feel desperate now. This had to work in order to make proof of concept in my company (Hemofarm, STADA) for RHEL 5.3 as an Itanium virtualization platform. Now I feel exhausted, hours of work are gone leaving me with only one step left unfinished - network access for Windows guest ... please, please, help ! This would lead at least to a more serious support agreement with Red Hat ... ZP. PS. My temporary RHN subscription is 1170505. We have a regional support center, this might also lead me to a solution ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mchouque at free.fr Tue Mar 17 20:53:14 2009 From: mchouque at free.fr (Mathieu Chouquet-Stringer) Date: Tue, 17 Mar 2009 21:53:14 +0100 Subject: [Fedora-xen] Fedora 10 on RHEL5.3 x86_64 Message-ID: <20090317205314.GA3337@mobydick> Hello Mike, I've been browsing the web for I've been having the same issue you describe in the email attached below... Have you made any progress? I've been able to install F10 on RHEL 5.3 but only has an HVM. Now I'm trying to switch it to paravirt and no luck. It just doesn't even start booting. Creating an empty shell and telling it to use F10 initrd and kernel yields the same result. I should get more time to investigate this week but I was wondering if you figured it out? Best, > On Fri, 13 Feb 2009, Mike McGrath wrote: > > On Fri, 13 Feb 2009, Mark McLoughlin wrote: > > On Thu, 2009-02-12 at 21:21 +0100, Olivier Renault wrote: > > > > > There is no xen kernel within F10 so you will need to install it as > > > a > > > FV VM. > > > > Yes, there is - the bare-metal kernel has pv_ops Xen support. You may > > have been bitten by this bug, though: > > > > https://bugzilla.redhat.com/470905 > > anaconda installs the wrong kernel for i686 xen guests. > > > > Its not even getting to stage 2 during install I'm afraid. > > -Mike -- Mathieu Chouquet-Stringer mchouque at free.fr The sun itself sees not till heaven clears. -- William Shakespeare -- From bill.murray at stfc.ac.uk Fri Mar 20 15:54:08 2009 From: bill.murray at stfc.ac.uk (William John Murray) Date: Fri, 20 Mar 2009 16:54:08 +0100 Subject: [Fedora-xen] kvm memory corruption? In-Reply-To: <1237551378.4938.63.camel@blaa> References: <49B6C658.5010708@stfc.ac.uk> <1237551378.4938.63.camel@blaa> Message-ID: <49C3BC20.1060704@stfc.ac.uk> Hi Mark, Yes, you are correct. Trouble is it is a pig to do. I have to actually use the machine to generate a hang, and when I do who knows what it costs me. But I'll try. Would you think virt-manager is the culprit? I see nothing suspicious in the log file there. Or kvm? or libvirt? Bill Mark McLoughlin wrote: > Hi Bill, > > On Tue, 2009-03-10 at 20:58 +0100, William Murray wrote: > >> Hello there, >> I have a VM installed in Fedora 10 with the virt-manager >> gui. Its >> great! I love the fact I can mount disks so guest and host can both see >> them. >> But..I created it with 1-2GB ram (from my total 4), and it defaults to 1GB. >> That works. If I increase it to 2 I start to see weird crashes in the host. >> >> How can I migrate this system to having always 2GB please? >> ---and safely! >> > > If this hasn't already been sorted out, please file a bug against the > kvm package which as many details as possible. See: > > https://fedoraproject.org/wiki/Reporting_virtualization_bugs > > Also - the fedora-virt at redhat.com list would be more appropriate. > > Thanks, > Mark. > > From bill.murray at stfc.ac.uk Fri Mar 20 17:37:12 2009 From: bill.murray at stfc.ac.uk (William John Murray) Date: Fri, 20 Mar 2009 18:37:12 +0100 Subject: [Fedora-xen] kvm memory corruption? In-Reply-To: <49C3BC20.1060704@stfc.ac.uk> References: <49B6C658.5010708@stfc.ac.uk> <1237551378.4938.63.camel@blaa> <49C3BC20.1060704@stfc.ac.uk> Message-ID: <49C3D448.9080105@stfc.ac.uk> OK, well after a couple of hours of running 'valgrind' on a massive piece of code I have had no problem at all. Maybe something has change - but it is not in libvirt/kvm, there have been no fedora changes there in the last few days. Unless it is the guest, but that seems unlikely - it should not be allowed out! Bill William John Murray wrote: > > Hi Mark, > Yes, you are correct. Trouble is it is a pig to do. I have to > actually use the machine > to generate a hang, and when I do who knows what it costs me. > But I'll try. > > Would you think virt-manager is the culprit? I see nothing > suspicious in the log file > there. Or kvm? or libvirt? > Bill > Mark McLoughlin wrote: >> Hi Bill, >> >> On Tue, 2009-03-10 at 20:58 +0100, William Murray wrote: >> >>> Hello there, >>> I have a VM installed in Fedora 10 with the virt-manager >>> gui. Its >>> great! I love the fact I can mount disks so guest and host can both >>> see them. >>> But..I created it with 1-2GB ram (from my total 4), and it defaults >>> to 1GB. >>> That works. If I increase it to 2 I start to see weird crashes in >>> the host. >>> >>> How can I migrate this system to having always 2GB please? >>> ---and safely! >>> >> >> If this hasn't already been sorted out, please file a bug against the >> kvm package which as many details as possible. See: >> >> https://fedoraproject.org/wiki/Reporting_virtualization_bugs >> >> Also - the fedora-virt at redhat.com list would be more appropriate. >> >> Thanks, >> Mark. >> >> > > From markmc at redhat.com Fri Mar 20 17:46:41 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 20 Mar 2009 17:46:41 +0000 Subject: [Fedora-xen] kvm memory corruption? In-Reply-To: <49C3BC20.1060704@stfc.ac.uk> References: <49B6C658.5010708@stfc.ac.uk> <1237551378.4938.63.camel@blaa> <49C3BC20.1060704@stfc.ac.uk> Message-ID: <1237571201.18253.1.camel@blaa> On Fri, 2009-03-20 at 16:54 +0100, William John Murray wrote: > Would you think virt-manager is the culprit? I see nothing suspicious > in the log file > there. Or kvm? or libvirt? It sounds like it's most likely a kvm bug - if it causes a host kernel oops, then the most important thing is to get the full trace of that oops. Cheers, Mark. 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-xen] Re: [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 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 pasik at iki.fi Mon Mar 23 18:46:55 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 23 Mar 2009 20:46:55 +0200 Subject: [Fedora-xen] Fedora 10 on RHEL5.3 x86_64 In-Reply-To: <20090317205314.GA3337@mobydick> References: <20090317205314.GA3337@mobydick> Message-ID: <20090323184655.GG5528@edu.joroinen.fi> On Tue, Mar 17, 2009 at 09:53:14PM +0100, Mathieu Chouquet-Stringer wrote: > Hello Mike, > > I've been browsing the web for I've been having the same issue you > describe in the email attached below... Have you made any progress? > > I've been able to install F10 on RHEL 5.3 but only has an HVM. Now I'm > trying to switch it to paravirt and no luck. It just doesn't even start > booting. Creating an empty shell and telling it to use F10 initrd and > kernel yields the same result. > > I should get more time to investigate this week but I was wondering if > you figured it out? > I just installed 32bit Fedora 10 Xen domU guest on CentOS 5.3 dom0. It seems to work just fine.. I had to create a kickstart file that forces installation of kernel-PAE instead of normal non-PAE kernel, because only PAE kernels are supported for 32bit Xen PV domUs. It's known Fedora 10 anaconda installer bug: https://bugzilla.redhat.com/show_bug.cgi?id=470905 64bit Fedora 10 Xen domU shouldn't have this bug/problem. My F10 Xen domU kickstart installation file is here: http://pasik.reaktio.net/fedora/f10-xen-domu-ks.cfg -- Pasi > Best, > > > On Fri, 13 Feb 2009, Mike McGrath wrote: > > > On Fri, 13 Feb 2009, Mark McLoughlin wrote: > > > On Thu, 2009-02-12 at 21:21 +0100, Olivier Renault wrote: > > > > > > > There is no xen kernel within F10 so you will need to install it as > > > > a > > > > FV VM. > > > > > > Yes, there is - the bare-metal kernel has pv_ops Xen support. You may > > > have been bitten by this bug, though: > > > > > > https://bugzilla.redhat.com/470905 > > > anaconda installs the wrong kernel for i686 xen guests. > > > > > > > Its not even getting to stage 2 during install I'm afraid. > > > > -Mike > > > > -- > Mathieu Chouquet-Stringer mchouque at free.fr > The sun itself sees not till heaven clears. > -- William Shakespeare -- > From mchouque at free.fr Mon Mar 23 20:07:32 2009 From: mchouque at free.fr (Mathieu Chouquet-Stringer) Date: Mon, 23 Mar 2009 21:07:32 +0100 Subject: [Fedora-xen] Fedora 10 on RHEL5.3 x86_64 In-Reply-To: <20090323184655.GG5528@edu.joroinen.fi> References: <20090317205314.GA3337@mobydick> <20090323184655.GG5528@edu.joroinen.fi> Message-ID: <20090323200732.GA4377@mobydick> On Mon, Mar 23, 2009 at 08:46:55PM +0200, Pasi K?rkk?inen wrote: > I just installed 32bit Fedora 10 Xen domU guest on CentOS 5.3 dom0. It seems to > work just fine.. > > I had to create a kickstart file that forces installation of kernel-PAE instead of > normal non-PAE kernel, because only PAE kernels are supported for 32bit Xen PV domUs. > > It's known Fedora 10 anaconda installer bug: https://bugzilla.redhat.com/show_bug.cgi?id=470905 > [...] Yeah, I read about that. In my case it was an issue with NX... The F10 kernel was trying to use it though it was disabled on the host (dom0) causing 'invalid instruction' errors. I enabled it in the BIOS and it worked. That said it's still a bug but I found a fix mainstream (or even in bugzilla, don't remember). -- Mathieu Chouquet-Stringer mchouque at free.fr The sun itself sees not till heaven clears. -- William Shakespeare -- 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 sascha.mail at web.de Tue Mar 24 08:22:35 2009 From: sascha.mail at web.de (Alexander Sascha) Date: Tue, 24 Mar 2009 09:22:35 +0100 Subject: [Fedora-xen] Need help for thesis on Xen - disabling HAP for benchmarking purposes Message-ID: <49C8984B.90603@web.de> Hi, I'm a German student, writing my thesis on "Virtualization with Xen. Analysis and Comparision of Different Techniques such as Paravirtualization, Full Virtualization, and Utilization of Hardware Support Provided by the Processor". I'd like to know how I can disable HAP/RVI/Nested Paging for benchmarking purposes. I read somewhere (http://markmail.org/message/bbnivuqx6vjz7jg4) that Xen developers decided to disable the global grub parameter introducing a per domain flag for HAP instead (hap=0/1). I used virt-manager built in CentOS for setting up all domUs; virt-manager uses libvirt so that no "old-style" configuration files are stored in /etc/xen. I actually don't know how if libvirt-XML-files already support something like 0. How would you proceed to modify an already existing domain using libvirt/virt-manager? I really do apologize for my "newbie ignorance". Thanks in advance for any useful help. - Alex 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-xen] 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-xen] Re: [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-xen] Re: [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 orion at cora.nwra.com Wed Mar 25 16:43:15 2009 From: orion at cora.nwra.com (Orion Poplawski) Date: Wed, 25 Mar 2009 10:43:15 -0600 Subject: [Fedora-xen] Network issues with F11 guests Message-ID: <49CA5F23.3010102@cora.nwra.com> Has anyone experienced network trouble with F11 xen paravirt guests? I'm running centos 5.2 with a newer virttest kernel. During anaconda install it seems like it just gives up trying to download packages. Hit "retry" and on it goes. Seems like it may be IPv6/DNS/arp related. Last traffic I see from the guest is a DNS request followed by an arp request: 10:39:15.400256 IP 192.168.0.152.48599 > 192.168.0.8.domain: 39049+ AAAA? fedora.cora.nwra.com. (38) 10:39:15.401002 IP 192.168.0.8.domain > 192.168.0.152.48599: 39049* 1/1/0 CNAME[|domain] 10:39:15.401364 IP 192.168.0.152.51996 > 192.168.0.8.domain: 38381+ A? fedora.cora.nwra.com. (38) 10:39:15.402118 IP 192.168.0.8.domain > 192.168.0.152.51996: 38381* 2/4/2 CNAME[|domain] 10:39:18.315280 arp who-has 192.168.0.8 tell 192.168.0.152 10:39:18.315302 arp reply 192.168.0.8 is-at 00:06:5b:3f:72:c2 or: 10:41:59.317998 IP 192.168.0.152.39309 > 192.168.0.8.domain: 30991+ AAAA? fedora.cora.nwra.com. (38) 10:41:59.318392 IP 192.168.0.8.domain > 192.168.0.152.39309: 30991* 1/1/0 CNAME[|domain] 10:41:59.318671 IP 192.168.0.152.55043 > 192.168.0.8.domain: 51670+ A? fedora.cora.nwra.com. (38) 10:41:59.319105 IP 192.168.0.8.domain > 192.168.0.152.55043: 51670* 2/4/2 CNAME[|domain] 10:42:01.056915 arp who-has 192.168.0.152 tell 192.168.0.8 10:42:01.057115 arp reply 192.168.0.152 is-at 40:00:00:00:00:03 -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion at cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com 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-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 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-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 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-xen] 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-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: