Hi Peter,
That command line option doesn't work for boston, although I didn't get any obvious error, no Ethernet card appears either. Where can I get that arm image/command which can work well for you with " -netdev user,id=mynet -device virtio-net-pci,netdev=mynet" ? Anyway, if that command line option works for arm, I'm going to investigate the reason. Best regards, Tommy ________________________________ From: Peter Maydell <peter.mayd...@linaro.org> Sent: Tuesday, April 2, 2019 3:35:19 PM To: Tommy Jin Cc: Aleksandar Markovic; qemu-devel@nongnu.org; pburton.wavecomp....@gmail.com Subject: Re: [Qemu-devel] [PATCH] Adds virtio_net as the default netcard for mips boston board. On Tue, 2 Apr 2019 at 14:24, Tommy Jin <t...@wavecomp.com> wrote: > For the option2, I think specify the network model in command line is > not enough, per my understanding, we still need to create the device > using API like pci_create && qdev_set_nic_properties && qdev_init_nofail, > otherwise we'll get error prompts like "requested NIC (anonymous, model > virtio) was not created (not supported by this machine?)", currently I > just add these pieces of code in /hw/mips/boston.c, Do you call these > pieces of code board code and what's your suggestion? If the boston board has PCI support and it is implemented correctly then you should be able to create a virtio network setup with command line options like -netdev user,id=mynet -device virtio-net-pci,netdev=mynet (or any other netdev backend, eg tun/tap). I don't have a boston image/command line to test that with, but it works for arm boards and should be the same for any pci capable board model. thanks -- PMM
