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: Mon, 20 Jun 2005 16:28:12 +0100
Cc: Sascha Retzki <sretzki@xxxxxx>
Delivery-date: Mon, 20 Jun 2005 15:34:03 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050620151255.GB29014@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> <200506191708.56556.mark.williamson@xxxxxxxxxxxx> <20050620151255.GB29014@MEniac>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
> ah ok. A question: Why the the error-message that cryptic :) ?
> Isn't it (easily) possible to give out the involved line, or a short
> description why it failed or at least replacing "segment" with "device"?
> (The latter is another question, why is it a "segment"?)

Yes, this error probably should be made a bit more descriptive.  It probably 
hasn't got done yet because it doesn't come up often - just that when it does 
it really confuses people!

The message says "segment" for historical reasons: the block backend used to 
implement a basic LVM-style concatenated device abstraction.  The devices the 
guest saw were made up of "segments" of real disks.  Since the restructure 
for Xen 2.0 this is not necessary, since we can use real LVM where this 
capability is required.

> (The NetBSD-guide noted that xen wants to look-up the second argument,
> and make something so linux likes it better or whatever; However the guide
> says that xen would try to lookup hde1 on netbsd (that is not there);
> Said guide is http://www.NetBSD.org/Ports/xen/howto.html . Scroll down to
> "Create Linux unprivileged domains". (Actually, is major << 8 + minor of
> hde1 0x3301 :D ?))

At some point, Xend acquired code to convert handle Linux-style devices even 
if there aren't corresponding device nodes present - so it might Just Work 
with the Linux device name.

Your devid looks OK, though.

> However, that also gives me that error, so "uname=phy:/dev/wd0a". And trust
> me, that is there ;)

Interesting.  That device isn't mounted or something is it?  If it is, the 
tools should stop you using it, although IIRC they should produce a more 
useful error message in this case.

> > If you can get this working, then a patch would be very welcome.
> Well I deleted the sed-part that made /dev/ disappear. This time I
> get the old error, device (vbd (uname file:/xen/...) (dev hda1) (mode w)),
> error 8

Hmmm, weird.  It might be worth poking in the Xen code and trying to figure 
out where this error is coming from.  Could it actually be an errno value?


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

Xen-users mailing list