Custom Query (16363 matches)
Results (778 - 780 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12414 | obsolete | take-restore snapshot broken (Error: failed to start machine. Error message: Failed to load unit 'PATM' (VERR_SSM_STRUCTURE_MAGIC)) | ||
| Description |
taking a snapshot and restoring it result in error when starting vm. steps to reproduce: $ VBoxManage snapshot "Windows XP" restorecurrent Restoring snapshot a570b155-7d35-495c-8e5e-10816912aa5a 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% ### NOTE: Snapshot1 - Taken with 4.3.2 ### $ VBoxHeadless --startvm "Windows XP" & [1] 7888 Oracle VM VirtualBox Headless Interface 4.3.4 (C) 2008-2013 Oracle Corporation All rights reserved. VRDE server is listening on port 3389. ### Runs fine ### $ VBoxManage snapshot "Windows XP" take "Snapshot2" 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% $ VBoxManage controlvm "Windows XP" poweroff 0%...VRDE server is inactive. 10%...20%...30%...40%...50%...60%...70%...80%...90%...100% [1]+ Done VBoxHeadless --startvm "Windows XP" $ VBoxManage snapshot "Windows XP" restorecurrent Restoring snapshot c3e4b715-58f3-4aa8-becd-0298703957d3 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% $ VBoxHeadless --startvm "Windows XP" & [1] 7991 Oracle VM VirtualBox Headless Interface 4.3.4 (C) 2008-2013 Oracle Corporation All rights reserved. VRDE server is listening on port 3389. VRDE server is inactive. Error: failed to start machine. Error message: Failed to load unit 'PATM' (VERR_SSM_STRUCTURE_MAGIC) [1]+ Done VBoxHeadless --startvm "Windows XP" --- reproducible everytime |
|||
| #2008 | obsolete | tElock unpacker reports ''processor misbehavior'' | ||
| Description |
I was analyzing some software on (GUEST)Windows XP SP3 run on (HOST)Gentoo. This software was protected with tElock. It is a PE-File Encryptor/Compressor tool that was designed to process most .exe, .ocx and .dll files. It compresses and encrypts those file types while leaving them executable and protects against patching and disassembling. In VirtualBox environment packed application is unable to unpack its self because of processor VBox processor missbehaviour. During the unpacking routine it checks the unpacked data and prints CRC error. (rightfully) Packer:
Software using this packer:
Virtualization doensn't affect the result. It's not caused by fault file copy. I found this problem reported on more Windows and VBox versions. |
|||
| #7810 | duplicate | system sticks with virtualbox 3.2.12 | ||
| Description |
i'm using archlinux, when i update the kernel to 2.6.36, virtualbox 3.2.10(maybe, that's the version before 3.2.12) sticks, and the system is till ok, but when i update virtualbox to version 3.2.12, the system sticks as long as virtualbox does. the guest os is windows xp. |
|||

