Windows 2012R2/Windows 2016 cloud-init problem

parker0909

Well-Known Member
Aug 5, 2019
87
0
46
36
Hello All,

We are facing the problem when we tried to deploy the windows server 2012R2/2016 via cloud-init. we have tested in the PVE 5.3 and it should be working.But we found that the cloud-init should not working in PVE 5.4 and we got the error during the VM creation. I not attached the print screen to show the error message when we start up the VM. Any idea to fix the problem. Thank you very much.

Parker
 

Attachments

  • cloudinit.png
    cloudinit.png
    29.6 KB · Views: 43
Please post your VM config ('qm config <vmid>') and the cloudbase-init version used in the VM.
Please also post the output of 'pveversion -v'
 
Please post your VM config ('qm config <vmid>') and the cloudbase-init version used in the VM.
Please also post the output of 'pveversion -v'

Thank you. I have installed the Cloud-init 0.9.11 into the windows server 2012 R2 VM. I have posted the VM config and pveversion -v' result as below.

VM config
"my" variable $uuid masks earlier declaration in same scope at /usr/share/perl5/
PVE/QemuServer/Cloudinit.pm line 214, <DATA> line 755.
agent: 1
boot: cd
bootdisk: ide0
cipassword: **********
cores: 2
cpu: kvm64
ide0: cccs_storage:vm-20235-disk-0,size=80G
ide1: none,media=cdrom
ide2: none,media=cdrom
ide3: cccs_storage:vm-20235-cloudinit,media=cdrom
ipconfig0: ip=103.1.14.116/24,gw=103.1.14.1
lock: migrate
memory: 4096
name: parkertest4.local
net0: virtio=26:19:B3:90:57:F1,bridge=vmbr0,rate=10
net1: virtio=42:37:EC:51:57:3A,bridge=vmbr0,firewall=1,rate=100
numa: 1
ostype: win8
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=8bc54975-621c-4dba-b733-dfd514553b1d
sockets: 1
vga: serial0
vmgenid: f7156a3b-9227-4d2b-8d8c-9180a15ac683


pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-12-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph: 12.2.12-pve1
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-54
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-37
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
 
You have a modified Cloudinit.pm file. Please reset it to the original by running 'apt install --reinstall qemu-server'. You should also update your PVE to the latest version.
 
You have a modified Cloudinit.pm file. Please reset it to the original by running 'apt install --reinstall qemu-server'. You should also update your PVE to the latest version.

Thank you. I have reinstalled the qemu-server and upgrade the PVE via pve-no-subscription. The problem should be same with before.

http://download.proxmox.com/debian/pve stretch pve-no-subscription

pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-12-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph: 12.2.12-pve1
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-54
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-5
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
root@cccs05:~# pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-12-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph: 12.2.12-pve1
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-54
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-5
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
 

Attachments

  • error.png
    error.png
    26.6 KB · Views: 10
Does the same error happen on Windows Server 2016? Is it the latest cloudbase-init version?