Custom Query (16363 matches)
Results (1738 - 1740 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16825 | fixed | Host Only NIC: VM exclusivly needed | ||
| Description |
As to configure VMs in part of a complex simulated network including an Multi-NIC FirewallRouter such as ClearOS it is needed, that the Virtual NICs on the - in my case - Windows-Host does only have the VirtualBox-Option, not any other of Windows, even TCP/IP enabled - thats for the VMs behind the VM and Host should NOT be able to direvt communicate via TCP/IP. Szenario:
Initial Configration of VirtualNICs in VirtualBox works well. In 2nd step disabling other Options in Windows NIC Manager incl. ZCP/IP, except VirtualBox. This works well so far, setup of ClearOS as FirewallRouter and ClientVMs in different VirtualNetworks, attached to the ClearOS - incl. Routing and Firewall works well. Problem: Starting VirtualBox completely new, a Warning is displayed networking failures on the VirtualNICs. Thsi is caused by the missing TCP/IP - Host address, which is deleted in the VirtualBox-VirtualNIC-HostOnly Adapter - it displays 0.0.0.0/0.0.0.0 This can be temporarily cleared by setting IP-Addresses on the VirtualNIXCs in VirtualBox, but it is back again on next start. You can bypass the warning by "Ignore" ad everything works well, but if you need to change any other default value, you have to temporaily set ip-addresses to finalize the dialog. Request: An Option to disable Host-TCP/IP on Virtual Host-Only-NICs or create a new type of adapter "VM-Only". |
|||
| #16824 | invalid | Error starting Windows 10 64 guest os (VERR_VMX_UNEXPECTED_INTERRUPTION_EXIT_TYPE) | ||
| Description |
Its giving me guru error. I tried every thing and using latest versionof v box for ubuntu zetsy. |
|||
| #16823 | invalid | unable to create a nickname | ||

