Yes the emulation type is the same.<br>I came back to my other PC where I created the VM (it has F12+rawvirt qemu-kvm) and I verified I have exactly the same problem.<br>So it is not a problem related to different versions of qemu, but it seems something related to <br>
windows XP + qcow2 disk combination perhaps<br>My definition is for both of this kind (in qemu for rh el 5.4 I created the domain based on this xml, only changing the path before running "virsh create winxp.xml and the other things I wrote in first post):<br>
<br> <disk type='file' device='disk'><br> <driver name='qemu' type='qcow2'/><br> <source file='/data/virtstorage/winxp_maggi.img'/><br> <target dev='hda' bus='ide'/><br>
<address type='drive' controller='0' bus='0' unit='0'/><br> </disk><br> <disk type='file' device='cdrom'><br> <driver name='qemu'/><br>
<source file='/winxp/temp/iso maggi/WinLite.iso'/><br> <target dev='hdc' bus='ide'/><br> <readonly/><br> <address type='drive' controller='0' bus='1' unit='0'/><br>
</disk><br> <controller type='ide' index='0'/><br><br>I tried erasing of CD in F12 too, and the problem persist.<br>I have to create CD and connect it to iso to have then win xp boot.<br>
<br>BTW, I tried to re-create a winxp vm in F12+rawvirt with virt-manager.<br>One note: in step 2 I select "Windows" as OS type and "Microsoft Windows XP (x86)" as flavour.<br>In step 5 if I expand "advanced options" I can see that it automatically put <br>
virt type: kvm ---> OK<br>architecture: x86_64 ----> KO in my opinion<br><br>I would expect this only if I had selected "Microsoft Windows XP (x86_64)" option before in step 2...<br>I changed this field to i686 before install (also in my previous vm that manifests this boot problem) thinking it was a bug... (and in case I report this here).<br>
Any way that there is a reason instead, perhaps, to put it to x86_64 anyway???<br><br>Based on this I get in this new xml:<br> <type arch='i686' machine='fedora-13'>hvm</type><br><br>While by default I would get:<br>
<os><br> <type arch='x86_64' machine='fedora-13'>hvm</type><br> <boot dev='cdrom'/><br> </os><br>(just for curiosity, I made a "virsh edit winxp.xml" changing to x86_64, but the problem remains: donna if having x86_64 at installation time impacts in any way in terms of boot loader, or cpu type installed in windows though...)<br>
<br>Is this correct? What exactly does it mean "fedora-13" (that in rh el is instead "pc")?<br>Is it something comparable to virtual hw version of VMware guests, that should say what kind of hw features that vm can have?<br>
<br>Coming back to my VM, I slipstreamed a WIndows XP sp2 cd with nlite, taking it to sp3 and installed from that iso...<br>I will try to install on no-qcow2 based hd... could it be that causing problems with nt boot loader perhaps?<br>
Anyone installed successfully winxp sp3 on qcow2 disks?<br>Thanks for your attention,<br>Gianluca<br><br>