virtualbox.org

I have been using this machine for many years. The only new thing I did was take a snap shot, anything else was inside of the guest, which shouldn't have had any effect on the machine.

00:00:03.501568 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:03.501582 Console: Machine state changed to 'Running'
00:00:03.501796 GUI: Capturing keyboard on resume
00:00:03.504361 VMMDev: Guest Log: BIOS: VirtualBox 6.1.34
00:00:03.504429 PCI: Setting up resources and interrupts
00:00:03.505272 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:03.510516 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:03.559941 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:03.560097 VMMDev: Guest Log: CPUID EDX: 0x178bfbff
00:00:03.560524 VMMDev: Guest Log: BIOS: No PCI IDE controller, not probing IDE
00:00:03.560726 AHCI#0: Reset the HBA
00:00:03.560733 VD#0: Cancelling all active requests
00:00:03.560760 AHCI#0: Port 0 reset
00:00:03.560821 VD#0: Cancelling all active requests
00:00:03.561253 VMMDev: Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 0x0000000007dfe340 sectors
00:00:03.561287 AHCI#0: Port 1 reset
00:00:03.561435 AHCI#0: Port 2 reset
00:00:03.726267 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:03.780537 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000d1b0000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
00:00:04.002819 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1920x967
00:00:04.004527 GUI: 2D video acceleration is disabled
00:00:04.004611 GUI: HID LEDs sync is enabled
00:00:04.013120 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:06.217727 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:06.217901 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0312
00:00:06.257972 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:06.273054 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:06.548101 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000d1b0000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0 origin=0,0
00:00:07.232521 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:07.232537 Console: Machine state changed to 'GuruMeditation'

The guru meditated on a "Triple Fault". The VM 'hardware' was working fine. The "Y:" drive Virtualbox Shared Folder could not be set up, because there was no Y drive on the host. I am not certain that this could cause the problem, though: it is labeled as a non-fatal error.

sparkie wrote:The only new thing I did was take a snap shot, anything else was inside of the guest, which shouldn't have had any effect on the machine.

The Triple Fault error means that the OS inside the VM tried to do something that Virtualbox had no idea how to interpret. So there is possibly something wrong in the VM OS. The "anything else was inside of the guest" stuff could very well have broken something.

Whether this was caused by making a snapshot is open to question. Snapshots merely stop writing to a VM disk and start writing to a child disk. You could take a backup copy of the entire VM folder, and any disks existing outside the VM folder. Then "Restore" (not "Delete") the previous snapshot. You should probably let Virtualbox make a new snapshot of the current state too, just so you can get back to where you are now. The backup will allow putting everything back as it is now.

Once you have restored to the previous snapshot, try the VM.

I was only trying to activate some software that had expired. They are a pain.

I had to restore a previous snapshot, go through it all again, turn off, and take another snapshot.

Thanks much