From: NAHieu <nahieu@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Chris Bainbridge <chris.bainbridge@gmail.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Cannot create domU
Date: Sun, 25 Sep 2005 02:32:15 +0900 [thread overview]
Message-ID: <5d7aca95050924103260c3ecaf@mail.gmail.com> (raw)
In-Reply-To: <9f173d1d7dea2ed7b9d458acd070f552@cl.cam.ac.uk>
My problem has been fixed: I overwrited /etc/xen/scripts with the new
scripts from tools/examples found in the tree. Now domU can be
created.
Many thanks,
Hieu
On 9/24/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>
> On 24 Sep 2005, at 11:54, Chris Bainbridge wrote:
>
> > I just tried echo /sbin/hotplug > /proc/sys/kernel/hotplug and it
> > works! Woohoo! I can now mount the virtual device. So... there is
> > something wrong with either xen or udevsend that should be fixed. I
> > have no experience with hotplug, but if someone can point me in the
> > right direction I'll try to debug.
>
> As I understand it, there are two standard locations for hotplug
> scripts. One is a directory called /etc/hotplug.d/<name>, the other is
> a file called /etc/hotplug/<name>.agent.
>
> We moved our script to the latter location, as we found that to work
> across debian, suse and redhat distros (unlike /etc/hotplug.d). You'll
> probably find that udevsend is a shell script -- take a look and see if
> it tries to do any hotplug stuff.
>
> I guess it's possible it is looking in /etc/hotplug.d. If so it really
> ought to be updated. Alternatively, some distros have /sbin/hotplug
> search in /etc/hotplug.d, but they add a script to
> /etc/hotplug.d/defaults/ which also searches in /etc/hotplug/. That
> gives you the benefit of searching in both locations.
>
> Anyway, I think it's gentoo's udevsend that is at fault here. Every
> other distro we know of searches /etc/hotplug/ these days.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-09-24 17:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 14:15 Cannot create domU NAHieu
2005-09-23 17:37 ` Michael Vrable
2005-09-23 17:43 ` Michael Vrable
2005-09-23 18:00 ` Michael Vrable
2005-09-23 22:39 ` Chris Bainbridge
2005-09-24 7:38 ` Keir Fraser
2005-09-24 10:54 ` Chris Bainbridge
2005-09-24 13:21 ` Keir Fraser
2005-09-24 17:32 ` NAHieu [this message]
2005-09-24 20:00 ` Chris Bainbridge
2005-09-25 10:19 ` Keir Fraser
[not found] ` <20050926124707.GA13414@kroah.com>
2005-09-26 13:23 ` Keir Fraser
[not found] ` <20050926141407.GA15384@kroah.com>
2005-09-26 14:41 ` Keir Fraser
2005-09-26 15:01 ` Greg KH
2005-09-26 15:41 ` Keir Fraser
2005-09-26 21:22 ` Greg KH
2005-09-27 15:33 ` Chris Bainbridge
2005-09-30 14:48 ` Chris Bainbridge
2005-09-26 14:59 ` Gerd Knorr
2005-09-26 15:54 ` Chris Bainbridge
2005-10-06 15:54 ` network & block device setup via udev Gerd Knorr
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=5d7aca95050924103260c3ecaf@mail.gmail.com \
--to=nahieu@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=chris.bainbridge@gmail.com \
--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.