From: Cornelia Huck <cohuck@redhat.com>
To: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
Cc: david@redhat.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [PATCH] virtio-pmem-pci: force virtio version 1
Date: Fri, 25 Sep 2020 12:38:37 +0200 [thread overview]
Message-ID: <20200925123837.1733dcdc.cohuck@redhat.com> (raw)
In-Reply-To: <20200925102251.7216-1-pankaj.gupta.linux@gmail.com>
On Fri, 25 Sep 2020 12:22:51 +0200
Pankaj Gupta <pankaj.gupta.linux@gmail.com> wrote:
> Qemu fails with below error when trying to run with virtio pmem:
>
> (qemu) qemu-system-x86_64: -device virtio-pmem-pci,memdev=mem1,id=nv1:
> device is modern-only, use disable-legacy=on
Oh, another one :(
>
> This patch fixes this by forcing virtio 1 with virtio-pmem.
>
> fixes: adf0748a49 ("virtio-pci: Proxy for virtio-pmem")
> Signed-off-by: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
> ---
> hw/virtio/virtio-pmem-pci.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/virtio/virtio-pmem-pci.c b/hw/virtio/virtio-pmem-pci.c
> index 21a457d151..2b2a0b1eae 100644
> --- a/hw/virtio/virtio-pmem-pci.c
> +++ b/hw/virtio/virtio-pmem-pci.c
> @@ -22,6 +22,7 @@ static void virtio_pmem_pci_realize(VirtIOPCIProxy *vpci_dev, Error **errp)
> VirtIOPMEMPCI *pmem_pci = VIRTIO_PMEM_PCI(vpci_dev);
> DeviceState *vdev = DEVICE(&pmem_pci->vdev);
>
> + virtio_pci_force_virtio_1(vpci_dev);
> qdev_realize(vdev, BUS(&vpci_dev->bus), errp);
> }
>
The alternative would be to force virtio 1 only for 5.1 and later (see
https://lore.kernel.org/qemu-devel/20200921122506.82515-1-sgarzare@redhat.com/).
next prev parent reply other threads:[~2020-09-25 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 10:22 [PATCH] virtio-pmem-pci: force virtio version 1 Pankaj Gupta
2020-09-25 10:23 ` David Hildenbrand
2020-09-25 10:38 ` Cornelia Huck [this message]
2020-09-25 11:49 ` Pankaj Gupta
2020-09-25 12:19 ` Cornelia Huck
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=20200925123837.1733dcdc.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=pankaj.gupta.linux@gmail.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).