disk2vhd and VHD

[martino]

I used the MS Sysinternals utility disk2vhd to generate a VM as a clone of my PC's C drive.
I select only the first two volumes "C:\" and "\\?\volume....." and started the VM generation of more than 400GB in H:\HP6470B.vhd file.
No errors till now. At this point i try to start Vmware 4.3.30 and generate a new VM specifiyng the storage with the HP6470B.vhd file: ok too.
Then i start the VM and after some seconds showing "Windows starting ..." i get the fail message here enclosed, and the VM reload itself and
goes in loop with this error, until i stop the VM manually.
What could be causing this ?
Regards,

[scottgus1]

I'm assuming you meant Virtualbox, not VMware.

I'm not certain of the consequences of not checking all the checkboxes in the Disk2VHD selection box, so that may be something to consider.

A clone of a physical PC is made using the "P2V" process, for Physical-to-Virtual. It is essentially the same as making a disk image backup of a PC and restoring the backup to other hardware. Here's a link that may help, Migrate existing Windows installations to VirtualBox Also google/bing for "P2V site:forums.virtualbox.org"

Regarding the Windows stop error, you can google it to see what it would mean on a physical PC. It means the same thing in Virtualbox.

Note that a P2V of a Windows OS will cause activation issues at least, since all the hardware the OS was running on has now changed to virtual hardware. If you get the virtual copy activated, the physical copy may one day unactivate itself. And if the physical PC is a big-box brand like Dell or HP or such, the Windows OS is locked to the BIOS of the physical PC and will not activate on another PC, physical or virtual.

[mpack]

I guess it's too much to ask that people mention something as unimportant as what the guest OS is. I'm going to guess Win7, based on the fact that there's a partition before C:\.

Stop 0x7B is a disk controller change. Try configuring the VM to use an IDE controller.

AFAIK, the MergeIDE stuff mentioned in the Wiki is only needed by XP, and nothing else in the wiki applies either.

Clearly this is an image of an HP system, in which case they have their own Windows distro which may not work in a VM. Still, it costs nothing but time to try.

[scottgus1]

the MergeIDE stuff mentioned in the Wiki is only needed by XP, and nothing else in the wiki applies either.

I'll keep this in mind. Thanks!

[mpack]

Btw, moved to "Windows Guests" since the host is irrelevant to the question asked.

[martino]

Thank You Scottgus1 ... yes Virtualbox
I am cloning again the HP PC in a bigger external HD so that i can select all the volumes shown by disk2vhd.
In the meanwhile i have tested the same vhd file (the one obtained selecting only two volumes in disk2vhd) with a Virtualbox ver 5.1.4
with similar failure.

[martino]

Sorry , the guest is Win7 Pro 64bit (the OS in the HP6470B.vhd file) . I apologize for that, but i noticed that when i created the new VM, are proposed only 32-bit version of Windows OS in the General Setup. No one is 64-bit in the Virtualbox i am using: ver 5.1.4
Why only 32-bit OS version are proposed ?

[martino]

About the 32-bit only version of proposed OS versions, i have understand the cause.
Some days ago i update the BIOS of the PC running the Virtualbox v 5.1.4. The update seemed to end well, but the
Virtualization Technology was disabled (default setting maybe) as i discovered now, also by means of the MS Sysinternals utility
"coreinfo -v". Without VT Enabled at the BIOS level, Virtualbox was not able to show any 64-bit version OS.
Sorry for the loss of time.

[scottgus1]

No problem, and no loss of time! Glad you were able to get things going!