From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: Compatibility between -device sga and -machine graphics=off
Date: Wed, 8 Sep 2021 17:36:29 +0100 [thread overview]
Message-ID: <YTjmjfbjqD4dA/VM@redhat.com> (raw)
In-Reply-To: <364031a0-982d-f6bd-cbcc-9f6d9be4ba69@redhat.com>
On Wed, Sep 08, 2021 at 06:28:01PM +0200, Paolo Bonzini wrote:
> On 08/09/21 18:08, Daniel P. Berrangé wrote:
> > Despite this difference, I was able migrate from a x86 guest using SGA
> > to a guest using graphics=off without errors being reported. So it
> > doesn't seem to change the migration data sections sent on the wire
> > at least.
>
> It would probably break with Windows XP/2003 guests on AMD processors, as
> those are the ones that use kvmvapic. On other guests and processors, it's
> a no-op.
After running an incoming migrate, the target QEMU's 'info mtree'
changed to reflect what the src QEMU originally reported. So whatever
difference 'graphics=off' causes compared to -device sga initially,
appears to have been eliminated by running the migrate. Not sure if
that's true in the general case or not - I'm just testing with a
minimalist CLI and no real OS running
qemu-system-x86_64 -nodefaults -display sdl -device VGA -serial stdio -device sga
vs
qemu-system-x86_64 -nodefaults -display sdl -device VGA -serial stdio -machine graphics=off
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-09-08 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 16:08 Compatibility between -device sga and -machine graphics=off Daniel P. Berrangé
2021-09-08 16:28 ` Paolo Bonzini
2021-09-08 16:36 ` Daniel P. Berrangé [this message]
2021-09-08 18:59 ` Paolo Bonzini
2021-09-08 16:33 ` Richard W.M. Jones
2021-09-08 20:50 ` Gerd Hoffmann
2021-09-08 22:10 ` Daniel P. Berrangé
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=YTjmjfbjqD4dA/VM@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 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).