Custom Query (16363 matches)
Results (2125 - 2127 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15999 | fixed | RamSize wrong value in VBox.log | ||
| Description |
Create a VM. Any will do. Set the memory to a non nice, binary, "round" number, for example 3043 MB (I just saw it on a test case, don't blame me). Here's what VBox.log has to say about it: RamSize <integer> = 0x00000000be300000 (3 190 816 768, 2 GB) Although the RAM is set to 2.97 GB, it is identified as 2 GB. Yes, it is correctly identified to the byte, but it is not correctly identified in the "human readable" version. Some sort of lower(), int() conversion? This should be trivial to fix. And since we're at it, it would make sense to report that value in MB, the same that it is reported everywhere else, like the total host memory or the available host memory. BTW, I left the VBox version as empty, because this is way older behavior than the current 5.1.6 |
|||
| #15998 | fixed | segfault at 18 in libc-2.19.so with VB 5.1.6 | ||
| Description |
Guest and all VBox controls totally unresponsive. Had to kill VBoxSVC from another session to regain control. CPU was NOT at 100% as in previous freezes. Sep 26 16:44:20 Gull2 kernel: usb 3-11.4: Manufacturer: Logitech Sep 27 10:00:40 Gull2 kernel: EMT-0[1624]: segfault at 18 ip 00007f94cfcd3b48 sp 00007f949e15a6e0 error 4 in libc-2.19.so[7f94cfc5b000+19e000] Sep 27 10:00:40 Gull2 kernel: device Net1 left promiscuous mode Sep 27 10:00:40 Gull2 kernel: vboxnetflt: 0 out of 15388517 packets were not sent (directed to host) Sep 27 10:01:06 Gull2 kernel: vboxdrv: ffffffffa14a1020 VMMR0.r0 Sep 27 10:01:06 Gull2 kernel: vboxdrv: ffffffffa15a0020 VBoxDDR0.r0 Sep 27 10:01:06 Gull2 kernel: VBoxNetFlt: attached to 'Net1' / ec:b1:d7:37:82:1c Sep 27 10:01:07 Gull2 kernel: vboxdrv: ffffffffa001e020 VBoxEhciR0.r0 Sep 27 10:01:07 Gull2 kernel: device Net1 entered promiscuous mode Sep 27 15:37:56 Gull2 kernel: usb 3-11.4: Manufacturer: Logitech Sep 27 15:44:30 Gull2 kernel: usb 3-11.4: Manufacturer: Logitech A VBox.Log is attached. However, this is from after the restart. It looks like the log from the fault was overwritten. |
|||
| #15988 | fixed | Sound starts crackling after a few minutes playing audio, Windows 8.1 guest crashes after selecting recording devices | ||
| Description |
Seems to be related to the microphone. I disabled in the host as a precaution after noticing the problem. Didn't change anything. I think the way Virtualbox interacts with the sound system must have changed. Using ALSA and AC97 with a Windows 8.1 Guest on an Arch Linux host. Disabling the enhancements in playback device seems to help with the crackling, but that shouldn't be necessary. It doesn't eliminate the crash on selecting recording devices, however. I even tried disabling the microphone in the device manager. Never had these problems before this version, but I haven't updated for a while. |
|||

