virtualbox.org

Hello, i use virtual box 5.1.14 (last version) with a Win7 VM on a RedHat 7.x laptop.

Within the VM i use 3 Monitors. (Laptop + 2 external connected LCDs)

After about 5 to 8 hours working every click within the windows VM gets slow... you cannot click on anyhting... you see always the mouse "hourglasses"
if you press CTRL-F (relase FULL screen) this is no more possible - no reaction

its getting slower and slower (no reaction on any click) till i get a "linux message" VM do not react - will you wait/or close...

then i wait and click 5 to 10 minutes within the VM till all windows are closed and the VM is shutting down.
if VM is then off the linux host is working fine and i can new start the VM and everything works again fine for about 5-8 hours....

if i click close the VM crash and after this i can start the VM new without any issue till again after 5-8 hours the same issue starts...

so ???
it's really disturbing!

Any help?
Thx.
Martin.

Please post a VM log file. With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.

Hi, here is the log from "just now" - same situation with a shutdown at the end....

Thx!

I'm seeing a lot of weird NAT activity, the IP lease being offered and accepted every few minutes ad nauseum. This is not normal. Is there something odd about your network connection? Are you behind a business proxy server that might be getting confused by your VM? In particular, could there be another NAT server issueing 10.x addresses?

You might want to see what happens if you use bridged networking. Of course you might need IT support to enable that for you.

10.0.0.138 is my DSL router which is also a DHCP server. my LINUX laptop gets from this 10.0.0.21
and there on this laptop (redhat 7) i run the windows VM gets 10.0.2.15 in my opinion from the LINUX as on the local network 10.0.2.x is not available / known netowork ID...
so this always check/renew the DHCP offer must be a "communication" between the LINUX host (virtual box) and the windows VM.

mPILZ wrote:so this always check/renew the DHCP offer must be a "communication" between the LINUX host (virtual box) and the windows VM.

I don't think so. I'm seeing 10.x addresses that I don't normally see on NAT. I'm not networking expert, but it seems to me that you have VirtualBox NAT using the same IP address range as your host network, and this could quite possibly cause problems, such as packet cascades. I'm sure that the reason VirtualBox NAT uses the 10.x address range is so it can identify the packets which come from a VM.

I'd like to know what happens if one or the other network mode is changed.

You say "DSL router" - do you mean a DSL modem? Typically a router on a LAN uses an address range such as 192.168.x.x, which VirtualBox NAT would not conflict with.