Opened 2 years ago

Closed 2 years ago

#17980 closed bug (no change required)

Network status continuously changing under QEMU

Reported by: bitigchi Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Network & Internet Version: R1/beta3
Keywords: QEMU Cc:
Blocked By: Blocking:
Platform: All

Description

hrev56521

QEMU output and screen grab attached.

After boot up, network status continuously cycles between Read, No Connection, Connecting etc. Internet seems to be active during this period to the naked eye.

Attachments (1)

qemu.txt (64.7 KB ) - added by bitigchi 2 years ago.
QEMU output

Download all attachments as: .zip

Change History (9)

by bitigchi, 2 years ago

Attachment: qemu.txt added

QEMU output

comment:2 by humdinger, 2 years ago

FWIW, it works here - hrev56522 - with this command, running under Linux Mint:

sudo qemu-system-x86_64 /dev/sda -cpu host -smp 6 -m 4096 --enable-kvm --usb -usbdevice tablet

comment:3 by waddlesplash, 2 years ago

This is likely due to the use of the "e1000e" network device. This used to work, but then FreeBSD changed something in their driver and now it does not work there too, I believe. The "e1000" device should still work.

comment:4 by bitigchi, 2 years ago

I've tried using the e1000 device with the -device e1000 option, its connection looks stable, but the first one is still active (two ethernet devices visible) and still fluctuating. When I disable it, the second one does not work still. What's the proper syntax for using an explicit network adapter selection?

comment:5 by waddlesplash, 2 years ago

Pretty sure you want the -nic option.

comment:6 by Starcrasher, 2 years ago

I have this in NIC section of the manager, I hope it helps.

<interface type="network">

<mac address="52:54:00:5e:79:a4"/> <source network="Haiku-Net"/> <model type="e1000"/> <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x0"/>

</interface>

Using qemu+kvm myself with an e1000, it works fine. But network problems can be deeper. I noticed that sometimes the device works (stable) and you get address via DHCP (So Haiku side looks good) but actually nothing works because despite virtmanager reporting it OK, NAT is not. Usually, when it happens, you can't restart the network from the interface, it's throwing python errors. You need either playing with hosts services or reboot.

comment:7 by bitigchi, 2 years ago

e1000 works great, thanks waddlesplash and Starcrasher.

comment:8 by waddlesplash, 2 years ago

Resolution: no change required
Status: newclosed

Since upstream FreeBSD claims the driver works on bare metal with this specific device I am going to just close this ticket.

Note: See TracTickets for help on using tickets.