All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	Olaf Hering <olaf@aepfle.de>, Wei Liu <Wei.Liu2@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: 4.7 qemu regression: HVM guests fail to boot from xvda
Date: Wed, 1 Jun 2016 10:48:52 +0100	[thread overview]
Message-ID: <20160601094852.GD5160@citrix.com> (raw)
In-Reply-To: <CAFLBxZYMAMiH8WweWeNxee7r5h8EZRK-LRM37e=34OGvHEHb6A@mail.gmail.com>

On Tue, May 31, 2016 at 01:00:45PM +0100, George Dunlap wrote:
> On Tue, May 31, 2016 at 12:41 PM, Olaf Hering <olaf@aepfle.de> wrote:
> > On Tue, May 31, George Dunlap wrote:
> >
> >> Sorry, can you expand on this a bit?  Are you saying that on SuSE, if
> >> you specify "vdev=xvda" in your config file, that you'll get PV
> >> devices named "/dev/xvda", but that if you specify "vdev=hda", that
> >> you'll get PV devices but named "/dev/hda"?
> >
> > Yes, thats exactly what the xenlinux block frontend does.
> > pvops forces xvda, independent of the name 'vdev' in domU.cfg.
> > Up to xen-4.2 'vdev=hd*' was required to tell qemu to create an emulated
> > disk to boot from. Starting with xen-4.3 qemu also recognized
> > 'vdev=xvd*' for the emulated disk. And starting with xen-4.7 qemu
> > requires 'xvda=hd*' again.
> >
> > I think if some domU.cfg for xen-4.3+ has 'vdev=xvd*' and the domU uses
> > for some reason kernel names in config files and the domU uses a
> > xenlinux kernel, then changing domU.cfg to 'hd*' will allow the guest to
> > boot again. But its userland will miss the /dev/xvd* device nodes.
> > That probably remained unnoticed during testing the referenced commit if
> > a pvops based kernel was used.
> 
> Or if -- as is the case for most of my own test systems -- filesystem
> UUIDs are used rather than device names.  (This means things work the
> same on PV with PV disks, HVM with PV disks, and HVM with emulated
> disks -- for instance, if you're using nested virtualization and your
> L1 dom0 can't access L0 xenbus.)
> 
> Do you have a concrete proposal?
> 
> Anthony, does the OVMF-with-pv-only-drivers actually still work at the moment?
> 

It works. We got pushes to our ovmf tree regularly (only now it fails on
merlot).

Having an extra emulated device shouldn't break OVMF, we've had that for
a long time before that patch was applied.

So I think the safest option now is to revert the said patch and figure
out what to do next.

Anthony and Ian, what do you think?

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-06-01  9:48 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 20:42 4.7 qemu regression: HVM guests fail to boot from xvda Olaf Hering
2016-05-31 11:02 ` George Dunlap
2016-05-31 11:16   ` Olaf Hering
2016-05-31 11:32     ` George Dunlap
2016-05-31 11:41       ` Olaf Hering
2016-05-31 12:00         ` George Dunlap
2016-05-31 12:04           ` Olaf Hering
2016-06-01 13:17             ` Olaf Hering
2016-06-01 21:40               ` Olaf Hering
2016-06-02 11:49                 ` Wei Liu
2016-06-02 12:06                   ` Olaf Hering
2016-05-31 12:15           ` Jan Beulich
2016-06-01  9:48           ` Wei Liu [this message]
2016-06-01 13:34             ` Olaf Hering
2016-06-01 14:11               ` Wei Liu
2016-06-01 14:32                 ` Olaf Hering
2016-06-01 15:36           ` Ian Jackson
2016-06-03 10:13             ` George Dunlap
2016-06-03 11:20               ` Olaf Hering
2016-06-03 11:27                 ` George Dunlap
2016-06-03 11:45                   ` Ian Jackson
2016-06-06 10:39                     ` George Dunlap
2016-06-06 10:52                       ` Ian Jackson
2016-06-06 11:43                         ` George Dunlap
2016-06-06 12:49                     ` George Dunlap
2016-06-07 14:08                     ` George Dunlap
2016-06-07 14:27                       ` Olaf Hering
2016-06-08 10:17                       ` Ian Jackson
2016-06-07 19:06                     ` Olaf Hering
2016-06-08 10:18                       ` Ian Jackson
2016-06-08 10:23                         ` George Dunlap
2016-06-08 10:30                           ` Ian Jackson
2016-06-08 10:49                             ` George Dunlap
2016-06-08 11:13                               ` Olaf Hering
2016-06-08 15:56                                 ` Konrad Rzeszutek Wilk
2016-06-03 11:50                   ` Olaf Hering
2016-05-31 12:10       ` Jan Beulich
2016-05-31 13:41         ` George Dunlap
2016-05-31 14:10           ` Jan Beulich
2016-05-31 16:15     ` Konrad Rzeszutek Wilk
2016-06-08 11:38 ` Wei Liu
2016-06-08 12:04   ` Olaf Hering
2016-06-08 12:09     ` Wei Liu

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=20160601094852.GD5160@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.org \
    /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.