WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] failed startup caused by unpriveledged domain device nod

To: Mark Williamson <Mark.Williamson@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] failed startup caused by unpriveledged domain device nodes not present in priviledged domain
From: Scott Mohekey <smohekey@xxxxxxxxxxxxxxxx>
Date: Thu, 23 Dec 2004 13:00:30 +1300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 23 Dec 2004 00:02:14 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <200412221257.28044.maw48@xxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <41C96A74.6090308@xxxxxxxxxxxxxxxx> <200412221257.28044.maw48@xxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20041211)
Thanks, using the number manually worked perfectly. However, now I'm back to the original error I was having in another post:

Using config file "/etc/xen/ns1".
Error: Error creating domain: vbd: Segment not found: uname=phy:fs/ns1

This is after entering:
xm create ns1 -c

Thanks for your time.
Scott.

Mark Williamson wrote:

Using config file "/etc/xen/ns1".
Error: Error creating domain: vbd: Device not found: sda1

Xend uses the local device nodes in domain zero to look up the major / minor numbers for a virtual device before creating it.

On udev / devfs dom0s this problem does crop up, so it's also possible to specify the the device node number manually: try replacing sda1 with 0801.

Cheers,
Mark

If I replace sda1 with hdc it works (except that it now complains about
sda2).

This strikes me as odd behaviour, shouldn't the device nodes in the
priviledged domains be largely irrelevant for the unpriviledged domains
(in the case of vbds at any rate)?

Thanks in advance,
Scott.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel