xen March 2009

xen@lists.fedoraproject.org

21 participants
18 discussions

Dom0 kernels
by M A Young 13 Mar '10

13 Mar '10

I have built a new set of kernel packages based on fedora rawhide kernels and the xen/dom0/hackery branch of Jeremy's git repository ( http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary ). This batch (kernel-2.6.29-0.114.2.6.rc6.fc11) is available via the koji build system at http://koji.fedoraproject.org/koji/taskinfo?taskID=1149500 These are really for development and debugging purposes only, as I am still having problems getting them to boot, but others have reported more success at getting kernels based on this git repository working, so you might be lucky. Note to install these packages on Fedora 10 you will need to have rpm-4.6.0-1.fc10 installed (currently in updates-testing but it should be available in updates soon) because of the change to SHA-256 file digest hashing in recent Fedora 11 builds. Michael Young

12 99

Success with Fedora 10 Xen pv_ops 2.6.29-rc8 dom0
by Pasi Kärkkäinen 27 Jul '09

27 Jul '09

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

2 7

Guest shutdown problems
by Christian Axelsson 02 Apr '09

02 Apr '09

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@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(a)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) ) ) )

3 3

Network issues with F11 guests
by Orion Poplawski 25 Mar '09

25 Mar '09

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(a)cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com

1 0

Need help for thesis on Xen - disabling HAP for benchmarking purposes
by Alexander Sascha 24 Mar '09

24 Mar '09

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 <hap>0</hap>. 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

1 0

virt-install (and virt-manager) unsupported virtualization type 'xen' with pv_ops dom0 on Fedora 10
by Pasi Kärkkäinen 23 Mar '09

23 Mar '09

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… 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@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/…" ERROR Unsupported virtualization type 'xen' Has Xen support been dropped from virt-install, or is this just some bug? -- Pasi

3 15

Re: [Fedora-xen] Fedora 10 on RHEL5.3 x86_64
by Mathieu Chouquet-Stringer 23 Mar '09

23 Mar '09

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(a)free.fr The sun itself sees not till heaven clears. -- William Shakespeare --

2 2

kvm memory corruption?
by William John Murray 20 Mar '09

20 Mar '09

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

2 4

ia64 HVM network problem !!!
by shoom 17 Mar '09

17 Mar '09

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 ?

1 0

configuration files
by Urs Golla 16 Mar '09

16 Mar '09

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

5 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen March 2009