Custom Query (16363 matches)
Results (2200 - 2202 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10661 | obsolete | NSIS_ERROR | ||
| Description |
Installation of VB guest additions fails with an NSIS Error: "Installer integrity check has failed... Contact the installer's author to obtain a new copy." http://nsis.sf.net/NSIS_ERROR is given for more information. This is a 7-32bit client running on 7-64bit host, version 4.1.16 r78094. |
|||
| #10667 | obsolete | GM(VERR_REM_VIRTUAL_CPU_ERROR) at sleep/resume | ||
| Description |
Always after I stop guest Windows XP by using sleep mode, I'm not able resume working, system ask for deleting resume information and starts from scratch - so I can't save work and then continue. |
|||
| #10668 | obsolete | After deleting snapshot VM is inaccessible and behaves strange until restart | ||
| Description |
I didn't found any similar bug and hope that it'll be fixed with the next version. This bug is very simple to reproduce: I've got a VM with WinXP and one snapshot on my Host (Win7-64) and Vbox 4.1.16. After this VM run and snapshot changed I create a second snapshot, e.g. -+--Snapshot A
No I want to merge Snapshot A to the root vdi-file and delete Snapshot A. But it's strange that Current state says "changed" (doesn't change after restarting Virtualbox Manager):
Then I press "restore Snapshot B" to return to Snapshot B. Now it takes a while and then it states "The selected virtual machine is inaccessible. Please inspect the error message shown below and press the Refresh button..." but there is no error message and refreshing doesnt change anything. After restarting Virtualbox Manager it takes few seconds and still shows the same but without "inaccessible" error: -+--Snapshot B
Now if I restore to Snapshot B it succeeds that "(changed)" disappears and it seems that it repaired itself. If I look into "Virtual Media Manager" to the VM I see 2 snapshots, one attached and the other one not attached. After deleting the "not attached" everything works again. Could you please fix that bug? |
|||

