I agree with David, you can try the RTL8139.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1702621
Title:
colo: secondary vm crash during loadvm
Status in QEMU:
New
Bug description:
I haven't tried COLO for a while; I've got a note I hit a similar error in the
past -
I think I came to the conclusion it was the e1000 that was unhappy - probably
sending an interrupt after it had stopped.
Try a different NIC. I flipped to using a virtio-net at one point (but I think
I had
The qemu version is 2.9.0 release.
The 'irq_count' and 'irq_state' are sent by private vm, and loaded by secondary
vm. When they sent by private vm, they maybe not in a consistent state. So
sometimes 'bus->irq_count[i]' becomes '-1' on secondary vm.
I deleted the assertions and then tested it
