Hi there, see title. The command does not work as expected on 7.1-8. This command used to work fine (last known working version was 6.4.x). The documentation states it should work.
I'm following the instructions on my own blog post to create a Ubuntu cloud-init template. This is the full set of commands (with some error'd commands removed) I ran up to the error:
Any suggestions? Should I file a bug report?
Code:
qm set <vmid> [OPTIONS]
--agent [enabled=]<1|0> [,fstrim_cloned_disks=<1|0>] [,type=<virtio|isa>]Enable/disable communication with the Qemu Guest Agent and its properties.I'm following the instructions on my own blog post to create a Ubuntu cloud-init template. This is the full set of commands (with some error'd commands removed) I ran up to the error:
Code:
12 wget https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img
13 sudo apt install libguestfs-tools -y
14 sudo virt-customize -a focal-server-cloudimg-amd64.img --install qemu-guest-agent
16 sudo virt-customize -a focal-server-cloudimg-amd64.img --install git
17 sudo virt-customize -a focal-server-cloudimg-amd64.img --install htop
18 sudo virt-customize -a focal-server-cloudimg-amd64.img --run-command 'useradd austin'
25 sudo virt-customize -a focal-server-cloudimg-amd64.img --run-command 'mkdir -p /home/austin/.ssh'
26 sudo virt-customize -a focal-server-cloudimg-amd64.img --ssh-inject austin:file:/home/austin/.ssh/id_rsa.pub
27 sudo virt-customize -a focal-server-cloudimg-amd64.img --run-command 'chown -R austin:austin /home/austin'
28 history
29 sudo qm create 9000 --name "ubuntu-2004-cloudinit-template" --memory 2048 --cores 2 --net0 virtio,bridge=vmbr0
30 sudo qm importdisk 9000 focal-server-cloudimg-amd64.img local-zfs
31 sudo qm set 9000 --scsihw virtio-scsi-pci --scsi0 local-zfs:vm-9000-disk-0
32 sudo qm set 9000 --boot c --bootdisk scsi0
33 sudo qm set 9000 --ide2 local-zfs:cloudinit
34 sudo qm set 9000 --serial0 socket --vga serial0
35 sudo qm set 9000 –-agent 1
36 sudo qm set 9000 –-agent enabled
37 sudo qm set 9000 –-agent
39 pveversion -v
40 historyAny suggestions? Should I file a bug report?
Code:
austin@prox-3070:~$ sudo qm set 9000 –-agent 1
400 too many arguments
qm set <vmid> [OPTIONS]
austin@prox-3070:~$ sudo qm set 9000 –-agent enabled
400 too many arguments
qm set <vmid> [OPTIONS]
austin@prox-3070:~$ sudo qm set 9000 –-agent
400 too many arguments
qm set <vmid> [OPTIONS]
austin@prox-3070:~$ pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-8 (running version: 7.1-8/5b267f33)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3