xen June 2008

xen@lists.fedoraproject.org

39 participants
24 discussions

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

problems with f9 guest on f8 dom0
by Matt Cowan 22 Sep '08

22 Sep '08

Anytime I shutdown or restart (the guest will successfully restart) an f9 guest on an f8 dom0 it causes virt-manager to hang and virt-install to fail. Attempts to restart virt-manager hang at "Connecting". no luck restarting xend, libvirtd, or even xenstored, only solution I've found is a dom0 reboot! Same problem on 2 different host systems, different hardware, dom0 installed by different people. I have no trouble with <=f8 guests on either of these boxes. more details at https://bugzilla.redhat.com/show_bug.cgi?id=429403#c7 I assume other people are successfully running f9 guests on f8 dom0?! No one else having this issue? thanks. -matt

5 12

Cannot start HVM DomU
by Robert Locke 04 Jul '08

04 Jul '08

This has newly started, so I am presuming that it is perhaps related to some recently updated package on F8 in say the last week or so. I have a WindowsXP DomU that when I try to start from virt-manager gives the following error: Error starting domain: virDomainCreate() failed POST operation failed: (xend.err 'int argument required') Details shows: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 472, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 379, in startup self.vm.create() File "/usr/lib/python2.5/site-packages/libvirt.py", line 240, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: virDomainCreate() failed POST operation failed: (xend.err 'int argument required') I have no idea what other information to supply or where to particularly find it since this has generally "just worked" for the occasional running of a Windows instance that I have needed for the last several months. Thanks for any help, --Rob

2 2

xen to kvm migration question
by Paul Wouters 29 Jun '08

29 Jun '08

Hi, Although I was very happy with xen, it seems xen is losing out and kvm is the way to go. I had two migration questions that I couldn't find answers for. 1) Does kvm also run with para_virt (eg without VT capable cpu, but also just to be slightly more effecient). virt-manager only gave me a qemu option on my old amd64 cpu. 2) I boot all my xens using kernel+initrd outside a rootfs image, instead of a bootable virtual disk. Is that possible with kvm, or will I be stuck creating bootable disk images? Paul

4 8

PCI passthrough
by Andy Burns 28 Jun '08

28 Jun '08

I have an F8 dom0 (which could become a CentOS 5.2 dom0 if that would make anything easier) I'd like an F9 domU to have access to a PCI DVB tuner for a mythtv backend. I understand that I need to add "pciback.hide=(XX:YY.Z)" and possibly "pciback.permissive" to grub.conf for the dom0 How should I add the details of the corresponding "pci = ['XX:YY.Z']" to the domU config? I've looked in the documentation of the XML format at http://libvirt.org/formatdomain.html but can't see relevant tags.

1 2

Alistair J McGhie/AE/DuPont is out of the office.
by Alistair J McGhie 28 Jun '08

28 Jun '08

I will be out of the office starting 06/28/2008 and will not return until 07/08/2008. I will respond to your message when I return. Alistair This communication is for use by the intended recipient and contains information that may be Privileged, confidential or copyrighted under applicable law. If you are not the intended recipient, you are hereby formally notified that any use, copying or distribution of this e-mail, in whole or in part, is strictly prohibited. Please notify the sender by return e-mail and delete this e-mail from your system. Unless explicitly and conspicuously designated as "E-Contract Intended", this e-mail does not constitute a contract offer, a contract amendment, or an acceptance of a contract offer. This e-mail does not constitute a consent to the use of sender's contact information for direct marketing purposes or for transfers of data to third parties. Francais Deutsch Italiano Espanol Portugues Japanese Chinese Korean http://www.DuPont.com/corp/email_disclaimer.html

1 0

AUTO: Alex Upton is out of the office (returning 06/28/2008)
by Alex.Upton＠instinet.com 27 Jun '08

27 Jun '08

I am out of the office until 06/28/2008. I'm out of the office, please direct any support related issues to the "TSG SA" team. Any issues in need of escalation should be sent directly to Bob Sinko during this time. Thank you, Alex Note: This is an automated response to your message "Re: [Fedora-xen] xen to kvm migration question" sent on 6/27/2008 6:26:46 PM. This is the only notification you will receive while this person is away. ***************************************************************** <<<Disclaimer>>> In compliance with applicable rules and regulations, Instinet reviews and archives incoming and outgoing email communications, copies of which may be produced at the request of regulators. This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. Instinet accepts no liability for any content contained in the email, or any errors or omissions arising as a result of email transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. Instinet does not make recommendations of a particular security and the information contained in this email should not be considered as a recommendation, an offer or a solicitation of an offer to buy and sell securities. *****************************************************************

1 0

No Dom0 support in Fedora 9 and Fedora 8 EOL
by Martin Vuille 26 Jun '08

26 Jun '08

I'm putting together a virtualized server. I was planning to use Fedora 9, until I found out that Fedora 9 won't run as a Dom0, so I ended up using Fedora 8 instead. I also learned that the standard EOL policy is to discontinue support for release N one month after the release of release N+2. Since Dom0 support isn't expected until Fedora 10, it sounds like this means that I will have to upgrade my system in the first month immediately following the release of Fedora 10, or lose support. Neither option seems particularly reasonable to me. Since upgrading from Fedora 8 to Fedora 9 isn't an option for anyone using Xen, I am wondering if there is any plan to extend Fedora 8's support period beyond the usual one month? MV

6 11

Xen guests on the local network
by Dustin Black 25 Jun '08

25 Jun '08

I find that Fedora 8 is using a DHCP service via libvirtd/qemu to assign addresses to any guests that I create. I also see that libvirtd enables ip forwarding and creates iptables entries to allow the Xen server to act as a router for the guests. I need to change this setup such that the guests appear on the same network as the Xen server, and are able to receive DHCP assignments from another server on the network. It may be that I just haven't chosen the right terms to search for, but I can't seem to find any documentation or reference to disabling or bypassing the qemu dhcp assignment and libvirt routing. Any help would be much appreciated. -Dustin Black

2 2

Does my kernel support svm?
by Martin Jürgens 23 Jun '08

23 Jun '08

Hi, I read the Virtualization guide and installed a Xen kernel on my Fedora 8 system. The problem is that the Virtualization Guide says that I'd issue xm dmesg | grep SVM to find out if my Kernel supports svm. It says the following: # xm dmesg | grep SVM (XEN) AMD SVM: ASIDs disabled. (XEN) HVM: SVM enabled (XEN) AMD SVM: ASIDs disabled. As I can't select "hardware acceleration" in virt-manager I think that it means that something's wrong and I currently can't use svm. Does anyone have an idea about what's wrong? Thank you, Martin

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen June 2008