On 02/17/20 10:45, firstname.lastname@example.org wrote:
Some inputs:Ugh this makes my eyes bleed. :/ Please never use the "-bios" option
Anyway that's not our current topic here.
-drive file=/opt/gns3/projects/1a83274a-c57f-4337-8a0d-1e68a9312e9a/project-files/qemu/d8f37f0b-2b63-455f-b536-b309b9020e36/hda_disk.qcow2,if=ide,index=0,media=disk \Seems inconsistent with your intent to HTTP Boot... At least superfluous
with the below, I'd think
-device virtio-net-pci,mac=0c:2e:9a:0e:36:00,netdev=gns3-0 \Seems OK; so you are using virtio-net-pci.
-netdev socket,id=gns3-0,udp=127.0.0.1:10017,localaddr=127.0.0.1:10016 \Unfortunately, I'm entirely unused to "-netdev socket", especially with
"udp=...". I only use "-netdev tap" (via libvirt).
-nographic \Hmmm... Ah you mention "OVMF-RELEASE.fd" above. So that must be a
RELEASE build of OVMF, which indeed does not produce debug messages. Can
you try with DEBUG please?
Yes, I checked those lines after reading your earlier message.
I asked for your command line and the OVMF debug log because I wanted to
see if you were using the iPXE SNP driver for virtio-net (you most
likely are, from the info thus far). It could be interesting to try the
built-in virtio-net driver, for one data point. (This would be a
Second, I have no idea what's happening on the udp socket netdev
back-end. It could explain the virtual network glitches you are seeing.
I'm not sure.