[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian and QEMU virtio-net-device



Hi, Ian, and thanks again for your time.

No, this is an armhf kernel, installed from
debian-7.1.0-armhf-netinst.iso (and updated).  It does not include PCI
support (neither does hardware) and trying to use virtio-net-pci returns
a message about PCI not found (which it isn't).

I could try something else, but this is the kernel being used for the
development hardware and I'd like to stick with the same kernel.  It's
been good because I've been able to compile and test a lot of code on my
laptop, then port the binaries to the device.  But now I need to do some
testing that requires more network support than is available in the
limited QEMU default emulator.

I didn't realize the vexpress kernel wasn't dtb based - but then I'm not
great on Linux administration, either.  I thought I had to have it when
I installed they kernel, but that was over three years ago on another
project, and I don't recall everything I did from that time.

Jerry


On 11/11/2016 2:44 AM, Ian Campbell wrote:
> On Wed, 2016-11-09 at 08:18 -0500, Jerry Stuckle wrote:
>> Again, I appreciate any insight you can provide.
> 
> Looks like you are using the armel vexpress kernel, which AFAICT
> includes PCI based virtio support, unlike most other ARM configurations
> which include the MMIO (discovered via DTB or ACPI) variant. (Other
> platforms like x86 use the PCI based stuff though, so I'd expect it to
> work)
> 
> I think that might mean you need virtio-net-pci instead of virtio-net-
> device in your command line, but I'm not 100% sure. (The x86 example on
> http://www.linux-kvm.org/page/Virtio seems to suggest this too).
> 
> One other approach would be to ditch the vexpress kernel and initrd and
> instead use the armhf/armmp kernel and "-M virt" instead of "-M
> vexpress" and then virtio-net-device would be the correct thing to use.
> 
> In fact unless you have a good concrete reason to use armel and
> vexpress then that (armhf/armp) would be what I would most recommend.
> You could still run an armel userspace if you have that requirement,
> but if not then I'd recommend using armhf userspace too.
> 
> BTW your use of vexpress also answers Lennart's question wrt device
> tree, since that platform is not DTB based.
> 
> Lastly please note https://lists.debian.org/<1478646546.1727.22.camel@d
> ecadent.org.uk> i.e. there will likely be no armel/vexpress kernel in
> Stretch (so if you have a hard requirement for it then now would be a
> good time to speak, ideally on that other thread).
> 
> Ian.
> 
> 
> 


Reply to: