Page 1 of 1
Vbox on OpenSUSE
Posted: 26. Oct 2016, 11:18
by MissSB
Hi guys,
I'm having trouble loading my Windows 7 64-bit on virtualbox. I've tried changing UUIDs, and so many other things I feel like I had to stop and post on here before damaged my file (If I haven't already). When I click the VBox file VirtualBox application opens but nothing happens.
I get the errors below when I try to add the .vdi file.
Code: Select all
Failed to open virtual machine located in /home/sharone/VirtualBox VMs/Win 7/Win 7.vbox.
A differencing image of snapshot {b1f7f21c-bb5f-465c-8d34-4e9794ca67c5} could not be found. Could not find an open hard disk with UUID {fc23f60e-3380-4959-ae6b-28e86421358a}.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SnapshotMachine
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
Callee: IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
When I try to create new but use existing .vdi
Code: Select all
Failed to open virtual machine located in /home/sharone/VirtualBox VMs/Win 7/Win 7.vbox.
A differencing image of snapshot {b1f7f21c-bb5f-465c-8d34-4e9794ca67c5} could not be found. Could not find an open hard disk with UUID {fc23f60e-3380-4959-ae6b-28e86421358a}.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SnapshotMachine
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
Callee: IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
Code: Select all
VBoxManage showhdinfo /home/sharone/VirtualBox\ VMs/Win\ 7/Snapshots/\{c7b97368-ee56-4ba8-8d43-16ced0ef316d\}.vdi
VBoxManage: error: Parent medium with UUID {fc23f60e-3380-4959-ae6b-28e86421358a} of the medium '/home/sharone/VirtualBox VMs/Win 7/Snapshots/{c7b97368-ee56-4ba8-8d43-16ced0ef316d}.vdi' is not found in the media registry ('/root/.config/VirtualBox/VirtualBox.xml')
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 178 of file VBoxManageDisk.cpp
I have attached my vbox file and the backup I made before editing the tags <Attached Device UUID> for your review and advice. Thanks.
Re: Vbox on OpenSUSE
Posted: 27. Oct 2016, 07:22
by MissSB
Some help needed here please.
Re: Vbox on OpenSUSE
Posted: 27. Oct 2016, 08:03
by socratis
First of all, this is a user/volunteer forum, not a 24/7 support hotline. Just so we're in the same page.
MissSB wrote:I've tried changing UUIDs, and so many other things I feel like I had to stop and post on here before damaged my file (If I haven't already).
I'm afraid that you might have already done it. Let's hope not, we'll have to see. First of all, I need you to describe what you did, or you thought you did. And why. In full details.
Then, I need you to do:
For
every VDI in that output, do:
Oh, you need to undo the changes you made to the .vbox file and restore the backup. That, you did mess up for sure, after you manually deleted what you didn't feel like including in there. And please do not continue to manually edit the .vbox file, unless you
really know what you're doing. For example, what you tried to do manually (remove the ISO for GAs), you could have done it via the GUI, much safer...
PS. Nice thinking on using the {code} tag...
Re: Vbox on OpenSUSE
Posted: 27. Oct 2016, 08:29
by MissSB
First of all, this is a user/volunteer forum, not a 24/7 support hotline. Just so we're in the same page.
Yes we really are on the same page, thanks. I'm just really stranded and looking for some guidance because my work is on there.
I mainly tried to change the UUIDs, I have now rolled back to the .prev file back into the folder though because I made so many changes (based on advise from other forums) to the <Hard Disk>, <DVDImages> and also deleted the <AttachedDevice> UUIDs.
Code: Select all
ls -alR /home/sharone/VirtualBox\ VMs/Win\ 7/
/home/sharone/VirtualBox VMs/Win 7/:
total 76
drwxr-xr-x 4 sharone users 4096 Oct 27 09:17 .
drwxr-xr-x 7 sharone users 4096 Oct 26 12:18 ..
-rw------- 1 sharone users 59 Oct 26 08:08 .directory
drwx------ 2 sharone users 4096 Oct 24 08:07 Logs
drwx------ 2 sharone users 4096 Oct 24 08:19 Snapshots
-rw------- 1 sharone users 26087 Oct 24 10:11 Win 7.vbox
-rw------- 1 sharone users 26087 Oct 24 10:11 Win 7.vbox.txt
/home/sharone/VirtualBox VMs/Win 7/Logs:
total 716
drwx------ 2 sharone users 4096 Oct 24 08:07 .
drwxr-xr-x 4 sharone users 4096 Oct 27 09:17 ..
-rw------- 1 sharone users 60 Jun 20 10:46 .directory
-rw------- 1 sharone users 107267 Oct 24 08:16 VBox.log
-rw------- 1 sharone users 403772 Oct 21 13:51 VBox.log.1
-rw------- 1 sharone users 79347 Oct 18 08:47 VBox.log.2
-rw------- 1 sharone users 122782 Oct 14 16:48 VBox.log.3
/home/sharone/VirtualBox VMs/Win 7/Snapshots:
total 34784968
drwx------ 2 sharone users 4096 Oct 24 08:19 .
drwxr-xr-x 4 sharone users 4096 Oct 27 09:17 ..
-rw------- 1 sharone users 60 Oct 24 08:19 .directory
-rw------- 1 sharone users 1731568356 Jun 15 21:00 2016-06-15T18-00-20-961396000Z.sav
-rw------- 1 sharone users 33889976320 Oct 25 13:14 {c7b97368-ee56-4ba8-8d43-16ced0ef316d}.vdi
Code: Select all
VBoxManage showhdinfo {c7b97368-ee56-4ba8-8d43-16ced0ef316d}.vdi
VBoxManage: error: Could not find file for the medium '/root/{c7b97368-ee56-4ba8-8d43-16ced0ef316d}.vdi' (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 178 of file VBoxManageDisk.cpp
Re: Vbox on OpenSUSE
Posted: 27. Oct 2016, 09:09
by socratis
First of all there are a couple things missing from your post; your motivation for messing up with the whole thing (really important), the exact things that you did (of utmost importance) and finally your explanation of why you decided to do this whole exercise without a proper backup, since it seems that you have important data in the VM...
Second, why on earth are you running as root? A) it's way too dangerous and B) not only you don't have more privileges compared to your "sharone" account, but your VMs belong to "sharone" and "sharone" alone. "root" cannot see the VMs of "sharone". So, please perform the exercise while logged in as "sharone", not as "root".
Third, you didn't follow the instructions. I said to issue the VBoxManage command with the full path of the VDI. Please try again. At least you have reverted the .vbox file to something that is not corrupt/messed up.
Fourth, and this is kind of crucial, there is one file missing from the listing: "/home/sharone/VirtualBox VMs/Windows 7/Windows 7.vdk". I don't know where the "vdk" extension comes from, did it used to be a "vmdk"? Where is that file? That's the basis of your data! Without that, yes, you're screwed...
Re: Vbox on OpenSUSE
Posted: 27. Oct 2016, 09:53
by MissSB
socratis wrote:First of all there are a couple things missing from your post; your motivation for messing up with the whole thing (really important), the exact things that you did (of utmost importance) and finally your explanation of why you decided to do this whole exercise without a proper backup, since it seems that you have important data in the VM...
It all started when I tried to make a backup of my .vdi and in the process started investigating why my guest Windows 7 had "Error After Install" against it so it went downhill from there. I generated 2 new UUIDs using the command
Code: Select all
VBoxManage internalcommands sethduuid /home/sharone/VirtualBox\ VMs/Win_7/Snapshots/\{c7b97368-ee56-4ba8-8d43-16ced0ef316d\}.vdi
I replaced the <Machine uuid> using the first UUID I generated, and then replaced the <DVDImages & HardDisk uuids> with the second UUID i generated. As I went on troubleshooting, I deleted the entire <AttachedDevice> <image uuid> </AttachedDevice> tag in the same file. I hope this makes more sense.
Second, why on earth are you running as root? A) it's way too dangerous and B) not only you don't have more privileges compared to your "sharone" account, but your VMs belong to "sharone" and "sharone" alone. "root" cannot see the VMs of "sharone". So, please perform the exercise while logged in as "sharone", not as "root.
running as sharone
Code: Select all
ls -alR /home/sharone/VirtualBox\ VMs/Win\ 7/
/home/sharone/VirtualBox VMs/Win 7/:
total 76
drwxr-xr-x 4 sharone users 4096 Oct 27 09:17 .
drwxr-xr-x 7 sharone users 4096 Oct 26 12:18 ..
-rw------- 1 sharone users 59 Oct 26 08:08 .directory
drwx------ 2 sharone users 4096 Oct 24 08:07 Logs
drwx------ 2 sharone users 4096 Oct 24 08:19 Snapshots
-rw------- 1 sharone users 26087 Oct 24 10:11 Win 7.vbox
-rw------- 1 sharone users 26087 Oct 24 10:11 Win 7.vbox.txt
/home/sharone/VirtualBox VMs/Win 7/Logs:
total 716
drwx------ 2 sharone users 4096 Oct 24 08:07 .
drwxr-xr-x 4 sharone users 4096 Oct 27 09:17 ..
-rw------- 1 sharone users 60 Jun 20 10:46 .directory
-rw------- 1 sharone users 107267 Oct 24 08:16 VBox.log
-rw------- 1 sharone users 403772 Oct 21 13:51 VBox.log.1
-rw------- 1 sharone users 79347 Oct 18 08:47 VBox.log.2
-rw------- 1 sharone users 122782 Oct 14 16:48 VBox.log.3
/home/sharone/VirtualBox VMs/Win 7/Snapshots:
total 34784968
drwx------ 2 sharone users 4096 Oct 24 08:19 .
drwxr-xr-x 4 sharone users 4096 Oct 27 09:17 ..
-rw------- 1 sharone users 1731568356 Jun 15 21:00 2016-06-15T18-00-20-961396000Z.sav
-rw------- 1 sharone users 33889976320 Oct 25 13:14 {c7b97368-ee56-4ba8-8d43-16ced0ef316d}.vdi
-rw------- 1 sharone users 60 Oct 24 08:19 .directory
Code: Select all
VBoxManage showhdinfo /home/sharone/VirtualBox\ VMs/Win\ 7/Snapshots/\{c7b97368-ee56-4ba8-8d43-16ced0ef316d\}.vdi
VBoxManage: error: Parent medium with UUID {fc23f60e-3380-4959-ae6b-28e86421358a} of the medium '/home/sharone/VirtualBox VMs/Win 7/Snapshots/{c7b97368-ee56-4ba8-8d43-16ced0ef316d}.vdi' is not found in the media registry ('/home/sharone/.config/VirtualBox/VirtualBox.xml')
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 178 of file VBoxManageDisk.cpp
Fourth, and this is kind of crucial, there is one file missing from the listing: "/home/sharone/VirtualBox VMs/Windows 7/Windows 7.vdk". I don't know where the "vdk" extension comes from, did it used to be a "vmdk"? Where is that file? That's the basis of your data! Without that, yes, you're screwed...
I opted to create it as a .vdk as I understand it is a native format of VirtualBox as opposed to .vmdk file. Is it not valid?
Re: Vbox on OpenSUSE
Posted: 27. Oct 2016, 10:19
by socratis
The native format is VDI, but VMDK is supported as well. I don't know why you ended up with a Frankensteinian extension, but that would be OK, as long as the file was there.
It's missing! Your virtual HD is missing! That's the problem!
You only have a snapshot, which is a differential image based on the missing file, i.e. standalone garbage!
Re: Vbox on OpenSUSE
Posted: 27. Oct 2016, 11:06
by MissSB
Oh shoot! Does this mean I cannot use the .vdi/vdk file/snapshot to restore?
Code: Select all
ls -alR /home/sharone/VirtualBox\ VMs/Windows\ 7/
/home/sharone/VirtualBox VMs/Windows 7/:
total 60326584
drwxr-xr-x 3 sharone users 4096 Apr 22 2015 .
drwxr-xr-x 7 sharone users 4096 Oct 26 12:18 ..
-rw------- 1 sharone users 70 Apr 22 2015 .directory
drwxr-xr-x 2 sharone users 4096 Feb 2 2015 Logs
-rw------- 1 sharone users 13888 Jan 27 2014 Windows 7-1.12-linux.vbox
-rw------- 1 sharone users 11852 Jan 30 2015 Windows 7.vbox
-rw------- 1 sharone users 11887 Jan 30 2015 Windows 7.vbox-prev
-rw------- 1 sharone users 45056 Oct 25 11:01 Windows7.vdi
-rw------- 1 sharone users 61773815808 Jun 15 21:00 Windows 7.vdk
-rw------- 1 sharone users 489645 Jan 27 2014 Windows 7.webm
/home/sharone/VirtualBox VMs/Windows 7/Logs:
total 388
drwxr-xr-x 2 sharone users 4096 Feb 2 2015 .
drwxr-xr-x 3 sharone users 4096 Apr 22 2015 ..
-rw------- 1 sharone users 61598 Feb 2 2015 VBox.log
-rw------- 1 sharone users 131158 Jan 30 2015 VBox.log.1
-rw------- 1 sharone users 91601 Jan 27 2015 VBox.log.2
-rw------- 1 sharone users 90779 Jan 27 2015 VBox.log.3
Re: Vbox on OpenSUSE
Posted: 27. Oct 2016, 11:45
by socratis
Dude, what's going on? Honestly I'm at a loss. Now you posted the 'ls' from
a different directory.
Can we get the facts straight? Things that do
NOT make sense, in no particular order:
- You have a "Windows7.vdi" that's tiny for a VDI (44 KB ???). Modification: 2016-10-25. Note the lack of space in the name.
- You have a "Windows 7.vdk" that's 57.5 GB. Modification: 2016-06-15. Note the space in the name.
- You have a "Windows 7.vbox". Modification: 2015-01-30.
- All three of these appear in the "Windows 7" sub-directory. With a space. And no snapshots.
- You have another directory called "Win 7".
- In there you have NO base HD, but you have a snapshot!
- Finally, to top it of, you listed that you changed the UUID in a snapshot located in a third directory, "Win_7". Note the underscore "_". ???
Two things:
- I have a plausible explanation. But I need to hear it from you first. The complete story.
- I need the output of:
Re: Vbox on OpenSUSE
Posted: 27. Oct 2016, 12:13
by mpack
A "snapshot" without a base hdd could indicate a linked clone.
We urgently need to establish what that "vdk" file is. Use a hex editor to save off the first 1Kb, zip and attach the zip here.
Re: Vbox on OpenSUSE
Posted: 27. Oct 2016, 12:23
by socratis
Just the .vdk file? What about the rest of the story? If nothing else I'd love to see that .vdi file that's only 44 KB.
@MissSB, upload what mpack asked you, plus, please upload the .vdi file (the one that's 45056 bytes). If the extension is not allowed, zip it.
And do not forget the narration, otherwise we can be guessing until the next Olympics.
Re: Vbox on OpenSUSE
Posted: 28. Oct 2016, 09:43
by MissSB
I managed to restore my virtualbox using the restored .vbox file of the 57GB .vdk. I got lucky I guess. The file did take me way back to June but it's better than nothing. I'll take precautionary measures this time. Thank you for your assistance.