[libvirt-users] Migrate Win2k3 to KVM
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
- 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@gmail.com> 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@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Hi, Thanks for your prompt answer! I don't know the format of the image. It was made by CloneZilla. Is that then a raw image? Of course I can post the XML of the VM config. I tried out all of the possibilities: IDE, SATA, SCSI and Virtio. The image was taken from a SATA hardware which is a normal Intel chipset. (I can check the real machine again, if it is important). I don't know whether the image booting or not. :-( How can I check it? The boot process is working because I can see the BSOD screen and the no system disk error message. Any ideas would be appreciated! TIA, Ruzsi 2015-07-11 17:40 GMT+02:00 Jeff Tchang <jeff.tchang@gmail.com>:
- 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@gmail.com> 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@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'/> <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
-----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@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. -----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-----
Hi, Do you need the exact error message (the codes)? 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). I don't know if my restore to iSCSI volume was perfect. There wasn't any error messages and the imag is able to boot until BSOD which means missing system disk. Is that right? First time I choosed SATA type for the image without success and I don't know why. Of course I read many M$ KB. I think my problem is the driver. Or anything else? TIA, Ruzsi
BTW: I checked the image with chkdsk from Win Repair Console. There wasn't any error found. TIA, Ruzsi
On Sat, Jul 11, 2015 at 9:28 AM, Ruzsinszky Attila < ruzsinszky.attila@gmail.com> wrote:
Hi,
Do you need the exact error message (the codes)?
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.
First time I choosed SATA type for the image without success and I don't know why.
Of course I read many M$ KB. I think my problem is the driver. Or anything else?
TIA, Ruzsi
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Hi, Do you need the exact error message (the codes)?
The error message "No system disk" means the disk is booting from a KVM perspective so no.
Wait a moment! There isn't any text format error messages! So no explicite "No system disk", either. There are long hexa codes. One of them is 0x0...7b if I remember well and the machine always reboot (of course I can disable automatic reboot).
I don't want Virtio. I want to boot my image first.
You already have it seems like.
Yes, I found a howto about virtio and I tried to use it. In the 1st time I choosed SATA.
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.
Nice. ;-)
There wasn't any error messages and the imag is able to boot until BSOD
which means missing system disk. Is that right?
Correct.
OK.My diagnostic is almost perfect (with Google help). TIA: Ruzsi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/07/2015 18:28, Ruzsinszky Attila wrote:
Do you need the exact error message (the codes)?
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. - -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVoUXeAAoJEHVFVWw9WFsLYcUP/iEuE+B6P1XGZCXT1Bu5gkHA 74/vHvxh+Ko1suvJGq4pxDkeZACB2+yVFaCQAWTLn3kiq70zoZOK0Dl35glwjKDm iQGE/nJYNgxgkOw9YtKyfBwL9yyOQgnRSlsHfrsegTo5E/EEU5m/gzojtLDcN4OC d/lfMOKskvPMZU9x/rPstpdh1mWpgowxanS3ucMB/zUEy3VV1IVN9XGQHYLKLJzr 2QJTkVNZJ3xkmt++MEcCkq1jqSIA6iALFPSLeLxea9NAU6AZ5fnrJ4HEenroNFZw KznhOG+cMh4mIJCKTj7RLd1UGpvYCd3I/0BlfPeezrPk6PCAJXNBN3DeJQ5nULDd TRXiIOqcxuaKxHhROupO6VN4zXKoCrF0LpxM+0XkhJDG5TJLZsvCRZSysQoak1vi lWfqMMi9HuLK2JuQwkv0QzK7WyD00o2n8tzuqZQhJGqk8kk9eBWi4+TkdOa3myho rRtlndgIlw7O96a5NQIaz0Vfr92G6OP10SG/gYjPsDsgKjUjOytV7Oo8Q+DzdrHG WSXFRMx2ntO2MRqTyQOXQRXza4A0gC4Skx7Jj5CcLGkGj8zqIs1wmsS0sdxZBdf4 ziy1rukWqG7lOAP2hdJYgopyhcL6VF5sRlAt8ifIJsTA2EsmK30g6OusVIzsZiUU XN5x4wUY2dMbnyV5tUW1 =YFMq -----END PGP SIGNATURE-----
Hi, The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034, 0x00000000, 0x00000000) Nothing more! (Of course there are some inrelevant text line about chkdsk, etc.)
Basically, what's required is the "STOP:" line + the image where it fails (so, the line below). Image being likely to be NTOSKRNL.EXE
Nothing about NTOSKRNL.EXE on the blue screen!
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?
Yes, I think.
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.
I think this is the problem. How can we solve it? TIA, Ruzs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/07/2015 20:01, Ruzsinszky Attila wrote:
The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034, 0x00000000, 0x00000000)
Perfect, this is what was expected. This should be easy to fix.
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?
Yes, I think.
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 (beware the case, again!) 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. What did you do? You just added the missing hardware ClassGUID for Intel IDE (which is what Qemu uses) to Windows registry. When installing, Windows just sets the strictly minimalistic ones to match your hardware. And then, you defined the associated drivers with these ClassGUID. These are defined as service to allow defining how they boot. When Start is set to 00000000, it means that you want them to be started at boot: when Windows needs to find its boot device. I hope this helped! [1]: key {value(type): data} primary_ide_channel { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): atapi } secondary_ide_channel { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): atapi } pci#ven_8086&dev_7010 { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): intelide } pci#ven_8086&dev_7111 { ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318} Service(REG_SZ): intelide } [2]: atapi { ErrorControl(REG_DWORD): 00000001 Group(REG_SZ): SCSI miniport Start(REG_DWORD): 00000000 Tag(REG_DWORD): 00000019 Type(REG_DWORD): 00000001 DisplayName(REG_SZ): Standard IDE/ESDI Hard Disk Controller ImagePath(REG_SZ): system32\drivers\atapi.sys } intelide { ErrorControl(REG_DWORD): 00000001 Group(REG_SZ): System Bus Extender Start(REG_DWORD): 00000000 Tag(REG_DWORD): 00000004 Type(REG_DWORD): 00000001 ImagePath(REG_SZ): system32\drivers\intelide.sys } - -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVoXrMAAoJEHVFVWw9WFsLnqoQAJlqZtukxBpQvsLF5H5Us0SN MmzH2szJbwz3G+i5jHl2lq+Gg0pP1dD3WBTxuzNZy91XT99hIUlyxW59KVvCk9XK KQmghUUGW3zHqxH/mQoS9NV9t1jZhtHmFOy7RC5dbIoF3WaMPIWxEhTP9SFuSRUs Ec/hcrfYKZ7yr1GSermvV7DdoaHbMc+ris+zCRL6xKydfWODzMhS+VuDiWTqA9Jn s6FFpJnTRWR+nmTOEcBThTy5PhbjIVd/RS762vHKlx9hizkMVBGfoT+KmZQ8oI2+ 5xnYwIkloBR1WFC2/OIlymbWmusTWuXLrYcYiEB0pOweW13Mt6EH13PXG/cZpyGb ByS+ymtkDCHRZWMMnzbsnM2lkIMf7VvIisNDy1Ap0jW8siMLPcvBEcGWtlq607Rm E1YTBA/2nRbD9SxQGp+K42WgnigKMGqAG+mbaG4HEE96unPN3ia0opc/JzCPLhE7 UvMd8LNtb8I6lKYFe9NvaSdVKDi38rnfpH3xO03dIKqL0ZA0iuO90G9buAN7hnBC g6XsWQ0EEqoTLZeoNBFV7tk7jHirEGkEkZiZRsB8/LcB9sQZ4b+6gWiguxkeTkcm EtUDpWFmLYDDFz+IuxV/T+Brgu2SFAYs6vu6knrhO+mjdgHyBmfoua+3G3d6736X ySk7BjS1lfpB9OVqX2hM =0+5z -----END PGP SIGNATURE-----
Hi Pierre, On 11/07/2015 20:01, Ruzsinszky Attila wrote:
The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034, 0x00000000, 0x00000000)
Perfect, this is what was expected. This should be easy to fix.
Good news! ;-)
Great, then, it opens possibilities. Let's try the following: - - Install chntpw
Is that a Linux program? I use Ubuntu 14.04 64 bit.
- - Mount your disk on Linux
Clear.
- - Move to Windows/System32/config (beware the case!)
OK.
- - Now, start registry editor: chntpw -e sam system security software
"system security software" is parameters?
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 ;-)).
I think I'll find SATA something, because the original image was taken from a SATA system.
- - Add the missing ones. For example: 'nk pci#ven_8086&dev_7111'
What does it mean "'nk"?
followed by: 'cd pci#ven_8086&dev_7111' followed by 'nv 1 Service' (1
... and "'nv"?
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)
Maybe I'll have question with registry. Tomorrow morning I'll try your steps. Can I a backup file from the registy before I start the procedure? And how?
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.
Now I copied the virtio drivers to the ./Drivers directory. I understand the 1st goal is booting from IDE. What about SATA? Thanks for your howto! I think I'll ask you about registry. Question not just for you: Why did I get error message "permission denied" for vir-win-reg command? TIA, Ruzsi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/07/2015 11:09, Ruzsinszky Attila wrote:
Great, then, it opens possibilities. Let's try the following: - - Install chntpw
Is that a Linux program? I use Ubuntu 14.04 64 bit.
Yes. And Ubuntu provides a package for this program.
- - Now, start registry editor: chntpw -e sam system security software
"system security software" is parameters?
All are parameters. '-e' means you want to start the program as registry editor. Then, the rest if just the list of the hives you want to open. SAM is mandatory, chntpw is always looking for it. Security & software might actually not be mandatory for what we do.
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 ;-)).
I think I'll find SATA something, because the original image was taken from a SATA system.
You'll likely find pci#vend_XXXX&dev_XXXX keys matching your SATA buses.
- - Add the missing ones. For example: 'nk pci#ven_8086&dev_7111'
What does it mean "'nk"?
It's the command for creating a 'new key'
followed by: 'cd pci#ven_8086&dev_7111' followed by 'nv 1 Service' (1
... and "'nv"?
It's the command for creating a 'new value' in a key.
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)
Maybe I'll have question with registry. Tomorrow morning I'll try your steps. Can I a backup file from the registy before I start the procedure? And how?
Backup the config directory files. They are the hives containing your Windows registry.
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.
Now I copied the virtio drivers to the ./Drivers directory. I understand the 1st goal is booting from IDE. What about SATA?
I unfortunately don't happen to have a VM using SATA buses, so I've no idea what HW IDs is Qemu using for its buses. It could be interesting to have a look though. - -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVojWlAAoJEHVFVWw9WFsLAh8P/1s7UBbw8Laip+59rzTxFjp5 4YMe1SgIG9QM05iBhGeoP0BqmbaU+4/aZtOouBC1HqtuuBE/NGKS8UymTapTxJhn vOQmLX6i+LTAUP51kc5+v4bWE7tu6fv1wpdRyHOktEbb6stwNAQCAg718UluhLRJ wbLavy7Y1KyabJ3zn6ntco83f8GsEIGy6VefYdjE9xmDrwL06lD82ayrtz0Xn7rS nD3XwmfUyumYHiyIPIxXYCZvH4ysu5D4ThHQpX4PYpwtslb8p9zC0TeMHmWKCzyX g88DZDncwX1bv/iZfRBBFKmWWdfZbqM86bf0NF9x0djEoP++RhoopExH+qHkzMAn vgslxMBtcRT8hxstE78cfAvSdXkCliZ0Qq1ZFMSeyJRyO+Yro7Ws5cNuS6/GPx6L FnQuridzmNpWZ355aFCJ5oM9Cu9UQ1ifW2e2AjyS33duSLcv4iGvh3e0AFNdV+fd igmUNf83Q4dSKQfTmTGdjqMD/jvFGgQbd6o2NSZYaH5MloEzUfcrK83IiJ9adYPb riN/H/VcyqOJNOhcy21/0+8zq5yUyBrb+ITLNericrI8qnkiys5cfW4mzYfkPWq5 AZnnNcdk8j87JEnZRikeHhtMCLBvQsxvTxtkUe93bVuslharSdQEPumXiB9oPdQ7 d/pbtNKMi/D4s4xs/41n =kQWD -----END PGP SIGNATURE-----
I agree with Pierre. Basically the image you have from CloneZilla has lots of settings inside it that tell the image itself where the boot drive is. The way I've done it in the past is to mount the image using whatever filesystem it uses (NTFS in this case). Make sure it is writable. And then start mucking around with the boot settings of the Windows image. I don't know if Windows 2013 still uses boot.ini but that is one source. You need to try and change the default system disk on the image. One other way you can do it is possibly by booting the Windows 2013 rescue disk and using command line utilities. This may or may not work. If it does let me know. Something like this: http://stackoverflow.com/questions/20239172/how-do-i-find-a-missing-hard-dri... On Sat, Jul 11, 2015 at 9:18 AM, Pierre Schweitzer <pierre@reactos.org> wrote:
-----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@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. -----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-----
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
participants (3)
-
Jeff Tchang -
Pierre Schweitzer -
Ruzsinszky Attila