[prev in list] [next in list] [prev in thread] [next in thread] 

List:       full-disclosure
Subject:    Re: [Full-disclosure] How to lock up a VirtualBox host machine with a guest using tracepath over vir
From:       ¬micier_Januszkiewicz <gauri () tut ! by>
Date:       2013-06-27 6:52:40
Message-ID: CAH72vihmXk3xXkz2ZAd4gzPb=5bzvB5GAxovmmWQnRYFYGf+Lg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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.boyce@gmail.com>

> On 6/21/13, Thomas Dreibholz <dreibh@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 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/
>

[Attachment #5 (text/html)]

<div dir="ltr"><div>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.<br><br></div> Cheers,<br>Z.<br></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">2013/6/27 Nick Boyce <span \
dir="ltr">&lt;<a href="mailto:nick.boyce@gmail.com" \
target="_blank">nick.boyce@gmail.com</a>&gt;</span><br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">On \
6/21/13, Thomas Dreibholz &lt;<a href="mailto:dreibh@simula.no">dreibh@simula.no</a>&gt; \
wrote:<br> <br>
&gt; I have discovered a problem with the VirtualBox virtio-net network driver<br>
&gt; that leads to a lockup of the host machine&#39;s kernel and the need for a<br>
&gt; hard reset to make it working again. The bug had been reported to the<br>
&gt; VirtualBox bug tracker 8 days ago<br>
&gt; (<a href="https://www.virtualbox.org/ticket/11863" \
target="_blank">https://www.virtualbox.org/ticket/11863</a>), with the usual reaction from<br> \
&gt; Oracle support (i.e. none).<br> <br>
</div>FWIW: *not* confirmed for :<br>
64-bit Linux host = Debian Squeeze 6.0.7 amd64<br>
32-bit Linux guest = Debian Squeeze 6.0.7 i386<br>
VirtualBox = 4.1.26 (guest network adapter set to virtio for the test)<br>
<br>
&#39;$ tracepath 8.8.8.8&#39; run in the guest works fine, and no unpleasant<br>
effects are noticed on either host or guest.<br>
<br>
I note that VirtualBox 4.1.26 (latest update to 4.1 series) was<br>
released on the same day as 4.2.14 (latest update to 4.2 series) -<br>
specifically 21st.June.2013 - which happens to be the same day you<br>
reported the problem here after getting apparently zero response from<br>
Oracle Support for 8 days.  Maybe they just silently fixed the bug<br>
during those 8 days - in which case they should have had the manners<br>
to let you know.<br>
<br>
Cheers<br>
<span class="HOEnZb"><font color="#888888">Nick Boyce<br>
--<br>
I can&#39;t watch TV longer than five minutes without praying for nuclear<br>
holocaust ~~ Bill Hicks<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Full-Disclosure - We believe in it.<br>
Charter: <a href="http://lists.grok.org.uk/full-disclosure-charter.html" \
target="_blank">http://lists.grok.org.uk/full-disclosure-charter.html</a><br> Hosted and \
sponsored by Secunia - <a href="http://secunia.com/" \
target="_blank">http://secunia.com/</a><br> </div></div></blockquote></div><br></div>



_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic