installing win2k 32 bit with kvm on AMD 64 bit (dual core)

[Xu Nakajima <xunakaj-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>]

Hello,
 I have an AMD machine with  3800+ Dual Core Processor

Athlon(tm) processor (x86_64).
FC6 (x86_64) is installed on this machine.

This processor DOES support SVM 
(cat /proc/cpuinfo | grep flags shows a line which
includes "svm").
I had built kvm-7 on that machine.
I had tried , according to kvm howto , the following:


modprobe kvm-amd

/usr/local/kvm/bin/qemu-img create -f qcow vdisk.img
10G

/usr/local/kvm/bin/qemu-system-x86_64 -no-acpi -hda
vdisk.img -cdrom /dev/hdb -boot d -m 384

where in the cdrom there is a win2k installation disk
(for 32 bit)
(and the cdrom is **NOT** mounted).

I get immediately an error: 

the console shows:
Segmentation fault

Message from syslogd@rh at Fri Dec 22 14:10:36 2006
...
rh kernel: general protection fault: 0000 [1] SMP 
  
The kernel shows:
...
...
Dec 22 14:10:36 rh kernel: general protection fault:
0000 [1] SMP 
Dec 22 14:10:36 rh kernel: last sysfs file:
/devices/pci0000:00/0000:00:00.0/irq
Dec 22 14:10:36 rh kernel: CPU 0 
Dec 22 14:10:36 rh kernel: Modules linked in:
kvm_amd(U) kvm(U) radeon(U) drm(U) netloop(U) netbk(U)
blktap(U) blkbk(U) autofs4(U) ppp_synctty(U)
ppp_async(U) crc_ccitt(U) ppp_generic(U) slhc(U)
ip_conntrack_netbios_ns(U) ipt_REJECT(U) xt_state(U)
ip_conntrack(U) nfnetlink(U) xt_tcpudp(U)
iptable_filter(U) ip_tables(U) x_tables(U)
nls_ascii(U) vfat(U) fat(U) dm_mirror(U)
dm_multipath(U) dm_mod(U) video(U) sbs(U) i2c_ec(U)
button(U) battery(U) asus_acpi(U) ac(U) floppy(U)
snd_hda_intel(U) snd_hda_codec(U) snd_seq_dummy(U)
snd_seq_oss(U) snd_seq_midi_event(U) sg(U) snd_seq(U)
snd_seq_device(U) pcspkr(U) snd_pcm_oss(U)
snd_mixer_oss(U) shpchp(U) i2c_nforce2(U) snd_pcm(U)
forcedeth(U) i2c_core(U) snd_timer(U) snd(U)
soundcore(U) snd_page_alloc(U) serio_raw(U) usblp(U)
ide_cd(U) cdrom(U) sata_nv(U) libata(U) sd_mod(U)
scsi_mod(U) ext3(U) jbd(U) ehci_hcd(U) ohci_hcd(U)
uhci_hcd(U)
Dec 22 14:10:36 rh kernel: Pid: 29316, comm:
qemu-system-x86 Not tainted 2.6.18-prep #2
Dec 22 14:10:36 rh kernel: RIP:
e030:[<ffffffff8854e7ee>]  [<ffffffff8854e7ee>]
:kvm_amd:svm_vcpu_run+0x6e/0x4c0
Dec 22 14:10:36 rh kernel: RSP: e02b:ffff880038233c88 
EFLAGS: 00010246
Dec 22 14:10:36 rh kernel: RAX: ffffffff88550ec0 RBX:
ffff88000777c0d0 RCX: 0000000000000000
Dec 22 14:10:36 rh kernel: RDX: 0000000000000000 RSI:
ffff880038233d08 RDI: ffff88000777c0d0
Dec 22 14:10:36 rh kernel: RBP: ffff88000777c0d0 R08:
0000000000000000 R09: 0000000000000000
Dec 22 14:10:36 rh kernel: R10: 0000000000000000 R11:
ffffffff8854d0e0 R12: 00007fff55fb0ff0
Dec 22 14:10:36 rh kernel: R13: ffff880038233d08 R14:
ffff880038233d08 R15: ffffffff8061b200
Dec 22 14:10:36 rh kernel: FS:  00002aaaaaacc560(0000)
GS:ffffffff805a1000(0000) knlGS:0000000000000000
Dec 22 14:10:37 rh kernel: CS:  e033 DS: 0000 ES: 0000
Dec 22 14:10:37 rh kernel: Process qemu-system-x86
(pid: 29316, threadinfo ffff880038232000, task
ffff880000b45830)
Dec 22 14:10:37 rh kernel: Stack:  ffff88000777c0e0 
0000000000000000  ffff88000777c0d0  00007fff55fb0ff0 
Dec 22 14:10:37 rh kernel:  ffff880038233d08 
0000000000000000  0000000000000000  ffffffff8853742b 
Dec 22 14:10:37 rh kernel:  ffff880000b45830 
00000000000280d2 
Dec 22 14:10:37 rh kernel: Call Trace:
Dec 22 14:10:37 rh kernel:  [<ffffffff8853742b>]
:kvm:kvm_dev_ioctl+0x2ab/0x11e0
Dec 22 14:10:37 rh kernel:  [<ffffffff8021125f>]
__alloc_pages+0x10f/0x300
Dec 22 14:10:37 rh kernel:  [<ffffffff8021003b>]
mark_page_accessed+0x1b/0x40
Dec 22 14:10:37 rh kernel:  [<ffffffff80215e8c>]
filemap_nopage+0x19c/0x390
Dec 22 14:10:37 rh kernel:  [<ffffffff80209965>]
__handle_mm_fault+0xfd5/0x1020
Dec 22 14:10:37 rh kernel:  [<ffffffff8026d311>]
_spin_lock_irqsave+0x21/0x40
Dec 22 14:10:37 rh kernel:  [<ffffffff80225fb7>]
__up_read+0x27/0xb0
Dec 22 14:10:37 rh kernel:  [<ffffffff8026d409>]
_spin_unlock_irqrestore+0x9/0x20
Dec 22 14:10:37 rh kernel:  [<ffffffff8020c0d9>]
do_page_fault+0xe09/0x1210
Dec 22 14:10:37 rh kernel:  [<ffffffff80248e7f>]
do_ioctl+0x2f/0xa0
Dec 22 14:10:37 rh kernel:  [<ffffffff802360eb>]
vfs_ioctl+0x29b/0x2d0
Dec 22 14:10:37 rh kernel:  [<ffffffff80254efc>]
sys_ioctl+0x6c/0xb0
Dec 22 14:10:37 rh kernel:  [<ffffffff80268832>]
system_call+0x86/0x8b
Dec 22 14:10:37 rh kernel:  [<ffffffff802687ac>]
system_call+0x0/0x8b
Dec 22 14:10:37 rh kernel: 
Dec 22 14:10:37 rh kernel: 
Dec 22 14:10:37 rh kernel: Code: 0f 01 dd 65 8b 0c 25
2c 00 00 00 48 63 d1 4c 89 f8 48 8b 14 
Dec 22 14:10:37 rh kernel: RIP  [<ffffffff8854e7ee>]
:kvm_amd:svm_vcpu_run+0x6e/0x4c0
Dec 22 14:10:37 rh kernel:  RSP <ffff880038233c88>

...
...

So my two questions are:
1) is such an installation is supported at all on this

configuration (dual core x86_64 AMD with Win2K 
installation of 32 bit)?

2) is it possible to use the same method when there is
FC6 x86_64 installation DVD in the /dev/hdb (the
-cdrom 
parameter).

Regards,
Xu




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV