Opened 14 years ago
Closed 13 years ago
#7267 closed defect (fixed)
Windows 7 x64 guest causes host Fedora (11 & 13) x86 running 3.2.6 to hang when bridged networking is used
| Reported by: | William Pratt | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 3.2.6 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description
Since 3.2.6, when I attempt to start my win7 x64 guest it would freeze the host (x86 fedora 13) and force me to cold restart the machine. I couldn't ssh to or even ping the host. I searched around the bug tracker and never found an exact match for this bug, although is seems very similar to Bug #6898. I could boot all other guests (various *nix both nat & bridged) with no issues, but the Win7 x64 guest would freeze the host every time. After switching to NAT (not preferable for me) I can use the guest again and so far no host freezes. I don't have any logs to send as the Vbox logs contain nothing relevant as they are not written to as soon as the host hangs which is practically immediate. I'm running the latest stock fedora 13 PAE kernel 2.6.33.6-147.fc13.i686.PAE and the fedora 13 rpm version of 3.2.6 r63112. If you need any further info or want me to test anything please let me know and I'll be glad to help. I tried hard to find my exact issue in the tracker, but didn't seem to find it. If this is a duplicate I'm sorry and please mark it as such.
TIA, -Bill
Attachments (2)
Change History (11)
follow-up: 2 comment:1 by , 14 years ago
comment:2 by , 14 years ago
Replying to frank:
Please attach a VBox.log file from a VM which does not reboot the host. This will help us to identify your host configuration. Well, at least you are executing a 64-bit guest on a 32-bit host, correct? And do you have an AMD CPU or an Intel CPU?
Correct, I am running Fedora 13 x86 and this appears to only happen on Windows7 64-bit but it's possible it would happen on other 64-bit, I just don't have any other b4-bit guests to try. If you want I can install a fedora 64-bit guest and try. I attached a log from a CentOS 4 x86 host using bridged networking. This host works fine. Also, just to clarify, it doesn't actually reboot the host, it freezes it solid and forces me to perform a cold restart.
comment:3 by , 14 years ago
Oops, I misspoke in the above comment. The attachment is from a CentOS 4 x86 *guest* not host. The guest and host both work fine while this guest is running with bridged networking. Sorry for any confusion.
comment:4 by , 14 years ago
Ok, from your log file I can see that your host has an Intel Core 2 Duo E6850. Yes, it would be interesting if you are able to boot another 64-bit guest (e.g. Fedora like you proposed). Btw, your CentOS guest has very old (2.2.0) guest additions installed but this shouldn't trigger any problem.
When does your Windows 7 guest freeze the host? Very shortly after the VBox BIOS logo vanished?
comment:5 by , 14 years ago
Oh, and your Windows 7 guest does NOT freeze the host if you are using NAT networking, is that right?
comment:6 by , 14 years ago
Sorry about the old guest additions, that guest is a staging server for a rails app and it rarely gets used. I updated the guest additions to the latest and will attach the Vbox.log generated by booting it with the newer additions just in case it helps. The Win7 guest freezes the machine in a fraction of a second after starting. I don't even see the vbox splash screen. Yes, it is correct that when I use NAT the guest works fine. I have not had a freeze in the 2 days since I made that change and I've restarted the guest a few times just to try. I'll install fedora 13 x64 tonight to test and I'll comment on the results once I have them. Let me know if you need anything further.
by , 14 years ago
| Attachment: | VBox.log.bz2 added |
|---|
comment:7 by , 14 years ago
Ok, I installed a Fedora 13 64bit guest using NAT initially. I switched to bridged this evening, it booted up, I configured and brought up the interface successfully. I also rebooted a few times, and shut down completely, starting back from the Virtbox management console. I do not see the same crash behavior. I will attach the Vbox.log as Vbox_fedora13x64.log.bz2. Please let me know if you need any further info. I'll go through the settings between guests and see if I can find anything else that differs.
by , 14 years ago
| Attachment: | Vbox_fedora13x64.log.bz2 added |
|---|
Please attach a VBox.log file from a VM which does not reboot the host. This will help us to identify your host configuration. Well, at least you are executing a 64-bit guest on a 32-bit host, correct? And do you have an AMD CPU or an Intel CPU?