You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i enable the virtio driver in my qemu args VNC terminates after password authentication with the error "failed to recv data from socket" (windows TightVNC client). However with the default qemu e1000 driver all works fine.
Other connectivity seems fine from my brief tests with virtio, but VNC definitely seems to be effected.
I also see a number of the messages bellow in the Kernel log, which don't appear when using the e1000 driver:
2014-12-27 18:15:25 +0000 kernel[0]: virtio-net addPacketToQueue(): Warning! head mbuf 54 does not match mtu-seg 314
I'm on kernel 3.17.6-1-ARCH (Arch Linux) and qemu 2.1.2 currently, and running OSX 10.9.5 with virtio drivers 0.9.4
Thanks very much.
The text was updated successfully, but these errors were encountered:
This sounds very much like the issue described in bug #1. I'm going to claim it's a duplicate of that, so I'll post any progress with repro & fixing to that bug. If an eventual fix for #1 doesn't solve the problem for you, please let me know.
When i enable the virtio driver in my qemu args VNC terminates after password authentication with the error "failed to recv data from socket" (windows TightVNC client). However with the default qemu e1000 driver all works fine.
Other connectivity seems fine from my brief tests with virtio, but VNC definitely seems to be effected.
I also see a number of the messages bellow in the Kernel log, which don't appear when using the e1000 driver:
2014-12-27 18:15:25 +0000 kernel[0]: virtio-net addPacketToQueue(): Warning! head mbuf 54 does not match mtu-seg 314
I'm on kernel 3.17.6-1-ARCH (Arch Linux) and qemu 2.1.2 currently, and running OSX 10.9.5 with virtio drivers 0.9.4
Thanks very much.
The text was updated successfully, but these errors were encountered: