Latest activity
-
Kkayson replied to the thread Glusterfs is still maintained. Please don't drop support!.You are the one missing the point. Qemu dropped the glusterfs storage backend claiming it's not maintained, which just isn't true. Sure, you could make an argument that it lacks sufficient support for enterprise deployments or even that it's...
-
JJayK posted the thread [SOLVED] One node cant access NAS shared storage in Proxmox VE: Installation and configuration.I know this has come up before, but I still can't find a solution that works for me. I have a NAS storage shared with all 3 nodes in my cluster. All nodes are running 9.0.11. I get the little capacity icon under each node but when I look at the...
-
MMarkku reacted to guruevi's post in the thread Wait until the SAN and LUNs are available before continuing with the Proxmox boot process with
Like.
There are a few ways to solve it: The cleanest but most difficult way is whatever process is doing the re-connect (in this case iscsi.service likely) and make the dependent process wait on it. You can do a systemd override configuration on... -
JJohannes S replied to the thread Glusterfs is still maintained. Please don't drop support!.A new version or "another attempt at keeping life support on"? This doesn't matter for qemus gluster support anyhow. Debian packaging new gluster versions wom't help in maintaining the Code for qemus support of gluster as storage backend. You...
-
Gguruevi replied to the thread Wait until the SAN and LUNs are available before continuing with the Proxmox boot process.There are a few ways to solve it: The cleanest but most difficult way is whatever process is doing the re-connect (in this case iscsi.service likely) and make the dependent process wait on it. You can do a systemd override configuration on...
-
UdoB replied to the thread how to set quorum 3 on 6 nodes cluster ?.You can set "expected N" as soon as only N nodes are left up and running. I prefer to do it step-by-step: shutdown node 6 and then pvecm expected 5; shudown node 5, pvecm expected 4; shutdown node 4, pvecm expected 3. Correct! -
NNvaes posted the thread Wait until the SAN and LUNs are available before continuing with the Proxmox boot process in Proxmox VE: Installation and configuration.Hello, I’m using an LVM over iSCSI setup, but when there’s a power cut, the Proxmox hosts boot up before the SAN, which causes errors on the VMs. How can I tell Proxmox to wait for the iSCSI LUNs before continuing the boot process? Thank you
-
Kkrtek replied to the thread Host memory exhaustion: Shmem ~= AnonPages, no ZFS.Well I finally found it. It was file /dev/DS_folder/del-vm-xxx-disk-0. du -ahx /dev 2>/dev/null | sort -hr | head -10 189G /dev/DS_folder/del-vm-xxx-disk-0 It was created during a migration of a vm from network storage to local storage...
-
Ggasherbrum replied to the thread Server hardware recommendations for new 3–4 node Proxmox VE / Ceph cluster.ISO 27001 accounts for these things, for example if you worked for an engineering firm with CNC machines running on windows 95, that is an essential business function. ISO 27001 would be defining the risk, apply security controls as much as...
-
Bboisbleu reacted to TErxleben's post in the thread [SOLVED] HyperV-Fehler nach Migration / VM bootet nicht with Like.
Was dir auf alle Fälle eher früher als später (womöglich schon jetzt) auf die Füsse fallen wird, sind deine VMs selbst. Wenn es tatsächlich Win11 ist, war die letzte Version 23H2, die mit seabios/i440fx lief. Danach eine Zeit lang noch mit...
-
Jjabuzzard replied to the thread Server hardware recommendations for new 3–4 node Proxmox VE / Ceph cluster.If a vendor rarely or never issues firmware updates, they are not addressing security issues in that firmware. I would argue that one reason Supermicro is cheap is that they skimp on the engineering costs of ensuring their products are secure...
-
JJesperNilsson79 replied to the thread Proxmox VE 9.2-1 ISO not installing in nested Hyper-V.I have the Same issue, 9.2 do not work in Hyper-V nested virtualization, 8.4 works fine..
-
Hi Fiona, /etc/systemd/network/eth0.network [Match] Name = eth0 [Network] Description = Interface eth0 autoconfigured by PVE Address = xxx.xxx.xxx.xxx/16 Gateway = xxx.xxx.xxx.xxx DHCP = no IPv6AcceptRA = false 1: lo: <LOOPBACK,UP,LOWER_UP>... -
fiona replied to the thread [Feature Request] Proxmox 9.0 - iothread-vq-mapping.@werter please don't spam! @dominiaz please see https://pve.proxmox.com/wiki/Developer_Documentation if you want to submit your changes for inclusion. We also need a signed CLA from you. Also, please coordinate with Alexandre Derumier. His...
-
Cchralt posted the thread [SOLVED] Kein Zugriff auf Konsole einer Virtuellen Maschine in Proxmox VE (Deutsch/German).Hallo Zusammen, ich habe ein weiteres Problem an dem ich schon länger herumdoktere. Nach dem Upgrade von Proxmox-VE 8.4.17 auf 9.1.14 habe ich keinen Zugriff mehr auf zwei von mehreren VMen, leider, wie as immer so ist, auf den wichtigsten...
-
Jj.theisen reacted to Karcsi's post in the thread Routed setup on Hetzner with Failover IPs: "Destination Host Unreachable with Like.
Yes, I rebooted the PVE node after the changes. The output of cat /proc/sys/net/ipv4/conf/vmbr0/proxy_arp is: 1.qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq It...
-
Ffanton replied to the thread sa-update equivalent.Got it. Sorry about that. I forgot I had done that
-
Kkayson replied to the thread Glusterfs is still maintained. Please don't drop support!.Yes it does. It's a new version. A rude way to make that observation, but I dont disagree. Nonetheless, directory is far less convenient that having the integration.
-
DDomino replied to the thread Ryzen 5950X: "Uncorrected, software containable error" events after upgrade to kernel 7.0.x.No errors here on a 5950x. amd64-microcode is already the newest version (3.20251202.1~bpo13+1) Motherboard is an Asrock x570m pro4 with bios P5.65 Memory is M391A4G4AB1-CWE
-
Kkayson replied to the thread Restoring a container backup that has an idmap fails via PVE GUI, but works fine via CLI.I'm running it with sudo, but the resulting container has an identical config as to what was backed up? Its unprivileged. Or do you mean the restore operation's privilege? I don't see how restoring a container's filesystem with idmapping would...