From nagaraj.narayan at gmail.com Thu Apr 2 10:41:20 2009 From: nagaraj.narayan at gmail.com (nagarajn) Date: Thu, 2 Apr 2009 03:41:20 -0700 (PDT) Subject: [Fedora-xen] Guest shutdown problems In-Reply-To: <47E79BB7.50500@lanil.mine.nu> References: <47E79BB7.50500@lanil.mine.nu> Message-ID: <22845117.post@talk.nabble.com> Check to see if libvirtd is running else restarted libvirtd first and then restart xend. this will resolve the problem Christian Axelsson wrote: > > Hello > > I have a problem shutting down xen guests. Using xm shutdown guests get > shut down but gets stuck in state '---s-d' or sometimes '------'. > When trying to clone a domain when in this state (my original purpose of > the whole operation) I'll get the error: > > [root at hydra virtinst--devel]# ./virt-clone -o minimal -n new_img -f > /var/lib/xen/images/new_img.img > ERROR: virDomainGetXMLDesc() failed failed Xen syscall > xenDaemonDomainDumpXMLByID failed to find this domain -490299505 > > The same errors occurs when for example trying to attach to the console > using virsh. > > I have tried to use 'xm destroy' to kill the guest the hard way but it > has no effect - the state remains unchanged. I have also tried this on a > few different guest installations with the same result. A thing worth > noting is that the output from 'xm list --long' differs, I've attached > the out put pre boot, after boot and after shutdown. Note how all the > devices in the guests are missing after shutdown. > > Both the hosts and the guests are fedora 8 installations. > > Regards, > Christian Axelsson > smiler at lanil.mine.nu > > [?1034h(domain > (domid 0) > (on_crash restart) > (uuid 00000000-0000-0000-0000-000000000000) > (bootloader_args ) > (vcpus 2) > (name Domain-0) > (on_poweroff destroy) > (on_reboot restart) > (bootloader ) > (maxmem 16777215) > (memory 1491) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (cpu_time 1644.84369405) > (online_vcpus 2) > (image (linux (kernel ))) > (status 2) > (state r-----) > ) > (domain > (domid 2) > (on_crash restart) > (uuid a7638797-e237-3891-5e64-390f828238ca) > (bootloader_args ) > (vcpus 1) > (name minimal) > (on_poweroff destroy) > (on_reboot restart) > (bootloader /usr/bin/pygrub) > (maxmem 512) > (memory 512) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (start_time 1206360333.14) > (cpu_time 9.753408915) > (online_vcpus 1) > (image > (linux > (kernel ) > (notes > (FEATURES > > 'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel' > ) > (VIRT_BASE 18446744071562067968) > (GUEST_VERSION 2.6) > (PADDR_OFFSET 18446744071562067968) > (GUEST_OS linux) > (HYPERCALL_PAGE 18446744071564189696) > (LOADER generic) > (SUSPEND_CANCEL 1) > (ENTRY 18446744071564165120) > (XEN_VERSION xen-3.0) > ) > ) > ) > (status 2) > (state -b----) > (store_mfn 196619) > (console_mfn 196618) > (device > (vif > (bridge xenbr0) > (mac 00:16:3e:3f:93:b8) > (script vif-bridge) > (uuid 94afd732-920b-2e0b-b3d5-e79174754a80) > (backend 0) > ) > ) > (device > (vbd > (uname file:/var/lib/xen/images/minimal.img) > (uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd) > (mode w) > (dev xvda:disk) > (backend 0) > (bootable 1) > ) > ) > (device > (console > (protocol vt100) > (location 2) > (uuid 0046f2d3-058b-d524-9273-f1dac2ca950b) > ) > ) > ) > > [?1034h(domain > (domid 0) > (on_crash restart) > (uuid 00000000-0000-0000-0000-000000000000) > (bootloader_args ) > (vcpus 2) > (name Domain-0) > (on_poweroff destroy) > (on_reboot restart) > (bootloader ) > (maxmem 16777215) > (memory 1491) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (cpu_time 1648.92600832) > (online_vcpus 2) > (image (linux (kernel ))) > (status 2) > (state r-----) > ) > (domain > (domid 2) > (on_crash restart) > (uuid a7638797-e237-3891-5e64-390f828238ca) > (bootloader_args ) > (vcpus 1) > (name minimal) > (on_poweroff destroy) > (on_reboot restart) > (bootloader /usr/bin/pygrub) > (maxmem 512) > (memory 512) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (start_time 1206360333.14) > (cpu_time 13.048743365) > (online_vcpus 1) > (image > (linux > (kernel ) > (notes > (FEATURES > > 'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel' > ) > (VIRT_BASE 18446744071562067968) > (GUEST_VERSION 2.6) > (PADDR_OFFSET 18446744071562067968) > (GUEST_OS linux) > (HYPERCALL_PAGE 18446744071564189696) > (LOADER generic) > (SUSPEND_CANCEL 1) > (ENTRY 18446744071564165120) > (XEN_VERSION xen-3.0) > ) > ) > ) > (status 0) > (state ---s-d) > (store_mfn 196619) > (console_mfn 196618) > ) > > [?1034h(domain > (domid 0) > (on_crash restart) > (uuid 00000000-0000-0000-0000-000000000000) > (bootloader_args ) > (vcpus 2) > (name Domain-0) > (on_poweroff destroy) > (on_reboot restart) > (bootloader ) > (maxmem 16777215) > (memory 1491) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (cpu_time 1635.21430615) > (online_vcpus 2) > (image (linux (kernel ))) > (status 2) > (state r-----) > ) > (domain > (on_crash restart) > (uuid a7638797-e237-3891-5e64-390f828238ca) > (bootloader_args ) > (vcpus 1) > (name minimal) > (on_poweroff destroy) > (on_reboot restart) > (bootloader /usr/bin/pygrub) > (maxmem 512) > (memory 512) > (shadow_memory 0) > (cpu_weight 256) > (cpu_cap 0) > (features ) > (on_xend_start ignore) > (on_xend_stop ignore) > (start_time 1206309092.82) > (cpu_time 0.0) > (image > (linux > (kernel ) > (notes > (FEATURES > > 'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel' > ) > (VIRT_BASE 18446744071562067968) > (GUEST_VERSION 2.6) > (PADDR_OFFSET 18446744071562067968) > (GUEST_OS linux) > (HYPERCALL_PAGE 18446744071564189696) > (LOADER generic) > (SUSPEND_CANCEL 1) > (ENTRY 18446744071564165120) > (XEN_VERSION xen-3.0) > ) > ) > ) > (status 0) > (device > (vif > (bridge xenbr0) > (mac 00:16:3e:3f:93:b8) > (backend 0) > (uuid 94afd732-920b-2e0b-b3d5-e79174754a80) > (script vif-bridge) > ) > ) > (device > (vbd > (uuid 8f4f4da3-5f8a-3fee-28e8-41dc49e876cd) > (bootable 1) > (driver paravirtualised) > (dev xvda:disk) > (uname file:/var/lib/xen/images/minimal.img) > (mode w) > (backend 0) > ) > ) > (device > (console > (protocol vt100) > (location 2) > (uuid 0046f2d3-058b-d524-9273-f1dac2ca950b) > ) > ) > ) > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- View this message in context: http://www.nabble.com/Guest-shutdown-problems-tp16250249p22845117.html Sent from the Fedora Xen mailing list archive at Nabble.com. From zincumyx at gmail.com Wed Apr 8 06:44:33 2009 From: zincumyx at gmail.com (Yang Xin) Date: Wed, 8 Apr 2009 01:44:33 -0500 Subject: [Fedora-xen] Problem: mount: could not find,filesystem '/dev/root' Message-ID: <5f41cb0c0904072344r12510fefme096f421b9f763f1@mail.gmail.com> Hi, All: I got a problem (mount: could not find,filesystem '/dev/root') in booting a fedora7-xen kernel which was downloaded at http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/kernel-i686. Also I had tried fedora8-xen kernel, same problem. Here is my "grub.conf": title Fedora (2.6.21-7.fc7xen) root (hd0,0) kernel /xen.gz-2.6.21-7.fc7 module /vmlinuz-2.6.21-7.fc7xen ro /dev/VolGroup00/LogVol00 rhgb quiet module /initrd-2.6.21-7.fc7xen.img title Fedora (2.6.27.21-170.2.56.fc10.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.27.21-170.2.56.fc10.i686.PAE ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.27.21-170.2.56.fc10.i686.PAE.img title Fedora (2.6.27.21-170.2.56.fc10.i686) root (hd0,0) kernel /vmlinuz-2.6.27.21-170.2.56.fc10.i686 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.27.21-170.2.56.fc10.i686.img The "ro /dev/VolGroup00/LogVol00 rhgb quiet" part was the same in all the three ones, but "Fedora (2.6.27.21-170.2.56.fc10.i686.PAE)" and "Fedora (2.6.27.21-170.2.56.fc10.i686)" could boot normally (this showed the path should be right). The difference between the first and the latter two was "module", but the tries: title Fedora (2.6.21-7.fc7xen) root (hd0,0) kernel /xen.gz-2.6.21-7.fc7 ro /dev/VolGroup00/LogVol00 rhgb quiet module /vmlinuz-2.6.21-7.fc7xen module /initrd-2.6.21-7.fc7xen.img and title Fedora (2.6.21-7.fc7xen) root (hd0,0) kernel /xen.gz-2.6.21-7.fc7 ro /dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.21-7.fc7xen.img neither worked. My os was Fedora 10, and xen was install by "yum install xen". What should I do for this problem?? By the way, it seemed that "yum install kernel-xen" installed "2.6.27.21-170.2.56.fc10.i686.PAE", which did not worked. Since when I booted with this fedora-xen kernel, "xend start" command (or xm command) brought "ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory)" error, which I've no idea either. (From google, someone told that it was caused by wrong kernel...) Any helps will be very appreciated! Best Regards! Xin -------------- next part -------------- An HTML attachment was scrubbed... URL: From dlbewley at lib.ucdavis.edu Thu Apr 9 23:47:36 2009 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Thu, 09 Apr 2009 16:47:36 -0700 Subject: [Fedora-xen] Problem: mount: could not find,filesystem '/dev/root' In-Reply-To: <5f41cb0c0904072344r12510fefme096f421b9f763f1@mail.gmail.com> References: <5f41cb0c0904072344r12510fefme096f421b9f763f1@mail.gmail.com> Message-ID: <1239320856.14392.13.camel@tofu.lib.ucdavis.edu> On Wed, 2009-04-08 at 01:44 -0500, Yang Xin wrote: > By the way, it seemed that "yum install kernel-xen" installed > "2.6.27.21-170.2.56.fc10.i686.PAE", which did not worked. Since when I > booted with this fedora-xen kernel, "xend start" command (or xm > command) brought "ERROR Internal error: Could not obtain handle on > privileged command interface (2 = No such file or directory)" error, > which I've no idea either. (From google, someone told that it was > caused by wrong kernel...) Since an update to Fedora 9, the kernel-xen package has been obsoleted by the kernel package * http://fedoraproject.org/wiki/FWN/Issue137#kernel-xen_is_Dead * http://docs.fedoraproject.org/release-notes/f10/en_US/What_Do_System_Adminstrators_Care_About.html#sn-Unified_kernel_image The current kernels in F9 and F10 only function as a domU (xen guest). Fedora 10 does not function as a dom0 (xen host). It sounds like your initrd does not have sufficient intelligence to read your root device (hint mkinitrd). I don't even know if you could force a F7 or F8 kernel into F10, but I would not try it. If you need a Xen dom0 then use CentOS, RHEL, or F8 for your server. But F8 is end of life and not receiving any updates, so that is not the safest or recommended route. There are some highly experimental dom0 kernels for F10, but don't expect to use them for anything more than testing. * http://fedoraproject.org/wiki/FWN/Issue170#Experimental_Dom0_Kernel_Update -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From berrange at redhat.com Tue Apr 14 14:36:18 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 14 Apr 2009 15:36:18 +0100 Subject: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> Message-ID: <20090414143618.GH351@redhat.com> On Mon, Mar 30, 2009 at 11:06:57PM +0100, 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. I'm about to try out these kernels, but have one quick suggestion. Add the string 'xendom0' or 'dom0' into the Release: tag of the RPM builds. This'd just make it clear for people installing it which kernel is the Xen dom0 enabled one, and which is not :-) Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From itamar at ispbrasil.com.br Tue Apr 14 14:43:30 2009 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Tue, 14 Apr 2009 11:43:30 -0300 Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: <20090414143618.GH351@redhat.com> References: <20090328163545.GM31725@salstar.sk> <20090414143618.GH351@redhat.com> Message-ID: why not add simple -xen ? like older fedora kernel-xen ? > I'm about to try out these kernels, but have one quick suggestion. > Add the string 'xendom0' or 'dom0' into the Release: tag of the RPM > builds. This'd just make it clear for people installing it which kernel > is the Xen dom0 enabled one, and which is not :-) > > Regards, > Daniel ------------ 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 ondrejj at salstar.sk Tue Apr 14 14:47:04 2009 From: ondrejj at salstar.sk (=?utf-8?B?SsOhbiBPTkRSRUogKFNBTCk=?=) Date: Tue, 14 Apr 2009 16:47:04 +0200 Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> <20090414143618.GH351@redhat.com> Message-ID: <20090414144704.GA3331@salstar.sk> kernel-xen packages are obsoleted by kernel-PAE or kernel packages, so naming it kernel-xen do not allow to install this kernel. But may be a completelly different name, like kernel-xen0 or kernel-xendom0 is a better solution like adding something into Release tag. Each user can have installed dom0 kernel and "classic" kernel on same machine with normal updates. SAL On Tue, Apr 14, 2009 at 11:43:30AM -0300, Itamar Reis Peixoto wrote: > why not add simple -xen ? > > like older fedora kernel-xen ? > > > I'm about to try out these kernels, but have one quick suggestion. > > Add the string 'xendom0' or 'dom0' into the Release: tag of the RPM > > builds. This'd just make it clear for people installing it which kernel > > is the Xen dom0 enabled one, and which is not :-) > > > > Regards, > > Daniel > > > > ------------ > > 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 > > _______________________________________________ > Fedora-virt mailing list > Fedora-virt at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-virt From berrange at redhat.com Tue Apr 14 14:48:42 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 14 Apr 2009 15:48:42 +0100 Subject: [fedora-virt] Re: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> <20090414143618.GH351@redhat.com> Message-ID: <20090414144842.GV14297@redhat.com> On Tue, Apr 14, 2009 at 11:43:30AM -0300, Itamar Reis Peixoto wrote: > why not add simple -xen ? > > like older fedora kernel-xen ? I don't think we want to change the RPM name, since the goal is that the plain 'kernel' RPM contains the Dom0 bits. Since these RPMs of Michael's are sort of a 'preview' of how the end result will look i think just calling it 'kernel' and sticking an identifier in the Release tag is best Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From m.a.young at durham.ac.uk Wed Apr 15 17:57:44 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Wed, 15 Apr 2009 18:57:44 +0100 (BST) Subject: [Fedora-xen] Re: Dom0 kernels In-Reply-To: <20090414143618.GH351@redhat.com> References: <20090328163545.GM31725@salstar.sk> <20090414143618.GH351@redhat.com> Message-ID: On Tue, 14 Apr 2009, Daniel P. Berrange wrote: > On Mon, Mar 30, 2009 at 11:06:57PM +0100, 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. > > I'm about to try out these kernels, but have one quick suggestion. > Add the string 'xendom0' or 'dom0' into the Release: tag of the RPM > builds. This'd just make it clear for people installing it which kernel > is the Xen dom0 enabled one, and which is not :-) I have added xendom0 to the name of the latest build ( 2.6.29.1-1.2.20.xendom0.fc11 ) http://koji.fedoraproject.org/koji/taskinfo?taskID=1299170 for which the main rpms are also available from the repository http://fedorapeople.org/~myoung/dom0/ I based this on the F-11 branch and since that seemed to fit best to what is currently on the upstream git repository, though an updated set of branches should appear shortly (eg. see http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00416.html ) so this may change. Michael Young From samir.selman01 at gmail.com Sun Apr 19 00:44:12 2009 From: samir.selman01 at gmail.com (Samir Selman) Date: Sat, 18 Apr 2009 14:44:12 -1000 Subject: [Fedora-xen] Configuring Xen on FC10 Message-ID: <25ff87d80904181744l6e17566esa6436ce6975330d9@mail.gmail.com> Hi, I am working at Stanford on a research project and I have installed Fedora Core 10. Can someone help me on what are the steps to configure Xen on FC10. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From bernard at si-tech.com.hk Sun Apr 19 02:37:46 2009 From: bernard at si-tech.com.hk (Bernard J Parrett) Date: Sun, 19 Apr 2009 10:37:46 +0800 Subject: [Fedora-xen] Configuring Xen on FC10 In-Reply-To: <25ff87d80904181744l6e17566esa6436ce6975330d9@mail.gmail.com> References: <25ff87d80904181744l6e17566esa6436ce6975330d9@mail.gmail.com> Message-ID: <49EA8E7A.4040405@si-tech.com.hk> Hi I tried this and was told by many people in this site that Fedora no longer supports Kernel-Xen or Dom0 I had to use Centos for the Xen base and Fedora as a client. Regards Samir Selman wrote: > Hi, > > I am working at Stanford on a research project and I have installed > Fedora Core 10. Can someone help me on what are the steps to configure > Xen on FC10. > > Thanks > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bernard.vcf Type: text/x-vcard Size: 327 bytes Desc: not available URL: From stephen at wongstephen.com Sun Apr 19 13:18:21 2009 From: stephen at wongstephen.com (Stephen Wong) Date: Sun, 19 Apr 2009 21:18:21 +0800 Subject: [Fedora-xen] Configuring Xen on FC10 In-Reply-To: <25ff87d80904181744l6e17566esa6436ce6975330d9@mail.gmail.com> References: <25ff87d80904181744l6e17566esa6436ce6975330d9@mail.gmail.com> Message-ID: <4b357ae10904190618o56802f8fs87a0013c098e729@mail.gmail.com> Dear Samir, As I understand, the simple answer is 'no, there is no easy way to run Xen on Fedora10.' At least the current 2.6.27 kernel for Fedora10 cannot run Dom0. If you really want to run Xen, one option is RHEL5.3, or you have to go back to earlier version of FC. My 2 cents. Stephen WONG On Sun, Apr 19, 2009 at 8:44 AM, Samir Selman wrote: > Hi, > > I am working at Stanford on a research project and I have installed Fedora > Core 10. Can someone help me on what are the steps to configure Xen on FC10. > > Thanks > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > From pasik at iki.fi Sun Apr 19 14:38:25 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 19 Apr 2009 17:38:25 +0300 Subject: [Fedora-xen] Configuring Xen on FC10 In-Reply-To: <25ff87d80904181744l6e17566esa6436ce6975330d9@mail.gmail.com> References: <25ff87d80904181744l6e17566esa6436ce6975330d9@mail.gmail.com> Message-ID: <20090419143825.GZ24960@edu.joroinen.fi> On Sat, Apr 18, 2009 at 02:44:12PM -1000, Samir Selman wrote: > Hi, > > I am working at Stanford on a research project and I have installed Fedora > Core 10. Can someone help me on what are the steps to configure Xen on FC10. > http://fedoraproject.org/wiki/Features/XenPvopsDom0 Fedora 8 is currently the latest Fedora release to include dom0 capable kernel. Xen utils/libraries/hypervisor is included in Fedora 9 and 10, and upcoming 11, but dom0 capable kernel is missing until dom0 support is added/included into upstream (Linus) kernel. Your options are: - Use Fedora 8, or RHEL/CentOS 5.3 as your dom0 - Build custom dom0 kernel for your Fedora 10 (xenlinux 2.6.18 or pv_ops dom0) - Use some of the pre-built pv_ops dom0 capable kernels, note they are experimental! - Wait until dom0 capable kernel is back in Fedora (Fedora 12 or so..) See fedora-xen mailinglist archives for more information. -- Pasi From m.a.young at durham.ac.uk Sat Apr 25 12:12:37 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sat, 25 Apr 2009 13:12:37 +0100 (BST) Subject: [Fedora-xen] Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> <20090414143618.GH351@redhat.com> Message-ID: I have some new kernels, available at http://koji.fedoraproject.org/koji/taskinfo?taskID=1319832 and from the repository at http://fedorapeople.org/~myoung/dom0/ . This version (2.6.30-0.1.2.21.rc3.xendom0.fc12) is based on the Fedora devel kernel branch and xen-tip/next branch from the pvops kernel repository http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary . As explained at http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00955.html the branches have been reorganized and the head branches for dom0 are xen-tip/master and xen-tip/next. I may switch to xen-tip/master in future, but there was very little difference between the two when I put together this kernel. Incidentally, very few xen patches made it into 2.6.30, just bugfixes and tidy ups, so we are waiting at least until 2.6.31 for mainline dom0 support. Michael Young From schwier at rvs.uni-hannover.de Wed Apr 29 07:43:34 2009 From: schwier at rvs.uni-hannover.de (Harald Schwier) Date: Wed, 29 Apr 2009 09:43:34 +0200 Subject: [Fedora-xen] Live migration fails depending on on the kernel Version of DomU Message-ID: <49F80526.2030205@rvs.uni-hannover.de> Hi, I'm running a two node cluster xen-Cluster with CentOS 5.3. I'm using gfs2 for the cluster filesystem and kernel 2.6.18-128.1.6.el5xen #1 SMP for the Dom0 kernel. Live migration works fine as long as the DomU guest is running CentOS 5.3 or SLC 4.7 with kernel version 2.6.9-55.EL.cern. But if the SLC 4.7 guest is running the current 2.6.9-78.0.17.EL.cern kernel, the migration freezes without an error message. Any idea why the DomU kernel has an impact on live migration? Is there a possibility to migrate a DomU guest running kernel 2.6.9-78.0.17.EL.cern? Thanks in advance, Harald Migration from hosta to hostb hosta /var/log/xen/xend.log .... [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:510) hotplugStatusCallback 1. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:154) Waiting for devices usb. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:154) Waiting for devices vbd. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:160) Waiting for 768. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:496) hotplugStatusCallback /local/domain/0/backend/vbd/17/768/hotplug-status. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:496) hotplugStatusCallback /local/domain/0/backend/vbd/17/768/hotplug-status. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:510) hotplugStatusCallback 1. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:160) Waiting for 5632. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:496) hotplugStatusCallback /local/domain/0/backend/vbd/17/5632/hotplug-status. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:496) hotplugStatusCallback /local/domain/0/backend/vbd/17/5632/hotplug-status. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:510) hotplugStatusCallback 1. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:154) Waiting for devices irq. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:154) Waiting for devices vkbd. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:154) Waiting for devices vfb. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:154) Waiting for devices pci. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:154) Waiting for devices ioports. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:154) Waiting for devices tap. [2009-04-29 09:05:14 xend 5219] DEBUG (DevController:154) Waiting for devices vtpm. [2009-04-29 09:08:04 xend 5219] DEBUG (XendCheckpoint:89) [xc_save]: /usr/lib64/xen/bin/xc_save 23 17 0 0 5 [2009-04-29 09:08:14 xend 5219] INFO (XendCheckpoint:351) Saving memory pages: iter 1 95%^M 1: sent 982654, skipped 355, delta 9327ms, dom0 57%, target 1%, sent 3452Mb/s, dirtied 1Mb/s 412 pages [2009-04-29 09:08:14 xend 5219] INFO (XendCheckpoint:351) Saving memory pages: iter 2 0%^M 2: sent 398, skipped 15, delta 20 ms, dom0 100%, target 0%, sent 652Mb/s, dirtied 24Mb/s 15 pages [2009-04-29 09:08:14 xend 5219] INFO (XendCheckpoint:351) Saving memory pages: iter 3 0%^M 3: sent 0, skipped 15, Start last iteration [2009-04-29 09:08:14 xend 5219] DEBUG (XendCheckpoint:322) suspend [2009-04-29 09:08:14 xend 5219] DEBUG (XendCheckpoint:92) In saveInputHandler suspend [2009-04-29 09:08:14 xend 5219] DEBUG (XendCheckpoint:94) Suspending 17 ... [2009-04-29 09:08:14 xend.XendDomainInfo 5219] DEBUG (XendDomainInfo:1036) XendDomainInfo.handleShutdownWatch [2009-04-29 09:08:14 xend.XendDomainInfo 5219] DEBUG (XendDomainInfo:1036) XendDomainInfo.handleShutdownWatch hostb /var/log/xen/xend.log .... [2009-04-29 09:08:04 xend 5175] INFO (XendCheckpoint:179) restore hvm domain 11, apic=0, pae=0 [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: boot, val: c [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: fda, val: None [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: fdb, val: None [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: soundhw, val: None [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: localtime, val: None [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: serial, val: pty [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: std-vga, val: None [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: isa, val: None [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: vcpus, val: 1 [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: acpi, val: 1 [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: usb, val: 1 [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: usbdevice, val: None [2009-04-29 09:08:04 xend 5175] DEBUG (image:328) args: k, val: de [2009-04-29 09:08:05 xend 5175] DEBUG (image:388) No VNC passwd configured for vfb access [2009-04-29 09:08:05 xend 5175] DEBUG (XendCheckpoint:198) restore:shadow=0x9, _static_max=0x400, _static_min=0x400, [2009-04-29 09:08:05 xend 5175] DEBUG (balloon:143) Balloon: 29835376 KiB free; need 1065984; done. [2009-04-29 09:08:05 xend 5175] DEBUG (XendCheckpoint:215) [xc_restore]: /usr/lib64/xen/bin/xc_restore 23 11 2 3 1 0 0 [2009-04-29 09:08:05 xend 5175] INFO (XendCheckpoint:351) xc_domain_restore start: p2m_size = 100000 [2009-04-29 09:08:05 xend 5175] INFO (XendCheckpoint:351) Reloading memory pages: 0% From pasik at iki.fi Thu Apr 30 07:14:35 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 30 Apr 2009 10:14:35 +0300 Subject: [Fedora-xen] Live migration fails depending on on the kernel Version of DomU In-Reply-To: <49F80526.2030205@rvs.uni-hannover.de> References: <49F80526.2030205@rvs.uni-hannover.de> Message-ID: <20090430071435.GL24960@edu.joroinen.fi> On Wed, Apr 29, 2009 at 09:43:34AM +0200, Harald Schwier wrote: > Hi, > I'm running a two node cluster xen-Cluster with CentOS 5.3. I'm using > gfs2 for the cluster filesystem and kernel 2.6.18-128.1.6.el5xen #1 SMP > for the Dom0 kernel. > > Live migration works fine as long as the DomU guest is running CentOS 5.3 > or SLC 4.7 with kernel version 2.6.9-55.EL.cern. But if the SLC 4.7 guest is > running the current 2.6.9-78.0.17.EL.cern kernel, the migration freezes > without > an error message. > > Any idea why the DomU kernel has an impact on live migration? Is there a > possibility to migrate a DomU guest running kernel 2.6.9-78.0.17.EL.cern? > Thanks in advance, > Harald > This is fedora-xen list, not centos-virt .. :) This _sounds_ like upstream bug/issue, so you might want to get RHEL support contract and then report it to Redhat.. Or you could try rhelv5-list or xen-devel. I can't really help you with the actual issue.. -- Pasi From urs.golla at gmail.com Thu Apr 30 11:01:49 2009 From: urs.golla at gmail.com (Urs Golla) Date: Thu, 30 Apr 2009 13:01:49 +0200 Subject: [Fedora-xen] Live migration fails depending on on the kernel Version of DomU In-Reply-To: <20090430071435.GL24960@edu.joroinen.fi> References: <49F80526.2030205@rvs.uni-hannover.de> <20090430071435.GL24960@edu.joroinen.fi> Message-ID: <64e30f320904300401i6923122ehb7e59c2b8293d087@mail.gmail.com> what is the architecture of Dom-0 and userdomain? both the same (e.g. 32bit)? On Thu, Apr 30, 2009 at 9:14 AM, Pasi K?rkk?inen wrote: > On Wed, Apr 29, 2009 at 09:43:34AM +0200, Harald Schwier wrote: >> Hi, >> I'm running a two node cluster xen-Cluster with CentOS 5.3. I'm using >> gfs2 for the ?cluster filesystem and kernel 2.6.18-128.1.6.el5xen #1 SMP >> for the Dom0 kernel. >> >> Live migration works fine as long as the DomU guest is running CentOS 5.3 >> or SLC 4.7 with kernel version 2.6.9-55.EL.cern. But if the SLC 4.7 guest is >> running the current 2.6.9-78.0.17.EL.cern kernel, the migration freezes >> without >> an error message. >> >> Any idea why the DomU kernel has an impact on live migration? Is ?there a >> possibility to migrate a DomU guest running kernel 2.6.9-78.0.17.EL.cern? >> Thanks in advance, >> Harald >> > > This is fedora-xen list, not centos-virt .. :) > > This _sounds_ like upstream bug/issue, so you might want to get RHEL support > contract and then report it to Redhat.. > > Or you could try rhelv5-list or xen-devel. > I can't really help you with the actual issue.. > > -- Pasi > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen >