All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: "Jonathan M. McCune" <jonmccune@cmu.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: Error: Device 768 (vbd) could not be connected. Backend device not found.
Date: Wed, 19 Apr 2006 09:52:15 -0500	[thread overview]
Message-ID: <20060419145215.GQ16776@us.ibm.com> (raw)
In-Reply-To: <44464534.1090009@cmu.edu>

* Jonathan M. McCune <jonmccune@cmu.edu> [2006-04-19 09:14]:
> 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.
<snip>
> disk = [ 'file:/sarge/disk.img,ioemu:hda,w' ]

I got this when the loop driver (which is a module in -xen kernel config
is used) wasn't loaded.  Try modprobe loop, and re-run your create
command.


-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

  reply	other threads:[~2006-04-19 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 14:12 Error: Device 768 (vbd) could not be connected. Backend device not found Jonathan M. McCune
2006-04-19 14:52 ` Ryan Harper [this message]
  -- 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=20060419145215.GQ16776@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=jonmccune@cmu.edu \
    --cc=xen-devel@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.