Opened 13 years ago
Closed 8 years ago
#9563 closed defect (obsolete)
Installation of Windows 2000 Professional guest results in spontaneous reboots.
| Reported by: | bifferos | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.1.2 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description (last modified by )
Host OS: Slackware Linux 64-bit Host CPU: quad core I7-2600 @3.4GHz Guest: Windows 2000 professional, with default guest settings for win2k
I'm sure I've installed Windows 2000 without issue in the past. The guest reboots occur somewhere around the hardware detection phase,the exact point at which it happens seems to vary. I've just got myself a somewhat more powerful host, so a change in timing could also be the issue. The system runs very fast at any rate so I wonder if this could be triggering the win2k installer bug (see qemu -win2k-hack option).
Attachments (2)
Change History (8)
comment:1 by , 13 years ago
by , 13 years ago
Log of win2k install session rebooting during the "Installing Components" phase
comment:2 by , 13 years ago
Note that the reboot was not during device detection, but installing components. All settings where defaults, both for win2k and Virtual box (default memory for win2k, default disk size, expanding disk etc...).
comment:3 by , 13 years ago
I was a bit paranoid about my win2k ISO being corrupt, so I tried with the same image on another system. Installation completed OK. The VBox version is the same, 4.1.2, but host setup is:
a) Significantly slower b) 32-bits c) An earlier linux kernel version (2.6.33.4) d) Running off an IDE drive
See VBox.2.log for details.
I will try some more combinations if I get time.
comment:4 by , 13 years ago
There is the following work-around:
- Install win2k as normal, but when the random reboot occurs during "Installing Components" power off the VM.
- Change CPU execution cap to 10%
- Power up again, and let the install complete. You will have to enter any license key and go through some setup dialogs again.
- Power off the machine
- Remove the execution cap, normal win2k booting and use appears to be OK without it.
It's quite possible a higher execution cap can be used. Note you do *not* want to start win2k execution with an execution cap of 10% since the text mode "windows is copying files" stage will take some time!
comment:5 by , 12 years ago
This problem does still occurs under version 4.1.8 where the host is Windows 7 Home Premium 64 bits and Linux OpenSUSE 12.1 64bits.
comment:6 by , 8 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → obsolete |
| Status: | new → closed |
Do you have a VBox.log for such a session available?