qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	qemu-stable@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
	mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
	Jing Zhao <jinzhao@redhat.com>
Subject: Re: [PATCH] virtio: move 'use-disabled-flag' property to hw_compat_4_2
Date: Mon, 18 Jan 2021 16:03:12 +0000	[thread overview]
Message-ID: <20210118160312.GB9899@work-vm> (raw)
In-Reply-To: <20210108171252.209502-1-sgarzare@redhat.com>

* Stefano Garzarella (sgarzare@redhat.com) wrote:
> Commit 9d7bd0826f introduced a new 'use-disabled-flag' property
> set to true by default.
> To allow the migration, we set this property to false in the hw_compat,
> but in the wrong place (hw_compat_4_1).
> 
> Since commit 9d7bd0826f was released with QEMU 5.0, we move
> 'use-disabled-flag' property to hw_compat_4_2, so 4.2 machine types
> will have the pre-patch behavior and the migration can work.

Be a little careful that fixing this probably causes a migration from
5.2->6.0 to fail with this machine type;  so when we do these
type of fixes we often fix an old machine type between some pair of qemu
versions and then break it between a different set.

Dave

> The issue was discovered with vhost-vsock device and 4.2 machine
> type without running any kernel in the VM:
>     $ qemu-4.2 -M pc-q35-4.2,accel=kvm \
>         -device vhost-vsock-pci,guest-cid=4 \
>         -monitor stdio -incoming tcp:0:3333
> 
>     $ qemu-5.2 -M pc-q35-4.2,accel=kvm \
>         -device vhost-vsock-pci,guest-cid=3 \
>         -monitor stdio
>     (qemu) migrate -d tcp:0:3333
> 
>     # qemu-4.2 output
>     qemu-system-x86_64: Failed to load virtio-vhost_vsock:virtio
>     qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:03.0/virtio-vhost_vsock'
>     qemu-system-x86_64: load of migration failed: No such file or directory
> 
> Reported-by: Jing Zhao <jinzhao@redhat.com>
> Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1907255
> Fixes: 9d7bd0826f ("virtio-pci: disable vring processing when bus-mastering is disabled")
> Cc: mdroth@linux.vnet.ibm.com
> CC: qemu-stable@nongnu.org
> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
> ---
>  hw/core/machine.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/core/machine.c b/hw/core/machine.c
> index de3b8f1b31..5d6163ab70 100644
> --- a/hw/core/machine.c
> +++ b/hw/core/machine.c
> @@ -70,12 +70,12 @@ GlobalProperty hw_compat_4_2[] = {
>      { "qxl", "revision", "4" },
>      { "qxl-vga", "revision", "4" },
>      { "fw_cfg", "acpi-mr-restore", "false" },
> +    { "virtio-device", "use-disabled-flag", "false" },
>  };
>  const size_t hw_compat_4_2_len = G_N_ELEMENTS(hw_compat_4_2);
>  
>  GlobalProperty hw_compat_4_1[] = {
>      { "virtio-pci", "x-pcie-flr-init", "off" },
> -    { "virtio-device", "use-disabled-flag", "false" },
>  };
>  const size_t hw_compat_4_1_len = G_N_ELEMENTS(hw_compat_4_1);
>  
> -- 
> 2.26.2
> 
-- 
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK



  parent reply	other threads:[~2021-01-18 16:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 17:12 [PATCH] virtio: move 'use-disabled-flag' property to hw_compat_4_2 Stefano Garzarella
2021-01-18  9:19 ` Stefano Garzarella
2021-01-18 11:51   ` Michael S. Tsirkin
2021-01-18 16:03 ` Dr. David Alan Gilbert [this message]
2021-01-19  8:45   ` Stefano Garzarella
2021-01-26 14:17     ` Michael S. Tsirkin
2021-01-27 14:28     ` Dr. David Alan Gilbert
2021-01-27 14:34       ` Stefano Garzarella

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=20210118160312.GB9899@work-vm \
    --to=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jinzhao@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=sgarzare@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).