qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, George Kennedy <george.kennedy@oracle.com>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Maran Wilson <maran.wilson@oracle.com>,
	Liam Merwick <liam.merwick@oracle.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Richard Henderson <rth@twiddle.net>,
	Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 4/5] hw/i386/pc: use PVH option rom
Date: Mon, 21 Jan 2019 19:33:32 +0100	[thread overview]
Message-ID: <e889e61c-f5fe-51cc-c703-45487efd4d3f@redhat.com> (raw)
In-Reply-To: <20190121173650.ydihxdyhheq7xcpq@steredhat>

On 21/01/19 18:36, Stefano Garzarella wrote:
>>
>> | On Tue, Jan 15, 2019 at 01:57:22PM -0500, Michael S. Tsirkin wrote:
>> | > OK but this is guest visible so needs to be guarded by the
>> | > new machine type.
>> | 
>> | Aren't option ROMs treated like other firmware?  i.e.: guest
>> | visible, but copied during live migration and not considered part
>> | of guest ABI.
> I don't know the exact answer, but reading the wiki, I think Michael is right!
> (https://wiki.qemu.org/Features/Migration/Troubleshooting#ROMs)
> 
> Maybe it is related for PVH feature in general, because if we try to
> migrate to a QEMU version that doesn't support PVH I'm not sure what is
> the behaviour.

As far as I understand, QEMU would fail to migrate to the destination
because the PVH option ROM doesn't have a corresponding RAMBlock.

Paolo

  reply	other threads:[~2019-01-21 18:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 12:01 [Qemu-devel] [PATCH v5 0/5] pvh: add new PVH option rom Stefano Garzarella
2019-01-18 12:01 ` [Qemu-devel] [PATCH v5 1/5] linuxboot_dma: remove duplicate definitions of FW_CFG Stefano Garzarella
2019-01-18 12:01 ` [Qemu-devel] [PATCH v5 2/5] linuxboot_dma: move common functions in a new header Stefano Garzarella
2019-01-21 15:43   ` Paolo Bonzini
2019-01-21 16:20     ` Stefano Garzarella
2019-01-18 12:01 ` [Qemu-devel] [PATCH v5 3/5] optionrom: add new PVH option rom Stefano Garzarella
2019-01-21 17:37   ` Paolo Bonzini
2019-01-18 12:01 ` [Qemu-devel] [PATCH v5 4/5] hw/i386/pc: use " Stefano Garzarella
2019-01-21 17:05   ` Eduardo Habkost
2019-01-21 17:36     ` Stefano Garzarella
2019-01-21 18:33       ` Paolo Bonzini [this message]
2019-01-22  9:22         ` Stefano Garzarella
2019-01-22  9:29           ` Paolo Bonzini
2019-01-22  9:38             ` Stefano Garzarella
2019-01-18 12:01 ` [Qemu-devel] [PATCH v5 5/5] optionrom/pvh: load initrd from fw_cfg Stefano Garzarella
2019-01-21 10:17 ` [Qemu-devel] [PATCH v5 0/5] pvh: add new PVH option rom Stefan Hajnoczi

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=e889e61c-f5fe-51cc-c703-45487efd4d3f@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=eblake@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=george.kennedy@oracle.com \
    --cc=liam.merwick@oracle.com \
    --cc=maran.wilson@oracle.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).