Result verification failed (400) machine: value does not match the regex pattern

p.lakis

New Member
Jul 11, 2018
23
0
1
33
All of a sudden i can not add any thing via GUI.

All node but one:
Code:
pveversion:
pve-manager/5.3-9/ba817b29 (running kernel: 4.15.18-11-pve)
The other is:
Code:
pveversion:
pve-manager/5.3-9/ba817b29 (running kernel: 4.15.17-1-pve)
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
522
40
28
Where exactly does this happen? And what are you trying to add?
 

p.lakis

New Member
Jul 11, 2018
23
0
1
33
Anything via GUI, Hardware / Options / Cloud Init - CI PASSWORD

I can add via Shell no issues, eg.
Code:
qm set 9000 --ide2 local-lvm:cloudinit
But if i try to add a Cloud-Init drive via GUI i get the above
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
522
40
28
Please post the complete output of 'pveversion -v', 'apt update' and 'apt full-upgrade'
 

p.lakis

New Member
Jul 11, 2018
23
0
1
33
pveversion -v
Code:
proxmox-ve: 5.3-1 (running kernel: 4.15.18-11-pve)
pve-manager: 5.3-9 (running version: 5.3-9/ba817b29)
pve-kernel-4.15: 5.3-2
pve-kernel-4.15.18-11-pve: 4.15.18-33
pve-kernel-4.15.17-1-pve: 4.15.17-9
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-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-46
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-38
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-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-34
pve-docs: 5.3-2
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-46
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1

apt update
Code:
Hit:1 http://security.debian.org stretch/updates InRelease                                                               
Ign:2 http://ftp.debian.org/debian stretch InRelease                                                                     
Hit:3 http://ftp.debian.org/debian stretch Release           
Get:5 http://download.proxmox.com/debian/pve stretch InRelease [3,052 B]
Get:6 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 Packages [391 kB]
Fetched 394 kB in 4s (90.1 kB/s)   
Reading package lists... Done
Building dependency tree       
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
apt full-upgrade
Code:
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libpve-common-perl pve-docs pve-manager pve-qemu-kvm
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 20.3 MB of archives.
After this operation, 37.9 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 libpve-common-perl all 5.0-47 [94.6 kB]
Get:2 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 pve-docs all 5.3-3 [7,811 kB]
Get:3 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 pve-manager amd64 5.3-11 [1,939 kB]
Get:4 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 pve-qemu-kvm amd64 2.12.1-2 [10.5 MB]
Fetched 20.3 MB in 5s (3,907 kB/s)       
Reading changelogs... Done
(Reading database ... 46804 files and directories currently installed.)
Preparing to unpack .../libpve-common-perl_5.0-47_all.deb ...
Unpacking libpve-common-perl (5.0-47) over (5.0-46) ...
Preparing to unpack .../pve-docs_5.3-3_all.deb ...
Unpacking pve-docs (5.3-3) over (5.3-2) ...
Preparing to unpack .../pve-manager_5.3-11_amd64.deb ...
Unpacking pve-manager (5.3-11) over (5.3-9) ...
Preparing to unpack .../pve-qemu-kvm_2.12.1-2_amd64.deb ...
Unpacking pve-qemu-kvm (2.12.1-2) over (2.12.1-1) ...
Setting up libpve-common-perl (5.0-47) ...
Setting up pve-qemu-kvm (2.12.1-2) ...
Setting up pve-docs (5.3-3) ...
Processing triggers for pve-ha-manager (2.0-6) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up pve-manager (5.3-11) ...
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
522
40
28
Package versions are looking good. Do you have any extensions active in your browser? Clear the cache and try it again if possible.
 

p.lakis

New Member
Jul 11, 2018
23
0
1
33
Happening across multiple browsers in private and cleared cache scenarios.
 

p.lakis

New Member
Jul 11, 2018
23
0
1
33
Il just add.
I can add to one of the VMs in list but multiple are issuing the error, Its strange. Could a template restore cause this from another node??
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
522
40
28
Please post the config of a problematic VM. (cat /etc/pve/qemu-server/<vmid>.conf)
 

p.lakis

New Member
Jul 11, 2018
23
0
1
33
Here is one of many:

Code:
agent: 1
bios: ovmf
bootdisk: scsi0
cipassword: $5$YSXsMHgh$tSVGPAwOse4i/Dg1kT/dkXbne0pGlsl7jpXuxgL9V3.
ciuser: philliplakis
cores: 4
cpu: host
efidisk0: vmpool:base-660-disk-0/vm-105-disk-0,size=128K
ide2: vmpool:vm-105-cloudinit,media=cdrom,size=5M
ipconfig0: ip=19.0.6.123/24,gw=19.0.6.1
machine: q35,max-ram-below-4g=1G
memory: 12288
name: testhostname
net0: virtio=5E:D4:C5:6E:0A:6C,bridge=vmbr1
numa: 1
ostype: l26
scsi0: vmpool:base-660-disk-1/vm-105-disk-1,size=200G
scsihw: virtio-scsi-pci
smbios1: uuid=b7aa89fd-4ee6-4ab1-9f19-fc5c3c3d9060
sockets: 2
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
522
40
28
The ',max-ram-below-4g=1G' leads to the result verification failed error. You'll have to delete it from the config.
 

p.lakis

New Member
Jul 11, 2018
23
0
1
33
Indeed it does, Although i need that there when passing through GPUs.

This is a new error that wasnt there on 5.2
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
522
40
28
If you need it add it to the 'args'.
 

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
4,630
438
103
32
Vienna
Indeed it does, Although i need that there when passing through GPUs.

This is a new error that wasnt there on 5.2
this config entry did not work since at least pve 4.2, which means that you actually did not need it if it worked

sorry, what i wrote is wrong (we did add it to the commandline)

but now we enforce our schema on the webinterface

so if you want to set this, you have to do it like dlimbeck said and
add '-machine 'type=q35,max-ram-below-4g=1G' to 'args' with qm set
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!