From: Markus Armbruster <armbru@redhat.com>
To: Jens Freimann <jfreimann@redhat.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
pkrempa@redhat.com, ehabkost@redhat.com, mst@redhat.com,
qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com,
armbru@redhat.com, liran.alon@oracle.com, laine@redhat.com,
ogerlitz@mellanox.com, ailan@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] implement the failover feature for assigned network devices
Date: Mon, 08 Apr 2019 07:53:21 +0200 [thread overview]
Message-ID: <87imvpjb5a.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20190405092010.2hnwu36w4ited4rl@jenstp.localdomain> (Jens Freimann's message of "Fri, 5 Apr 2019 11:20:10 +0200")
Jens Freimann <jfreimann@redhat.com> writes:
> On Fri, Apr 05, 2019 at 09:56:29AM +0100, Dr. David Alan Gilbert wrote:
>>* Jens Freimann (jfreimann@redhat.com) wrote:
> [...]
>>> > Commandline: There is a dependency between vfio-pci and virtio-net
>>> > devices. One points to the other via new parameters
>>> > primar=<primary qdev id> and standby='<standby qdev id>'. This means
>>> > that the primary device needs to be specified after standby device on
>>> > the qemu command line. Not sure how to solve this.
>>> >
>>> > Error handling: Patches don't cover all possible error scenarios yet.
>>> >
>>> > I have tested this with a mlx5 NIC and was able to migrate the VM with
>>> > above mentioned workarounds for open problems.
>>> >
>>> > Command line example:
>>> >
>>> > qemu-system-x86_64 -enable-kvm -m 3072 -smp 3 \
>>> > -machine q35,kernel-irqchip=split -cpu host \
>>> > -k fr \
>>> > -serial stdio \
>>> > -net none \
>>> > -qmp unix:/tmp/qmp.socket,server,nowait \
>>> > -monitor telnet:127.0.0.1:5555,server,nowait \
>>> > -device pcie-root-port,id=root0,multifunction=on,chassis=0,addr=0xa \
>>> > -device pcie-root-port,id=root1,bus=pcie.0,chassis=1 \
>>> > -device pcie-root-port,id=root2,bus=pcie.0,chassis=2 \
>>> > -netdev tap,script=/root/bin/bridge.sh,downscript=no,id=hostnet1,vhost=on \
>>> > -device virtio-net-pci,netdev=hostnet1,id=net1,mac=52:54:00:6f:55:cc,bus=root2,primary=hostdev0 \
>>> > -device vfio-pci,host=5e:00.2,id=hostdev0,bus=root1,standby=net1 \
>>
>>Yes, that's a bit grim; it's circular dependency on the 'hostdev0' and
>>'net1' id's. cc'ing in Markus.
>
> Dan had an idea how to avoid having to specify the id for the
> virtio-net device. I'm currently looking into it, but it seems like it
> should work.
Excellent. A circular dependency between -device could only lead to
trouble.
WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Jens Freimann <jfreimann@redhat.com>
Cc: pkrempa@redhat.com, ehabkost@redhat.com, mst@redhat.com,
armbru@redhat.com, qemu-devel@nongnu.org,
mdroth@linux.vnet.ibm.com, liran.alon@oracle.com,
laine@redhat.com, ogerlitz@mellanox.com, ailan@redhat.com,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] implement the failover feature for assigned network devices
Date: Mon, 08 Apr 2019 07:53:21 +0200 [thread overview]
Message-ID: <87imvpjb5a.fsf@dusky.pond.sub.org> (raw)
Message-ID: <20190408055321.fdJb9hdbFYHs8HJsfgwz3UUwFGKuH7tj624_hKbCRvw@z> (raw)
In-Reply-To: <20190405092010.2hnwu36w4ited4rl@jenstp.localdomain> (Jens Freimann's message of "Fri, 5 Apr 2019 11:20:10 +0200")
Jens Freimann <jfreimann@redhat.com> writes:
> On Fri, Apr 05, 2019 at 09:56:29AM +0100, Dr. David Alan Gilbert wrote:
>>* Jens Freimann (jfreimann@redhat.com) wrote:
> [...]
>>> > Commandline: There is a dependency between vfio-pci and virtio-net
>>> > devices. One points to the other via new parameters
>>> > primar=<primary qdev id> and standby='<standby qdev id>'. This means
>>> > that the primary device needs to be specified after standby device on
>>> > the qemu command line. Not sure how to solve this.
>>> >
>>> > Error handling: Patches don't cover all possible error scenarios yet.
>>> >
>>> > I have tested this with a mlx5 NIC and was able to migrate the VM with
>>> > above mentioned workarounds for open problems.
>>> >
>>> > Command line example:
>>> >
>>> > qemu-system-x86_64 -enable-kvm -m 3072 -smp 3 \
>>> > -machine q35,kernel-irqchip=split -cpu host \
>>> > -k fr \
>>> > -serial stdio \
>>> > -net none \
>>> > -qmp unix:/tmp/qmp.socket,server,nowait \
>>> > -monitor telnet:127.0.0.1:5555,server,nowait \
>>> > -device pcie-root-port,id=root0,multifunction=on,chassis=0,addr=0xa \
>>> > -device pcie-root-port,id=root1,bus=pcie.0,chassis=1 \
>>> > -device pcie-root-port,id=root2,bus=pcie.0,chassis=2 \
>>> > -netdev tap,script=/root/bin/bridge.sh,downscript=no,id=hostnet1,vhost=on \
>>> > -device virtio-net-pci,netdev=hostnet1,id=net1,mac=52:54:00:6f:55:cc,bus=root2,primary=hostdev0 \
>>> > -device vfio-pci,host=5e:00.2,id=hostdev0,bus=root1,standby=net1 \
>>
>>Yes, that's a bit grim; it's circular dependency on the 'hostdev0' and
>>'net1' id's. cc'ing in Markus.
>
> Dan had an idea how to avoid having to specify the id for the
> virtio-net device. I'm currently looking into it, but it seems like it
> should work.
Excellent. A circular dependency between -device could only lead to
trouble.
next prev parent reply other threads:[~2019-04-08 6:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190322134447.14831-1-jfreimann@redhat.com>
2019-04-04 8:29 ` [Qemu-devel] [RFC PATCH 0/2] implement the failover feature for assigned network devices Jens Freimann
2019-04-05 8:56 ` Dr. David Alan Gilbert
2019-04-05 8:56 ` Dr. David Alan Gilbert
2019-04-05 9:20 ` Jens Freimann
2019-04-05 9:20 ` Jens Freimann
2019-04-08 5:53 ` Markus Armbruster [this message]
2019-04-08 5:53 ` Markus Armbruster
2019-04-05 23:22 ` Michael S. Tsirkin
2019-04-05 23:22 ` Michael S. Tsirkin
2019-04-05 23:46 ` Eduardo Habkost
2019-04-05 23:46 ` Eduardo Habkost
2019-04-08 5:26 ` Markus Armbruster
2019-04-08 5:26 ` Markus Armbruster
2019-04-12 19:50 ` Eduardo Habkost
2019-04-12 19:50 ` Eduardo Habkost
2019-04-08 9:16 ` Dr. David Alan Gilbert
2019-04-08 9:16 ` Dr. David Alan Gilbert
2019-04-08 13:00 ` Jens Freimann
2019-04-08 13:00 ` Jens Freimann
2019-04-08 17:00 ` Dr. David Alan Gilbert
2019-04-08 17:00 ` Dr. David Alan Gilbert
2019-04-08 13:22 ` Michael S. Tsirkin
2019-04-08 13:22 ` Michael S. Tsirkin
2019-05-29 0:35 ` si-wei liu
2019-05-29 2:47 ` Michael S. Tsirkin
2019-04-04 12:53 ` 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=87imvpjb5a.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=ailan@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jfreimann@redhat.com \
--cc=laine@redhat.com \
--cc=liran.alon@oracle.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=ogerlitz@mellanox.com \
--cc=pkrempa@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 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.