libvirt/qemu-kvm failing to start interfaces wasn't the problem (though I
thought it was since those interfaces weren't around when the VM wouldn't
start). I eventually realized that the socket I was telling libvirt to
accept on was in the ephemeral port range, and a webserver I was running on
On 03/27/2015 12:42 PM, Dave Sayles wrote:
I'm running libvirt with qemu-kvm underneath.
My network stack has the eth0 interface which is bridged to a br0 interface.
Usually, when a VM starts up, a new vnet interface is created as well by
libvirt. That vnet interface has a matching HWaddr
I'm running libvirt with qemu-kvm underneath.
My network stack has the eth0 interface which is bridged to a br0 interface.
Usually, when a VM starts up, a new vnet interface is created as well by
libvirt. That vnet interface has a matching HWaddr to the VM that was spun up
with it, so I'm
