All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Tramnitz <chris.ace@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: 2.6.37 PV on HVM issues
Date: Sun, 09 Jan 2011 19:52:10 +0100	[thread overview]
Message-ID: <4D2A03DA.2080603@gmx.net> (raw)
In-Reply-To: <77A2D23CEB181E1A3DF46B52@Ximines.local>

Alex Bligh wrote:
>
> Bug filed:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/684875
>

The bug has been marked as fixed and I can confirm that it now (using 
2.6.37-12-server) tries to create an xvd device (instead of sd) but I'm 
still unable to boot Natty PV-on-HVM (as HVM domain with just xvd and 
non-ioemu devices).
According to dmesg everything is fine:

DMI: /HVM domU, BIOS 4.0.1 09/28/2010
Hypervisor detected: Xen HVM
Xen version 4.0.
Xen Platform PCI: I/O protocol version 1
Netfront and the Xen platform PCI driver have been compiled for this 
kernel: unplug emulated NICs.
Blkfront and the Xen platform PCI driver have been compiled for this 
kernel: unplug emulated disks.
Booting paravirtualized kernel on Xen
Xen HVM callback vector for event delivery is enabled


But I cannot load xen-blkfront (manually creating the 202 device nodes 
does not help either):

register_blkdev: cannot get major 202 for xvd
xen_blk: can't get major 202 with name xvd
FATAL: Error inserting xen_blkfront 
(/lib/modules/2.6.37-12-server/kernel/drivers/block/xen-blkfront.ko): No 
such device

Does anyone have a running Natty domU with PV-on-HVM?


Best regards,
    Christian

  reply	other threads:[~2011-01-09 18:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 15:23 2.6.37 PV on HVM issues Alex Bligh
2010-12-02 15:26 ` Alex Bligh
2010-12-02 15:41 ` Stefano Stabellini
2010-12-02 16:09   ` Alex Bligh
2010-12-02 17:46     ` Stefano Stabellini
2010-12-02 18:59       ` Alex Bligh
2010-12-03 11:18         ` Stefano Stabellini
2010-12-03 11:24           ` Ian Campbell
2010-12-03 11:33             ` Stefano Stabellini
2010-12-03 16:29             ` Alex Bligh
2010-12-03 16:44               ` Ian Campbell
2010-12-03 17:25                 ` Alex Bligh
2010-12-03 17:21               ` Stefano Stabellini
2010-12-03 17:32                 ` Alex Bligh
2010-12-03 17:46                   ` Alex Bligh
2010-12-03 17:48                     ` Stefano Stabellini
2010-12-03 18:02                       ` Alex Bligh
2011-01-09 18:52                         ` Christian Tramnitz [this message]
2011-01-10 12:10                           ` Stefano Stabellini
2011-01-10 13:43                             ` Ian Campbell
2011-01-10 14:27                               ` Stefano Stabellini
2011-01-10 15:09                                 ` Stefano Stabellini
2010-12-03 16:27           ` Alex Bligh
2010-12-03 16:50             ` Pasi Kärkkäinen
2010-12-03 17:20             ` Stefano Stabellini
2010-12-03 17:30               ` Alex Bligh

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=4D2A03DA.2080603@gmx.net \
    --to=chris.ace@gmx.net \
    --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.