From: "Jonathan M. McCune" <jonmccune@cmu.edu>
To: xen-users@lists.xensource.com, xen-devel@lists.xensource.com
Subject: Error: Device 768 (vbd) could not be connected. Backend device not found.
Date: Wed, 19 Apr 2006 10:12:04 -0400 [thread overview]
Message-ID: <44464534.1090009@cmu.edu> (raw)
Hello,
I am getting this error when I try to start an HVM guest on an AMD
Sahara system. The xen-unstable-hvm.hg revision 8724 works fine. I
tried to upgrade to xen-unstable.hg revision 9668. I got 9668 to boot
using 'yaird' to build the initrd for the -xen kernel. I can
successfully start a paravirtualized guest, but I am now having trouble
starting an HVM guest. The error message is:
Error: Device 768 (vbd) could not be connected. Backend device not found.
I googled a bit and other people have seen this error, but no solutions
seem to be presented.
Each attempt to start the domain puts a line like the following in
/var/log/xen-hotplug.log (The '8' here is the domain ID):
xenstore-read: couldn't read path backend/vbd/8/768/node
Here is my config file:
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 260
name = "Sarge"
disk = [ 'file:/sarge/disk.img,ioemu:hda,w' ]
vif = [ 'type=ioemu, mac=00:14:bf:52:df:5e, bridge=xenbr0' ]
device_model = '/usr/lib/xen/bin/qemu-dm'
memmap = '/usr/lib/xen/boot/mem-map.sxp'
boot='c'
sdl=1
vnc=0
I have made sure that xend and xenstored are running, but I'm not sure
what else to check (it works on the older Xen!). Any suggestions would
be greatly appreciated.
Thanks,
-Jon
next reply other threads:[~2006-04-19 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 14:12 Jonathan M. McCune [this message]
2006-04-19 14:52 ` Error: Device 768 (vbd) could not be connected. Backend device not found Ryan Harper
-- strict thread matches above, loose matches on Subject: below --
2006-04-19 14:27 Petersson, Mats
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44464534.1090009@cmu.edu \
--to=jonmccune@cmu.edu \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.