Opened 16 years ago
Closed 10 years ago
#3094 closed defect (obsolete)
have to remove vbox modules to restart windows xp guest
Reported by: | Brian J. Murrell | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.1.2 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Linux |
Description (last modified by )
On the same host that runs virtualbox which I have filed tickets 1923, 1299 I have an additional problem. It seems that if I start my windows xp guest first time after a boot it starts fine. A subsequent boot of the winxp guest (i.e. after I have done a restart/shutdown in the winxp guest) will hang on startup at the winxp splash screen. I then have to stop the winxp guest, "rmmod vboxnetflt vboxdrv" and them modprobe them back in and restart the guest to have it working again.
BTW: this is also the host/guest where the mouse capture doesn't work, but that might be related to the ticket where adding the guest additions fails for some silly reason. It would appear that whoever was working on that issue simply threw up his hands in defeat.
Attachments (2)
Change History (12)
comment:1 by , 16 years ago
Host type: | Windows → Linux |
---|
by , 16 years ago
VBox.log while waiting for XP guess to finish post-reboot boot
by , 16 years ago
dmesg at the point of waiting for XP guess to finish post-reboot boot
follow-up: 3 comment:2 by , 16 years ago
OK. The two attached files are as per your request. They were taken while I am waiting (and waiting, and waiting) for this XP guest to finish booting after having done a "Shutdown->Reboot" in it.
I will let it finish it's boot up (will probably take a couple of hours to complete) and can attach the VBox.log and dmesg again if you wish.
comment:3 by , 16 years ago
Replying to brian:
OK. The two attached files are as per your request.
Were these files any help? Or the file in the duplicate ticket 3260?
follow-up: 5 comment:4 by , 16 years ago
Actually I didn't spot any problem in the log file. So as you ask for the status I assume that you still have this problem, right? And did you tried the latest release (VBox 3.0.6)?
comment:5 by , 16 years ago
Replying to frank:
Actually I didn't spot any problem in the log file. So as you ask for the status I assume that you still have this problem, right?
It's always been there, through every release of VBox I have ever used, so I would assume it's still there. Fortunately I don't have to use Windows all that often so it has been a while since I tried.
And did you tried the latest release (VBox 3.0.6)?
I confess I have not, but given the history of this issue, being that it's happened in all of the dozen(s) of releases I have tried in the past, I am not hopeful. I will try again with 3.0.6 when I can afford the resources from my host. It's running another VM at the moment.
follow-up: 8 comment:7 by , 16 years ago
Also, when this hang occurs, does terminating the VM work without any problem or do you have to kill the VM process? And are your guest additions up-to-date?
comment:8 by , 16 years ago
Replying to frank:
Also, when this hang occurs, does terminating the VM work without any problem
OK. VM is hung right now trying to "reboot" windows xp.
Machine->Close->Power Off...
seems to terminate the VM.
or do you have to kill the VM process?
No, this does not seem necessary.
And are your guest additions up-to-date?
They were prior to this most recent attempt. I forgot to update them while I had XP running.
Interestingly enough, I didn't need to remove the modules to start windows xp again this time. I wonder if that will remain consistent.
comment:9 by , 16 years ago
comment:10 by , 10 years ago
Description: | modified (diff) |
---|---|
Resolution: | → obsolete |
Status: | new → closed |
So it looks like your host is Linux. Please could you attach the following to this defect (please use the attach button, don't cut'n'paste):