From: Christophe Saout <christophe@saout.de>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: pv_ops dom0 and starting domU with vif's / vbd's attached?
Date: Thu, 05 Mar 2009 02:06:10 +0100 [thread overview]
Message-ID: <1236215170.4898.7.camel@leto.intern.saout.de> (raw)
Hi,
ok, dom0 support in the latest xen/dom0/hackery seems to be getting into
a real usable state (for those who are lucky to get it booting).
I've been able to start a domU, but unfortunately only without vif and
vbd attached. If I try that I get a timeout creating the device.
I am wondering where this could be not working. Both dom0 and domU have
both blk/net backends and frontends enabled (CONFIG_...=y).
xend seems to be telling xenstored everything and then waits for the
devices to come up, but they never do. I have been strace'ing udevd,
but I don't see any activity here, nor any log entries or anything, also
browsing through /sys doesn't show any devices appearing while waiting
for the hotplug event. Am I missing something or is this not yet
suppose to work? (I tried hard to find something on this list, but
didn't)
I don't really understand how the devices are supposed to be created.
It seems that there are xenbus messages changing somesthing and the
xenwatch process is supposed to pick up the changes and trigger the
device creation in blkback/netback, but that's as far as my
understanding goes (or I am even wrong about that). Any way to debug
this?
Thanks,
Christophe
next reply other threads:[~2009-03-05 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 1:06 Christophe Saout [this message]
2009-03-05 1:29 ` pv_ops dom0 and starting domU with vif's / vbd's attached? Jeremy Fitzhardinge
2009-03-05 1:43 ` Christophe Saout
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=1236215170.4898.7.camel@leto.intern.saout.de \
--to=christophe@saout.de \
--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.