Custom Query (16363 matches)
Results (1318 - 1320 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17917 | obsolete | hostonly + allow all can't ping guest from host | ||
| Description |
Host : Fedora 28, kernel =4.17.9-200.fc28.x86_64 VirtualBox : 5.2.16 Guest : MSEgde - Win10 image downloaded from Microsoft I have 2 NIC : NIC1 : NAT NIC2 : HostOnly Promiscious mode = Allow All The trouble : Host can't ping guest (ping 192.168.56.101 not working) Over informations : Guest can reach internet (via the NAT nic) Guest can ping Host (via Hosonly nic) (Host IP is 192.168.56.1) Guest Host Only Nic is 192.168.56.1.101 When pinging 192.168.56.101 (the guest) from the Host Got no answer but I see the incoming packets in the guest NetwordCard status screen. In my situation, I can't use Bridge network so I need the hostonly network working good to make the host reaching the guest I hope you will fix that bug soon. Thanks for your job, I like VirtualBox !! |
|||
| #17916 | invalid | VboxManage.exe spawns new window when exec run from docker-machine on windows 7 | ||
| Description |
When running docker-machine with vboxmanage version 5.2.8r121009 the pre-check always fails to detect the version or capture stdout because vboxmanage.exe spawns a new window. I have recreated this with two scripts (golang and python) and when running the "vboxmanage --version" in the cmd cli it runs okay and output is in the same window but when execing the command from the scripts causes a new window to spawn so stdout cannot be captured. Details here; https://stackoverflow.com/questions/51676072/vboxmange-command-spawns-new-window-tested-with-go-os-exec-run-why-how-do |
|||
| #17915 | obsolete | Error in the IDE controller | ||
| Description |
Subj.
I started the virtual machine FreeBSD 11.2 and started the assembly of the world in it.
At some point the machine crashed I apply the configuration of the machine and the logs. A similar error occurred in the old version of VirtualBox 5.2.14 |
|||


