blob: deb3a3a30fb577dfc74ea3c5b2fb0d3aa3f39dce (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
KVM: 0.529
kernel: 0.469
virtual: 0.423
device: 0.418
architecture: 0.402
hypervisor: 0.394
semantic: 0.361
x86: 0.332
graphic: 0.316
user-level: 0.258
peripherals: 0.251
performance: 0.195
boot: 0.169
mistranslation: 0.161
ppc: 0.150
socket: 0.126
PID: 0.112
assembly: 0.108
network: 0.091
register: 0.089
permissions: 0.083
files: 0.069
vnc: 0.067
i386: 0.062
debug: 0.055
risc-v: 0.055
arm: 0.043
VMM: 0.024
TCG: 0.022
Win98SE glitches RHEL6.2/CentOS6.2 QEMU
I'm not sure if this is something anyone will be interested in,
but I ran into some glitches setting up a Windows 98 SE
QEMU VM with a relatively recent version. Needed this
to restore an ancient backup and got it working well
enough to get the job done.
Versions
========
Distro: CentOS 6.2
Kernel: upstream 3.1.8
QEMU:
gpxe-roms-qemu-0.9.7-6.9.el6.noarch
qemu-img-0.12.1.2-2.209.el6_2.1.x86_64
qemu-kvm-0.12.1.2-2.209.el6_2.1.x86_64
Glitches:
1) Doesn't work in KVM mode, screen goes black
just after installer is finishing up and switching to
Win98. Saw this issue has been around for awhile.
2) Got it working in QEMU mode, but BIOS plug-n-play
driver fails. This prevents other devices from working.
a) CDROM not recognized
b) Realtek 8139C driver (installed separately after
Win98) not recognized.
I don't need these issues fixed, just reporting the
in case it's of interest and/or helpful. Can provide
more detail on request.
QEMU 0.12 is pretty much outdated nowadays - can you still reproduce these issues with the latest version of QEMU?
[Expired for QEMU because there has been no activity for 60 days.]
|