[opensuse] athlon unable to run qemu-kvm, poosibly caused by cpu-parameter
I tried to get WinXP installed under kvm, and noticed I could not get it installed, because the MS-Win setup-procedure got confused. I had run two commands: qemu-img create -f qcow2 ./winxp.img 10G this command worked fine, to prepare a WinXP- immage on disk (in direc- tory /mnt/a14). Secondly I wanted to install the XP on disk such that qemu-kvm can work on it, and therefor I used the command qemu-kvm -M pc -m 1G -cpu athlon -cdrom /dev/sr0 -boot d /mnt/a14/winxp.img Having given this command the Windows setup started to run, but ended in failure with the message "Cannot load file SETUPREG.HIV into memory. Errorcode is 3072. Push any key to stop the installation program" Even though setup complained of not being able to find the SETUPREG.HIV-file, this file was present in the subdirectory I386 of the Win-XP-CD. I assume the setup-procedure got confused by the cpu-parameter of the qemu-kvm - command: qemu-kvm -cpu athlon. If the parameter had had i386 as its value, I suppose the setup-procedure of MS-Win would have searched the I386 directory, and everything had worked fine. Is this a known problem of the installation of WinXP under qemu-kvm, and does a work-around exist? If I could use my present allready installed XP-version on a separate partition as an input to the qemu-kvm command (instead of the MS Win CD) the problem might be side-stepped. Is this possible at all? Thanks for your interest. -W- Julien Michielsen julien@michkloo.xs4all.nl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Julien Michielsen - 10:57 22.06.09 wrote:
I tried to get WinXP installed under kvm, and noticed I could not get it installed, because the MS-Win setup-procedure got confused. I had run two commands: qemu-img create -f qcow2 ./winxp.img 10G this command worked fine, to prepare a WinXP- immage on disk (in direc- tory /mnt/a14). Secondly I wanted to install the XP on disk such that qemu-kvm can work on it, and therefor I used the command qemu-kvm -M pc -m 1G -cpu athlon -cdrom /dev/sr0 -boot d /mnt/a14/winxp.img
Having given this command the Windows setup started to run, but ended in failure with the message "Cannot load file SETUPREG.HIV into memory. Errorcode is 3072. Push any key to stop the installation program" Even though setup complained of not being able to find the SETUPREG.HIV-file, this file was present in the subdirectory I386 of the Win-XP-CD. I assume the setup-procedure got confused by the cpu-parameter of the qemu-kvm - command: qemu-kvm -cpu athlon. If the parameter had had i386 as its value, I suppose the setup-procedure of MS-Win would have searched the I386 directory, and everything had worked fine. Is this a known problem of the installation of WinXP under qemu-kvm, and does a work-around exist? If I could use my present allready installed XP-version on a separate partition as an input to the qemu-kvm command (instead of the MS Win CD) the problem might be side-stepped. Is this possible at all? Thanks for your interest.
I didn't run into the same problem, but I'm using several virtual machines with kvm and I never needed to specify -M or -cpu. I thought that specific CPU is supported only by qemu with disabled kvm support and to make use of kvm I never used -M or -cpu with kvm. Anyway athlon can be probably treated as i386 and I guess Windows detects only architecture (if they support any other architecture then i386). I would try to use image of CD-ROM on my disk instead of real cdrom. I guess it using real cd-rom can make things response slower and confuse windows. And you can use your existing installation on hdd in kvm, although I'm not sure if windows are able to handle such a hardware change. But it would be quite dangerous, if you'll access same partition from two different places... It can lead to filesystem inconsistency. You can use kvm -hda /dev/sda but as this is really dangerous unless you are sure that you will use it in right way and you've got good bootloader and you know what are you doing, I wouldn't suggest it. I'll recommend you to try to install your windows using cdrom image first. -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz
On Monday 22 June 2009 12:51:16 Michal Hrusecky wrote:
Julien Michielsen - 10:57 22.06.09 wrote:
I tried to get WinXP installed under kvm, and noticed I could not get it installed, because the MS-Win setup-procedure got confused. I had run two commands: qemu-img create -f qcow2 ./winxp.img 10G this command worked fine, to prepare a WinXP- immage on disk (in direc- tory /mnt/a14). Secondly I wanted to install the XP on disk such that qemu-kvm can work on it, and therefor I used the command qemu-kvm -M pc -m 1G -cpu athlon -cdrom /dev/sr0 -boot d /mnt/a14/winxp.img
Having given this command the Windows setup started to run, but ended in failure with the message "Cannot load file SETUPREG.HIV into memory. Errorcode is 3072. Push any key to stop the installation program" Even though setup complained of not being able to find the SETUPREG.HIV-file, this file was present in the subdirectory I386 of the Win-XP-CD. I assume the setup-procedure got confused by the cpu-parameter of the qemu-kvm - command: qemu-kvm -cpu athlon. If the parameter had had i386 as its value, I suppose the setup-procedure of MS-Win would have searched the I386 directory, and everything had worked fine. Is this a known problem of the installation of WinXP under qemu-kvm, and does a work-around exist? If I could use my present allready installed XP-version on a separate partition as an input to the qemu-kvm command (instead of the MS Win CD) the problem might be side-stepped. Is this possible at all? Thanks for your interest.
I didn't run into the same problem, but I'm using several virtual machines with kvm and I never needed to specify -M or -cpu. I thought that specific CPU is supported only by qemu with disabled kvm support and to make use of kvm I never used -M or -cpu with kvm. Anyway athlon can be probably treated as i386 and I guess Windows detects only architecture (if they support any other architecture then i386). I would try to use image of CD-ROM on my disk instead of real cdrom. I guess it using real cd-rom can make things response slower and confuse windows. And you can use your existing installation on hdd in kvm, although I'm not sure if windows are able to handle such a hardware change. But it would be quite dangerous, if you'll access same partition from two different places... It can lead to filesystem inconsistency. You can use
kvm -hda /dev/sda
but as this is really dangerous unless you are sure that you will use it in right way and you've got good bootloader and you know what are you doing, I wouldn't suggest it. I'll recommend you to try to install your windows using cdrom image first.
Thank you for your reply. As a start I issued the qemu-kvm with the least parameters possible, and I tried qemu-kvm -M pc -m 1G -cpu athlon -hda /dev/sda2 -boot d /mnt/a14/winxp.img but this did not work, and I got the output open /dev/kvm: No such file or directory Could not initialize KVM. Do you have kvm-amd or kvm-intel modprobe'd? If you want to use CPU emulation, start with -no-kvm. appearently it did not recognize the cpu, so I tried again with qemu-kvm -M pc -m 1G -cpu athlon -hda /dev/sda2 -boot d /mnt/a14/winxp.img open /dev/kvm: No such file or directory Could not initialize KVM. Do you have kvm-amd or kvm-intel modprobe'd? If you want to use CPU emulation, start with -no-kvm. -- Julien Michielsen julien_at_michkloo.xs4all.nl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Julien Michielsen - 22:12 22.06.09 wrote:
I didn't run into the same problem, but I'm using several virtual machines with kvm and I never needed to specify -M or -cpu. I thought that specific CPU is supported only by qemu with disabled kvm support and to make use of kvm I never used -M or -cpu with kvm. Anyway athlon can be probably treated as i386 and I guess Windows detects only architecture (if they support any other architecture then i386). I would try to use image of CD-ROM on my disk instead of real cdrom. I guess it using real cd-rom can make things response slower and confuse windows. And you can use your existing installation on hdd in kvm, although I'm not sure if windows are able to handle such a hardware change. But it would be quite dangerous, if you'll access same partition from two different places... It can lead to filesystem inconsistency. You can use
kvm -hda /dev/sda
but as this is really dangerous unless you are sure that you will use it in right way and you've got good bootloader and you know what are you doing, I wouldn't suggest it. I'll recommend you to try to install your windows using cdrom image first.
Thank you for your reply. As a start I issued the qemu-kvm with the least parameters possible, and I tried
qemu-kvm -M pc -m 1G -cpu athlon -hda /dev/sda2 -boot d /mnt/a14/winxp.img
but this did not work, and I got the output open /dev/kvm: No such file or directory Could not initialize KVM. Do you have kvm-amd or kvm-intel modprobe'd? If you want to use CPU emulation, start with -no-kvm. appearently it did not recognize the cpu, so I tried again with
qemu-kvm -M pc -m 1G -cpu athlon -hda /dev/sda2 -boot d /mnt/a14/winxp.img open /dev/kvm: No such file or directory Could not initialize KVM. Do you have kvm-amd or kvm-intel modprobe'd? If you want to use CPU emulation, start with -no-kvm.
As it says, it can't find kvm kernel module. If you want to use kvm with paravirtualization support you need appropriate kernel module loaded. You can check if module is loaded by using following command: lsmod | grep kvm If it doesn't output anything, try running as root following commands: modprobe kvm modprobe kvm-amd And least parameters possible would be: qemu-kvm -m 1G -hda /dev/sda2 -boot d /mnt/a14/winxp.img But this will run kvm while assuming that /dev/sda2 if your whole disk and windows partitioner will try to partition that disk. If you want to install new clean windows, I would prefer qcow2 image on disk as it is compressed and uses less disk space (and you can move it anywhere you want (burn it on DVD and copy it back only if really need it)). -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz
On Tuesday 23 June 2009 14:44:59 Michal Hrusecky wrote: Thanks for your reply. My reply to yours is almost at the bottom, so jump to the end to see my question.
Julien Michielsen - 22:12 22.06.09 wrote:
I didn't run into the same problem, but I'm using several virtual machines with kvm and I never needed to specify -M or -cpu. I thought that specific CPU is supported only by qemu with disabled kvm support and to make use of kvm I never used -M or -cpu with kvm. Anyway athlon can be probably treated as i386 and I guess Windows detects only architecture (if they support any other architecture then i386). I would try to use image of CD-ROM on my disk instead of real cdrom. I guess it using real cd-rom can make things response slower and confuse windows. And you can use your existing installation on hdd in kvm, although I'm not sure if windows are able to handle such a hardware change. But it would be quite dangerous, if you'll access same partition from two different places... It can lead to filesystem inconsistency. You can use
kvm -hda /dev/sda
but as this is really dangerous unless you are sure that you will use it in right way and you've got good bootloader and you know what are you doing, I wouldn't suggest it. I'll recommend you to try to install your windows using cdrom image first.
Thank you for your reply. As a start I issued the qemu-kvm with the least parameters possible, and I tried
qemu-kvm -M pc -m 1G -cpu athlon -hda /dev/sda2 -boot d /mnt/a14/winxp.img
but this did not work, and I got the output open /dev/kvm: No such file or directory Could not initialize KVM. Do you have kvm-amd or kvm-intel modprobe'd? If you want to use CPU emulation, start with -no-kvm. appearently it did not recognize the cpu, so I tried again with
qemu-kvm -M pc -m 1G -cpu athlon -hda /dev/sda2 -boot d /mnt/a14/winxp.img open /dev/kvm: No such file or directory Could not initialize KVM. Do you have kvm-amd or kvm-intel modprobe'd? If you want to use CPU emulation, start with -no-kvm.
As it says, it can't find kvm kernel module. If you want to use kvm with paravirtualization support you need appropriate kernel module loaded. You can check if module is loaded by using following command: lsmod | grep kvm If it doesn't output anything, try running as root following commands: modprobe kvm modprobe kvm-amd
I tried to execute the modprobes you suggested. but they failed. The active kernel: uname -a Linux michkloo 2.6.27.23-0.1-default #1 SMP 2009-05-26 17:02:05 -0400 x86_64 x86_64 x86_64 GNU/Linux the corresponding modules: ls -l /lib/modules/2.6.27.19-3.2-default/updates/x86/kvm* -rw-r--r-- 1 root root 50496 Feb 25 19:09 /lib/modules/2.6.27.19-3.2-default/updates/x86/kvm-amd.ko -rw-r--r-- 1 root root 77176 Feb 25 19:09 /lib/modules/2.6.27.19-3.2-default/updates/x86/kvm-intel.ko -rw-r--r-- 1 root root 250176 Feb 25 19:09 /lib/modules/2.6.27.19-3.2-default/updates/x86/kvm.ko Even though the module is named kvm-amd.ko , it shows a different name in lsmod: lsmod|grep kvm kvm_amd 31744 0 kvm 172536 1 kvm_amd in lsmod it is shown with underscore: kvm_amd,
And least parameters possible would be: qemu-kvm -m 1G -hda /dev/sda2 -boot d /mnt/a14/winxp.img But this will run kvm while assuming that /dev/sda2 if your whole disk and windows partitioner will try to partition that disk. If you want to install new clean windows, I would prefer qcow2 image on disk as it is compressed and uses less disk space (and you can move it anywhere you want (burn it on DVD and copy it back only if really need it)).
-- Julien Michielsen julien_at_michkloo.xs4all.nl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 29 June 2009 15:08:40 Julien Michielsen wrote:
Even though the module is named kvm-amd.ko , it shows a different name in lsmod: lsmod|grep kvm kvm_amd 31744 0 kvm 172536 1 kvm_amd
in lsmod it is shown with underscore: kvm_amd,
That's no problem, everything is fine here. But what are the permissions of /dev/kvm? Does it work as root? If yes, add yourself to the kvm group (in /etc/group) and login again. It should work now, Andreas -- Andreas Jaeger, Director openSUSE, aj@{novell.com,opensuse.org} SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Julien Michielsen julien_at_michkloo.xs4all.nl On Tue, 30 Jun 2009, Andreas Jaeger wrote:
On Monday 29 June 2009 15:08:40 Julien Michielsen wrote:
Even though the module is named kvm-amd.ko , it shows a different name in lsmod: lsmod|grep kvm kvm_amd 31744 0 kvm 172536 1 kvm_amd
in lsmod it is shown with underscore: kvm_amd,
That's no problem, everything is fine here.
So I noticed, thank you
But what are the permissions of /dev/kvm? Does it work as root? If yes, add yourself to the kvm group (in /etc/group) and login again. It should work now,
I did as you suggested, and added myself to the kvm-group. I tried again, and launched the command qemu-kvm -M pc -m 1G -cdrom /dev/sr0 -boot d /mnt/a14/winxp.img After giving this command I got a screen displayed which you can see at http://www.xs4all.nl/~michkloo/ssqemu6.html I'll explain the messages below: After giving the qemu-kvm- command I got a screen, looking like a bootscreen, giving messages like QEMU BIOS version 1 ata0 master + description ata1 master cd + description Press F12 for boot menu I didn't press F12, and it continued Booting from CD-ROM therebelow in Dutch "Druk op een toets als u van CD wilt starten", which translates into Push a key if you want to boot from CD I didn't push any key, and it continued on its own initiative, ending with the errormessage "NTLDR is missinh Press Ctrl-Alt-Del to restart Did I execute the same qemu-kvm- command, and did I press F12 after it suggested me to do so. That took me to a screen which you can see at http://www.xs4all.nl/~michkloo/ssqemu7.html This screenimmage says (in Dutch) Kan het bestand \i386\ntkrnlmp.exe niet in het geheugen laden De Foutcode is 7 Setup kan niet doorgaan Druk op een toets om het installatieprogramma af te sluiten Which translates to Cannot load file \i386\ntkrnlmp.exe into memory Errorcode 7 Setup cannot continue Push any key to halt the installation programme This is my result of the attempt to install qemu-kvm. I hope someone has come across the same results I arrived at. If you recognise any mistakes I have made, I'd greatly appreciate your mentioning them to me. Thanks in advance! --- Julien Michielsen julien_at_michkloo.xs4all.nl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 22 June 2009 12:51:16 Michal Hrusecky wrote:
Julien Michielsen - 10:57 22.06.09 wrote:
I tried to get WinXP installed under kvm, and noticed I could not get it installed, because the MS-Win setup-procedure got confused. I had run two commands: qemu-img create -f qcow2 ./winxp.img 10G this command worked fine, to prepare a WinXP- immage on disk (in direc- tory /mnt/a14). Secondly I wanted to install the XP on disk such that qemu-kvm can work on it, and therefor I used the command qemu-kvm -M pc -m 1G -cpu athlon -cdrom /dev/sr0 -boot d /mnt/a14/winxp.img
Having given this command the Windows setup started to run, but ended in failure with the message "Cannot load file SETUPREG.HIV into memory. Errorcode is 3072. Push any key to stop the installation program" Even though setup complained of not being able to find the SETUPREG.HIV-file, this file was present in the subdirectory I386 of the Win-XP-CD. I assume the setup-procedure got confused by the cpu-parameter of the qemu-kvm - command: qemu-kvm -cpu athlon. If the parameter had had i386 as its value, I suppose the setup-procedure of MS-Win would have searched the I386 directory, and everything had worked fine. Is this a known problem of the installation of WinXP under qemu-kvm, and does a work-around exist? If I could use my present allready installed XP-version on a separate partition as an input to the qemu-kvm command (instead of the MS Win CD) the problem might be side-stepped. Is this possible at all? Thanks for your interest.
I didn't run into the same problem, but I'm using several virtual machines with kvm and I never needed to specify -M or -cpu. I thought that specific CPU is supported only by qemu with disabled kvm support and to make use of kvm I never used -M or -cpu with kvm. Anyway athlon can be probably treated as i386 and I guess Windows detects only architecture (if they support any other architecture then i386). I would try to use image of CD-ROM on my disk instead of real cdrom. I guess it using real cd-rom can make things response slower and confuse windows. And you can use your existing installation on hdd in kvm, although I'm not sure if windows are able to handle such a hardware change. But it would be quite dangerous, if you'll access same partition from two different places... It can lead to filesystem inconsistency. You can use
kvm -hda /dev/sda
but as this is really dangerous unless you are sure that you will use it in right way and you've got good bootloader and you know what are you doing, I wouldn't suggest it. I'll recommend you to try to install your windows using cdrom image first.
Thank you for your reply. I tried as you suggested, but did not arrive at a solution. I modified the qemu-kvm and used qemu-kvm -M pc -hda /dev/sda2 -boot d /mnt/a14/winxp.img differing from the qemu-kvm -M pc -m 1G -cpu athlon -cdrom /dev/sr0 -boot d /mnt/a14/winxp.img as I specified used originally. The differences in the two commands: I left out -m 1G and -cpu athlon, and also left out -cdrom /dev/sr0. For the latter I included -hda /dev/sda2, in the hope it would boot from my windows partition. But this did not work: I ended up with the error message you can see at -- Julien Michielsen julien_at_michkloo.xs4all.nl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Andreas Jaeger -
julien -
Julien Michielsen
-
Michal Hrusecky