dakralex's latest activity
-
dakralex reacted to NinjaBlizzard's post in the thread Trouble upgrading from 8.4.1 to 9.0 with
Like.
Thanks for the reply! I just confirmed that I was missing the correct Trixie repositories. After copying the correct repositories from another working trixie install, I was able to run apt full-upgrade; all upgrades completed successfully and the... -
dakralex replied to the thread Massenstart von VMs und Container.Es wird jedoch ein Skript pvenode startall ausführen. Haben Gäste z.B. hookscripts aktiv, die das ausführen? Oder ein systemd unit?
-
dakralex replied to the thread Massenstart von VMs und Container.Könnte es sein, dass Skripte die oben genannten CLI Kommandos/API Endpunkte in scheinbar unregelmäßigen Intervallen ausführen? z.B. Hook scripts, externe Automatisierungstools, etc. Scheinen in der Task Ausgabe bestimmte VMs/Container auf oder...
-
dakralex reacted to Zalaare's post in the thread ASM1166 issues with PVE 9 (kernel 6.14.11-1-pve) with Like.
Hello, This seems possibly related to this thread.
-
dakralex replied to the thread Massenstart von VMs und Container.Hilfreich wäre auch noch einen dieser Tasklogs (per Doppelklick auf den Task) zu sehen.
-
dakralex replied to the thread Massenstart von VMs und Container.Auf welcher Version befindet sich die Node und die packages darauf (pveversion -v)? Gibt es Auffälligkeiten im syslog (e.g. journalctl -xe)? Wie ist der Status von systemctl status pve-guests.service? Der "Massenstart von VMs und Container" ist...
-
dakralex replied to the thread Massenstart von VMs und Container.Hi! Könntest du einen Auszug aus den Tasklogs hier posten und wie einer der VM/Container Configs aussieht? Wird in dem Cluster/auf der Node der HA Manager betrieben?
-
dakralex replied to the thread NR status for quorum nodes in three node cluster.Hi! How did you add the node to the cluster? Note that it is required to remove the QDevice before adding (or deleting for that matter) a node to the cluster [0]. Also note that a QDevice in a odd numbered cluster is discouraged, see [1] for...
-
dakralex replied to the thread ASM1166 issues with PVE 9 (kernel 6.14.11-1-pve).Hi! Which kernel were you using before that made the ASM1166 controller stop working? Could you include a bootlog and the communication errors that you reported? AFAICS there were a few patches [0] [1] [2] regarding the ASM1166, but all of...
-
dakralex replied to the thread [SOLVED] VM won't start with PCI passthrough after upgrade to 9.0.As soon as there is a go-to solution to the problem, then yes, this will be backported to Proxmox VE 8 as well. Is there any trouble with the virtual machine on Proxmox VE 9 with the following? If yes, it would be valuable information to fix the...
-
dakralex replied to the thread Trouble upgrading from 8.4.1 to 9.0.Hi! Are there any Debian Bookworm / Proxmox VE 8 repositories left in /etc/apt/sources.list or /etc/apt/sources.list.d/*? You can also check the output with apt policy to see the priority of each configured repository.
-
dakralex replied to the thread pvestatd segfaults.Hi! As there are multiple programs segfaulting, I'd check if there are any problems with memory (memtest), filesystem corruptions or package corruptions (e.g. smart tests, checking packages with debsums -c, etc.).
-
dakralex replied to the thread Apparmor Problem nach Restore eines LXC-Containers vom PBS in ein HA-Cluster mit Ceph.Hi! Könntest du die Config des containers (i.e. cat /etc/pve/nodes/ha-node-01/lxc/105.conf) und den Output eines Debug-Starts des Containers (i.e. pct start 105 --debug) posten?
-
dakralex replied to the thread Cluster 6 nodes mixture of prox 8 and 9 possible.Hi! Mixing Proxmox VE versions in a cluster is not something we test against, except during the (hopefully brief) update procedure of the individual cluster nodes, so it's definitely not recommended to do that in a production environment. I'm...
-
dakralex replied to the thread [SOLVED] VM won't start with PCI passthrough after upgrade to 9.0.AFAICT from this error message, this is related to a wrong address width that is being sent to the iommufd (the vIOMMU functionality is provided by iommufd, which allows userspace programs to work directly with the IOMMU and therefore DMAR)...
-
dakralex replied to the thread [SOLVED] VM won't start with PCI passthrough after upgrade to 9.0.Yes, the guest-phys-bits cpu option is now exposed via the VM config for Proxmox VE too. Setting the cpu in -args overwrites the CPU option provided by Proxmox VE and there guest-phys-bits and phys-bits could've been set before too, even though...
-
dakralex replied to the thread [SOLVED] VM won't start with PCI passthrough after upgrade to 9.0.Great that it works. But no, for the intel-iommu it can only take 39 or 48 bits for now (it might allow 52 at a later time when 5-level paging is supported by QEMU, but that's for quite specific use cases and one needs the hardware that supports...
-
dakralex replied to the thread [SOLVED] VM won't start with PCI passthrough after upgrade to 9.0.I just sent the patch to the mailing list for review, if we go with exposing the aw-bits option then this patch will be available in a future release. For now, setting the machine version to 9.1 or lower or setting qm set <vmid> -args '-global...
-
dakralex replied to the thread [SOLVED] VM won't start with PCI passthrough after upgrade to 9.0.Just to update this thread too [0], the Intel vIOMMU's default address bit width value was increased from 39 bits to 48 bits in QEMU 9.2, so the error Failed to set vIOMMU: aw-bits 48 > host aw-bits 39 can be mitigated by pinning the machine...
-
dakralex replied to the thread After upgrade to PVE 9, qm, ha-manager, pvestatd, and more fail to start (unknown file 'ha/rules.cfg').Hm, please look into whether /etc/apt/sources.list.d/ contains the Debian Trixie repositories, Proxmox VE 9 / Trixie repositories, Ceph Trixie repositories and that you run apt dist-upgrade. Other packages might be held back because Proxmox VE 9...