NICs per PCI bridge, each NIC into a separate slot.
Best regards!
Jiaxin
> -Original Message-
> From: Laszlo Ersek [mailto:ler...@redhat.com]
> Sent: Thursday, July 6, 2017 5:46 PM
> To: Marcel Apfelbaum ; Wu, Jiaxin
> ; qemu-devel@nongnu.org; Alexander Bezzubikov
>
&g
On 07/06/17 11:24, Marcel Apfelbaum wrote:
> On 06/07/2017 11:31, Laszlo Ersek wrote:
>> > Now, I would normally recommend sticking with i440fx for simplicity.
>> However, each PCI bridge requires 4KB of IO space (meaning (1 + 5) * 4KB
>> = 24KB), and OVMF on the i440fx does not support that much
On 06/07/2017 11:31, Laszlo Ersek wrote:
Hi Jiaxin,
it's nice to see a question from you on qemu-devel! :)
On 07/06/17 08:20, Wu, Jiaxin wrote:
Hello experts,
We know QEMU has the capability to create the multiple network devices
in one QEMU guest with the -device syntax. But I met the below
Hi Jiaxin,
it's nice to see a question from you on qemu-devel! :)
On 07/06/17 08:20, Wu, Jiaxin wrote:
> Hello experts,
>
> We know QEMU has the capability to create the multiple network devices
> in one QEMU guest with the -device syntax. But I met the below failure
> when I'm trying to create m
On Thu, Jul 06, 2017 at 06:20:54AM +, Wu, Jiaxin wrote:
> Hello experts,
>
> We know QEMU has the capability to create the multiple network devices in one
> QEMU guest with the -device syntax. But I met the below failure when I'm
> trying to create more than 30 virtual devices with the each
Hello experts,
We know QEMU has the capability to create the multiple network devices in one
QEMU guest with the -device syntax. But I met the below failure when I'm trying
to create more than 30 virtual devices with the each TAP backend:
qemu-system-x86_64: -device e1000: PCI: no slot/function
