Well, I cannot reproduce the issue on 4.2.14, but there is nothing in
change logs for that version that can be related to virtio-net. They might
have done a silent fix for 4.1.x branch as well.
Cheers,
Z.
2013/6/27 Nick Boyce nick.bo...@gmail.com
On 6/21/13, Thomas Dreibholz dre...@simula.no
Hi,
Tested this on Windows 7 x64 host instead (no Linux box available atm);
confirmed the issue (consumes CPU and kills the host network adapter).
Can someone assign a CVE for this? Looks like this can be exploited to at
least DoS other VMs on the same host.
2013/6/21 Thomas Dreibholz
On Wednesday 26 June 2013 09:09:52 Źmicier Januszkiewicz wrote:
Can someone assign a CVE for this? Looks like this can be exploited to at
least DoS other VMs on the same host.
Usually oracle make the requests if needed.
--
Agostino Sarubbo
Gentoo Linux Developer
On 6/21/13, Thomas Dreibholz dre...@simula.no wrote:
I have discovered a problem with the VirtualBox virtio-net network driver
that leads to a lockup of the host machine's kernel and the need for a
hard reset to make it working again. The bug had been reported to the
VirtualBox bug tracker 8
Hi,
I have discovered a problem with the VirtualBox virtio-net network driver that
leads to a lockup of the host machine's kernel and the need for a hard reset
to make it working again. The bug had been reported to the VirtualBox bug
tracker 8 days ago
On Fri, 21 Jun 2013 16:33:35 +0200, Thomas Dreibholz said:
- The host system is a 64-bit Linux (tested with Ubuntu 12.04 LTS and Kubuntu
What does 'uname -r' on the host return?
This is almost certainly a bug in either the host network stack or the
VirtualBox modules (probably one of the
