Latest activity
-
Wwillybong posted the thread Stretched Proxmox cluster across 3 datacenters in Proxmox VE: Installation and configuration.Hi everyone, I'm facing a quite tricky quorum/partitioning issue in a stretched Proxmox cluster across 3 datacenters, and I’d really appreciate some insights from people with experience in similar setups. Cluster topology 7-node Proxmox...
-
LLongQT-sea replied to the thread Enabling virtual machine platform on fully patched windows 10 22H2 causes vm to hang at boot.@whiggs Try this: 1. Create /etc/pve/virtual-guest/cpu-models.conf # Proxmox VE Custom CPU Models cpu-model: amd-for-windows flags +vmx;-hypervisor;+invtsc;+hv-frequencies;+hv-reenlightenment;+hv-emsr-bitmap;+hv-tlbflush-direct phys-bits...
-
Now I feel stupid to miss that. But for the regular /etc/ directory (which OP also wants to backup if I didn't miss something) snapshots would work fine. And for /etc/pve consistency isn't that much of an issue like with the remainder of /etc... -
KKodey replied to the thread 203.30.8.0/21 is listed on the Policy Block List (PBL).The solution was fairly straightforward and involves only a vpn and lightly modified postfix on the pve. It isn't exactly as the diagram specifies since no emails traverse the pmg public ip, only the pve ip which has reverse ptr I know there are...
-
Uuzumo replied to the thread Force Host Device to use Xe instead of vfio-pci.It is not normal for the VM to switch from Xe to vfio-pci at startup even though 03:00.0 has not been specified for the VM you are attempting to start. When specifying 03:00.1 or 03:00.2 for the VM, did you select “ALL Functions”?
-
JJohannes S reacted to leesteken's post in the thread [SOLVED] systemd-timedated starting every minute filling up the journal with
Like.
Maybe Zabbix should not monitor that (oneshot) service, as it's not supposed to be running all the time? Maybe report this to Zabbix? -
JJohannes S reacted to Neobin's post in the thread [SOLVED] Log-Spam durch systemd-timedated with Like.
https://forum.proxmox.com/threads/systemd-timedated-starting-every-minute-filling-up-the-journal.182772 https://forum.proxmox.com/threads/systemd-timedated-starting-every-minute-filling-up-the-journal.182772/post-848992
-
TTechnolust replied to the thread [SOLVED] Proxmox confused about SAN Storage Capacity.Thank bbgeek17, interesting if it doesn’t have two stanzas/entries by default. We initially didn’t change the file until ChatGPT noted to change it. The only thing I could think of is we built the 10TB LVM and then removed it after it didn’t let...
-
Ddaddywombat replied to the thread [Solved] Recent updates caused problem with migration.Adding the No-subscription repo is allowing the updates to come down for proxmox too, thanks!
-
Ddaddywombat reacted to Impact's post in the thread [Solved] Recent updates caused problem with migration with Like.
I don't see any repos that provide it. Please make sure they are configured properly, then try the commands again. For reference, this is how it looks for me
-
Ddaddywombat replied to the thread [Solved] Recent updates caused problem with migration.Thanks, this was the answer. By modifying that line via nano /usr/share/perl5/PVE/LXC/Setup/Debian.pm it will now start. Cheers!!
-
Ddaddywombat replied to the thread [Solved] Recent updates caused problem with migration.pve-container: Installed: 6.0.9 Candidate: 6.0.9 Version table: *** 6.0.9 100 100 /var/lib/dpkg/status Not using the enterprise repos. But installed PM just last month.
-
Ddaddywombat reacted to Impact's post in the thread [Solved] Recent updates caused problem with migration with Like.
Please put command outputs in code blocks. Are you using enterprise repos? I don't have access to them but as far as I know this issue has been fixed for them too. What's apt policy pve-container say? The issue was fixed here...
-
Ddaddywombat replied to the thread [Solved] Recent updates caused problem with migration.Thanks, didn't help; Starting system upgrade: apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not...
-
Ddaddywombat reacted to Impact's post in the thread [Solved] Recent updates caused problem with migration with Like.
You might need to upgrade the node, for example via pveupdate && pveupgrade.
-
Ttestermox reacted to aureladmin's post in the thread [TUTORIAL] HiveStation — Developer Workstation for Proxmox Virtual Environment with Like.
HiveStation — Developer Workstation for Proxmox Virtual Environment Formerly "Proxmox VE Developer Workstation" — renamed to HiveStation for Proxmox trademark compliance. HiveStation is an independent community project. It is not affiliated with...
-
Ddaddywombat replied to the thread [Solved] Recent updates caused problem with migration."Unsupported debian version 13.4"??
-
Ddaddywombat replied to the thread [Solved] Recent updates caused problem with migration.Thanks, in the order requested. Also apparmor is 4.1.1-pmx1 pveversion -v proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve) pve-manager: 9.0.3 (running version: 9.0.3/025864202ebb6109) proxmox-kernel-helper: 9.0.3...
-
powersupport replied to the thread Caching drive replacement.This looks more like a cache path / mount issue than an S3 problem. When PBS marks an S3 datastore as “unavailable,” it’s usually because the local cache directory isn’t accessible or doesn’t match what PBS expects. Here are a few things to... -
Ddaddywombat reacted to dakralex's post in the thread [Solved] Recent updates caused problem with migration with Like.
Hi! Could you post the output of pveversion -v, pct start 103 --debug and syslog which includes the starting of the container? Also what version of apparmor is running on the host?