[qm] unable to parse value of 'name' - value does not look like a valid DNS name

[_Lars_]

After the last update most of the names of my kvm guests in the web interface are gone.
They are just named "(VM 101)" etc. The only properly labeled VMs are those w/o
underscores in their names. A 'qm list' shows:

vm 103 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 106 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 101 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 102 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 100 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 105 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 107 - unable to parse value of 'name' - value does not look like a valid DNS name

Before the update (pve-manager/2.0/af81df02) 'qm' had no problem with names like
"WXP32_test001". Did I miss something?

Thanks
Lars

 

[udo]

After the last update most of the names of my kvm guests in the web interface are gone.
They are just named "(VM 101)" etc. The only properly labeled VMs are those w/o
underscores in their names. A 'qm list' shows:

vm 103 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 106 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 101 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 102 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 100 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 105 - unable to parse value of 'name' - value does not look like a valid DNS name
vm 107 - unable to parse value of 'name' - value does not look like a valid DNS name

Before the update (pve-manager/2.0/af81df02) 'qm' had no problem with names like
"WXP32_test001". Did I miss something?

Thanks
Lars

Hi Lars,
the error is right. The underscore isn't an valid part of an dns-name. So if you rename your VM to WXP32-test001 it schould work properly.

Udo

 

[dietmar]

We changed that and now only allow DNS like names. I suuggest you simply change the names of those VMs.

 

[_Lars_]

May I ask for the purpose? I use these labels to get a quick summary over all guests.
Mostly in this manner "OSTYPE_HOSTDESCR". I think changing
"LNX26_TestSrv_ORACLE" to "lnx26-testsrv-oracle" isn't really clear. Also, a host's
name may change without the need to change its label.
KVM is using the '-name' parameter also just as a label. Are hostname restrictions for
labels really necessary?

 

[dietmar]

Are hostname restrictions for labels really necessary?

We changed that so that we can use that in future for DNS/DHCP (for routed network setups).

Anyway, I don't really see why LNX26_TestSrv_ORACLE is better than LNX26-TestSrv-ORACLE?