Custom Query (16363 matches)
Results (2146 - 2148 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15951 | fixed | Sound doesn't work ( Pulseaudio ) | ||
| Description |
My system has a USB sound card. It works fine in host ( Debian x64 ). It used to work fine a couple of weeks ago in Virtualbox guest. But, it doesn't work anymore in guest. When I explicitly attach the USB sound card from the USB menu in status bar, the entire VirtualBox window hangs, and the following output scrolls in VBox.log 00:02:38.835174 VUSB: Attached '00007f8ba0bd6310[proxy 0d8c:013c]' to port 2 00:02:41.155880 AssertLogRel /local/packages/source/svn/vbox/src/VBox/VMM/VMMAll/PGMAllPhys.cpp(2345) VBOXSTRICTRC pgmPhysReadHandler(PVM, PPGMPAGE, RTGCPHYS, void*, size_t, PGMACCESSORIGIN): PGM_HANDLER_PHYS_IS_VALID_STATUS(rcStrict, false) 00:02:41.155942 rcStrict=VERR_IOM_MMIO_IPE_2 GCPhys=00000000f000ff50 00:02:41.156036 AssertLogRel /local/packages/source/svn/vbox/src/VBox/VMM/VMMAll/PGMAllPhys.cpp(2345) VBOXSTRICTRC pgmPhysReadHandler(PVM, PPGMPAGE, RTGCPHYS, void*, size_t, PGMACCESSORIGIN): PGM_HANDLER_PHYS_IS_VALID_STATUS(rcStrict, false) 00:02:41.156052 rcStrict=VERR_IOM_MMIO_IPE_2 GCPhys=00000000f000ff50 00:02:41.156122 AssertLogRel /local/packages/source/svn/vbox/src/VBox/VMM/VMMAll/PGMAllPhys.cpp(2345) VBOXSTRICTRC pgmPhysReadHandler(PVM, PPGMPAGE, RTGCPHYS, void*, size_t, PGMACCESSORIGIN): PGM_HANDLER_PHYS_IS_VALID_STATUS(rcStrict, false) I have to close the window and abort the VM for things to get back to normal. This is the case with VirtualBox 5.1.4 / 5.1.6 and svn 5.1.51 r63850. |
|||
| #15949 | wontfix | Change default time stamp of Vbox.log to absolute (not relative) | ||
| Description |
Each entry of the release log (VBox.log) appears to have a time stamp. The format of which is hh:mm:ss: but relative to the start of the virtual machine. So an entry starting 00:24:31.123456 is 24 minutes and 31 seconds from when the guest was started. However, most if not all logs from within the guest (examples being the linux kernel log or the windows event log) prefix their entries with the wall clock time. This makes attempting to synchronise entries in both logs, for troubleshooting purposes, quite difficult. I did find out myself that I could get actual (not relative) time stamps in the release log by using the VBoxManage command but some users that are new to the product may not feel confident in attempting such commands, or indeed know about the command at all. Perhaps consideration could be given to changing the release log time stamp to show the wall clock time by default ? |
|||
| #15948 | fixed | vbox segfaults with large numbers of search domains in /etc/resolv.conf => Fixed in SVN | ||
| Description |
While vbox makes sure it doesn't read in more than RCPS_MAX_NAMESERVERS nameserver lines when parsing /etc/resolv.conf, it doesn't enforce a similar check against RCPS_MAX_SEARCHLIST for search domains. When using a VPN, sometimes absurd numbers of search domains happen (glibc only supports 6) and vbox will just segfault. I've made a fix (the resolv.conf parser helpfully compiles as a standalone program, which made locating the problematic chunk trivial) that I'll attach to this bug. Obligatory "patch is under the MIT license" because I did read the contributer guidelines. |
|||

