Search results

Which Version of virtIO-Drivers are you using? There is a known issue which has been fixed recently with the .266-Version....

Sorry... not for the installer problem but for the real problem this thread is all about: https://forum.proxmox.com/threads/redhat-virtio-developers-would-like-to-coordinate-with-proxmox-devs-re-vioscsi-reset-to-device-system-unresponsive.139160/post-691337

Virtio 266 was released... maybe there is the fix in? https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.266-1/

You can always write a feature request for Proxmox. https://bugzilla.proxmox.com/

Currently not, but you can use Live-Restore which starts the VM the moment restore begins... it will be slower but available....

Have a look here: https://forum.proxmox.com/threads/proxmox-dell-powerstore.145414/ Basically, create new Volumes on your Powerstorage, map them to your PVE-Nodes, which need a local boot-drive and format the LUNs LVM thick. (Thin has issues with powerstorage and does not support snapshots) and...

Also auch mit aktuellem Ceph Reef steigt die Performance bei regulären SSDs (SATA mit PLP) bei 2 bis 4 OSDs pro SSD durchaus noch um teils 40% an (IOPS)... bei NVMEs nicht so stark, aber es kann durchaus mit aktuellen Ceph und Bluestore noch Sinn machen. Wenn man sich der "komplexität" natürlich...

Use your SAN like before and connect your Proxmox-Nodes to ist... it's just another LVM then, which can be shared.... To check for compatibility, what SAN are you currently using?

An der Meldung gibt es nix zu rütteln.... to extract file: failed to copy file contents: No space left on device (os error 28) Wenn dein Restore-Ziel nicht wieder ein ZFS mit aktivierter Kompression ist, hast du verloren....

Es empfiehlt sich das ganze Thema Aufbewarung, Prune, GC immer am PBS zu machen und nicht in den Backup-Jobs am PVE.... Das sollte mindestens so oft laufen, wie neue Backups hinzukommen und alte gelöscht werden... meist also täglich....

Das findest du im PBS unter den Datastores...

Aber nen GC Job hast du schon laufen?

Server still runs, but we are on only one server where Hardening is done.... long term prototype....

For upgrading to Windows Server 2022, make sure guest network is connected while performing guest OS in-place upgrade, or take the following steps which also apply to upgrading to Windows 11: So change your NIC before upgrade to something that is always there. like Intel E2000 and try again...

Just to be sure... the pure upgrade would not enable any "Crimson" feature for now? It's just the latest version and for anything else manual configuration will be necessary?

Quick Update... we made the change in the file on about 10 3 Node Clusters now, all at all about 400 Windows VMs and some Linux VMs and Containers on these Hosts.... all looking stable and the Windows Guests benefit from the change, also the LinuxVMs and LXC did not show any draw-backs.... so I...

You need to reset the license in Proxmox Licensing Portal. Just logon there and "free" the license.... then you can reuse it on a new server....

Crimson's first tech preview release! Supporting RBD workloads on Replicated pools. For more information please visit: https://ceph.io/en/news/crimson

Try to delete and recreate your EFI-Partition... this might help in case there is an issue with the "secure-boot" config in Windows....

I think the problem is already known. Inplace Upgrades sometimes fail at second reboot.... I guess you have to wait until Microsoft provides a fix., In a german blog someone reported about this issue. https://www.borncity.com/blog/2024/10/17/probleme-mit-windows-11-24h2-windows-server-2025/