Re: [libvirt-users] Migrate Win2k3 to KVM

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/07/2015 20:01, Ruzsinszky Attila wrote: 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 (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.