Custom Query (16363 matches)
Results (2107 - 2109 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3018 | duplicate | Cloning seems to corrupt filesystem | ||
| Description |
I've often cloned xpdisks.vdi under windows xp with no errors. The newest version seems to corrupt filesystem meta information. After starting the cloned image I always get new Hardware detected: VBOX HARDDISC, dll-files are missing when invoking the system hardware information, installation process can't write into certain windows directories. When ignoring those installation errors, filesystem check occurs after rebooting and many lost files will be recovered. cloned system is not useable. |
|||
| #6325 | obsolete | Close Virtual Machine randomly appearing | ||
| Description |
I am running VB 3.1.4 in OSX 10.6.2 although this issue has appeared on earlier versions. At times when I start a guest, the Close Virtual Machine dialog box pops up when it first tries to run a guest. After I hit cancel the guest boots normally. It doesn't seem to happen every time and seems to happen more often if I had opened another guset first, shut that one down, and start a different guest. It doesn't seem to matter whether I was running a Windows guest or a Linux guest. Doesn't seem to matter which I try to start. And as I said, it seems random although I suppose one of the guests on shutdown is doing something untoward on shutdown that leaves VB in a strange state. I included the last guest log file. |
|||
| #6326 | duplicate | Close Virtual Machine randomly appearing | ||
| Description |
I am running VB 3.1.4 in OSX 10.6.2 although this issue has appeared on earlier versions. At times when I start a guest, the Close Virtual Machine dialog box pops up when it first tries to run a guest. After I hit cancel the guest boots normally. It doesn't seem to happen every time and seems to happen more often if I had opened another guset first, shut that one down, and start a different guest. It doesn't seem to matter whether I was running a Windows guest or a Linux guest. Doesn't seem to matter which I try to start. And as I said, it seems random although I suppose one of the guests on shutdown is doing something untoward on shutdown that leaves VB in a strange state. I included the last guest log file. |
|||

