Latest activity
-
Ssiren4161 replied to the thread New router, PVE host can't connect to network at all.Great thread, thank you for the link and thanks @UdoB for writing it. Following this tutorial, I ran ip link and returned state DOWN for my interface eno1. I have tried several cables and the LEDs on the router and NIC are illuminated. I have...
-
Ssiren4161 replied to the thread New router, PVE host can't connect to network at all.Thanks, please see the outputs in the attached photos. Yes, I've tried several. Unfortunately I don't have a switch available, but I have tried two different routers and multiple ports on each.
-
-
PIt still works with current kernels as the io_uring bug has been fixed. According to https://www.kernel.org/doc/html/latest/process/maintainers.html OCFS2 is actively maintained.
-
Ppalladin9479 replied to the thread PVE+ISCSI.Yes random guy on forum says it's not for some random reason... According to the maintainers, the ones maintaining the code, OCFS2 is actively maintained. Oh the code base for the non-kernel tools used in Debian and RHEL distros...
-
Wwendellrodriguez replied to the thread High VM-EXIT and Host CPU usage on idle with Windows Server 2025.Please try to set CPU to native like a host and testing again.
-
SteveITS reacted to complexplaster27's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with
Like.
Hello I've have installed this new driver on our Test servers and have done the following in terms of multi-day testing: Boot-volume operation on vioscsi 0.1.302 Multiple reboots and device checks Five active VirtIO SCSI controllers Overnight... -
G_gabriel replied to the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth.Never expose 8006 port publicly. https://forum.proxmox.com/threads/proxmox-virtual-environment-security-advisories.149331/post-867929
-
G_gabriel reacted to complexplaster27's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with Like.
Hello I've have installed this new driver on our Test servers and have done the following in terms of multi-day testing: Boot-volume operation on vioscsi 0.1.302 Multiple reboots and device checks Five active VirtIO SCSI controllers Overnight...
-
Ccomplexplaster27 replied to the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive".Hello I've have installed this new driver on our Test servers and have done the following in terms of multi-day testing: Boot-volume operation on vioscsi 0.1.302 Multiple reboots and device checks Five active VirtIO SCSI controllers Overnight...
-
bbgeek17 replied to the thread From LVM storage screen, please allow binding LVM volume to VM.I would always recommend to stay within the bumpers of the system. Especially when an easy to use procedure is available. IMHO this is such a rare situation that complicating UI with handling this case is counterproductive. That said - feel free... -
MMDSOperator replied to the thread Proxmox VE 7 is vulnerable to some type of 0day/RCE non auth.Proxmox VE 7.1 - cryptojacking rootkit + root SSH backdoor: full teardown TL;DR Two PVE 7 hosts were compromised and running an XMRig cryptominer hidden by a preload rootkit. The same "install_and_mine.sh / libhide" toolchain planted: A...
-
Ssantiagobiali replied to the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive".The TRIM issue occurs because Microsoft introduced some trim functions not yet implemented in virtio's driver. It's not related to ZFS's backend. I've added what I found in this github issue...
-
BI see this is a long dead there but we would like to be able to use microvm's for the additional isolation they provide paired with the near-contrainer-like spin time and(?) the cloud-init support.
-
BI'm curious if there are any future plans to support MicroVMs in Proxmox? https://firecracker-microvm.github.io/ looks very promising for creating very low resource usage VMs (not containers) and is the technology backing AWS Fargate 1.4 without...
-
It still works with current kernels as the io_uring bug has been fixed. According to https://www.kernel.org/doc/html/latest/process/maintainers.html OCFS2 is actively maintained. -
BBabou posted the thread Proxmox Secure Boot issue on Minisforum MS-A1 (MOK/PK enrollment blocking boot) in Proxmox VE: Installation and configuration.Bonjour, J'ai récemment acquis un Minisforum MS-A1 équipé de trois SSD NVMe. J'ai installé Proxmox à partir d'une image ISO 9.2-1 et de Rufus. L'installation s'est déroulée sans problème et, après la mise à jour vers la dernière version, j'ai...
-
Kkayson replied to the thread SR-IOV IOMMU Groups Keep Changing.Turns out the issue was a race condition! I have systemd-udevd link files for each PF that creates the VFs. systemd's rules/events fire in parallel, so whichever VFs happened to get created first got the lower iommu groups. The solution was to...
-
JWell, in the end it turned out that adding hw.virtio.pci.transitional to /boot/loader.conf.local did the trick and unlocks the modern virtio, even if Proxmox uses the PCI bus and not PCIe. Multiqueue is also working fine then, als long as you...
-
G_gabriel reacted to SteveITS's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with Like.
discard_granularity was still needed on driver .266, at least for the CPU usage/timeouts. We are using Ceph for VM storage. ref: 2024 post...
-
SteveITS replied to the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive".discard_granularity was still needed on driver .266, at least for the CPU usage/timeouts. We are using Ceph for VM storage. ref: 2024 post...
