This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] VM does not start after shutdown

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] VM does not start after shutdown
From: "Petrescu, Florin" <fpetrescu@xxxxxxxxxxxxxxxx>
Date: Mon, 21 Jun 2010 17:14:25 -0500
Delivery-date: Mon, 21 Jun 2010 15:17:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcsRjxu3gDS1M6jwQzG5FwWESKWp/w==
Thread-topic: VM does not start after shutdown

I have 5 “identical” VMs, created from a “golden_copy” of an install of Centos 5.5.


I have used :

xm shutdown –a –w

to shutdown all VMs, and wait for each of them to come down gracefully.


However, after restarting, one of the VM is not coming up anymore, with a “device 0 not connected” error.


Traceback (most recent call last):

  File "/usr/share/virt-manager/virtManager/engine.py", line 493, in run_domain


  File "/usr/share/virt-manager/virtManager/domain.py", line 558, in startup


  File "/usr/lib64/python2.4/site-packages/libvirt.py", line 293, in create

    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)

libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 0 not connected')


here is the /var/log/xen/ qemu-dm log file:


domid: 15

qemu: the number of cpus is 2

config qemu network with xen bridge for  tap15.0 xenbr0

Watching /local/domain/0/device-model/15/logdirty/next-active

Watching /local/domain/0/device-model/15/command

char device redirected to /dev/pts/11

qemu_map_cache_init nr_buckets = 10000 size 4194304

shared page at pfn feffd

buffered io page at pfn feffb

Guest uuid = 75034f1e-b4df-ed75-17d1-1e17b6ddc255

Time offset set 0

populating video RAM at ff000000

mapping video RAM from ff000000

Register xen platform.

Done register platform.

xs_read(/vm/75034f1e-b4df-ed75-17d1-1e17b6ddc255/log-throttling): read error

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.

xs_read(/local/domain/0/device-model/15/xen_extended_power_mgmt): read error

xs_read(): vncpasswd get error. /vm/75034f1e-b4df-ed75-17d1-1e17b6ddc255/vncpasswd.

bind() failed



What is at issue? Any hints would be highly appreciated.







The materials in this message are private and may contain Protected Healthcare Information. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>