From: Guryanov Dmitry <dimak@dgap.mipt.ru>
To: xen-devel@lists.xensource.com
Subject: Re: Bugs with block devices to domU - let's find solution
Date: Wed, 19 Oct 2005 19:03:15 +0400 [thread overview]
Message-ID: <43566033.8050205@dgap.mipt.ru> (raw)
In-Reply-To: <20051019125634.GI26910@leeni.uk.xensource.com>
Ewan Mellor wrote:
>On Tue, Oct 18, 2005 at 09:06:51PM +0400, Guryanov Dmitry wrote:
>
>
>
>>Hello
>>
>>I have the same bug, that've been disscussed before - domU can't find
>>any block devices and crashes with "Unable to mount root fs". I've spend
>>a week under heavy debugging and find, that this bug take place because
>>dom0 backend driver can't read parameter physical-device from xenstore.
>>For example /local/domain/0/backend/vbd/1/776/physical_device, where 1-
>>domU id, 776=0x308 - major and minor numbers of block device, which will
>>used by domU.
>>This parameter must be written by script /etc/xen/scripts/block, which
>>must start like /etc/xen/scripts/vif-bridge any time as domU starts, but
>>it doesn't.
>>
>>So, there is a question to xen developers: when and how must this script
>>must been started ?
>>
>>
>
>This script is run by your hotplug / udev installation inside dom0 when the
>domU starts up. Do you have hotplug and udev installed in dom0?
>
>
>
>Ewan.
>
>
>
Thanks, that's was a bug, now it works properly.
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2005-10-19 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 17:06 Bugs with block devices to domU - let's find solution Guryanov Dmitry
2005-10-19 12:56 ` Ewan Mellor
2005-10-19 15:03 ` Guryanov Dmitry [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-18 17:23 Stephan Boni
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=43566033.8050205@dgap.mipt.ru \
--to=dimak@dgap.mipt.ru \
--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.