Custom Query (16363 matches)
Results (1534 - 1536 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13404 | wontfix | Swap Ctrl/Caps Lock not working in VirtualBox 4.3.16 -> intentional change | ||
| Description |
Until now my keyboard mapping in Kubuntu 14.04 has worked seamlessly in the guest OS of Windows 7, which I run in VirtualBox. But after the upgrade to VirtualBox version 4.3.16 r95972 the swapping of Ctrl & Caps Lock is not respected. Any ideas for fixing this - or is it a known bug in the new VirtualBox version? Thanks! -HStovring |
|||
| #15293 | obsolete | Can't start VM after configuring host only network | ||
| Description |
Running Windows 7 sp1 on the host, a 64-bit Debian (wheezy) server with first network adapter connected to hostonlyif - "VirtualBox Host-Only Ethernet Adapter" Steps to reproduce:
I would also like to point out that a lot of related defects have been closed after people have tried another version, but the thing is, it always works after reinstall, but the issue is still not fixed. So I believe this way to reproduce could be a nice opportunity to finally solve this problem. Error message when it fails: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND). Perhaps related: https://www.virtualbox.org/ticket/15103 https://www.virtualbox.org/ticket/15060 Tested with 5.0.10, 5.0.12, 5.0.14, 5.0.16, 5.0.17-106359 |
|||
| #15334 | fixed | vboxmanage startvm reports success even if virtualization is turned of and the vm won't start | ||
| Description |
vboxmanage startvm reports: VM successfully started, but the VM is not started, and if you try to start the vm from the GUI, you get an error message with the error code: VERR_VMX_MSR_ALL_VMX_DISABLED I'm running a Debian wheezy64 guest on Windows 7 SP1. So the workaround is to enable virtualization in the BIOS, but I would like to know that my script starting the server failed, instead of succeeded. |
|||

