Custom Query (16363 matches)
Results (142 - 144 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8531 | duplicate | whole system freeze when left running - 3.2.8, 4.0.0, and 4.0.4 | ||
| Description |
VirtualBox appears to be freezing my system when left running for more than a few minutes. It doesn't happen quickly but every time I have it running for at least 20 minutes or so (I haven't kept track of the actual time) I will be confronted with a completely frozen computer. This has happened on a 17" i7 MBP, and a 15" Core2duo MBP running 10.6.5 and 10.6.6. In version 3.2.8 I would get kernel panics whether I was running VirtualBox or not, and in version 4 the system just freezes in place while I'm running VirtualBox. Most of the time this has happened when I let the computers sit idle for some time. A couple times it has happened while I was actively doing something in the host OS. I don't recall a freeze yet happening if I was actively clicking around in the guest OS. |
|||
| #2306 | fixed | where mouse is drawn on guest does not match mouse coordinates -> fixed in SVN | ||
| Description |
I've observed this on Debian Etch 64-bit guest running on Ubuntu 8.04 64-bit host; VirtualBox 2.0.2. With *some* guest screen resolutions (not all) the mouse seems to be drawn in the wrong location. Near the top of the screen, the mouse is OK. But as the mouse progresses through the Y axis towards the bottom of the screen, an offset appears between the drawn mouse and where X think the mouse is located. Near the bottom of the screen, I've seen a difference of maybe 100 pixels between the drawn mouse and where X thinks the mouse is located. This is very obvious when dragging a window towards the bottom of the screen, or trying to click on a button located near the bottom of the screen. End result is you must click anywhere between 50 to 100 pixels "higher" than where you actually want to click. Example resolution (/etc/X11/xorg.conf) where this problem does not happen: 1280x1024 Example resolutions where this problem occurs: 1400x940, 1152x864, 1200x950 Workaround: if I disable mouse integration then the mouse works fine. |
|||
| #1559 | fixed | when starting a 1.6.0 VM on fedor8 or fedora 9 with hardware assist virtualization enabled vboxdrv gives a general protection faults | ||
| Description |
general protection fault: 0000 [1] SMP CPU 0 Modules linked in: tun vboxdrv autofs4 coretemp hwmon lockd sunrpc bridge nf_con ntrack_netbios_ns xt_tcpudp ipt_REJECT ipt_LOG nf_conntrack_ipv4 xt_state nf_con ntrack iptable_filter ip_tables x_tables acpi_cpufreq freq_table dm_multipath kv m_intel kvm snd_hda_intel snd_usb_audio snd_usb_lib snd_rawmidi snd_seq_dummy sn d_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss ppdev snd_mixer_ oss firewire_ohci firewire_core parport_pc snd_pcm dcdbas floppy parport snd_tim er iTCO_wdt snd_page_alloc iTCO_vendor_support i2c_i801 crc_itu_t tg3 pcspkr i82 975x_edac i2c_core button snd_hwdep serio_raw edac_core sg snd sr_mod soundcore cdrom ata_piix dm_snapshot dm_zero dm_mirror dm_mod ahci libata sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: microcode] Pid: 5453, comm: VirtualBox Not tainted 2.6.25.3-18.fc9.x86_64 #1 RIP: 0010:[<ffffc200052d716f>] [<ffffc200052d716f>] RSP: 0018:ffff8100d084fd40 EFLAGS: 00010002 RAX: 0000000000000264 RBX: ffffc20005295320 RCX: 0000000000000000 RDX: ffffc20005295320 RSI: 0000000000000004 RDI: ffffc20005295000 RBP: ffff8100d084fd68 R08: 0000000000000000 R09: ffffc20005295000 R10: 0000000000000001 R11: ffff8100d3433bc0 R12: 00000000ffffffdb R13: ffff8100dd095ed0 R14: 00000000c0305689 R15: 000000004210fe40 FS: 0000000042110950(0063) GS:ffffffff813f6000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000008a0225 CR3: 00000000d0820000 CR4: 00000000000026e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process VirtualBox (pid: 5453, threadinfo ffff8100d084e000, task ffff8100d084c000) Stack: ffffc200052d7012 0000000000000010 ffffffff883ad541 00000000fffffff9
Call Trace:
Code: 20 d8 48 89 82 a0 02 00 00 0f 20 e0 48 89 82 a8 02 00 00 48 83 e0 70 8b 8a
RIP [<ffffc200052d716f>]
---[ end trace a92775f681caeef6 ]--- |
|||

