- What format is the image is? - Can you post an XML file of the VM config? Changing the driver to VirtIO via registry edits may exacerbate the problem. I've never done this but wouldn't it make sense to stick to the more supported IDE drive emulation until you get it booted and thus remove possible variables of it not booting? Are you able to boot the image any other way? On Sat, Jul 11, 2015 at 8:28 AM, Ruzsinszky Attila < ruzsinszky.attila(a)gmail.com&gt; wrote: > Hi, > > I made a disk image with CloneZilla from the original physical machine. > > That image was restored on an iSCSI volume. > It isn't booting. I got BSOD. > I tried IDE, SATA, SCSI disk type without any success. > I tried to using virtio driver and if I use my image+W2k3 install > CD+virtio VFD the Windows repair console see the disk and I can use the > repair console with my image but the windows not start > (or not booting because the system disk can't be seen by original > "registry"). > > The drivers from virtio VFD image were copied to Windows' Driver > directory manually. > > I tried to use virt-win-reg: > rattila@amd1:~$ virt-win-reg SJ-SIMISPC > /dev/disk/by-path/<iSCSI-path>:simispc-lun-2: Engedély megtagadva at > /usr/bin/virt-win-reg line 260. > (it means: Permission denied.) > > What can I do changing the original driver to virtio (or IDE/SATA/SCSI in > KVM)? > > I can't do anything with the physical machine so the only option is > playing with the disk image. > > TIA, > Ruzsi > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users >

Hi, Here is the XML file of the my VM: <!-- WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE OVERWRITTEN AND LOST. Changes to this xml configuration should be made using: virsh edit SJ-SIMISPC or other application using the libvirt API. --> <domain type='kvm'> <name>SJ-SIMISPC</name> <uuid>b503aeb4-23e6-8c99-cce2-67c36558b950</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='i686' machine='pc-i440fx-trusty'>hvm</type> <boot dev='hd'/> <bootmenu enable='yes'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/kvm-spice</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/kvm-img/isok/Windows_2003_Server.iso'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-path/ip-192.168.52.142:3260-iscsi-iqn.2015-06.hu.mavrt.bbf.fc.amd2:simispc-lun-2'/>

<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> <disk type='file' device='floppy'> <driver name='qemu' type='raw'/> <source file='/kvm-img/isok/virtio-win-drivers-20120712-1.vfd'/> <target dev='fda' bus='fdc'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='fdc' index='0'/> <filesystem type='mount' accessmode='passthrough'> <source dir='/kvm-other'/> <target dir='/source'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </filesystem> <interface type='network'> <mac address='52:54:00:bb:cc:a7'/> <source network='belso0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <sound model='ich6'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> TIA, Ruzsi _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVoUHNAAoJEHVFVWw9WFsLNQ4P/jpl2XGESzOHkO7l0ZIBlRFk zFbpRgZJH345HWQyxt++sWo7gcdEUP7zRkUyKRlfr2INVAWam0Sblph5Z+DWQ8h4 T7EkOolH/h135R2W1cOtIi47XokSQOMP4atmSt+1/EQ+bEdAntEtnqzipb8Hz/c0 1bzsuHJIDpz1e+lBfhbdo2TS9D0ADRNpdxTKTaw1+pflc6Pd0nGvzG7nkBAz8X8X d+sDC1T0b4tItg6JkwN0Hn67QC+FFzrVm9bXIgyOiH/HWX+jjPItub1NT46YF6M1 gVms+ZgL2IACq2487mhgaGYo6C24e1yHtCG5bD3RNoXDZ6SJTH8jYtvNGItNnl2n QegNp+Dit/SWJ2x+CoJkkm+5Ay2PKAJYQlV/U1Vme+U+LS/YcF5FGXpPGZjX8XzE IyuLA+j6cuiCT5aIQCb2eAZ8VK1wxSLmW6QzA7PAAVuWEb5H16e5t1CjJ1jeVtr7 TAbPvrwjfNyc31xjJNQYgoknR3PS+4u/P5BHClxI3Bt9qEHq2iwa9bqIIRXlORvy 1eg7+dgPn3yEuCQ6TzoPqq85b3Hp8chQOCkpYdDf+J4y9MpBj2VO/741eV3Y0Bkd FxiY16ZGtp54L+gU0uL/wqgg3GjKbbrVXRpH1tdwxylXZHDMEocup1/AuqIw908y zrdO9mfckV3k5xfcBrbh =oW4B -----END PGP SIGNATURE-----

> > The error message "No system disk" means the disk is booting from a KVM perspective so no.

> I don't want Virtio. I want to boot my image first. > You already have it seems like.

As I mentioned I can't use the mergeide.req on the physical machine but I > can do anything with the image (if I don't het error messages from the > virt-win-reg). > I don't know if my restore to iSCSI volume was perfect. > It looks liek your restore to the ISCSI volume went well.

There wasn't any error messages and the imag is able to boot until BSOD > which means missing system disk. Is that right? > Correct.

Basically, what's required is the "STOP:" line + the image where it fails (so, the line below). Image being likely to be NTOSKRNL.EXE

> I don't want Virtio. I want to boot my image first. As I mentioned > I can't use the mergeide.req on the physical machine but I can do > anything with the image (if I don't het error messages from the > virt-win-reg). Well, then, you can mount the image in a Linux machine and use the chntpw tool to edit manually the registry and add the missing driver information?

Basically, most you're missing here is linking some hardware classes to proper device (likely intelide.sys) so that your Windows can properly setup its storage stack.

> The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034, > 0x00000000, 0x00000000) Perfect, this is what was expected. This should be easy to fix.

Great, then, it opens possibilities. Let's try the following: - - Install chntpw

- - Mount your disk on Linux

- - Move to Windows/System32/config (beware the case!)

- - Now, start registry editor: chntpw -e sam system security software

The following commands are to type in chntpw prompt: - - hive 1 (to move to system) - - cd ControlSet001 - - cd Control - - cd CriticalDeviceDatabase - - Check you have the following keys: primary_ide_channel, secondary_ide_channel, pci#ven_8086&dev_7010, pci#ven_8086&dev_7111 keys. Some will be missing (otherwise, you'd boot ;-)).

- - Add the missing ones. For example: 'nk pci#ven_8086&dev_7111'

followed by: 'cd pci#ven_8086&dev_7111' followed by 'nv 1 Service' (1

for REG_SZ) followed by 'ed Service' and type intelide. Proceed like that will all the missing keys & values[1], 'cd ..' when you're done with all the values of a key, to proceed for the others - - cd .. (you're now in Control) - - cd .. (you're now in ControlSet001) - - cd Services - - Check you have the following keys: atapi and intelide - - Add the missing ones[2]. REG_DWORD type is 4 when doing nv. (like nv 4 ErrorControl) - - You're done, so: q to quit chntpw (of course, reply 'y' to write hives)

Back to your linux term: - - cd ../drivers/ - - Check you have atapi.sys and intelide.sys. In case you don't, extract them from the cab file you can find in Windows\Driver Cache\i386 - - Umount - - Try to boot again, and report.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Having the BSOD value (first ID) should provide intel about what's getting wrong in your setup. It's likely that your storage stack is incomplete in your setup due to hardware change for HDD, and thus, Windows cannot find its boot device any longer. Reading this KB might help: https://support.microsoft.com/en-us/kb/314082 Once you get proper booting with IDE, you can consider installing virtio drivers and switching to virtio. With my best regards, On 11/07/2015 17:56, Ruzsinszky Attila wrote: > Hi, > > Here is the XML file of the my VM: > > <!-- WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE > LIKELY TO BE OVERWRITTEN AND LOST. Changes to this xml > configuration should be made using: virsh edit SJ-SIMISPC or other > application using the libvirt API. --> > > <domain type='kvm'> <name>SJ-SIMISPC</name> > <uuid>b503aeb4-23e6-8c99-cce2-67c36558b950</uuid> <memory > unit='KiB'>1048576</memory> <currentMemory > unit='KiB'>1048576</currentMemory> <vcpu > placement='static'>1</vcpu> <os> <type arch='i686' > machine='pc-i440fx-trusty'>hvm</type> <boot dev='hd'/> <bootmenu > enable='yes'/> </os> <features> <acpi/> <apic/> <pae/> </features> > <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> > <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> > <devices> <emulator>/usr/bin/kvm-spice</emulator> <disk type='file' > device='cdrom'> <driver name='qemu' type='raw'/> <source > file='/kvm-img/isok/Windows_2003_Server.iso'/> <target dev='hdc' > bus='ide'/> <readonly/> <address type='drive' controller='0' > bus='1' target='0' unit='0'/> </disk> <disk type='block' > device='disk'> <driver name='qemu' type='raw'/> <source > dev='/dev/disk/by-path/ip-192.168.52.142:3260-iscsi-iqn.2015-06.hu.mavrt.bbf.fc.amd2:simispc-lun-2'/> > > <target dev='vda' bus='virtio'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x07' > function='0x0'/> </disk> <disk type='file' device='floppy'> <driver > name='qemu' type='raw'/> <source > file='/kvm-img/isok/virtio-win-drivers-20120712-1.vfd'/> <target > dev='fda' bus='fdc'/> <address type='drive' controller='0' bus='0' > target='0' unit='0'/> </disk> <controller type='usb' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' > function='0x2'/> </controller> <controller type='pci' index='0' > model='pci-root'/> <controller type='ide' index='0'> <address > type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> > </controller> <controller type='fdc' index='0'/> <filesystem > type='mount' accessmode='passthrough'> <source dir='/kvm-other'/> > <target dir='/source'/> <address type='pci' domain='0x0000' > bus='0x00' slot='0x05' function='0x0'/> </filesystem> <interface > type='network'> <mac address='52:54:00:bb:cc:a7'/> <source > network='belso0'/> <model type='virtio'/> <address type='pci' > domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > </interface> <serial type='pty'> <target port='0'/> </serial> > <console type='pty'> <target type='serial' port='0'/> </console> > <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> > <graphics type='vnc' port='-1' autoport='yes'/> <sound > model='ich6'> <address type='pci' domain='0x0000' bus='0x00' > slot='0x04' function='0x0'/> </sound> <video> <model type='cirrus' > vram='9216' heads='1'/> <address type='pci' domain='0x0000' > bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon > model='virtio'> <address type='pci' domain='0x0000' bus='0x00' > slot='0x06' function='0x0'/> </memballoon> </devices> </domain> > > TIA, Ruzsi > > > > _______________________________________________ libvirt-users > mailing list libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users > - -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users