Custom Query (16363 matches)
Results (979 - 981 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9164 | invalid | revert to old snapshot - need to rejoin domain | ||
| Description |
I do the following on virtual machine with Windows XP SP3
When I then start the machine and try to logon to the domain, there's message that the machine is not member of the domain. I then need to logon as local administrator, drop the machine from the domain, and re-join domain. I tried reverting to the snapshot at once, after I saved it, as well as after couple of days, but this did not happen. It looks like it happens only if the interval has been long enough, several weeks. |
|||
| #9937 | obsolete | resuming a VM saved via keyboard causes keys to not be seen | ||
| Description |
I use Command-Q to Save my guest and stop VB. Actually, I have re-bound Command-Q to be Control-Option-Command-Q, since I want the Command-Q binding to go to my VM. The rebinding of the menu option was done with the Mac's "defaults" command. That part works... I hit Control-Option-Command-Q, VB asks me if I want to Save, Shutdown, or Power Off. I save. Some time later I restore. The keyboard does not work at that point. Or depending on which window has focus, it might do unexpected things. What fixes it, is I press and release each of the modifier keys. I am guessing that what is happening is that the saved VM things I'm still holding down Control-Option-Command, from when I used the keyboard to Save & Quit from VB before. When restoring the guest it has missed the key-up events, and thinks I'm still holding them down. Probably the restore operation needs to do a little keyboard dance with the guest so that the guest sees the correct state of the modifiers when the guest is resumed. Since I have figured out what is going on this is minor. But it could be a real problem for somebody that doesn't get it. I'm submitting with a priority of "Minor" anyhow. My guest at the moment is CentOS 6.0 x86_64, and I have the 4.1.6 extensions and guest additions installed. |
|||
| #13161 | obsolete | resume failed with SSM: LoadExec failed for 'HGCM' rc=VERR_SSM_LOADED_TOO_MUCH | ||
| Description |
I have a VM in safed state made with 4.3.10 and after upgrade to 4.3.12 I got 00:00:07.001778 SSM: LoadExec failed for 'HGCM' instance #0 (version 2, pass 0xffffffff): VERR_SSM_LOADED_TOO_MUCH 00:00:07.001823 VMSetError: /home/vbox/vbox-4.3.10/src/VBox/VMM/VMMR3/SSM.cpp(8349) int ssmR3LoadExecV2(PVM, PSSMHANDLE); rc=VERR_SSM_LOADED_TOO_MUCH 00:00:07.001825 VMSetError: Failed to load unit 'HGCM' 00:00:07.001850 Releasing keys... 00:00:07.001892 Changing the VM state from 'LOADING' to 'LOAD_FAILURE'. 00:00:07.001921 Changing the VM state from 'LOAD_FAILURE' to 'POWERING_OFF'. switching back to 4.3.10 did not solve the problem Guest: Win_8.1 Host: Linux 3.13.10-200.fc20.x86_64 |
|||

