Opened 16 years ago
Closed 15 years ago
#3317 closed defect (duplicate)
VT-x defect with windows 3.11, 95, 98 guest
Reported by: | slimjim8094 | Owned by: | |
---|---|---|---|
Component: | VMM/HWACCM | Version: | VirtualBox 2.1.2 |
Keywords: | vt-x, vtx windows, crash, first boot | Cc: | |
Guest type: | Windows | Host type: | Linux |
Description ¶
With (at least) Windows 3.11 (workgroups), Windows 95, and Windows 98, the first-boot (and subsequent boots) fail without error if VT-x is enabled. Specificlly, Windows 3.11 experiences severe (unusable) graphics corruption.
Without VT-x, these all work fine.
Linux x86-64 host with a Core2 Duo. Windows XP, Vista, 2k3, 2k8, 7, Linux guests all work fine with VT-x enabled. Nothing specific in the log file.
Untested on x86 linux host, windows host, amd, etc.
Change History (17)
follow-up: 2 comment:1 by , 16 years ago
comment:2 by , 16 years ago
comment:3 by , 16 years ago
i have the same issue. with VT-x on it locks solid on startup. without VT-x, it's fine (but slow).
i took a bootlog from windows booting up with vt-x enabled and booting with it disabled
when enabled, the bootlog ends with
LoadSuccess = msmouse.vxd
when i disable the VT-x and boot again (ie: in order to see what would come next if everything was working OK, i see):
SYSCRITINIT = VMM
so probably the thing that is crashing is the "SYSCRITINIT = VMM" part, whatever that means.
comment:5 by , 16 years ago
booting the host OS in single-CPU (ie: linux 'nosmp' boot parameter) does not help either so it is unlikely to be related to the fact that enabling VT-x also allows multiple cores to be visible (unless 'nosmp' fails to disable this...)
comment:6 by , 16 years ago
anybody figure this out or know if it worked in a previous release of virtualbox?
if it didn't work in a previous virtualbox version, i wonder if a fix could be made by using some custom bootloader in the VM. i've been wanting to learn more about the internals of the newer intel CPUs. i'll take a look and see if any registers pop out as maybe needing a small adjustment to work with 98.
comment:7 by , 16 years ago
I tried this on a Mac OS X 10.6.0 host today on a P8400 Core 2 Duo Mac Mini. Same results. Hung immediately after attempting to start the graphical mode for Windows 3.11 in the installer (after disk 2). Disabling VT-x fixed this problem.
comment:8 by , 15 years ago
Cc: | removed |
---|
Try again with 3.0.8 and attach the session's VBox.log here please.
comment:9 by , 15 years ago
comment:10 by , 15 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Retry with 3.1.4 please. Note that no VBox.log means we can't help in any way. Marking this one as invalid until such a log file is attached.
comment:11 by , 15 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Still an issue with VirtualBox 3.1.6, Windows 98 guest, Slackware64 13 host.
Install program has heavy graphics corruption.
by , 15 years ago
VBox.log for booting install cd, entering install program and then powering off
by , 15 years ago
Attachment: | ash-with-vtx-hang.log added |
---|
Fresh install of MSDOS 6.22 and Windows 3.11, VT-x turned on (Hangs upon transition into GUI)
by , 15 years ago
Attachment: | ash-no-vtx-nohang.log added |
---|
Fresh install of MSDOS 6.22 and Windows 3.11, VT-x turned off (Continues to next step upon transition into GUI for Windows install)
comment:12 by , 15 years ago
I have attached a crashing-with-VTx and not-crashing-without-VTx log that correspond to the issue I am having. Since my initial report, I have upgraded to Mac OS X 10.6.3 on the host and Virtual Box 3.1.6. I created a fresh VM to guarantee easy replication.
comment:14 by , 15 years ago
Resolution: | → duplicate |
---|---|
Status: | reopened → closed |
x86 linux host: win98 fails with VT-x and works without it.