[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACqxkW+h9FT6PRX2gU+xDQ96V4ejSvz_He6zPMxWm_29eeOUNw@mail.gmail.com>
Date: Thu, 27 Jun 2013 00:17:45 +0100
From: Nick Boyce <nick.boyce@...il.com>
To: full-disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: How to lock up a VirtualBox host machine with
a guest using tracepath over virtio-net network interface
On 6/21/13, Thomas Dreibholz <dreibh@...ula.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 days ago
> (https://www.virtualbox.org/ticket/11863), with the usual reaction from
> Oracle support (i.e. none).
FWIW: *not* confirmed for :
64-bit Linux host = Debian Squeeze 6.0.7 amd64
32-bit Linux guest = Debian Squeeze 6.0.7 i386
VirtualBox = 4.1.26 (guest network adapter set to virtio for the test)
'$ tracepath 8.8.8.8' run in the guest works fine, and no unpleasant
effects are noticed on either host or guest.
I note that VirtualBox 4.1.26 (latest update to 4.1 series) was
released on the same day as 4.2.14 (latest update to 4.2 series) -
specifically 21st.June.2013 - which happens to be the same day you
reported the problem here after getting apparently zero response from
Oracle Support for 8 days. Maybe they just silently fixed the bug
during those 8 days - in which case they should have had the manners
to let you know.
Cheers
Nick Boyce
--
I can't watch TV longer than five minutes without praying for nuclear
holocaust ~~ Bill Hicks
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists