Custom Query (16363 matches)
Results (1945 - 1947 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #20248 | duplicate | When updated virtualbox. EVERY VIRTUAL MACHINE ARE NOT STARTING ANYMORE. | ||
| Description |
i Updated virtualbox only too see if they fixed a bug. then. No virtual machine wants to start! IDK why but i am MAD that is happening The thing is that I cant activate hypervisor partition. What do i do?? Here is the error that appears when i open a virtual machine Fallo al abrir una sesión para la máquina virtual Windows 7 Ultimate. Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE). AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED). Código resultado: E_FAIL (0x80004005) Componente: ConsoleWrap Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} |
|||
| #17198 | duplicate | Problema con el Bridge wifi (adaptador puente Wifi) | ||
| Description |
Hola, he actualizado el vbox a la ultima version igual mi SO win 10 donde esta instalado el vbox, problema es con el adpatador puente con mi tarjeta wifi esta config. no le da direccionamiento ip a las maquinas virtuales, por medio de adaptador puente Ethernet si da el direccionamiento a las maquinas, pero por wifi no , he actualizado el paquete de extensiones vbox, el driver de la tarjeta wifi y nada. |
|||
| #7547 | duplicate | Windows7 Linux guest frequently crashes with "Critical Error" (assertion: out of hyper memory) | ||
| Description |
Host is Windows7. Guest is Fedora 13. Guest frequently crashes during various tasks/programs. The error message displayed reads "A critical error has occurred while running the virtual machine and the machine execution has been stopped. I am attaching the most recent vbox.log and screenshot file to this ticket. |
|||

