Ian, That's interesting, because when I do lsb_release-a returns
No LSB modules are available. Distribution ID: Debian Description: Debian GNU/Linux 8.6 (jessie) Release: 8.6 Codename: Jessie /etc/apt/sources.list entries all point at stable, which should be jessie, I think. And the system is up to date. Right now I have no idea what's causing the difference in versions. Any ideas? This could be part of the cause of my problems. Jerry On 11/12/2016 1:15 PM, Ian Campbell wrote: > On Sat, 2016-11-12 at 10:22 -0500, Jerry Stuckle wrote: >> Ian, >> >> Thanks for clarifying this - I misunderstood your previous statement >> and >> thought it was the Wheezy kernel which supported virtio and not >> Jessie. >> >> However, I am already running Jessie. > > The logs you posted earlier contain: > > [ 0.000000] Linux version 3.2.0-4-vexpress > (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 > SMP Debian 3.2.73-2+deb7u3 > > which is from the Wheezy kernel (vexpress flavour). You can see in http > s://tracker.debian.org/pkg/linux that 3.2.x is shown as oldstable > (Wheezy) while the Jessie (stable) kernel is 3.16 based. > > You can also see in > https://packages.debian.org/search?keywords=linux-image-vexpress > that the vexpress flavour went away after Wheezy, it was subsumed into > https://packages.debian.org/search?keywords=linux-image-armmp in > Jessie. > >> The only non-PCI nic QEMU supports for a bridge is the virtio_device. > > You seem to have inferred some linkage between the device model (the > virtual/emulated device, configured with -device) and the networking > backend (the virtual network infrastructure, e.g. bridge etc, > configured with -netdev) where I do not believe such a linkage exists. > > Grabbing netboot/vmlinuz, netboot/initrd.gz and device-tree/vexpress- > v2p-ca9.dtb from http://ftp.uk.debian.org/debian/dists/jessie/main/inst > aller-armhf/current/images/ lets me boot and detect networking with: > > qemu-system-arm -M vexpress-a9 -cpu cortex-a9 -kernel vmlinuz -initrd > initrd.gz -append console=ttyAMA0,115200 -dtb vexpress-v2p-ca9.dtb -net > nic,model=lan9118,netdev=net0 -netdev user,id=net0 > > or I can switch to a tap device with (need nographic due to sudo): > > sudo qemu-system-arm -M vexpress-a9 -cpu cortex-a9 -kernel vmlinuz -initrd > initrd.gz -append console=ttyAMA0,115200 -dtb vexpress-v2p-ca9.dtb -net > nic,model=lan9118,netdev=net0 -netdev tap,id=net0 -nographic > > I don't have a bridge setup on this machine so I can't try that > precisely but I hope that has demonstrated that the emulation and the > netdev are independent. > > Note that I'm passing -dtb here because it is a Jessie kernel, with the > Wheezy kernel this would not be necessary. > >> The one used for SLIRP is >> not an option. Not that it would help anyway - it's a very limited >> emulation, and the reason I need to get a bridge running. > > As I say, the emulation and the user of bridge vs slirp are > independent. Although it is a bit moot since if you switch the Jessie > kernel virtio net should work fine anyway and will most likely be > faster. > > Ian. > > >
