Custom Query (16363 matches)
Results (1444 - 1446 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2271 | worksforme | VirtualBox got killed by host because out of memory | ||
| Description |
Hi, My system: Ubuntu Linux 8.04. Memory: 2GBytes Windows XP host: using 1GByt of memory. Problem: randomly my virtual Windows got killed by Linux host with this log entry: Sep 18 09:49:19 my-host-name kernel: [ 648.872976] Out of memory: kill process 7392 (VBoxSVC) score 2218291 or a child Please help Thanks, |
|||
| #2320 | obsolete | "Close Virtual Machine" dialog pop up at boot up. | ||
| Description |
Recently, after upgraded to 2.0.2, I saw at random time (sometime frequently), the "Close Virtual Machine" dialog pop up during boot up. If I click Cancel then the boot process continued without and problem.
My two systems: Here is the portion of the log where the VM got suspended: 00:01:25.471 Guest Additions information report: additionsVersion = 0x00010004 osType = 0x00033000 00:01:25.485 Guest reported fixed hypervisor window at 0x00000000f6000000 (size = 0xc00000, rc = VINF_SUCCESS) 00:01:25.496 Audio: set_record_source ars=0 als=0 (not implemented) 00:01:25.497 Audio: set_record_source ars=0 als=0 (not implemented) 00:01:25.510 OHCI: Software reset 00:01:25.510 OHCI: USB Reset 00:01:25.510 OHCI: USB Operational 00:01:25.602 SharedFolders host service: connected, u32ClientID = 1 00:01:25.832 PCNet#0: Init: ss32=1 GCRDRA=0x06975420[64] GCTDRA=0x06975020[64] 00:01:26.631 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00007f67ae000000 w=1920 h=1056 bpp=32 cbLine=0x1E00 00:01:26.632 VBVA: Enabled. 00:01:26.696 OHCI: USB Suspended 00:01:26.874 Guest requests mouse pointer integration 00:01:26.883 Changing the VM state from 'RUNNING' to 'SUSPENDED'. 00:01:32.816 Changing the VM state from 'SUSPENDED' to 'RUNNING'. 00:01:33.120 EHCI: USB Suspended 00:01:35.398 NAT: DHCP offered IP address 10.0.2.15 00:01:35.646 PCNet#0: Init: ss32=1 GCRDRA=0x06975420[64] GCTDRA=0x06975020[64] |
|||
| #15427 | fixed | 5.0.21 107262 enables paravirtualisation on old saved guest => it won't start | ||
| Description |
Somehow the new test versions (tried 5.0.21-107170 and 5.0.21-107262) decide to enable the paravirtualisation support (Hyper-V) on my old VM (state was saved in 2014). Therefore it won't start with memory write error and "pdm#1: Device 'GIMDev'/0 not found in the saved state" in the log. So I have to manually add <Paravirt provider="None"/> to fix the VM. I've attached the original VM config. It's Win7 x32 VM on Win7 x64 host. |
|||

