Recent content by EagleTG

Was also noticing this today, and took note that the calls to the Ubuntu servers (during cloud-init and mirror validation, as two examples) were running quite slow compared to what I'm used to, may be a red herring though as switching to the Pilot Fiber Mirror did not fix it in my case (maybe...

A bit of a delayed reaction, but for the record, we proceeded exactly like Spirit indicated, and it worked like a charm. Thank you so much for the help. We also moved quickly during the upgrade process to mitigate potential issues with mixing versions within the cluster.

Update, this post makes it pretty clear that it's important to only mix versions during the upgrade process: https://forum.proxmox.com/threads/mix-cluster-proxmox-ve-6-and-7-version.92644/

Ahh, I was hesitant to do this based on some of the forum posts I found regarding mixing 6.x and 7.x versions within the same cluster. There were quite a few posts that seemed to recommend against mixing versions, or maybe more accurately did not necessarily endorse it. I also found this thread...

I just found this article, which seems to confirm that my plan is sound: https://pve.proxmox.com/wiki/Bypassing_backup_and_restore_when_upgrading One difference being that I do not need to modify the storage.cfg as I already completed that manually.

Hi everyone, I read all of the relevant documentation and quite a few forum posts regarding upgrading from 6.x to 7.x. I know the recommended approach is generally to back up the VM, copy it to the new host/cluster, and restore, but I think I settled on a faster/better migration process (for my...

Hi everyone, Yes, it works fine on a bonded interface. In our production cluster, I'm using an LACP bond of two 10 Gbe interfaces with a VLAN for Corosync and it works perfectly. I posted a while back about this, citing the same area of the documentation...

Ahhhh, that was my bad. I was looking at the host level, not the datacenter level. I had modified my /etc/pve/storage.cfg to have sparse 1 which took care of the issue (and shows checked in the interface where you mentioned). Thank you! Chalk this one up as user error. Hahah. ;)

Hi everyone, Sorry if i'm being obtuse here, but I can't seem to find the thin settings for disks/volumes in PVE 7.2. I'm working on a new installation, storage is on a ZFS pool. I created one VM with an attached disk and noticed that it thick provisioned by deault. Thinking that I must have...

Since your weapon of choice is Bash, have you tried the Proxmox command line tools like qm? I’ve been able to do everything I’ve wanted to do with Bash and qm (or a few of the other standard PVE tools). If your goal is just starting and stopping, qm will do that perfectly. Manual for qm...

Hi mira, Yes, opening Guacamole and then the NoVNC console seems to work properly. Thanks! Edit: However, even after this, if the Guacamole session is reconnected in any way (even sometimes switching browser tabs), the issue occurs.

Just a quick update for anyone finding this thread, I decided to take the full outage just in case. I shut down all workloads and everything went perfectly. Upon booting everything up, I ran some testing with disconnecting offline workloads from storage and can confirm everything BBGeek said...

Hi mira, here are the results: From gdb bt: #0 0x0000000000000000 in ?? () #1 0x0000560bb69164dd in protocol_client_msg (vs=0x560bb9c334e0, data=0x560bb96f0620 "\006", len=12) at ../ui/vnc.c:2459 #2 0x0000560bb6913a77 in vnc_client_read (vs=0x560bb9c334e0) at ../ui/vnc.c:1621 #3...

Guacamole itself generally works fine, as long as I stay away from using the Proxmox UI at the same time. Additionally (and weirdly), other VNC clients (Specifically the TigerVNC Mac OS client) seem to co-exist and can connect at the same time perfectly fine. I launched via a temporary BASH...

Hi everyone, I've run into an issue that is kind of specific to what I'm using Proxmox for, so I'm not entirely sure if anyone will care to pursue the issue. I've found a work-around at this point, so my use case is 'fixed'. This may also be something for the qemu or kvm teams, so please guide...