Search results

while we have been "lucky" during the last days, not seeing any recent freezes, what puzzles me is that even a watchdog is not able to interact with such a frozen VM. That is, no matter what has been configured (eg. reboot), the VM is and remains frozen. As far as I understand how the kernel...

We're probably in the same boat as well, we're seing some very high load Debian 11 VMs (high load on CPU, RAM and I/O) freezing randomly. Sometimes they run without issues for weeks and sometimes they crash after days following a reboot. In our case, the common determinator is that they run on...

well, I dug a bit deeper as well and it looks like as if the version of the ureq HTTPS client used (as indicated in the exception /usr/share/cargo/registry/ureq-2.4.0/) is outdated. There is a fix for dealing with those "UnsupportedCriticalExtension" since ureq 2.6.0...

Allright, after temporarily removing the local CA certificates from /usr/local/share/ca-certificates and running "update-ca-certificates --fresh" again, pvesubscription update successfully completes. So the issue must have something to do with those custom CA certificates, but as they have been...

yes, there are some local CA certificates in that directory. They have been put there in Nov 2019, so that's quite a while :) I however noticed that one of the certificates didn't have .crt but .pem as a filename extension. After listing all known certificates from...

thanks. I can ping & connect to shop.proxmox.com on the node's commandline, but "pvesubscription update" throws an ugly exception: root@sisyphos:~# RUST_BACKTRACE=full pvesubscription update thread '<unnamed>' panicked at 'Failed to add native certificate too root store...

Hi, one of our nodes feels unhappy about its subscription state and displays "invalid: subscription information too old" in the node's subscription page: When I click "Check", a popup opens and displays "Connection error 596: Broken pipe". Nothing conclusive in the logs, maybe anyone else...

When it comes to storage, we have been using ZFS over iSCSI in our clusters for years. Now for a couple of new projects, we require S3 compatible storage and I am unsure about the best way to handle this situation. I am tempted to use MinIO, but I've read mixed reviews about it and Ceph seems...

alright, figured it out myself. The "problem" is that I ticked "privilege separation" when I created the token. After unchecking privilege separation, everything works now as expected!

I am trying to use the terraform<->proxmox plugin and for that purpose, I have created a dedicated terraform provisioning user like this: pveum role add TerraformProv -privs "VM.Allocate VM.Clone VM.Config.CDROM VM.Config.CPU VM.Config.Cloudinit VM.Config.Disk VM.Config.HWType VM.Config.Memory...

I'm in the process of migrating our infrastructure to a more declarative, GitOps/terraform style. As a part of this, a lot of VMs will be created using customized cloud-init images (debian, fwiw). Now the only thing missing for my little puzzle is to get networking right. When creating VMs...

This is weird. What version of PVE are you using? And did you mangle with your (global) bash configuration?

It is almost 3 years now that I posted my "solution" and things have evolved a lot, since. QEMU and the linux kernel have received numerous updates, that also affect nested virtualization. Because of both performance and stability issues, we've since completely gotten rid of all Windows VMs...

HI, I need to replace a switch in one of our datacenters, that is used by a couple of PVE nodes for almost anything (corosync, ZFS over iSCSI, node to node traffic for VMs etc.). The replacement shouldn't take long, but still it may take a minute or so. For all the traffic except ZFS over...

there's actually an simple workaround for this. Say for example if your boot device that is NOT attached to the HP P420i is sda and your HP P420i devices only start at sdd, then just modify char_index from. old: char_index=({a..p}) to new char_index=({d..s}) That way, the wrapper script won't...

Thanks, but I highly doubt this has got anything to do with my issue. I'm talking about a linux guest (debian buster) running it's own kernel and I can't imagine the PV host kernel would interfere with the device renaming in a guest VM.

here you go: $ cat /usr/lib/systemd/network/99-default.link # SPDX-License-Identifier: LGPL-2.1+ # # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free...

I've recently upgraded one of our installations from 6.x to the latest 7.x. Because of that I have been monitoring the VMs a little bit more closely, which is why I noticed one linux VM behaving strangely. This is a debian 10 VM with more than 10 NICs and after closer inspection, I saw that a...

I'm "suffering" from the same situation, with a P420i controller in RAID mode. The UI would only show an error when trying to access the SMART values via the "Disks" page. So what I did was to write a little wrapper script around smartctl, adding the "-d cciss,X" as needed. /dev/sda will get...

Yes, there are some windows VMs running on that server, but I haven never seen those messages before for a windows VM. The only "special" thing on this server is a MacOS VM, so I guess that's where the noise is coming from.