"virtual-guest" folder not found

[ubk77]

Hello to everyone!

I can't find "virtual-guest" folder in /etc/pve.

Is it normal not to find this folder if I have never used a custom cpu?

Thanks.

 

[t.lamprecht]

Hi!

Is it normal not to find this folder if I have never used a custom cpu?

Yes that's normal, that folder isn't auto-created as it's currently only used for the slightly niche feature of custom CPUs.

Just create it. For example. as root run: mkdir /etc/pve/virtual-guest

 

[ubk77]

Thank you.

I created cpu-models.conf with this content:

cpu-model: avx
    flags +avx;+avx2
    phys-bits host
    hidden 0
    hv-vendor-id proxmox
    reported-model kvm64

Then in VM config file:

cpu: custom-avx

But it fails when I enter

qm config [VM_id]

with this error

unable to parse value of 'cpu' - format error

I'm stuck!

What I'm doing wrong?

Thanks.

 

[fiona]

Hi,
what's the output of pveversion -v and cat /etc/pve/qemu-server/<ID>.conf?

 

[t.lamprecht]

What I'm doing wrong?

It needs to be

cpu: cputype=custom-avx

 

[fiona]

It needs to be

cpu: cputype=custom-avx

cputype is the default key, so it should also work without specifying that

 

[ubk77]

Hi,
what's the output of pveversion -v and cat /etc/pve/qemu-server/<ID>.conf?

pveversion -v output

proxmox-ve: 5.4-2 (running kernel: 4.15.18-21-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-9
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.13.13-2-pve: 4.13.13-33
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-55
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-7
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

cat /etc/pve/qemu-server/<ID>.conf

bootdisk: ide0
cores: 4
cpu: cputype=custom-avx
ide0: local-lvm:vm-105-disk-1,size=100G
ide2: local:,media=cdrom,size=3426360K
memory: 16000
name: VM105
net0: rtl8139=mac,bridge=vmbr0
numa: 0
onboot: 1
ostype: win8
scsihw: virtio-scsi-pci
smbios1: uuid=uuid
sockets: 2

qm config ID output

unable to parse value of 'cpu' - format error
cputype: value 'custom-avx' does not have a value in the enumeration '486, athlon, Broadwell, Broadwell-IBRS, Broadwell-noTSX, Broadwell-noTSX-IBRS, Conroe, core2duo, coreduo, EPYC, EPYC-IBPB, Haswell, Haswell-IBRS, Haswell-noTSX, Haswell-noTSX-IBRS, host, IvyBridge, IvyBridge-IBRS, kvm32, kvm64, max, Nehalem, Nehalem-IBRS, Opteron_G1, Opteron_G2, Opteron_G3, Opteron_G4, Opteron_G5, Penryn, pentium, pentium2, pentium3, phenom, qemu32, qemu64, SandyBridge, SandyBridge-IBRS, Skylake-Client, Skylake-Client-IBRS, Skylake-Server, Skylake-Server-IBRS, Westmere, Westmere-IBRS'

Thanks.

 

[t.lamprecht]

proxmox-ve: 5.4-2 (running kernel: 4.15.18-21-pve)

Ok, this is a quite ancient version, released over three and a half years and EOL since over two yeas.
https://pve.proxmox.com/pve-docs/chapter-pve-faq.html#faq-support-table

It just lacks support for custom CPU's due being so old.
I'd heavily recommend upgrading, first to 6.x and then to the current stable and only supported 7.x release.
https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

 

[ubk77]

My bad! I'm so sorry!

Thank you to all.

 

[ubk77]

Just last question:

with proxmox 5.4 the "flags" option in the VM config file is available?

Thanks.

 

[fiona]

Just last question:

with proxmox 5.4 the "flags" option in the VM config file is available?

Thanks.

You mean flags as part of the cpu setting? From a very quick look in the log, it seems to be (although with fewer possible flags than nowadays). Easy way to see such things is trying it out