Custom Query (16363 matches)
Results (1690 - 1692 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16923 | duplicate | host only networking (hostonlyif) broken | ||
| Description |
We have just upgrade all our VM hosts to 5.1.24r117012 which obviously broke the whole vm networking across 300 VMs (hostonlyifs). It is not possible to ping the hostonly interface from the guest and the host system shows that all packets to the interface are being dropped. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial $ uname -a Linux mars 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ vboxmanage --version 5.1.24r117012 VBoxManage hostonlyif create VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.56.1 VBoxManage dhcpserver add --ifname vboxnet0 --ip 192.168.56.10 --netmask 255.255.255.0 --lowerip 192.168.56.200 --upperip VBoxManage dhcpserver modify --ifname vboxnet0 --enable $ sudo ifconfig vboxnet0 vboxnet0 Link encap:Ethernet HWaddr 0a:00:27:00:00:00
Note: Please consider the "dropped" count. All packets are being dropped. |
|||
| #16922 | duplicate | vboxnetX interfaces are not brought automatically up after upgrade from 5.1.22 to 5.1.24 | ||
| Description |
Just like title says: after upgrade to 5.1.24 host-only network does not work. I found that I need to invoke manually on the host sudo ifconfig vboxnet1 up to bring network interface up and than it works. It wasn't so on previous versions. Host: Linux Mint 18.2, 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux VirtualBox installed from deb http://download.virtualbox.org/virtualbox/debian xenial contrib |
|||
| #16921 | fixed | auto_logon fails on win7 guest | ||
| Description |
Using vbox 5.1.24 from debian-jessie (host), i noticed (only since upgrade from 5.1.22) the autologon fails. When trying to make use of it, the screen flickers endlessly (maybe failing to log in and retrying to in an endless loop). Manual login works fine though, but that is not intended. The last time, i did complain about this feature being broken was after 5.1 did appear (see https://www.virtualbox.org/ticket/15904) Behavior was different though. Now this feature is disfunctional once again. |
|||

