Page 1 of 1
Virtual machine will not restart during sysprep and capture
Posted: 29. Jul 2021, 22:11
by SteveSS
I've created a new loaded image on a Windows 10 20H2 VirtualBox on a 20H2 host machine. Using a sysprep and capture task sequence through MDT, my VM will run the TS (sysprep) up until reboot, upon reboot during the "Loading Files" (begin capture) stage, the vm halts with a black screen and hangs up.
Thankfully, I'm working on a clone of the original machine and haven't lost seven hours of time in image creation, but I've tried cloning the original twice now and get the same results when trying to sysprep and capture. I'm not real sure what's happening here, so I'm reaching out for help. I've broken the log out into smaller files to satisfy file size limits.
Re: Virtual machine will not restart during sysprep and capture
Posted: 29. Jul 2021, 22:37
by scottgus1
Zipped logs will fit.
I don't know if it is interfering, but Hyper-V is enabled. See
HMR3Init: Attempting fall back to NEM (Hyper-V is active).
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 00:02
by SteveSS
Great suggestion. I had totally forgotten that Hyper-V and VirtualBox didn't play well together.
Unfortunately, my problem persists even after removing Hyper-V.
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 00:17
by scottgus1
Bummer. We'll have to wait for someone who understands Sysprep in a VM.
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 01:13
by fth0
Please provide a new (zipped) VBox.log file from a VM run without Hyper-V.
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 15:19
by SteveSS
fth0 wrote:Please provide a new (zipped) VBox.log file from a VM run without Hyper-V.
New zipped log file as requested.
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 15:35
by mpack
Why is the VM using a VHD format disk? Those are not the native format in VirtualBox, and they are prone to corruption and poor performance. The only reason this format ever got anywhere is because Microsoft bought the company. But even MS don't use VHD any more for anything serious, instead they use VHDX, a completely unrelated format named so you'd assume it was related.
I ask because the VM may be showing signs of possible disk corruption.
Other notes: I notice that the extension pack is not installed, only one CPU core has been assigned, the VM only has 4GB of RAM (the host can spare more), and 3D acceleration has not been enabled.
00:00:06.385560 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:06.437141 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:06.819472 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000c960000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0 origin=0,0
00:00:15.270330 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:15.270357 Console: Machine state changed to 'GuruMeditation'
00:00:15.270480 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:15.270480 !!
00:00:15.270480 !! VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
...
00:00:15.271871 7377462: 0x00009f1bb517692a/-3229 00000000000f8eda 0x40002 I/O port write
00:00:15.271872 7377461: 0x00009f1bb5175c3c/-3310 00000000000f8ec0 0x40002 I/O port write
00:00:15.271874 7377460: 0x00009f1bb5174f99/-3235 00000000000f8ea8 0x40002 I/O port write
00:00:15.271876 7377459: 0x00009f1bb51742b0/-3305 00000000000f8e8e 0x40002 I/O port write
00:00:15.271877 7377458: 0x00009f1bb5173608/-3240 00000000000f8e76 0x40002 I/O port write
00:00:15.271879 7377457: 0x00009f1bb5172915/-3315 00000000000f8e5c 0x40002 I/O port write
00:00:15.271880 7377456: 0x00009f1bb5171c5f/-3254 00000000000f8e3c 0x40002 I/O port write
00:00:15.271882 7377455: 0x00009f1bb5170f70/-3311 00000000000f8e22 0x40002 I/O port write
00:00:15.271883 7377454: 0x00009f1bb51702c9/-3239 00000000000f8e0a 0x40002 I/O port write
00:00:15.271885 7377453: 0x00009f1bb516f5d0/-3321 00000000000f8df0 0x40002 I/O port write
00:00:15.271886 7377452: 0x00009f1bb516e916/-3258 00000000000f8dd0 0x40002 I/O port write
00:00:15.271888 7377451: 0x00009f1bb516dbd0/-3398 00000000000f8d68 0x40001 I/O port read
00:00:15.271889 7377450: 0x00009f1bb516cf4a/-3206 00000000000f8d63 0x40002 I/O port write
.. etc etc etc
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 16:10
by fth0
I analyzed a very similar case a year ago, but AFAIK it wasn't solved despite me triggering the appropriate VirtualBox developer. Read
Windows 10 Enterprise 2004 crashing in virtualbox after reboot for details.
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 16:11
by SteveSS
mpack wrote:Why is the VM using a VHD format disk? Those are not the native format in VirtualBox, and they are prone to corruption and poor performance. The only reason this format ever got anywhere is because Microsoft bought the company. But even MS don't use VHD any more for anything serious, instead they use VHDX, a completely unrelated format named so you'd assume it was related.
I ask because the VM may be showing signs of possible disk corruption.
Other notes: I notice that the extension pack is not installed, only one CPU core has been assigned, the VM only has 4GB of RAM (the host can spare more), and 3D acceleration has not been enabled.
I chose VHD in the event that I leave here someday, I can copy the disks to a share and someone else can manipulate them in Hyper-V if they chose. No real reason other than that. Which also explains why I had Hyper-V installed at first. I couldn't get the VM to capture, so I tried to load it into Hyper-V.
I can add a couple CPU's and more memory, and see about adding the extension pack. Oh and the 3d acceleration.
Fingers crossed, I guess.
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 16:34
by mpack
SteveSS wrote:
I chose VHD in the event that I leave here someday, I can copy the disks to a share and someone else can manipulate them in Hyper-V if they chose.
You have better options available for doing that. (a) leave it as a VirtualBox VM and let them decide what format is best for them at the time, (b) use VBoxManage to convert VDI to to whatever you need when you need (e.g. VHDX), or (c) export as an OVA appliance.
No need to permanently handicap the VM before that day comes (VHD only supports a subset of operations VirtualBox can do).
The comments I made about CPU cores etc were under "Other notes", i.e. not expected to have any bearing on your immediate problem, which seems to be caused by disk corruption. To fix that you could perhaps try cloning the VM (to one that uses VDI). If the problem is I/O errors caused by bad host disk then cloning the container copies it to a new disk location, which stands a moderate chance of affecting the problem.
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 16:37
by SteveSS
fth0 wrote:I analyzed a very similar case a year ago, but AFAIK it wasn't solved despite me triggering the appropriate VirtualBox developer. Read for details.
Yep. That's the problem I'm having exactly.
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 16:42
by SteveSS
Well I gave it half the memory, half the CPU's, added the extension pack, and 3D. No change in results.
Adding a final log just in case. Looks like I'll be starting it fresh on Monday. Oh well.
In all seriousness though....this is the most helpful forum I've ever visited. I appreciate everyone who replied with suggestions.
Cheers!
Re: Virtual machine will not restart during sysprep and capture
Posted: 30. Jul 2021, 18:12
by fth0
SteveSS wrote:Adding a final log just in case.
It shows the same crash as the previous VBox.log file.