Strange vm configuration

Melanxolik

Well-Known Member
Dec 18, 2013
86
0
46
I have a lot of customers virtual servers. Our storage system based on ceph rbd pool.

Now I see strange record in configuration:


Code:
qemu-server/352.conf
bootdisk: virtio0
cores: 2
cpu: kvm64
cpuunits: 1000
ide2: none,media=cdrom
memory: 3000
name: name
net0: virtio=72::DC:79:3A,bridge=vmbr8,rate=48
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=776fc5f8-f3d8-4f58-9365-801bbb313244
sockets: 1
vga: std
virtio0: file=ST01:vm-352-disk-1,cache=writeback,iops_rd=400,iops_wr=300,mbps_rd=60,mbps_wr=50,size=35000M

other configuration, looks:
Code:
cat ./cluster-2-6/qemu-server/7005.conf
bootdisk: virtio0
cores: 1
memory: 512
name: tetest
net0: e1000=16:EE:63:2C:65:A7,bridge=vmbr159
numa: 0
ostype: l26
smbios1: uuid=4027e193-5f90-4718-a680-88364b19ad1b
sockets: 1
virtio0: ST01:vm-7005-disk-1,size=1G

This too strings different:
virtio0: file=ST01:vm-352-disk-1,cache=writeback,iops_rd=400,iops_wr=300,mbps_rd=60,mbps_wr=50,size=35000M

virtio0: ST01:vm-7005-disk-1,size=1G

In first case we see file= befor storage name, in second case we don't have file=
 
the file= is the default key for the volume and was accidentally included in a previous version of qemu-server - if you upgrade the nodes and do any operation that writes the config file, it will go away. it is just cosmetic though ;) the other differences are options for read/write throttling
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!