[Solved] I broke .vbox config file. The machine does not start
[Solved] I broke .vbox config file. The machine does not start
Hello.
At first the path was defaultMachineFolder on drive E and the virtual machine was also on disk E. Then I changed the way to drive D. However, the virtual machine is left on E.
A few months later I decided to move a virtual machine from E to D. Copy the desired folder and change the path in the file "c: \ Users \ konst \ .VirtualBox \ VirtualBox.xml" to drive D.
After these steps, I can not boot from the virtual machine configuration and lost all wheels.
All files: .vdi, .sav, logs, Snapshots remain.
The virtual machine has two snapshot.
I tried many ways to recreate the configuration, but it is impossible. (You need to restore all the snapshots). Please tell me how you can restore the virtual machine. All files are available, but not spelled out in the configuration information on the disks, and snapshots.
At first the path was defaultMachineFolder on drive E and the virtual machine was also on disk E. Then I changed the way to drive D. However, the virtual machine is left on E.
A few months later I decided to move a virtual machine from E to D. Copy the desired folder and change the path in the file "c: \ Users \ konst \ .VirtualBox \ VirtualBox.xml" to drive D.
After these steps, I can not boot from the virtual machine configuration and lost all wheels.
All files: .vdi, .sav, logs, Snapshots remain.
The virtual machine has two snapshot.
I tried many ways to recreate the configuration, but it is impossible. (You need to restore all the snapshots). Please tell me how you can restore the virtual machine. All files are available, but not spelled out in the configuration information on the disks, and snapshots.
Last edited by coder_asd on 29. Jul 2016, 18:30, edited 1 time in total.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: I broke .vbox config file. The machine does not start
Post the following two files:
- c: \ Users \ konst \ .VirtualBox \ VirtualBox.xml
- The .VBOX file located where your VM is.
Also, open up a command prompt and list the contents of the directory where your VM is, including it's subdirectories.
- c: \ Users \ konst \ .VirtualBox \ VirtualBox.xml
- The .VBOX file located where your VM is.
Also, open up a command prompt and list the contents of the directory where your VM is, including it's subdirectories.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: I broke .vbox config file. The machine does not start
VirtualBox.xml: "fnpaste. com /PvNR"
Windows 7 x64.vbox: "fnpaste. com /NQnY"
dir catalogs: "fnpaste. com /nge4"
fnpaste - This is the link to remove the gaps
--
sorry, code not insert - "You must be a member for 1 days and have 1 posts before you can post urls."
Windows 7 x64.vbox: "fnpaste. com /NQnY"
dir catalogs: "fnpaste. com /nge4"
fnpaste - This is the link to remove the gaps
--
sorry, code not insert - "You must be a member for 1 days and have 1 posts before you can post urls."
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: I broke .vbox config file. The machine does not start
Please attach the files locally. Not a lot of people will go to 3rd party sites, including myself.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: I broke .vbox config file. The machine does not start
dir:
Code: Select all
E:\home\VPS\VirtualBox VMs\Windows 7 x64>dir
Том в устройстве E имеет метку 2
Серийный номер тома: FC8A-00C0
Содержимое папки E:\home\VPS\VirtualBox VMs\Windows 7 x64
29.07.2016 11:24 <DIR> .
29.07.2016 11:24 <DIR> ..
29.07.2016 09:56 <DIR> Logs
29.07.2016 09:57 <DIR> Snapshots
29.07.2016 11:43 6 852 Windows 7 x64.vbox
29.07.2016 11:24 6 852 Windows 7 x64.vbox-prev
25.07.2016 14:42 27 774 681 088 Windows 7 x64.vdi
3 файлов 27 774 694 792 байт
4 папок 336 437 547 008 байт свободно
E:\home\VPS\VirtualBox VMs\Windows 7 x64>dir Logs
Том в устройстве E имеет метку 2
Серийный номер тома: FC8A-00C0
Содержимое папки E:\home\VPS\VirtualBox VMs\Windows 7 x64\Logs
29.07.2016 09:56 <DIR> .
29.07.2016 09:56 <DIR> ..
29.07.2016 10:55 117 844 VBox.log
28.07.2016 23:26 131 323 VBox.log.1
28.07.2016 08:47 118 463 VBox.log.2
27.07.2016 22:15 148 492 VBox.log.3
29.07.2016 10:55 361 882 VBoxHardening.log
5 файлов 878 004 байт
2 папок 336 437 547 008 байт свободно
E:\home\VPS\VirtualBox VMs\Windows 7 x64>dir Snapshots
Том в устройстве E имеет метку 2
Серийный номер тома: FC8A-00C0
Содержимое папки E:\home\VPS\VirtualBox VMs\Windows 7 x64\Snapshots
29.07.2016 09:57 <DIR> .
29.07.2016 09:57 <DIR> ..
25.07.2016 14:42 1 330 323 045 2016-07-25T11-42-29-980243300Z.sav
27.07.2016 22:15 1 117 871 461 2016-07-27T19-15-32-443622200Z.sav
27.07.2016 22:15 4 712 300 544 {1575d704-0853-4975-a4ba-b4a9879e55e6}.vdi
29.07.2016 10:55 3 805 282 304 {e6b52c8d-adcb-4204-b0d2-e0469b707fbb}.vdi
4 файлов 10 965 777 354 байт
2 папок 336 437 547 008 байт свободно
- Attachments
-
- files.zip
- VirtualBox.xml, Windows 7 x64.vbox
- (3.38 KiB) Downloaded 59 times
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: I broke .vbox config file. The machine does not start
Let me see if I have this right so we won't be making any mistakes:
- You mentioned that you copied the VM folder from "E:\home\VPS\VirtualBox VMs\Windows 7 x64" to "D:\home\VPS\VirtualBox VMs\Windows 7 x64". That means that you currently have two copies?
- If so, are the contents of the directories identical (as far as the VDI and SAV files is concerned)?
- Is the "Windows 7 x64.vbox" that you attached the one from "E:\home\VPS\VirtualBox VMs\Windows 7 x64"? If it is, I'm sorry, but I don't see any snapshots. If on the other hand it is from "D:\home\VPS\VirtualBox VMs\Windows 7 x64", then we may have something.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: I broke .vbox config file. The machine does not start
socratis,
Yes, I did backups. But backup is already broken.
VDI and SAV files contain the necessary information, you need to restore the entire tree snapshots (two snapshot).
This is a problem that in the file "Windows 7 x64.vbox" no information about the snapshot. They themselves have disappeared somewhere.
Yes, I did backups. But backup is already broken.
VDI and SAV files contain the necessary information, you need to restore the entire tree snapshots (two snapshot).
This is a problem that in the file "Windows 7 x64.vbox" no information about the snapshot. They themselves have disappeared somewhere.
Code: Select all
{e6b52c8d-adcb-4204-b0d2-e0469b707fbb}.vdi - 2 snapshot
2016-07-27T19-15-32-443622200Z.sav - 2 snapshot
{1575d704-0853-4975-a4ba-b4a9879e55e6}.vdi - 1 snapshot
2016-07-25T11-42-29-980243300Z.sav - 1 snapshot
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: I broke .vbox config file. The machine does not start
I'm not sure I quite understand your reply, so let me try once more. If you have two folders with the Win7x64 VM, one in drive D:\ and one in drive E:\, I would need the following information to clear up the mess:
- List the contents of the directory "D:\home\VPS\VirtualBox VMs\Windows 7 x64".
- List the contents of the directory "E:\home\VPS\VirtualBox VMs\Windows 7 x64". (I already have that).
- Post the file "D:\home\VPS\VirtualBox VMs\Windows 7 x64\Windows 7 x64.vbox".
- Post the file "E:\home\VPS\VirtualBox VMs\Windows 7 x64\Windows 7 x64.vbox".
Usually they are not. That's the purpose of a backup.coder_asd wrote:Yes, I did backups. But backup is already broken.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: I broke .vbox config file. The machine does not start
"D:\home\VPS\VirtualBox VMs\Windows 7 x64" = "E:\home\VPS\VirtualBox VMs\Windows 7 x64".
I tried different ways to adjust the configuration, but it is impossible.
I tried different ways to adjust the configuration, but it is impossible.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: I broke .vbox config file. The machine does not start
If D:\... = E:\... then, there are no snapshots in there. This is usually the result of someone messing with the configuration files manually, like in your case.
There is a chance to fix some of the damage. Use the CloneVDI tool. Put your main VDI and the snapshots VDI files in the same folder. From the time stamp it looks like {e6b52c8d-adcb-4204-b0d2-e0469b707fbb}.vdi is your latest snapshot. Then, take a look at these instructions: viewtopic.php?f=6&t=78822&p=367786#p367786 by mpack, the author of CloneVDI.
Good luck.
There is a chance to fix some of the damage. Use the CloneVDI tool. Put your main VDI and the snapshots VDI files in the same folder. From the time stamp it looks like {e6b52c8d-adcb-4204-b0d2-e0469b707fbb}.vdi is your latest snapshot. Then, take a look at these instructions: viewtopic.php?f=6&t=78822&p=367786#p367786 by mpack, the author of CloneVDI.
Good luck.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: I broke .vbox config file. The machine does not start
socratis, a great big thank you for help! Vdi combined into one file. I create a virtual machine. Working.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: [Solved] I broke .vbox config file. The machine does not start
Nice to hear about it! Just a last piece of advice for future reference. If you take a backup of anything, you do NOT touch the original, you only work on the copy, so if something goes bad, you always have the original to create a *new* copy to experiment with.
Thanks should go to mpack as well for his CloneVDI! I definitely didn't want to start messing and recreating the snapshot chain in the .vbox file
Thanks should go to mpack as well for his CloneVDI! I definitely didn't want to start messing and recreating the snapshot chain in the .vbox file
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.