From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Boris Derzhavets <bderzhavets@yahoo.com>, xen-devel@lists.xensource.com
Subject: Re: Latest pvops dom0 kernel and missing /dev/xen/evtchn, xenstored and xend not starting
Date: Sat, 19 Jun 2010 18:42:28 +0100 [thread overview]
Message-ID: <4C1D0184.4060203@goop.org> (raw)
In-Reply-To: <20100619163830.GP17817@reaktio.net>
On 06/19/2010 05:38 PM, Pasi Kärkkäinen wrote:
> On Sat, Jun 19, 2010 at 04:21:54PM +0100, Jeremy Fitzhardinge wrote:
>
>> On 06/19/2010 02:37 PM, Pasi Kärkkäinen wrote:
>>
>>> On Sat, Jun 19, 2010 at 06:32:21AM -0700, Boris Derzhavets wrote:
>>>
>>>
>>>> > Looks like it's this one in xen-4.0.1-rc2-pre:
>>>> [1]> http://xenbits.xen.org/xen-4.0-testing.hg?rev/0e1521f654f2
>>>>
>>>> I believe you are right.
>>>>
>>>> > What was the corresponding changeset/patch in xen/stable-2.6.32.x that
>>>> breaks things > with Xen 4.0.0 ?
>>>>
>>>> If you mean PV network issue after merge netback-tasklets .
>>>>
>>>>
>>>>
>>> No, I don't mean that.
>>>
>>> I mean older xen/stable-2.6.32.x kernels DO work with xen-4.0.0,
>>> but the latest xen/stable-2.6.32.x does NOT work with xen-4.0.0.
>>>
>>> So there is some change/patch in the dom0 kernel that breaks things with xen 4.0.0.
>>>
>>>
>> 376d908f52427591cef4acd172db9c3ef28676ec and
>> 9d85e25edbcb8a684db8470119077475ac4d90b5
>>
>>
> Ok, thanks.
>
> I seem to have these major/minors on my devices:
>
> # ls -la /dev/xen
> total 0
> drwxr-xr-x 2 root root 80 Jun 19 19:17 .
> drwxr-xr-x 20 root root 4580 Jun 19 19:33 ..
> crw-rw---- 1 root root 10, 58 Jun 19 19:17 evtchn
> crw-rw---- 1 root root 10, 57 Jun 19 19:17 gntdev
>
> Is that correct? They don't seem to match what you pasted earlier..
>
> Then again things seem to work.. I can install new guests using virt-manager etc :)
>
The major/minors are completely dynamic, depending on what else you've
got in your kernel. /proc/misc will tell you what they should be. The
problem is that (old) libxc has some completely broken code to re-create
the device which ends up destroying any correctly created device if it
fails to determine what the major/minor is - and with the change in
kernel device name, it does fail.
J
J
next prev parent reply other threads:[~2010-06-19 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 12:32 Latest pvops dom0 kernel and missing /dev/xen/evtchn, xenstored and xend not starting Pasi Kärkkäinen
2010-06-19 12:44 ` Boris Derzhavets
2010-06-19 13:18 ` Pasi Kärkkäinen
2010-06-19 13:32 ` Boris Derzhavets
2010-06-19 13:37 ` Pasi Kärkkäinen
2010-06-19 15:21 ` Jeremy Fitzhardinge
2010-06-19 16:38 ` Pasi Kärkkäinen
2010-06-19 17:42 ` Jeremy Fitzhardinge [this message]
2010-06-19 18:04 ` Pasi Kärkkäinen
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=4C1D0184.4060203@goop.org \
--to=jeremy@goop.org \
--cc=bderzhavets@yahoo.com \
--cc=pasik@iki.fi \
--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.