Custom Query (16363 matches)
Results (61 - 63 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11223 | obsolete | Problems if USB-Serial adapter on host was removed during a session. | ||
| Description |
Scenario: Guest system have to interact with a device connected to an USB to RS232 adapter. Guest OS don't have driver for this adapter. Host OS (Linux) have this driver working fine. On host was created an udev rule to ensure that the specific adapter always have a symlink with the same name (/dev/ttyUSB.TK): KERNEL=="ttyUSB[0-9]*", DEVPATH=="/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/ttyUSB[0-9]*", SYMLINK+="ttyUSB.TK" VM have thins conf: <UART>
<Port slot="0" enabled="true" IOBase="0x3f8" IRQ="4" path="/dev/ttyUSB.TK" hostMode="HostDevice"/>
</UART>
Guest use his "hardware" serial device. So now I attach serial adapter, start virtual machine and all works fine. If the serial adapter is disconnected and reconnected while VM still running on VBox.log I see: 02:41:55.101588 VM: Raising runtime error 'DrvHostSerialFail' (fFlags=0x0) 02:41:55.101633 Console: VM runtime error: fatal=false, errorID=DrvHostSerialFail message="Ioctl failed for serial host device '/dev/ttyUSB.TK' (VERR_DEV_IO_ERROR). The device will not work properly" 02:41:55.102740 HostSerial#0: Serial Write failed with VERR_DEV_IO_ERROR; terminating send thread 02:41:55.102759 PDMThread: Thread 'SerSend' (00007f76e8461d50) quit unexpectedly with rc=VERR_DEV_IO_ERROR. and serial port on Guest stop to work. Now I have to Shutdown Guest (no reboot) and restart it. Summarizing: at the first I/O error on device VBox "disconnect" virtual device, closer real device and ignore it during all the session. I think that would be better if VBox trying to reopen real device, every X seconds, and restore functionality of virtualized device. |
|||
| #5423 | fixed | CentOS 5.x and nolapic (Enable IO APIC) | ||
| Description |
Host: Kubuntu 9.10 (Linux 2.6.31-14-generic 48-Ubuntu SMP x86_64) Guest: CentOS 5.x In VBox 3.0.10 I must append kernel boot parameter nolapic or enable IO APIC in the settings of the guest. Without that guest hangs during boot at NET: Registered protocol 2. |
|||
| #14844 | obsolete | OS X guest periodically freezes with Remote Management enabled | ||
| Description |
I maintain VirtualBox support for Tim Sutton's osx-vm-templates (https://github.com/timsutton/osx-vm-templates), which can use Packer to create a Vagrant-compatible OS X system. When building a new El Capitan box recently under 4.3 (verified up through 5.0.10), I discovered that the resulting box freezes periodically for about 5 seconds every 10 seconds. It seems the entire VM is frozen, since both SSH sessions and the console itself are unresponsive. This is specific to the VirtualBox provider; building the Vagrant box with VMware Fusion using the same artifacts and configuration doesn't exhibit this freezing behavior. I discovered that I can work around this issue by not enabling Apple's Remote Management service during the first-run installation. I added support to disable this to osx-vm-templates; pass -D DISABLE_REMOTE_MANAGEMENT to prepare_iso when building the DMG. Let me know if I can be of any help. Tim has been able to reproduce this issue on his system as well, see https://github.com/timsutton/osx-vm-templates/issues/43. I've written a blog post about building the Vagrant box using osx-vm-templates in case it's useful: http://spin.atomicobject.com/2015/11/17/vagrant-osx/ |
|||

