xen August 2008

xen@lists.fedoraproject.org

23 participants
20 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

ANNOUNCE: virt-what 1.0 - a shell script to detect if you are running in a virtual machine
by Richard W.M. Jones 31 Aug '08

31 Aug '08

I'm pleased to announce the first release of 'virt-what', which is a simple shell script that detects if you are running inside a virtual machine, and prints some "facts" about that virtual machine. This is a frequently requested feature. Home page: http://et.redhat.com/~rjones/virt-what/ Source and RPMs: http://et.redhat.com/~rjones/virt-what/files/ So far we can detect: - Xen - QEMU and KVM (but not distinguish between them) - VMware - Microsoft VirtualPC I'm hoping that people who run or develop other virtualization technology will be able to contribute snippets to detect those. It's worth saying (before Dan Berrange says it anyway) that although people often think they need this sort of feature, in most cases using this script is the WRONG THING. If you need a specific virtualization feature, then add code to your application to detect that feature. eg. If you need to make Xen hypervisor calls, your application should try to open /proc/xen/privcmd. As Dan once put it: A shell script just printing out 'native', 'dom0' or 'domU' is too simplistic to be broadly useful to management applications. The concepts are also ill-defined, eg 'native' as a concept can be a baremetal kernel, or a fully-virtualized guest, or both. 'DomU' does not distinguish full or paravirt. The distinction of 'dom0' vs 'native' is irrelevant in non-Xen virtualization systems (eg KVM). Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top

2 2

Is it possible to run F8-DomUs under Fedora 10-Dom0?
by Franz Von Hahn 30 Aug '08

30 Aug '08

Hey, I'm a bit confused, if it will be possible to run a F8-DomU on top of a Fedora10-Dom0? Currently I'm using a Fedora8-DomU with PCI-Passthrough on a Fedora8-Dom0 for being able to use an ISDN-Card with badly designed drivers. And since the vendor's closed souce driver doesn't support kernel versions >= 2.6.22, it would be great, if i could still use that ISDN-Card in it's existing DomU without losing the benefits of upcoming Fedora 10. Greets, FvH __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com

2 1

[Xen-devel] ANNOUNCE: Xen 3.3.0 released!
by Pasi Kärkkäinen 23 Aug '08

23 Aug '08

----- Forwarded message from Keir Fraser <keir.fraser(a)eu.citrix.com> ----- From: Keir Fraser <keir.fraser(a)eu.citrix.com> To: "xen-devel(a)lists.xensource.com" <xen-devel(a)lists.xensource.com> Date: Fri, 22 Aug 2008 12:53:35 +0100 Subject: [Xen-devel] ANNOUNCE: Xen 3.3.0 released! Folks, We're pleased to announce the official release of Xen 3.3.0! This is a major new release with a host of new features including: - Power management (P & C states) in the hypervisor - HVM emulation domains ('qemu-on-minios') for better scalability, performance and security - PVGrub: boot PV kernels using real GRUB inside the PV domain - Better PV performance: domain lock removed from pagetable-update paths - Shadow3: optimisations to make this the best shadow pagetable algorithm yet, making HVM performance better than ever - Hardware Assisted Paging enhancements: 2MB page support for better TLB locality - CPUID feature levelling: allows safe domain migration across systems with different CPU models. - PVSCSI drivers for SCSI access direct into PV guests - HVM framebuffer optimisations: scan for framebuffer updates more efficiently - Device passthrough enhancements - Full x86 real-mode emulation for HVM guests on Intel VT: supports a much wider range of legacy guest OSes - New qemu merge with upstream development - Many other changes in both x86 and IA64 ports You can get the source using mercurial from: http://xenbits.xensource.com/xen-3.3-testing.hg A pre-prepared source tarball is available from: http://www.xen.org/download/ (please ignore the 'Xen 3.2' graphic used in the download listing :-). Cheers, Keir (on behalf of the whole Xen dev team) _______________________________________________ Xen-devel mailing list Xen-devel(a)lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message -----

1 0

F10 crystal ball gazing
by Andy Burns 23 Aug '08

23 Aug '08

Given that xen is entering feature freeze for updated release ~August is it too early to ask what the *hopes* are for xen in fedora10? xen 3.3.0 (or late rc) or is this still likely to be 3.2.1 or 3.2.2? kernel 2.6.27(or late rc) with pv_ops for 32 and 64 bit, dom0 and domU? oVirt? updates to libvirt/virt-manager as usual

5 18

sd_mod and selinux problem using f8xen kernel on f9 system
by Paul Wouters 20 Aug '08

20 Aug '08

Hey, So I'm using F9 on a laptop installed with rootfs disk encryption. Now I wanted to run a dom0 xen on it, so i had to go back to a 2.6.21 based f8 kernel. This kernel did not boot, due to sd_mod not being included in the initrd. scsi_mod is there, but sd_mod is not. Rebuilding the fc8xen initrd on f9 using mkinitrd --preload sd_mod resolved that issue. Additionally, there is a missing "clear" somewhere, so the xen boot lines and the kernel boot lines interleave badly. Where should I report this so the next f8xen kernel update will have that fixed? Next, I'm getting the following error, after unlocking the encrypted rootfs: security: class 31 is incorrect, found x_drawable, but should be drabable security: the definition of a class is incorect SElinux: Could not load policy file /etc/selinux/targeted/policy/policy.23: Invalid argument and then the machine halts. Note that f9 has been the first version where I didnt run into SElinux issues and I'm surprised that I found myself not disabling it yet, so congrats on that front. Paul

1 1

starting XEN with /usr mounted through NFS
by Luca 20 Aug '08

20 Aug '08

Hi all, I'm trying to boot Xen mounting the /usr directory through NFS. I get though the following error: Starting xen daemons: xenstored blktapctrl xenconsoled xendTraceback (most recent call last): File "/usr/sbin/yum-updatesd", line 39, in <module> import gamin File "/usr/lib64/python2.5/site-packages/gamin.py", line 39, err = _gamin.Errno() TabError: inconsistent use of tabs and spaces in indentation Does anyone know what that means? Thanks, Luca

2 1

Creating VMs on Fedora Dom0 using config files
by Marcel Damásio 18 Aug '08

18 Aug '08

Hello everybody! I'm trying to create a Debian DomU on a Fedora Dom0. I can't do this using virt-install and I don't know how to use config files to create a VM on a Fedora Dom0 (I just know on Debian Dom0, using xen-create-image script). Could someone help me? -- Marcel Damásio Moreira 9º período de Ciência da Computação - UFES (27) 8128-7106 Estagiário do NPD - UFES

2 2

Installing FC9 guest on Centos 5 fails installing OO writer2latex
by Kenneth Tanzer 13 Aug '08

13 Aug '08

I've tried three times to install Fedora Core 9 as a PV guest on a Centos 5 host. Every time, it gets most of the way through the install, and then hangs on installing openoffice.org-writer2latex-0.5-2.fc9.i386. The first two attempts were with the official FC9 DVD, and for the third I tried the Unity respin from 7/18/08. Does anyone know what the problem could be? Alternatively, what useful information could I provide to this list? Thanks. Ken

7 10

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen August 2008