Hi everyone,
I am new to PVE but have setup most things I wanted in my test PVE.
Unfortunately, the PVE itself and all VMs/LXCs become unreachable via ethernet from time to time and become immediately reachable again as soon as I log in on the...
Ok, dank KI & OpenCode konnte ich die Ursache jetzt doch selbst finden (lassen): In "/etc/pve/priv/tfa.cfg" wurde der Zugang gesperrt mit …"totp-locked":true… . Wenn man dort das auf "false" setzt, geht es wieder. Ich lass den Post mal so stehen...
Ich wollte auf einem Hetzner Dedicated nun endlich mal das Upgrade zu PVE 9 machen. Bei den Vorbereitungen über SSH fiel mir auf, dass die Systemzeit nicht stimmt und deswegen der Login in der Proxmox-Weboberfläche nicht mehr per TOTP möglich...
It might be, that feature compatability between QEMU and kernel version "causes" this message. That means one side trying to use a feature that the other cannot deal with. Easy to try out, if you are right with your assumption.
Looking forward to...
1. I think that because of NovaCore, the Proxmox 9.2 doesn't work with Nvidia RTX cards. `nomodeset` doesn't help.
2. In some cases, during upgrade, something is failing / misconfigured with the network stack, so even SSH access is not available...
The kernel version is irrelevant, if you answer none of the other questions.
Here is the exact code line where this is coming from:
https://github.com/qemu/qemu/blob/master/hw/vfio/region.c#L324
Same code is not included in QEMU 10.1...
I'm using a single dns entry (as PVE is a consul service in my network), to point to all the nodes in my proxmox cluster. All of them have their own unique SSL certificate, but all of them also have a common name (let's call it pve.my.domain)...
And what exactly is the issue here? How often do you see this message? Why does it bother you?
As you might have already seen in your search, this start with kernels >v6.19.
However, from what I read, it is intended just to be that, a "warning"...
Bei den HDDs würde ich aus Performancegründen gar kein ZFS bevorzugen. Mit HW Raid und ext4 / LVM Thin fährt man da deutlich besser.
Außerdem soll das je eh nicht produktiv werden sondern ist zum Erfahrungen sammeln.
Ich habe mich heute mal damit beschäftigt wie man VMs in Masse oder gezielt über Ansible oder Terraform ausrollen kann.
Hier meine kleine Mitschrift
https://pad.cooltux.net/MB4j0lq1S_CzII7zs0r66A
Grüße
What are the keywords specifically for this? I'm not sure if its zero trust, encryption, end-to-end encryption or something else? What I should be searching for?
How do you guard the datacenter? You don't mean physical guarding?
If you can find a way to do this with Linux then you can probably also do this with Proxmox (and I'll help you if there are Proxmox specific issues). You might want to consider robbers that steal your computer wile keeping it powered, if you are...
Hmm... it might just be that it loses focus. I've seen this happen when you have a password manager like Bitwarden or KeePassX installed in a Chrome-based browser. In that case, it helps not to click on the TOTP window, click somewhere else...
That is interesting because I had to change the browser to make it to work and this browser didn't have password manager installed like on the firefox. My totp is located in password manager that is in the system software so the password manager...
If a thieves were to enter in to my house and I had my proxmox VE up and running, unencrypted. Doesn't this mean that they can access everything they want on my PVE serve (containers, services, etc.)?
If this is true, then how do I protect myself...
As mentioned those commands can't see anything but the NVME device. The other devices are recognized by the kernel, since lsblk can list them. To my limited knowledge; I think and am leaning towards the issue seeming to be volume mapping related...
Hi Maxim,
with 4x 2.5GbE per node and your setup using Corosync, HA and ZFS replication without Ceph, I would separate the traffic types as much as possible to keep the cluster stable and easier to troubleshoot.
I would use one dedicated NIC...