From: Guryanov Dmitry <dimak@dgap.mipt.ru>
To: xen-devel@lists.xensource.com
Subject: Bugs with block devices to domU - let's find solution
Date: Tue, 18 Oct 2005 21:06:51 +0400 [thread overview]
Message-ID: <43552BAB.8@dgap.mipt.ru> (raw)
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 ?
P.S.
To start domU i comment out block in backend driver, where this
parameter must be obtained and give explicitly value for that variable:
file - linux-.../drivers/xen/blkback/xenbus.c
function - backend_changed
replace
---------------------
err = xenbus_scanf(NULL, dev->nodename,
"physical-device", "%li", &pdev);
if (XENBUS_EXIST_ERR(err))
return;
---------------------
with, for example:
---------------------
pdev=0x307; //hda7 - physical device
err=1;
---------------------
--
Guryanov Dmitry
next reply other threads:[~2005-10-18 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 17:06 Guryanov Dmitry [this message]
2005-10-19 12:56 ` Bugs with block devices to domU - let's find solution Ewan Mellor
2005-10-19 15:03 ` Guryanov Dmitry
-- 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=43552BAB.8@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.