Custom Query (16363 matches)
Results (622 - 624 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #625 | fixed | Winxp host freezes when attempting to use a host serial port. -> fixed in SVN/1.5.2 | ||
| Description |
When attempting to use a host serial port under a windows xp professional host, the host system freezes when trying to start the virtual machine It is not possible to use ctrl+alt+del to kill vbox from the task manager at this point, the task manager doesn't even come up. The only way to get out of this is to use the reset button. The serial port was configured as follows: vboxmanage modifyvm debian -uart1 0x03f8 4 -uartmode1 COM2 and vboxmanage returned no errors. Using showvminfo verifies that uart1 is attached to host device com2. It doesn't matter if uart1, or uart2 is used, and it doesn't matter which valid host com port is used, the result is still the same. If uartmode1 is set to disconnected instead of COM2, the vm boots without problems, and a virtual serial port is visible inside the guest. This problem exists in already created virtual machines, as well as any new machines created with various settings. The only thing they all have in common is that the virtual serial port is attached to a physical host serial port. A log file from a run of a virtual machine attached to host com2 is included with this bug report. I waited 2 minutes from the time I started the vm, to the time I used the reset button. Normally, this is long enough to start the debian vm without the host serial port attached, and to be sitting at the login screen for some time. In other words, normally, it takes the debian vm much less than 2 minutes to get from start-up, to the login screen. |
|||
| #626 | invalid | problem with installation of VirtualBox_1.5.0_Win_amd64.msi | ||
| Description |
My computer uses an AMD Athlon 3200 processor. However, when I tried to install the VirtualBox_1.5.0_Win_amd64.msi I received a notice that "This installation package is unsupported for this type of processor". (Note that the quote is a translation, the original message was in dutch). What am I missing here? |
|||
| #627 | fixed | virtualbox doesn't play pc speaker sounds generated by the guest -> partly fixed, contributions welcome (see description) | ||
| Description |
When the guest generates sounds via the pc speaker, they aren't played on the host through either the host's pc speaker if one exists, and/or through the host's sound card. I believe that vmware sends pc speaker sounds generated by the guest to the host's pc speaker, and I know that both qemu, as well as virtualpc send pc speaker sounds generated by the guest to the host's sound card. I personally would find it very helpful to hear any pc speaker beeps which the guest generates, and would appreciate it if the inclusion of this feature in virtualbox could please be considered. Update Oct 1 2018: This was fixed in a very limited way<1> in VirtualBox 5.0.18. Patches for a more general fix are welcome. Please write to the vbox-dev mailing list if you are seriously interested in contributing. |
|||

