Custom Query (16363 matches)
Results (2368 - 2370 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. |
|||
| #12157 | obsolete | cdc_acm disconnect and reconnect | ||
| Description |
Hi, I have a Dell Poweredge with Debian Squeeze 64 bit and kernel 3.2.0-0.bpo.2-amd64 (host). I've tried with both virtualbox-4.2_4.2.18-88780~Debian~squeeze_amd64 and virtualbox-4.1_4.1.26-84997~Debian~squeeze_amd64 but same problem. Windows XP Professional as guest. I've connected an Arduino Leonardo to the usb of Linux Host. Here it creates two input HID devices and one serial (/dev/ttyACM0) managed by cdc_acm module. I connect it via serial port of Windows guest (Com1, Host Device, /dev/ttyACM0), but when i start the guest (just after Windows xp screen appears) the host disconnect the usb device and then reconnects it. But in this case ttyACM0 is busy by VB and udev create new device as /dev/ttyACM1. Obviously in windows guest if i connect to COM1 I have no response (it is attached to an actually inexistent device, ttyACM0). Here is extract from /var/log/syslog after guest starting: Oct 4 08:47:41 esxi kernel: [43501.099490] device eth0 left promiscuous mode Oct 4 08:47:42 esxi kernel: [43501.868198] vboxnetflt: dropped 0 out of 15419 packets Oct 4 08:48:11 esxi kernel: [43530.368526] device eth0 entered promiscuous mode Oct 4 08:48:17 esxi kernel: [43537.233623] usb 2-4: USB disconnect, device number 41 Oct 4 08:48:18 esxi kernel: [43537.744032] usb 2-4: new full-speed USB device number 42 using ohci_hcd Oct 4 08:48:18 esxi kernel: [43537.957038] usb 2-4: New USB device found, idVendor=2341, idProduct=0036 Oct 4 08:48:18 esxi kernel: [43537.957042] usb 2-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0 Oct 4 08:48:18 esxi kernel: [43537.957045] usb 2-4: Product: Arduino Leonardo Oct 4 08:48:18 esxi kernel: [43537.957048] usb 2-4: Manufacturer: Arduino LLC Oct 4 08:48:18 esxi kernel: [43537.960202] cdc_acm 2-4:1.0: ttyACM1: USB ACM device Oct 4 08:48:25 esxi kernel: [43545.330102] usb 2-4: USB disconnect, device number 42 Oct 4 08:48:26 esxi kernel: [43545.784024] usb 2-4: new full-speed USB device number 43 using ohci_hcd Oct 4 08:48:26 esxi kernel: [43546.006027] usb 2-4: New USB device found, idVendor=2341, idProduct=8036 Oct 4 08:48:26 esxi kernel: [43546.006032] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Oct 4 08:48:26 esxi kernel: [43546.006035] usb 2-4: Product: Arduino Leonardo Oct 4 08:48:26 esxi kernel: [43546.006037] usb 2-4: Manufacturer: Arduino LLC Oct 4 08:48:26 esxi kernel: [43546.009152] cdc_acm 2-4:1.0: This device cannot do calls on its own. It is not a modem. Oct 4 08:48:26 esxi kernel: [43546.012843] cdc_acm 2-4:1.0: ttyACM1: USB ACM device Oct 4 08:48:26 esxi kernel: [43546.027148] input: Arduino LLC Arduino Leonardo as /devices/pci0000:00/0000:00:02.0/usb2/2-4/2-4:1.2/input/input35 Oct 4 08:48:26 esxi kernel: [43546.027422] generic-usb 0003:2341:8036.0021: input,hidraw0: USB HID v1.01 Mouse [Arduino LLC Arduino Leonardo] on usb-0000:00:02.0-4/input2 Have you got any idea? thanks |
|||
| #12158 | obsolete | Arduino usb device | ||
| Description |
Hi, I have a Dell Poweredge with Debian Squeeze 64 bit and kernel 3.2.0-0.bpo.2-amd64 (host). I've tried with both virtualbox-4.2_4.2.18-88780~Debian~squeeze_amd64 and virtualbox-4.1_4.1.26-84997~Debian~squeeze_amd64 but same problem. Windows XP Professional as guest. I've reported a bug where i tried to attach serial device to /dev/ttyACM0 in #12157 , now i want to try to attach usb device to windows guest. I've tried both with USB Controller 2.0 enabled and disabled, same result. If i attach Arduino leonardo device (Bus 002 Device 043: ID 2341:8036) to windows guest it correctly recognise it and install HID device and COM port. But com port is not usable, if i connect with putty nothing come in (arduino is writing on serial) and if i try to send a character it gives me an error (writing to serial failed). Antoher issue: If i try to attach it vith phpvirtualbox 4.2-7 it gives me this error: VirtualBox error: USB device 'Arduino LLC Arduino Leonardo' with UUID {ad319708-42a5-4048-a5b6-4f4a001fb66c} is busy with a previous request. Please try again later (0x80070057) With previous version (4.1) of virtualbox and phpVB it attach it correctly (but in guest it doesn't work). Have you got any idea? thanks |
|||

