Search results

you can disable it / hide it, from Datacenter \ Storage.

post your host "interfaces" and guest ".conf" in [CODE] tags please.

as your Guest use all vCpu, iperf3 thread can't keep running in the same ccd/numa. NPS=4 is for running many guests with 8 vCpu max. Each VM should run within its own ccd/numa, pinning cores can be required.

@tyger81 sorry seems I didn't refresh page before posting , my previous post was for @lilyrose I've edited.

Without details about your config , like VM .conf , nobody can help you. As listed above, first tips is to use the default vCPU "x86-64-v2-aes" instead "host".

Within guest only but PVE take care of SMART directly.

I bet they don't use ZFS. ZFS isn't just a RAID like mdadm or hw raid.

Yes, it can be an HDD , not as passthrough , as virtual disk within a regular Lvmthin datastore. This is a "within guest" backup. it's a problem if you define "Minimum memory" too low , as Windows can up to kill/crash apps because Ballooning service installed with Guest Agent inflates its RAM...

You can move within guest backup to a dedicated drive. But your storage seems can't handle substained writes. Don't forget ZFS require datacenter drives. RAID10 / Striped Mirrors is recommended for VM / DB.

Have you checked Windows's Volume scheduled Shadow Copies ?

Precisely, you need to set NUMA NPS to 4

Seems hit the bug , with a Windows XP Guest, which x86 , qemu32 , 1vcpu , 3 GB RAM , SeaBIOS i440fx-5.2 No /PAE Windows boot option, but a SQL Server , perhaps does something , IDK. Apps and Windows EXE crash with pop-ups errors, like explorer.exe , Start Menu "Theme" is lost then revert back to...

1/ Yes 2/ You can create a new Namespace on your PBS then add it to your New PVE. ( Datastore stay the same with data dedup over all Namespaces )

Do you select subfolder amd64 ? or vioscsi\w10\amd64 ?

special efidisk is missing, try adding it , it used to store efi/bios settings.

What do you mean ? if SSD is dying, then like bare metal, replace it, restore backup or reinstall. PVE is out the scope.

PBS has its own issues depending configuration of course, like PBS over WAN or slow link can timeout source VM, PBS fleecing can help nowadays. But to dig out, I should start disabling PBS temporarily and keep vzdump.

Are you using Proxmox Backup Server ?

Linked fix is to inplace upgrade from setup.exe from Windows 11 24H2 iso directly , never tried directly from Windows Update, I assume there is a check from Windows Update itself.

What makes you think that? URL for Debian 12 ( = bookworm) = Proxmox 8 is same since late 2023. EDIT: indeed, nowadays it's HTTPS only