From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: Error: Device 768 (vbd) could not be connected. Backend device not found. Date: Wed, 19 Apr 2006 09:52:15 -0500 Message-ID: <20060419145215.GQ16776@us.ibm.com> References: <44464534.1090009@cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <44464534.1090009@cmu.edu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Jonathan M. McCune" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org * Jonathan M. McCune [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. > 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