Search results

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.

As @alexskysilk said, Have you tried, with hdd as ide, booting from xp iso to install over existing ? it's often required for pre Windows Vista

so check before write... edit your topic to add SOLVED

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 prevents boot (was in VMware workstation)...

posting wireguard configs (without keys) will help.

no, it should work like your VMs/LXCs. There is something else elsewhere.

Proxmox uses BTRFS subvolumes for block level type volumes : https://pve.proxmox.com/wiki/BTRFS As said, if homelab/budget constraint , use M2 disc N1 as LVMthin , then backup (like an asynchronous raid) to the M2 disc N2 , with PBS. If N1 fails, replace it, restore from N2. For business, it's...

is PVE has unifi router as gateway ?

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 controller. Each hypervisor has their own hardware...

Only if you have enabled Proxmox side firewall, then you need to add rules to only incoming from another subnet.

Proxmox doesn't support RAID with LVM. Only ZFS and BTRFS are supported by Proxmox for RAID. and ZFS/BTRFS/Ceph and any RAID require datacenter drives if you really care of your data. For Homelab, I should use backup before RAID. With PBS , daily backup on the second disk is really fast , even...

Check if they killed if high memory usage : journalctl -t kernel --since "2 days ago" -g oom

BTW, proxmox-backup-debug recover index output is RAW .img with fully allocated space even zeroes are written to destination drive which is slow when allocated space is lot of more than used space. If PBS is available, proxmox-backup-client map then qemu-img convert -p -f raw /dev/loop0 -O...

They are informational, each time a guest is shutdown/started. Here, I disable "dmesg" displaying on console with crontab : @reboot echo "1" > /proc/sys/kernel/printk

AFAIK, BIOS can't read md RAID. That's why there is Proxmox Boot Tool which sync each ESP boot partitions.

it's the default since PVE 8.x with Debian 12

Choose your own target-name , as target-name will be an "alias" based on MAC address.

ZFS encryption only prevents read data directly from the disks (e.g. un/plug into another system) ZFS encryption doesn't prevent breach.

VM and the PVE/QEMU doesn't know the "Storage backend" (ZFS,Lvmthin,Ceph,QCOW2) neither if encrypted or not. So backup of VM should be encrypted by itself , that's why exist backup encryption in PBS.