Thanks guys - after further testing I can report that:
- I need a new install from winXP medium to a new proxmox disk in order to get rid of the operating system not found.
- From there either a copy of the old install either via linux...
As foreseen by _gabriel the famous bluescreen could be fixed by a winxp-sp3 repair install over it after applying the wim file. Now the only thing to find out remaining is howto avoid the setup to need re-activation.
And yes, I tried to use...
I didnt as I beleived you that rsync is not the way to go thus now following the wim way you proposed.
For reference - as it might help somebody in the future here is what I have done so far:
added the winxp source disk and the winxp...
Making progress. At least it started booting and then bluescreened, so my next try is to attach both disks - the source and the empty but created by proxmox one to a running win10 guest and use wim as soon as I learned howto do it :)
I see, then my google wasnt correct so thanks for pointing it out. Then this will be my last resort to try. Thanks again for your feedback much appreciated.
wrong, "wim" capture isn't imaging / sector-based , it's file-based, like rsync.
"wim" can be restorerd over existing data, without deleting others folders already present.
You can't copy Windows system with rsync. That's why "wim" exist. it's...
Hello Gabriel, but this is a imaging thing, which I already did with clonezilla with the same result even fixing the mbr afterwards by winxp cd didnt help, so my assumption is that the disk created by vmware is problematic while a disk created...
There isn't universal procedure.
Stop at "Booting from Harddisk" looks like missing active/boot flag partition or boot sector or broken table partition.
I can try myself if you PM me.
what a stubborn donkey this setup is. Well I tried now with a newly created disk within proxmox instead of importing or configuring the disk I got from esx - either by converting it from vmdx, or by import wizard or by restoring it from...
Re-install besides the original setup changed the boot message:
It now reads:
Booting from Harddisk... then nothing more following.
Here is the current vm config:
bios: seabios
boot: order=ide0;ide2
cores: 2
cpu: x86-64-v2-AES
ide0...
I did firstly tried with fixmbr - you mean install over it, will do this right now as next step. Thanks
Reinstall as repair option didn't help, as it resulted in the same error; next step. Complete new install on the disk/pve guest. I will first...
Will try to install from scratch on the pve guest to see if it boots, but how could I get the setup from the esx server disk - is there a way with dd somehow?
Hi MarkusKo,
as mentioned in the opening post, I also tried with two different versions of mergeide.reg even with the one exact version you added a link for without success. I also read through advanced migration techniques and pretty much tried...
Thanks again - tried with options you have provided, which were missing, and besides the line args: -acpitable which didnt let me start the vm and proxmox said:
kvm: -acpitable: requires an argument
TASK ERROR: start failed: QEMU exited with...
done - although as written above from win7 onwards I had not problems at all to port windows vms to proxmox. Those last two winxp I have to make available still giving me some headache but I ll try and report back.
Title should be edited, as problem is about Windows "conversion",
which is a problem since Windows exists, even before virtualization.
Windows "conversion" is always a "YMMV", because it doesn't like swapping motherboard/cpu and mainly disk...