Custom Query (16363 matches)
Results (1864 - 1866 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16595 | obsolete | VirtualBox built-in DHCP server does not respond for host-only interface | ||
| Description |
I created virtual machine with 2 interfaces, first is NAT (eth0), second is host-only (eth1). Host-only interface eth1 is configured to use DHCP to obtain it's IP address. When I start the guest, only eth0 gets IP address from dhcp server, eth1 is unable to receive it's IP address. This is an excerpt from guest syslog: Mar 23 09:29:21 vagrant-ubuntu-trusty-64 kernel: [ 17.917469] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready Mar 23 09:29:21 vagrant-ubuntu-trusty-64 kernel: [ 17.918347] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Mar 23 09:29:21 vagrant-ubuntu-trusty-64 kernel: [ 17.918715] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Mar 23 09:29:21 vagrant-ubuntu-trusty-64 dhclient: Listening on LPF/eth1/08:00:27:e1:d3:44 Mar 23 09:29:21 vagrant-ubuntu-trusty-64 dhclient: Sending on LPF/eth1/08:00:27:e1:d3:44 Mar 23 09:29:21 vagrant-ubuntu-trusty-64 dhclient: Sending on Socket/fallback Mar 23 09:29:21 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 (xid=0xd467f16c) Mar 23 09:29:24 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6 (xid=0xd467f16c) Mar 23 09:29:30 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11 (xid=0xd467f16c) Mar 23 09:29:41 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 20 (xid=0xd467f16c) Mar 23 09:30:01 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 (xid=0xd467f16c) Mar 23 09:30:09 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14 (xid=0xd467f16c) Mar 23 09:30:23 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19 (xid=0xd467f16c) Mar 23 09:30:42 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 (xid=0xd467f16c) Mar 23 09:30:50 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15 (xid=0xd467f16c) Mar 23 09:31:05 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14 (xid=0xd467f16c) Mar 23 09:31:19 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12 (xid=0xd467f16c) Mar 23 09:31:31 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12 (xid=0xd467f16c) Mar 23 09:31:43 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 (xid=0xd467f16c) Mar 23 09:31:50 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 (xid=0xd467f16c) Mar 23 09:31:57 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12 (xid=0xd467f16c) Mar 23 09:32:09 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12 (xid=0xd467f16c) Mar 23 09:32:21 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16 (xid=0xd467f16c) Mar 23 09:32:37 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 (xid=0xd467f16c) Mar 23 09:32:45 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 (xid=0xd467f16c) Mar 23 09:32:53 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12 (xid=0xd467f16c) Mar 23 09:33:05 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16 (xid=0xd467f16c) Mar 23 09:33:21 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15 (xid=0xd467f16c) Mar 23 09:33:36 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15 (xid=0xd467f16c) Mar 23 09:33:51 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18 (xid=0xd467f16c) Mar 23 09:34:09 vagrant-ubuntu-trusty-64 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13 (xid=0xd467f16c) Mar 23 09:34:22 vagrant-ubuntu-trusty-64 dhclient: No DHCPOFFERS received. Mar 23 09:34:22 vagrant-ubuntu-trusty-64 dhclient: No working leases in persistent database - sleeping. Host OS is Debian 8.7 64 bit, guest OS is ubuntu 14.04 64 bit. I am using vagrant to create and start this guest. This issue appeared randomly and rarely for same time on two different linux hosts (debian and ubuntu 14.04). Now, I am unable to start the guest at all. |
|||
| #16593 | fixed | VM window size not being restored for jessie VMs -> fixed in releases higher than 5.1.22 | ||
| Description |
Host is jessie (debian 8), VBox version is 5.1.18 (just recently updated from 5.0) All VM's save and restore their window positions and size properly upon restarting them, except for the ones using jessie as guest too. Only the VM GUI position stays, the size gets reset to some (small) standard. I am not familar enough with the virtualbox.xml file format (or vmname.vbox for that matter) to determine, if the problem exists at save time or at restore time. |
|||
| #16592 | worksforme | Processor Core on 100% with VirtualBox | ||
| Description |
When the VM start the process turn 100%. This produces processor heating. |
|||

