VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (991 - 993 of 16363)

Ticket Resolution Summary Owner Reporter
#20510 duplicate Attaching Yubikey USB device to VM causes Guest VM to Crash within Seconds OtterFlip
Description

Host OS: macOS 11.5.1 Guest OS: Ubuntu 20.04.2.0 x64 with Guest Additions installed VBox: 6.1.26

Within the Guest OS, when accessing a website that uses FIDO/U2F authentication with a Yubikey USB device, I attached the Yubikey to my host machine and then used the Devices | USB menu to pass through the Yubikey USB device to the Guest machine. The device worked properly and authentication with the website succeeded within the guest. However within a few seconds (perhaps 5 seconds) the guest VM process crashed and macOS displayed a "Problem Report for VirtualBox VM" dump report window with stack traces (see attachment). I repeated this three times and each time the crash occurred. On the third time, after successfully passing through and authenticating with the Yubikey USB device, I quickly accessed the Devices menu to detach the Yubikey USB device, which detachment appeared to succeed (the checkmark next to it was removed), however, again, a few seconds later the guest VM process crashed.

#15884 worksforme Attaching a BIOS file to a VM does not work in VirtualBox 5.1.4 bmn
Description

In VirtualBox 5.0.x it is possible to use the command
VBoxManage.exe setextradata MyVM VBoxInternal/Devices/pcbios/0/Config/BiosRom C:\bios.bin
to attach a BIOS file to a VM.

This feature is broken in VirtualBox 5.1.4. When the command is applied, the VM hangs during startup and does not boot the guest OS. (The same VM does boot the guest OS when no BIOS file is attached to it.)

The problem seems to be independent from the BIOS file, since it occurs even if the file bios.bin is an unaltered copy of VirtualBox 5.1.4's own BIOS (as it can be extracted from VBoxDD2.dll).

#4992 obsolete Attaching to host serial port on Windows 7: Permission problem Steve Weidman
Description

I am attempting to pass the RS-232 serial ports of the host operating through to the guest operating systems. I have fully functional COM1 and COM2 ports available and working in the host system. Serial Ports are set up in the guest operating system as Port 1, COM1, Host Device (COM1) and Port 2, COM2, Host Device (COM2) When I attempt to "map" these devices to the guest operating system, I receive the following error:

"Failed to start the virtual machine (Windows 7 RC, Windows 98SE and Windows 95C report the same error). Cannot open host device 'COM1'for read/write access. Check the permissions for the device. (VERR_ACCESS_DENIED). Unknown error creating VM(VERR_ACCESS_DENIED). Details: Result Code: E_FAIL (0x80004005) Component Console Interface: IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}"

The only way for the guest systems to start is to "disconnect" the serial ports.

Host System Details: Windows XP Pro, Version 2002, Service Pack 3 Intel Pentium 4, 3.00GHz 3.00GHz, 3.5GB of RAM COM1 I/O 03F8-03FF, IRQ 04 COM2 I/O 02F8-02FF, IRQ 03

VirtualBox 3.0.6 r52128

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy