Hi @Taleya,
If you have set it to x86-64-v2-AES in PVE then QEMU Virtual CPU version 2.5+ will be shown in Windows
If you want the VM to see the CPU Type of our host set the CPU in PVE to host
CPU in PVE: x86-64-v2-AES
In Windows:
CPU in PVE...
Can't be done as hardware is changed.
Others oftwares tied to hardware require re-activation too.
seems problem with table partition (perhaps partition alignment).
Sounds a bit like you have never created a VM on Proxmox before? You can chose the MAC address of all virtual network interfaces yourself (in the VM Creation wizard and also in the VM Settings afterwards) and Proxmox does not randomly change the...
Testing Random 4k Queue 1 and Thread 1 is the worst case.
What are results from Windows bare metal ?
here on bare metal with 1 x Micron 7450 Pro 1,92 TB and 1 x Samsung PM983 3,84 TB (similar numbers)
running on M2 PCie x4 ports from prosumer...
It's quite possible that your are cpu limited, as currently vm can only use 1 core for 1 virtual disk.
Multiple threading (with multiple iothread by disk), should be available soon, I have already send patch to the proxmox dev mailing list.
read bluescreen stop code , if the famous 7B then it's disk controller problem, exist since NT4.
Repair XP with the install over it from booting from iso shoud work. with disk attached as ide.
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...
yes, "wim" capture/restore from another Windows 7 or 10 more easy,
then need correct bootsect /nt52 afterward.
As already said, that's Windows things, which existed before virtualization, not really a Proxmox issue.
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.
Why is everyone using passive voice when recounting that "consumer drives are discouraged?" by whom? and under what circumstances? There is nothing INHERENTLY wrong with using non enterprise drives for zfs pools, as long as you understand the...
I remember a case while virtualizing a physical NT4 from HP Vectra.
Thanks to pre Windows Vista , install/repair booting from CD over an existing Windows was possible and saved days many times.
HAL.dll was from HP locked to their hardware, which...