Custom Query (16363 matches)
Results (1579 - 1581 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17194 | invalid | VBOX Guest additions 5.2 does not work with Ubuntu 17.10 -> guest configuration problem, please install gcc and make | ||
| Description |
I did install VirtualBox 5.2 in Windows 10 64-bit, version 1709 build 16299.19 The guest is Ubuntu 17.10 64-bit. Neither version of the guest additions work. I tried with:
An error is produced during Linux startup: VBoxClient: VBoxClient (seamless): failed to start. Stage: Setting guest IRQ filter mask Error: VERR_INTERNAL_ERROR |
|||
| #17193 | invalid | Networking with DHCP broken in 5.2.0 (at least release version) | ||
| Description |
Hello, Networking is broken for all of my VMs (DHCP). There are outgoing packets but incoming packets never reach the VM. Revert to 5.1.30 is ok. Thnx. |
|||
| #17191 | obsolete | VERR_SVM_NO_SVM with Windows 10 Version 1709 | ||
| Description |
I'm unable to start any VM with "AMD-V is not available (VERR_SVM_NO_SVM)" I've updated to Windows 10 Version 1709 and Virtual Box 5.2.0 because I got Blue Screens with Windows 10 Version 1709 and VirtualBox 5.1.26 (SYSTEM_SERVICE_EXCEPTION in VBoxDrv) All works fine a week ago with Windows 10 Version 1703 and VirtualBox 5.1.26 I've checked Hyper-V (as described in Ticket #14362) after the Windows Update and Hyper-V is not installed. Full message: AMD-V is not available (VERR_SVM_NO_SVM). Fehlercode:E_FAIL (0x80004005) Komponente:ConsoleWrap Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed} |
|||

