Custom Query (16363 matches)
Results (2014 - 2016 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16255 | obsolete | host memory leak on CentOS 7 with VirtualBox 5.1.10 | ||
| Description |
I appear to be experiencing a host memory leak running VirtualBox 5.1.10 on CentOS 7 hostVM (uname -r) 3.10.0-327.36.3.el7.x86_64 Guest VM is Windows 10, build 1607 Suspect lines from the logs are: 48:01:00.432446 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :=>DxgkDdiQueryCurrentFenceNew 48:01:00.481870 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :uncompleted fences, u32FenceSubmitted(2257299), u32FenceCompleted(2257297) u32FenceProcessed(2257297) Originally, the VM was set for 12GB (Host has 16GB) and the VirtualBox user process ran up to 16GB, system started using swap heavily and ground to a halt. Reset VM to 10GB and user process has grown to 14GB and continues to grow slowly, requiring that the guest be shutdown and VirtualBox exited to free the memory. |
|||
| #16251 | fixed | VB Guru meditation with emR3Debug: rc=VERR_IEM_ASPECT_NOT_IMPLEMENTED | ||
| Description |
I was using vagrant to start a virtual box. The box comes up and almost immediately goes into a guru mediation state. The log show VERR_IEM_ASPECT_NOT_IMPLEMENTED. This error is happening for several of the current kernels for RHEL 5. Mark |
|||
| #16248 | wontfix | virtio netkvm DriverVer=08/11/2016,61.73.104.12600 not working in W7 amd64 guest | ||
| Description |
Host is Linux 3.10.0-514.el7.x86_64, VirtualBox 5.1.9_111846_el7. DriverVer=04/29/2014,61.70.104.8100 is working. Both drivers install successfully, tried NAT and bridged mode with same results. By "not working" i mean that guest is unable to get IP address from DHCP server and any attempt to change virtio-net driver properties (for ex. link speed in guest) will end up with hanging props window. |
|||

