Recent content by Phill

remove any entry from the network tab in the gui

hello i have four single pve nodes with custom ssh ports. for me it works very well. greetings phill ;-)

hallo, also ich wüsste jetzt auch nicht wie du eine einfach neuinstallation hinbekommst. aber was spricht gegen folgendes: einfach lxc container löschen und mit gleicher ID (+sonstigen einstellungen) wieder neu anlegen? liebe grüße philipp ;-)

soooooo... i try to reproduce it... you must unmakr the checkbox and load the driver from vioscsi and also the driver from viostor

try to remove the checkbox "hide drivers that are not compatible....." ?

thats not possible with LXC - there is no simfs, so you don't see the FS from the containers! but it's so mutch more easy - make a simple backup with vzdump! (from the host shell oder via GUI) use "stop mode" & "tar.gz" & and afterwards move the xyz.tar.gz from you backup folder to the...

6a) clean it (apt-get clean, remove hostname, resolv.conf, ect.)

i will try it to explain it in english: 1) download a normal lxc / openvz template 2) create an lxc container with this template 3) boot it 4) open it (pct enter <id>) 5) install / modificat everything you want 6) remove all network interfaces 7) shutdown the container 8) make a backup with...

i'm on your side, but you are here on the wrong address.... it's not an proxmox problem - it's an lxcfs problem, so (i think) they must fix it

You can also remove the obsolete OpenVZ container data from your local storage. rm -f /etc/pve/openvz/<ct-id>.conf rm -R <storage-path>/private/*

hello tukiyo3 here is my unofficial workaround: 1) open the CT config on the host node (/etc/pve/nodes/HOSTNAME/lxc/CTID.conf) 2) search for "rootfs: local:CTID/vm-CTID-disk-1.raw,size=XXXG" and edit size=XXX to the new rootfs size you want 3) make a backup of the CT (via gui or cli) 4)...