Really weird: W7 VM boots fine in VBox but crashes as VM in Hyper-V

[stepgilb]

Greetings commuity!

I created a vhd from a Windows 7 computer and created a VM using the latest Virtualbox version: the VM boots and runs fine. Creating A VM with the sam vhd on Hyper-V brings back the original problem when I first tried to clone the system onto a new harddrive (using EaseUS): the VM (or clone) crashes on loading classpnp.sys (BSOD). Has Virtualbox a "classpnp.sys"prevention built in? Thank for yor time!

SG

[mpack]

I don't understand your question. You seem to be saying that VirtualBox works fine? But you want our help with Hyper-v? Here on a VirtualBox forum?

I'm afraid that isn't how it works. Our skills lie in knowing how to fault find in VirtualBox using logs etc. Finding a non-fault... would be tricky.

[scottgus1]

Has Virtualbox a "classpnp.sys"prevention built in?

The only OS .sys's I have ever heard Virtualbox having a problem with during a P2V are agp440.sys & intelppm.sys from the old Migrating tutorial.

You'd have to peruse the Virtualbox source code to see if "classpnp.sys" is handled specially.

[mpack]

The only OS .sys's I have ever heard Virtualbox having a problem with during a P2V are agp440.sys

Note that he seems to be saying that VirtualBox does not have a problem, but Hyper-v does.

[stepgilb]

Thank you for your input! I posted this message to possibly find someone who noticed the same phenomenon. Clearly Virtualbox does something to avoid BSOD on a classpnp.sys crash.

[scottgus1]

It is also entirely possible that Virtualbox does nothing about classpnp.sys, and Hyper-V has a bug.

You'd have to peruse the Virtualbox source code to see if "classpnp.sys" is handled specially.

[mpack]

Clearly Virtualbox does something to avoid BSOD on a classpnp.sys crash.

That isn't so clear to me. I don't know of any mechanism that VirtualBox could use to interfere with guest code in that way, and in any case it isn't VirtualBox's job to stop guest code crashing if it wants to. It's an execution path, as valid as any other.

More likely is (a) that the VMs are configured differently, or (b) that the affected feature simply doesn't exist in a VirtualBox VM. But without having detailed knowledge of the crash I don't see this speculation being useful.

[fth0]

You'd have to peruse the Virtualbox source code to see if "classpnp.sys" is handled specially.

FWIW, the string "classpnp" is not part of the (publicly available) VirtualBox source code.

[mpack]

FWIW, the string "classpnp" is not part of the (publicly available) VirtualBox source code.

I'd be surprised if the OP installed the GAs, so I doubt that any VirtualBox code is involved.

[stepgilb]

It is also entirely possible that Virtualbox does nothing about classpnp.sys, and Hyper-V has a bug.

You'd have to peruse the Virtualbox source code to see if "classpnp.sys" is handled specially.

As I mentioned in my first post, the classpnp.sys crash happens also on a cloned hardisk and physical machine, not only on Hyper-V.
The original PC features a small RAID 1 SATA card - transparent to the OS, it's driver is probably the reason for the BSOD.