Recent content by Gilberto Ferreira

It's a little weird container inside a container. I think inside a VM is the way to achieve better performance. And needs to mention that LXC reboots when migrate.

Do a backup beforehand is highly advisable.

Wow! Datacenter bulk actions??? This in come im handy. I asked this feature a long time ago... https://bugzilla.proxmox.com/show_bug.cgi?id=4200 Thank you guys... You are amazing.

Hi Just a follow up about this issue. It's seems to be solved after some last updates. Thanks.

brctl show will help too and ss -atpn | grep :8006 df -h systemctl status pve-proxy cat /etc/hosts

In order to better assist, we need to know the content of the files and commands ouput cat /etc/network/interfaces dmesg | grep -i eth ip a

Hi there. Just to clarify: one can still use glusterfs as a directory based storage. I've been doing it for years now, and works fine with any Proxmox VE version or Qemu. Just my 2 cents.

Sill missing vCPU on the first screen of the Wizard.

very good

https://forum.proxmox.com/threads/opt-in-linux-6-17-kernel-for-proxmox-ve-9-available-on-test-no-subscription.173920/

Make sure you do a backup, BEFOREHAND. (Just a double advice!)

Usually the vm disks are in LVM volume Try in the shell lvs Alternativaly you can use a grep filter lvs | grep 100 But like @Impact said, needs to see /etc/pve/storage.cfg to be sure how the storage layout.

I don't think so. At least I have installed this kernel 6.17 in a bunch o PVE 9 using no-sub repo.

Hi I have create a snapshot and than detach a 32G second disk. After that I was unable to delete a snapshot. Even after reatach de detached disk. So, I went ahead and remove the snap_lvm thing with lvremove Now I can't initiate the VM TASK ERROR: qemu-img: Could not open...

Could this kernel been available to Proxmox VE 8?