[Resolved] win xp32 stuck on loading screen

[Giannis]

hello, i'm trying to boot a winxp32 guest on 64bit win7 and win 10 hosts but stuck on loading win xp screen.
i have the same stuck with two formats of this image, the first created with disk2vhd(vhd) and the other with paragon (vdi), but i think that vhd is most common, so lets talk about this.
i use VBox 6.0 and i have the log of vhd

[socratis]

22d8.3a0:     ProductName:     Avast Antivirus 
22d8.3a0:     ProductName:     Malwarebytes Anti-Malware
22d8.3a0:     ProductName:     COMODO Internet Security
22d8.3a0: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 66204 ms, the end);

Gianni, what are you trying to do? Make your computer slower that molasses in the winter on the Arctic circle? You have 3 additional antivirus, on top of the very well behaving built-in Win7 one!

These days they are so "smart" that they actually start scanning the VHDs and the VMDKs, slowing the startup sequence tremendously!!! Get rid of all of them, you don't need them, they're slowing your computer down. Despite all this however, your ExitCode is 0x0, i.e. no error. Impressive...

One of the most common P2V failures is the use of a different I/O APIC setting compared to the original one. What you have is:

00:00:01.226831 IOAPIC <integer> = 0x0000000000000000 (0)

which means disabled. See if enabling it makes a difference...

00:00:57.735678 Changing the VM state from 'RUNNING' to 'SUSPENDING'

Are you sure you waited long enough? It doesn't look like it...

[Giannis]

thank you for the reply , now i had the time to check it
i removed the malware bytes, but comodo is firewall and avast i think is better from windows 7 default.
nothing happend after this and of course after i turn the IOAPIC enable...maybe is some other error behind this?

* but for a reason that i dont know the other format(vdi) work suddenly and it seem to work stable..and i'm happy for now. i already remove some not necessery programs and save the statement.
so, if i copy the vdi now it will work on other pc with win10, what do you think? or is there a proper procedure for do this?

[socratis]

You don't copy a VDI, you copy the whole VM folder. A VDI is like a hard disk. If I take my hard disk and put it in a random computer, will it work? Of course not.

See the FAQ "Moving a VM" and interpret it as "Backing up a VM" or "Copying a VM".

[Giannis]

I read the user manual and made clone vm. After moved the created folder to the other pc and import it to vbox, it works great. So my conclusion is that Paragon probably make better vhd images than disk2vhd, except if I'm doing something wrong... I don't know but my job done
Thanks for your support

[socratis]

So my conclusion is that Paragon probably make better vhd images than disk2vhd, except if I'm doing something wrong...

Nope, it's not the conversion that's the problem. This is the problem:

00:00:01.200370 File system of 'G:\ADMIN-winxp32.VHD' is ntfs

22d8.3a0:     ProductName:     Avast Antivirus 
22d8.3a0:     ProductName:     Malwarebytes Anti-Malware
22d8.3a0:     ProductName:     COMODO Internet Security

I told you that the antivirus these days have actually gained the ability to scan VHD files. Once you converted that VHD into a VDI, they can't actively keep on scanning it, therefore launching the performance into new heights!

In fact, here's my canned answer for P2V conversions:

• Use Disk2VHD, a Microsoft tool, to save your physical disk in the VHD format.
• Convert the VHD to VDI, which is native to VirtualBox. You can either read ch 8.24. VBoxManage clonemedium, or use the nice CloneVDI utility to do so.
• Create a new VM as close to the original as possible. When prompted for a disk, choose the VDI you just created.

Glad the cloning helped you, marking as [Resolved].