Custom Query (16363 matches)
Results (1852 - 1854 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11456 | fixed | Cannot power on a virtual machine: NS_ERROR_CALL_FAILED (0x800706BE)/IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913} => Fixed in SVN | ||
| Description |
Whenever I try to power on my Windows 8 64 bit UEFI guest I get this error. 00:00:00.531823 VMSetError: /home/vbox/vbox-4.2.6/src/VBox/Devices/EFI/DevOVMF.cpp(1343) int efiConstruct(PDMDEVINS*, int, CFGMNODE*); rc=VERR_CFGM_INTEGER_TOO_BIG 00:00:00.531832 VMSetError: Can't attach Nvram Storage driver 00:00:00.531846 PDM: Failed to construct 'efi'/0! VERR_CFGM_INTEGER_TOO_BIG (-2100) - The integer value was too big for the requested representation.
Host: Linux 3.7.6 vanilla x86 PAE |
|||
| #13006 | obsolete | Cannot re-add virtual machine after removing from the gui | ||
| Description |
Hello, I have this reproducible problem with the GUI (version 4.3.10):
[work with the created clone or not, doesn't matter]
Failed to open virtual machine located in D:/virtualbox/test123/test123.vbox. Could not find an open hard disk with UUID {ef334bc1-017a-4d9b-a28d-199d13a7f684}. Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) Component: VirtualBox Interface: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554} Configuration file attached ... Greetings Michael |
|||
| #9667 | fixed | Cannot read TPR | ||
| Description |
I recently upgraded to VirtualBox 4.1.2, unfortunately I having some trouble with it. Reading of the TPR does not seem to function, I tracked the problem down to the fact that reading the TPR just not return anything. Reading is done by: mov eax, DWORD PTR [ecx+edx] with ecx holding the mapped APIC base address and edx the offset to the TPR. After the Instruction which seemed to be replaced by a vmmcall the eax register is not modified at all. I remembered that my old virtual system which was set up with a Version of VirtualBox 3 running in VirtualBox 4.0.10 I don't had the problem, so I downgraded to 4.0.10, but still the problem, but the interesting thing is, that when i start the old virtual system I don't experience the problem.
|
|||

