Opened 15 years ago
Closed 15 years ago
#5095 closed defect (duplicate)
Incoherent network connection causes Virtualbox to freeze
| Reported by: | MoC | Owned by: | |
|---|---|---|---|
| Component: | network/NAT | Version: | VirtualBox 3.0.6 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
Hi,
I use VirtualBox on Windows XP SP3 to run Fedora 11 (I'm pretty sure though, that this problem does not depend on the type of the guest system, it also occured on e. g. Ubuntu 9.04.) and use a NAT to connect the virtual machine to my internet connection. I'm in a network with a traffic shaper, which causes the transfer rate to "jump around". Whenever the speed is near or equal 0, VirtualBox will freeze consuming all available CPU resources and is almost completely inresponsive. Now, I know that tickets like #2888 but since I don't know wether they are in a similiar network I thought I'd better open a seperate ticket. Frankly I cannot provide a log file since VirtualBox seems to write the logs to disk only if it exits dignifiedly (Why is that so?), but I made a screenshot showing the network load ("Netzwerk" tab in the task manager, above connection) and a snapshot of the CPU usage ("CPU-Auslastung" in the status bar of the task manager). This really is a blocker and I'd be really thankful if you could fix it as soon as possible.
Attachments (3)
Change History (9)
by , 15 years ago
| Attachment: | VirtualBox-IceCold.png added |
|---|
comment:1 by , 15 years ago
Could you please look at your home directory, find .VirtualBox\Machine\<your-machine-name>\Logs\VBox.log and attach it to the ticket?
comment:2 by , 15 years ago
| Component: | network → network/NAT |
|---|
by , 15 years ago
follow-up: 4 comment:3 by , 15 years ago
Like I said, it did not create a log (and I assume it's because I killed the process, though that's not good practice - if my assumption is true). The VBox.log is from a later session where I did not use the internet connection. But in case it still can help, I attached it.
follow-up: 5 comment:4 by , 15 years ago
Replying to MoC:
Like I said, it did not create a log (and I assume it's because I killed the process, though that's not good practice - if my assumption is true).
Hm ... sounds strange ...
The VBox.log is from a later session where I did not use the internet connection. But in case it still can help, I attached it.
Yes, please.
comment:5 by , 15 years ago
Replying to Hachiman:
Hm ... sounds strange ...
Ok, I do have to correct myself, it might very well be that it created a log file, I missleadingly assumed that even if you kill a process, Windows would update the mtime. Sorry for that. I reproduced above situation and attached the correct log.
VirtualBox freezing.