This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] help with "error extent to vbd failed: ... error 8"

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] help with "error extent to vbd failed: ... error 8"
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Sun, 19 Jun 2005 17:08:56 +0100
Cc: Sascha Retzki <sretzki@xxxxxx>
Delivery-date: Sun, 19 Jun 2005 16:14:36 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050612093514.GB12852@MEniac>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D2821BA@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20050612093514.GB12852@MEniac>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
> > > My dom0-OS is NetBSD 3.0_BETA, btw. This may explain a lot,
> > > still I'd like to have as much detailed information as possible ;)

I imagine the error is just a "command not found error" - it's not a normal 
Xend error.

> > I'll bet you'll need to hack the /etc/xen/scripts/block-file script to
> > work on NetBSD unless the syntax for losetup is identical.
> Ah, so those files are loopmounted, like in mount -o loop ...?

Yes, basically. (They're bound to a loop device but not actually mounted).

> (Net,Open, Maybe DragonFly)BSD use a different system, with slightly
> other syntaxes. Here is the diff I hacked quickly (just taking NetBSD
> into account):

Ah, great.  I thought it probably wouldn't work on BSD :-)  I did wonder what 
the NetBSD guys had done about it.

> If you prefer a different diff(1) method, tell me :)

Thanks for the patch.  We should get it merged once you can confirm 
everything's working as expected!

> However, that gives me:
> Error: Error creating domain: vbd: Segment not found:
> uname=file:/xen/slackware-linux-10/linux.img
> I don't know how that "uname=" thing came into there

The "uname" format is the {file,phy,nbd}:/{path}:{other stuff} form we use to 
describe the "source device" in dom0.

The "segment not found" message suggests that the device node output from the 
block script was not found in /dev.  That's probably because you're stripping 
off the "/dev" prefix in order to fit with the BSD command syntax.  Xend 
probably needs the full path in order to find the device node - if you 
prepend /dev to the name of the device before the script echos it then it 
should work.

If you can get this working, then a patch would be very welcome.


Xen-users mailing list