Note: It's a good idea to create a second test VM so you can refer to it's. Look in /etc/pve/qemu-server/ for a file with the VM number followed by. You can copy the files directly there.įor adding the existing file to the VM, edit the VM's. There should be a subdirectory called images with a directory for each VM (named by the VM number).
Local storage on ProxMox is in /var/lib/vz directory.
conf file or replace previously created system image file used for booting the guest. Use scp or any other comparable tool as that will use SSH for the upload and it does not require any additional configuration.Įither copy the file to the server and then manually edit the VM's. Then you have to manually upload the CHR disk (in qcow format) on the ProxMox host.
Touch /etc/apt//pve-no-subscription.listĬreate a new guest with the system disk and other devices as required. Should I enable the Qemu agent in the CHR VM in some way?ĭo note, that trying to use the command to enable chr.provision-agent (which I don't know what it is for, presumably opening a TCP/IP channel for comms? ) works, but then gives an error when I try to bring the VM up.Rm -f /etc/apt//pve-enterprise.list However even though my hypervisor (Proxmox 5.3) does support it as well and I've enabled the "Qemu agent" in the respective VM settings, proxmox still can not connect to the Qemu agent on CHR: from the proxmox gui, it is noted that "Guest Agent is not running". According to, CHR VMs do support this feature.
This could be accomplished if the VM supported the QEMU Agent. The error during shutdown is TASK ERROR: VM quit/powerdown failed This was not always a problem, problems have started appearing about 1-2 months ago. Since I've been having problems with shutting the VM down before taking a backup from PVE, I've been searching for a way to notify the VM. I've been running a Mikrotik CHR VM version 6.41.2 for some time now, only for the record of using the embedded TheDude network monitoring package.
0 kommentar(er)
