[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Rebooting a DomU in xen 4.1.3 from within the DomU gives "failed to run bootloader: -3"



Hi all,
after upgrading to Xen-4.1.3 on an Ubuntu, restarting the guest (shutdown -r now) gives the error "failed to run bootloader: -3"
Starting the guest from Dom0 works though
I could reboot a guest from within while running on 4.1.2

The log :

root@dctst0007:~# cat /var/log/xen/xl-25662.log
Waiting for domain 25662 (domid 28) to die [pid 23663]
Domain 28 is dead
Action for shutdown reason code 1 is restart
Domain 28 needs to be cleaned up: destroying the domain
libxl: debug: libxl_dm.c:754:libxl__destroy_device_model Device Model signaled
Done. Rebooting now
libxl: debug: libxl.c:1080:libxl_device_disk_local_attach attaching PHY disk /dev/iscsi/4e2345eebe1347a0 to domain 0
failed to run bootloader: -3


Configfile :
root@dctst0007:~# cat /var/lib/xend/domains/25662/config.cfg
bootloader="/usr/lib/xen-4.1/bin/pygrub"
uuid="5a657ce6-e401-44fe-80ac-1f0bf0ea324b"
usbdevice="tablet"
device_model="/usr/lib/xen-4.1/bin/qemu-dm"
builder="linux"
vnclisten="0.0.0.0"
vfb=['type=vnc,vnclisten=0.0.0.0']
>
>
vcpus=1
memory=1024
real_disk=['']
disk=['phy:/dev/iscsi/4e2345eebe1347a0,xvda,w']
maxvcpus=1
name="25662"

Someone any idea ? 
What info can I provide you with ?

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.