[SOLVED] 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

Discussions related to using VirtualBox on Windows hosts.
DeGarcen
Posts: 91
Joined: 20. Mar 2009, 14:27

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

Post by DeGarcen »

Ok you are not being totally clear. There are:
1.snapshot
2.current state

Which of these can be recovered, or both? Presumably current state and snapshot match, meaning I just took snapshot with vm powered off, then closed Virtualbox. Next time I opened it there was this freezing error. But in case there were some additional data on current state over the snapshot, which states can be recovered among the two, first, second, or both of them (even if it has to be to 2 different vms)?
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

Post by scottgus1 »

I guess the "parent/child" relationship of the disks, though commonly referred to here on the forum, is over your head. So let's try this:

The old guest's .vbox file is too confused. You will need to make a new guest. Don't make a new drive with the new guest. You will be attaching a cloned drive later.

If you make a clone of "manjaro-kde.vdi" only using CloneVDI, and attach this clone to the new guest's SATA port 0, you will have the data before you took the snapshot. You will not have the data after the snapshot was taken.

If you move "manjaro-kde.vdi" into the Snapshots folder with "{8c2e89ee-380a-4b49-9e55-7c12691f5eaa}.vdi" then make a clone of "{8c2e89ee-380a-4b49-9e55-7c12691f5eaa}.vdi" with CloneVDI. and then attach this clone to a new guest's SATA port 0, you will have all the data.

This assumes that the data in "manjaro-kde.vdi" and "{8c2e89ee-380a-4b49-9e55-7c12691f5eaa}.vdi" are not corrupted somehow.

Since you would be running the new guests with clones of the drives, not the original drive files, you can do both guests if you want.
DeGarcen
Posts: 91
Joined: 20. Mar 2009, 14:27

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

Post by DeGarcen »

Thank you. More information on the 2 vdi files:

Code: Select all

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showmediuminfo "C:\manjaro-kde\manjaro-kde.vdi"
UUID:           1eae7798-c6ba-45af-9d3a-f35993216e4f
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       C:\manjaro-kde\manjaro-kde.vdi
Storage format: VDI
Format variant: dynamic default
Capacity:       10240 MBytes
Size on disk:   10111 MBytes
Encryption:     disabled
Property:       AllocationBlockSize=1048576

Code: Select all

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showmediuminfo "C:\manjaro-kde\Snapshots\{8c2e89ee-380a-4b49-9e55-7c12691f5eaa}.vdi"
UUID:           8c2e89ee-380a-4b49-9e55-7c12691f5eaa
Parent UUID:    1eae7798-c6ba-45af-9d3a-f35993216e4f
State:          created
Type:           normal (differencing)
Auto-Reset:     off
Location:       C:\manjaro-kde\Snapshots\{8c2e89ee-380a-4b49-9e55-7c12691f5eaa}.vdi
Storage format: VDI
Format variant: differencing default
Capacity:       10240 MBytes
Size on disk:   3719 MBytes
Encryption:     disabled
Property:       AllocationBlockSize=1048576
DeGarcen
Posts: 91
Joined: 20. Mar 2009, 14:27

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

Post by DeGarcen »

Finally did as you said and worked. Virtual machine working so far so good now Steps taken:
  • "C:\manjaro-kde\Snapshots\{8c2e89ee-380a-4b49-9e55-7c12691f5eaa}.vdi" preserved in that place
  • "C:\manjaro-kde\manjaro-kde.vdi" moved to "C:\manjaro-kde\Snapshots\manjaro-kde.vdi"
  • Open "C:\manjaro-kde\Snapshots\{8c2e89ee-380a-4b49-9e55-7c12691f5eaa}.vdi" with "CloneVDI.exe" -> select destination as "S:\vms\Clone of {8c2e89ee-380a-4b49-9e55-7c12691f5eaa}.vdi" -> Generate new UUID -> Proceed.
Resulting vdi looks like:

Code: Select all

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showmediuminfo "S:\vms\Clone of {8c2e89ee-380a-4b49-9e55-7c12691f5eaa}.vdi"
UUID:           b425f33b-4a1a-4de7-bba7-1721c559610c
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       S:\vms\Clone of {8c2e89ee-380a-4b49-9e55-7c12691f5eaa}.vdi
Storage format: VDI
Format variant: dynamic default
Capacity:       10240 MBytes
Size on disk:   10087 MBytes
Encryption:     disabled
Property:       AllocationBlockSize=1048576
Screenshots:
CloneVDI-01.png
CloneVDI-01.png (14.16 KiB) Viewed 1915 times
CloneVDI-02.png
CloneVDI-02.png (12.25 KiB) Viewed 1915 times
CloneVDI-03.PNG
CloneVDI-03.PNG (4.68 KiB) Viewed 1915 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

Post by scottgus1 »

Nice! glad you have working guests!
DeGarcen
Posts: 91
Joined: 20. Mar 2009, 14:27

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

Post by DeGarcen »

scottgus1 wrote:Nice! glad you have working guests!
I'm happy for having fixed it, however couldn't find cause of error. Hope doesn't happen again.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: [SOLVED] 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

Post by scottgus1 »

Glitches happen. Backups of the guests will help, both through in-the-guest 3rd-party software, and host-level file backups while the guest is fully shut down.

A copy of the shut-down (not save-stated) guest folder with all files therein, as well as the guest disk files if they are not in the guest folder, serves as a complete backup of the activated guest. You can FC file-compare the backup to confirm the copy. If the original is lost, move a copy of the backup back to the original location and the guest will be ready again. The copy can be used on a different host PC too, just by registering the guest's .vbox file. (note that if the original guest had all the guest disk files in the guest folder, the guest is completely usable on any capable host and host OS. If the disk files are outside the guest folder then the .vbox file has absolute paths to the disk files and these paths must be either reproduced on the new host or the .vbox file must be modified.) Virtualbox 6.0.x and later have the right-click-the-guest Move command to move the guest folder to the same drive the guest drive file is on, and the File menu's Virtual Media Manager's Move command to move the guest's drive file into the guest folder next to the .vbox file, to achieve the optimum guest format.
Post Reply