I changed the VM interface from virtio to e1000 and then I do not get
this problem and the job finishes perfectly fine. Although e1000 may not
be the best solution but at least it doesnt break my setup.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Thanks - both of those seem to suggest there is a bug in the virtio
driver in the guest kernel. Are the guests in both cases on the
same release and same kernel?
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
yes, i've used the same virtual machines in both cases. everything is
the same except the driver. I switch from virtio to e1000
glance image-update --property hw_vif_model=e1000 image-id
Now I relaunch the virtual cluster and everything works perfectly fine.
I've tested with 5 times the load
@Brad
I have already sent the apport-collect from the host machine.
I am not sure if I could apport-collect from the guest vm because on the
guest I cannot access any network unless I restart the VM.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: qemu
Importance: Undecided
Status: New
** Also affects: libvirt
Importance: Undecided
Status: New
** No longer affects: qemu
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
apport information
** Tags added: apport-collected precise third-party-packages
** Description changed:
Networking breaks after awhile in kvm guests using virtio networking. We
run data intensive jobs on our virtual cluster (OpenStack Grizzly
Installed on Ubuntu 12.04 Server). The job
@serge
Yes. Thats correct.
$ virsh reboot instance-name
or a soft reboot from from inside the vm (while logged in through the
serial console) does the trick. The VM is back online and accessible.
And we can reproduce the process very easily.
--
You received this bug notification because you
