Custom Query (16363 matches)
Results (2470 - 2472 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9999 | duplicate | Create Snapshot break VirtualMachine (lost snapshot or lost entire Virtual machine) -> duplicate of #10000 | ||
| Description |
Hi have a Virtual Machine with two snapshot. It work fine but whenever i create snaphost / save state / restore snapshot randomly it stop working. Some times i found the .vbox file corrupted i.e <HardDisks/> tag is as i write empty with no data , but the snapshot are fully described. Last time i create a snapshot, restore a state and similar operation (2 or three operation for testing purpose) and the GUI show that the machine was "inaccesible". Restart the gui i see that i lost the last Snapshot (this time the <HardDisks> tag is not empty). I attach the vbox.log , and i have backup the machine so i can recreate the problem if it could be usefull to help to found a solution. Thank you |
|||
| #11761 | worksforme | Create Snapshot, immediately VM is NOT accessible | ||
| Description |
Windows 7, 64-bit host. Windows XP sp3 client/vm. IF I have a clean, working VHD, on a newly created VM, IF I create a snapshot, without doing anything else, that VM is immediately NOT accessible. It gives an error of: Failed to open a session for the virtual machine winXPtest. No error info. Result Code: E_FAIL (0x80004005) Component: ProgressProxy Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913} I've have backup VHD files, and can manually restore this, and make the problem happen MANY times. NOT random. Happens every time. I've tried assigning new UUID to the original/base VHD. I've tried re-assigning parent UUID to the snapshot. Doesn't matter. It doesn't work. The snapshot that VBox Manager just made by itself, it corrupt. |
|||
| #16482 | duplicate | Create a "path" environment variable during instalation process of VB or update an User's manual tu instruct us what to do before we begin using VBoxManage as described in chapter 8 of User's manual. | ||
| Description |
Hi, is it possible that a VB installer creates a system environment variable "path"? I ask this because before I' found that I should have created it, it was very frustrating. I thought that it was already created synce in User's manual has not been written that it should be created by users of this great product. If it is not possible, is it possible to update an User's manual to instruct us that if we want use a command line, we must first create an environment variable or type a path to VBoxManage.exe. Observed in VB 5.1.14 on Windows, but probably a linux users can also benefit. Thank you. Jožef p.s. this ticket can be also categorised as documentation. |
|||

