Latest activity
-
Ttrev458 reacted to fabian's post in the thread GRUB "no server is specified" / can't boot after extending pve/root LV onto second disk — bug ruled out with
Like.
you could also do what proxmox-boot-tool does and put the grub stage2, kernel and initrd on the ESP - grub only needs to read from the ESP then, and the kernel takes over before LVM is involved at all. -
Eet-ducky replied to the thread Windows Server 2025 + FSLogix Fileserver: sporadic vioscsi Event ID 129 ("Reset to device \Device\RaidPortX") causing inaccessible volume.Any defrag event 258's from the storage optimizer near the 129 event? Drafted with AI, reviewed by me.
-
MMagg replied to the thread S3 Hetzner failures with Gargbage collection.I hope it's ok if I join this thread. I am seeing the same issue. I tried w/o limits and it crashed, and then with 100 req/s and it crashed after less than 10 min. Currently running at 10 req/s and it's been running for 22 minutes. I can see from...
-
Bbzr replied to the thread Windows Server 2025 + FSLogix Fileserver: sporadic vioscsi Event ID 129 ("Reset to device \Device\RaidPortX") causing inaccessible volume.no they dont line up. Last time the backup finished at 21:45 and first 129 event was thrown at 23:26. i hope that i can kick the can quite some time and the error never occurs again... that would be my relief
-
Eet-ducky replied to the thread Windows Server 2025 + FSLogix Fileserver: sporadic vioscsi Event ID 129 ("Reset to device \Device\RaidPortX") causing inaccessible volume.Do the Event 129 timestamps line up with a scheduled vzdump backup or snapshot of those two VMs? Sometimes I feel a little load off when I say "all I can do is wait" because I have so much stuff to do that kicking the can down the road is a...
-
Bbzr replied to the thread Windows Server 2025 + FSLogix Fileserver: sporadic vioscsi Event ID 129 ("Reset to device \Device\RaidPortX") causing inaccessible volume.i cant see any ceph related performance issues. i have multiple VMs running on the same Ceph Cluster. Even the SQL Server runs flawlessly on virtio 0.1.285, but it is still on Windows 2016... i set Cache to none on both machines and updated one...
-
Bbzr reacted to PaulKo's post in the thread Windows Server 2025 + FSLogix Fileserver: sporadic vioscsi Event ID 129 ("Reset to device \Device\RaidPortX") causing inaccessible volume with Like.
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.302-1/
-
CchOzcA75vE0poCY0F6XC reacted to emz's post in the thread Mellanox ConnectX-4 LX and brigde-vlan-aware on Proxmox 8.0.1 with Like.
Adding another data point plus a workaround that doesn't need promisc or switchdev. Setup: MCX4121A-ACAT (ConnectX-4 Lx), FW 14.32.1912, PVE 9 with kernels 7.0.14-17-pve, 7.0.2-6-pve and 6.x (all identical), legacy eswitch, SR-IOV tested both on...
-
Ddrwtsn32 reacted to emz's post in the thread Mellanox ConnectX-4 LX and brigde-vlan-aware on Proxmox 8.0.1 with Like.
Adding another data point plus a workaround that doesn't need promisc or switchdev. Setup: MCX4121A-ACAT (ConnectX-4 Lx), FW 14.32.1912, PVE 9 with kernels 7.0.14-17-pve, 7.0.2-6-pve and 6.x (all identical), legacy eswitch, SR-IOV tested both on...
-
Eemz replied to the thread Mellanox ConnectX-4 LX and brigde-vlan-aware on Proxmox 8.0.1.Adding another data point plus a workaround that doesn't need promisc or switchdev. Setup: MCX4121A-ACAT (ConnectX-4 Lx), FW 14.32.1912, PVE 9 with kernels 7.0.14-17-pve, 7.0.2-6-pve and 6.x (all identical), legacy eswitch, SR-IOV tested both on...
-
JJohannes S reacted to Bu66as's post in the thread I want to understand the Hotplug for CPU with Like.
Yeah, you're reading it right. Sockets and cores are the maximum topology, QEMU needs that fixed at VM start, so those two fields are greyed out while the VM runs. The only value you can change live is vcpus, that's how many of the max cores are...
-
Jaside from using the tape drive/changers via iscsi there is no other possibility at the moment. we only do datastore-> tape backup, not direct to tape, nor can we 'mount' a foreign pbs datatstore (e.g. for locking reasons) using it via iscsi...
-
JJohannes S reacted to UdoB's post in the thread Wünschenswert: Anzeige der NIC-Geschwindigkeit with Like.
Nein. Ein automatisches downgrade geschieht nicht. (Ein downgrade klappt nur manuell per CLI.) "apt full-upgrade" macht (ohne manuelle Intervention) immer nur upgrades von älteren auf neuere Pakete. In der Realität kommen die Pakete aus non-sub...
-
Dhttps://bugzilla.proxmox.com/show_bug.cgi?id=7244
-
DBug is open
-
Dyou can't, at the moment - the code in question there assumes 4k pages at the moment, and this is also encoded in the on-disk format, so can't just be bumped without breaking compatibility. we'd need to implement a fallback path there that works...
-
bbgeek17 replied to the thread losing dirty-bitmaps during Live Migration.Hi @aday , welcome to the forum. The journal line Cannot find device='z…' nor node-name='z…' on the target comes from the incoming dirty-bitmap migration: it couldn't find the block node the bitmap was attached to, so QEMU dropped the bitmap and... -
UdoB replied to the thread Wünschenswert: Anzeige der NIC-Geschwindigkeit.Nein. Ein automatisches downgrade geschieht nicht. (Ein downgrade klappt nur manuell per CLI.) "apt full-upgrade" macht (ohne manuelle Intervention) immer nur upgrades von älteren auf neuere Pakete. In der Realität kommen die Pakete aus non-sub... -
UdoB reacted to leesteken's post in the thread [SOLVED] Windows VM with a passed through GPU slows down whole host to near not responding when powered on with Like.
Your CPU only has 6 cores with 2 threads each and you are giving at least one VM 12 VCPUs while Proxmox (and other VMs) also needs to do stuff like graphs and emulating the e1000. Try giving your VMs no more than 4 cores (each) and Proxmox will...
-
Please use code blocks.