Custom Query (16363 matches)
Results (2515 - 2517 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15315 | invalid | VirtualBox SEGV:s on s12_96 host, no problems on s12_95 | ||
| Description |
After upgrading my host and guest to s12_96 VirtualBox SEGV:s within minutes after starting the guest. Appears to be networking related. Stack trace: # mdb core.VirtualBox.2715 Loading modules: [ libc.so.1 libnvpair.so.1 libuutil.so.1 ld.so.1 ] > $C ffff80ffbe24b920 libc.so.1`mutex_lock_impl+0x4c() ffff80ffbe24b930 libc.so.1`mutex_lock+0xc() ffff80ffbe24b960 VBoxRT.so`RTSemEventSignal+0x7c() ffff80ffbe24b980 VBoxRT.so`rtReqQueueSubmit+0x48() ffff80ffbe24b9b0 VBoxRT.so`RTReqSubmit+0xc8() ffff80ffbe24ba00 VBoxRT.so`RTReqQueueCallV+0x1a5() ffff80ffbe24baf0 VBoxRT.so`RTReqQueueCallEx+0x85() ffff80ffbe24bb30 VBoxDD.so`slirp_output+0x62() ffff80ffbe24bbc0 VBoxDD.so`ip_output0+0x482() ffff80ffbe24bc00 VBoxDD.so`udp_output+0x68() ffff80ffbe24be30 VBoxDD.so`sorecvfrom+0x203() ffff80ffbe24be90 VBoxDD.so`slirp_select_poll+0x3b4() ffff80ffbe24bef0 VBoxDD.so`_Z19drvNATAsyncIoThreadP9PDMDRVINSP9PDMTHREAD+0x134() ffff80ffbe24bf30 VBoxVMM.so`_Z15pdmR3ThreadMainP11RTTHREADINTPv+0x6a() ffff80ffbe24bf50 VBoxRT.so`rtThreadMain+0x2c() ffff80ffbe24bf80 VBoxRT.so`_Z18rtThreadNativeMainPv+0x51() ffff80ffbe24bfa0 libc.so.1`_thrp_setup+0xa4() ffff80ffbe24bfb0 libc.so.1`_lwp_start() > |
|||
| #15313 | obsolete | Guest "chokes" and becomes unusable after random period of time | ||
| Description |
I am running a 3 core Centos 7 headless webserver guest on my Centos 6 host with AMD Phenom II X4. After random (but generally no less than a couple of days or a week) period of time, my guest hangs at high CPU usage (no less than 100% or 1 core full util) and becomes completely unresponsive or very very slow to respond (I can log in via SSH if I wait, but is practically unable to serve any requests). Top command inside guess reveals nothing - no proccess is using CPU, there is free physical memory and free swap. Top command in host also shows no abnormalities, apart from the guest CPU usage pegged at above 100%. After restarting (controlvm poweroff, startvm) file system corruption is commonplace, especially MySQL innodb, which is running in guest. Recently it was so bad that guest could no longer boot (something related to XFS filesystem got corrupted). Couple of years ago I recalled similar symptoms which I could solve by disabling IOAPIC. Now, I can no longer afford running guest with just 1 CPU. Guest is generally quite busy serving web requests and sustains about 1 - 3 load average 24/7. Interesting observation is that there is a "curve" to the way it becomes unresponsive - it is not abrupt and can happen over a period of couple of hours. See the Google Analytics graph of served users: |
|||
| #15311 | worksforme | Insane virtualbox interface problems | ||
| Description |
Hey guys Im having a lot of trouble with virtualbox on my computer : virtualbox interface is unusable,no matter the guest ! On a running VM,when i click on a menu it works fine, but when i want to click on a menu again, the menu are buggy and dont work anymore, AND the host screen doesnt react, change or is usable anymore ! This problems occurs even with the lastest test build version. Makes virtualbox unusable... |
|||


