Recent content by voarsh

Currently I am running GitLab CE in an LXC (13.4.7) and I cannot upgrade to 13.8 There was an error running gitlab-ctl reconfigure: execute[reload all sysctl conf] (package::sysctl line 18) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received...

I am experiencing the same problems with a Win 10 VM..........

If you're using an LXC for your bindmounts (which you seem to have referenced), why not use mergerfs and snapraid on the hypervisor host system and then mount the mergerfs directory on your LXC?

I added the following custom IPTable rules in a VM router (OpenMPTCProuter): iptables -A INPUT -p tcp --src 192.168.1.1 -m tcp -m multiport ! --dports 80,443 -j DROP iptables --append INPUT --protocol udp --src 192.168.1.1 --sport 67 --jump DROP iptables --append INPUT --protocol tcp--src...

Hi. I need to change the eth0/net0 gateway on my Ubuntu VM's that are running with CloudInit, I can change the GW in the configuration file but requires restart. Networking with CloudInit is different than just running a normal Ubuntu image, I think... Does anyone know how I can change the...

Grab the ISO and make a bootdrive, however you wish: https://proxmox.com/en/downloads/item/proxmox-ve-6-4-iso-installer Grab all the configs from /etc/pve/qemu-server and /etc/pve/lxc/ Have all the VM's backed up in PBS, if not, keeping the .raw/.qcow2 files and throwing them on a storage you...

I wouldn't try to downgrade a host to a previous major version. You can however, backup VM disks and put them on a new (previous version on a fresh install) and use the VM config's as well from the old host. I stick with the yearly major versions, we're now at PVE7 and PVE6 is on life support...

Looks like I'll be sticking with PVE V6X until GPU passthru is ironed out a bit more.

I often get timeouts for 6-9 GB's of RAM when resuming VM's - a bit frustrating. It's "spinning rust", even using striped HDD's which is faster than a single HDD. Any news about making the resume timeout configurable?

yes, I know this, but PVE team can compare what's in the cluster and what's in the new joining node, rename VM/CT IDs and disk names to not be what's in the cluster, so when joining it's unique. Only workaround is to backup every VM/CT and restore after joining (oh, and dealing with VM/CT IDs)

Thanks! I thought it was a strange one. I'm still on 6.4 - I'm not sure if it'll be addressed, and I haven't tested if it exists on V7.

Oh gosh, I didn't know that. So, you can't migrate containers at all? When I do a migration from host to host, the disk target isn't visible for me, and of course the issue in this thread....

Following from: https://forum.proxmox.com/threads/lxc-cant-migrate-to-a-remote-disk-i-choose.96472/post-424130 I can start a migration but the storage E.G. Node 1 (storage X) to Node 2, tries to use storage X, but I want storage Y on node 2, but the GUI or CLI doesn't let me specify a storage...

The solution was from here: https://forum.proxmox.com/threads/migration-error-proxmox-to-proxmox.8895/post-50348 The storage wasn't available on the other node. But it wouldn't use that storage (it's not a NFS/shared storage), so I think it's going to use local or something.

Yeah, thanks. Like I said, I'll get a larger drive that can fit all of the datastores backup, then trim the ones I don't need. Eagerly await exclusions for retentions, etc.