Could you confirm me this BSOD bug is well-known ?

This is for discussing general topics about how to use VirtualBox.
Post Reply
FMJ999
Posts: 3
Joined: 23. Mar 2022, 23:26

Could you confirm me this BSOD bug is well-known ?

Post by FMJ999 »

Hello,
I use VB 6.1.32 on a Win10 64b B19043.1526.
I can generate an automatic BSOD wih this procedure :
> With a functional VM (any OS) using a NIC
> Associate the NIC you want (I experienced with Virtual Host-Only Ethernet Adapter)
> Start the VM
> Pause the VM
> Disable the NIC in Windows network parameters
> Resume the VM
> And ... enjoy ....!

Could you confirm me that Oacle knows this bug ? Thank you
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Could you confirm me this BSOD bug is well-known ?

Post by mpack »

Removing hardware from a PC that is still running often ends badly. VirtualBox normally grays out such options. So the fact that it crashes is not a bug, the fact that the UI allows it was the bug.
Martin
Volunteer
Posts: 2561
Joined: 30. May 2007, 18:05
Primary OS: Fedora other
VBox Version: PUEL
Guest OSses: XP, Win7, Win10, Linux, OS/2

Re: Could you confirm me this BSOD bug is well-known ?

Post by Martin »

When you pause a VM it expects the exact same environment after the pause.
Removing some "parts" outside of Virtualbox by disabling the network card in Windows is not a supported use case. ;)
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Could you confirm me this BSOD bug is well-known ?

Post by mpack »

Ah, I didn't notice the "Disable the NIC in Windows Network Parameters" part, I thought the NIC was being disabled in VirtualBox.

Ok, so the important change was outside VirtualBox's control. In that case I agree with Martin, and I would struggle to regard this as a bug. More like user error.
FMJ999
Posts: 3
Joined: 23. Mar 2022, 23:26

Re: Could you confirm me this BSOD bug is well-known ?

Post by FMJ999 »

If this led to VB crash, I would agree. But as it drives to an OS crash, I would name that a serious bug, user error or not. I shouln't be !
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Could you confirm me this BSOD bug is well-known ?

Post by scottgus1 »

FMJ999 wrote:as it drives to an OS crash
I get the impression that this is the host OS you're talking about. However, this from the OP:
FMJ999 wrote:I can generate an automatic BSOD wih this procedure :
doesn't specifically mention that it's the host OS you're referring to. Though "BSOD" is implied to be a Windows thing and you mentioned "any OS" for the VM OS, folks have crossed "BSOD" to refer to Linux crashes, too.

So your procedure causes the host OS to crash? Interesting. While not quite ready to call this a bug myself, I could call it an unprogrammed-for problem. I don't have a host that's free to attempt this on at this moment, so I haven't tried it. Please post as detailed a reproduction procedure as possible on the Bugtracker, let's see what the devs can say.
FMJ999
Posts: 3
Joined: 23. Mar 2022, 23:26

Re: Could you confirm me this BSOD bug is well-known ?

Post by FMJ999 »

Indeed, I talked about the crash of the hypervisor OS.
I will make the bug report and will give you news.
Thanks
Martin
Volunteer
Posts: 2561
Joined: 30. May 2007, 18:05
Primary OS: Fedora other
VBox Version: PUEL
Guest OSses: XP, Win7, Win10, Linux, OS/2

Re: Could you confirm me this BSOD bug is well-known ?

Post by Martin »

Do you have any 3rd party security, AV or VPN software installed?
Post Reply