Search results

did it - i think - will do some testing and then come back with final report

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 livesystem and rsync -a or a copy via wim file from...

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 display -> vmware. @donhwyo - made no difference. To...

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 destination disk to a win10 guest. Added an additional disk...

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.

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 within proxmox let me install winxp from scratch...

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 clonezilla. But a new created disk in proxmox and new...

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 didnt help, as it resultet in the same error; next step. Complete new install on the disk/pve guest. I will first try if it works to leave the install and resize...

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?

Tried with WinXP iso - booted and issued fixmbr, but still getting message: error at loading operating system.

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 mucht tried everything, for ex. imaging with rescuezilla...

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 code 1 I tried with the ones, I didnt have, like...

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.

Thanks for providing those informations. Will try to adapt and report back

Thanks will organize a winxp iso and try although a colleague of mine already tested booting in a winxp iso and fixmbr or install over but apparently didnt help. Will report back when I find time to try myself. Thanks

Hi bbgeek17 and thanks for you taking the time to reply. You are right, I didnt mention it as my procedure for migrating all those other vms was to first boot with sata or ide attached disk and only then on the proxmox host started vm add a dummy network device and scsi disk to then install the...

We are in the process of replacing our esxi Servers with ProxMox, and I have converted dozens of linux and Windows VMs. When it comes to Windows everything works fine from win7 onwards, but we have two winXP guests, that need to be around for archive just in case. The error is always the same...

You mean qm set 100 --args "-cpu cortex-a72" Thus creating an entry like args: -cpu cortex-a72 in 100.conf. That way the vm boots, I'll check the cpu type and add prefix solved to the title. This would mean the only package needed to install for arm is pve-edk2-firmware-aarch64