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

[Xen-users] Error: ... Backend device not found.



One problem and one question to xen

1.
I can't create a domU. This following error I get. Once it seemed that domU was started because xm list was showing etch03 running but xm console etch03 points to an error and etch03 crashed.

server1:/vd# xm create -c etch03.cfg
Using config file "/etc/xen/etch03.cfg".
Error: Device 771 (vbd) could not be connected. Backend device not found.

---
title           Xen 3.0.3-1-i386 / Debian GNU/Linux, kernel 2.6.18-5-xen-686
root            (hd0,0)
kernel          /xen-3.0.3-1-i386-pae.gz
module /vmlinuz-2.6.18-5-xen-686 root=/dev/md1 ro xencons=off console=tty0
module          /initrd.img-2.6.18-5-xen-686
savedefault
---

...
kernel = "/boot/vmlinuz-2.6.18-5-xen-686"
ramdisk = "/boot/initrd.img-2.6.18-5-xen-686"

disk = ['file:/vd/etch03.vd,hda3,w','file:/vd/etch03.sd,hda2,w']
...

2.
I'm also not sure if I should use xen-3.0.3-1-i386.gz instead of xen-3.0.3-1-i386-pae.gz, but xen-3.0.3-1-i386-pae.gz boots the dom0 and xen-3.0.3-1-i386.gz does'nt. The maschine has only 512 MB RAM so I think its not nessesary to use xen-3.0.3-1-i386-pae.gz. Does it makes a big differens to use xen-3.0.3-1-i386-pae.gz instead of xen-3.0.3-1-i386.gz if this case?

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

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