Hi There,
I have noticed that whether a VM is started with fixed memory, or dynamic memory it starts with the same CLI string.
e.g.
VM with 16GB fixed memory:
VM with 16GB/8GB dynamic
I would have thought the "fixed" memory configuration VM would not have a balloon device, e.g. would be started with "-balloon none"
Have I found a bug? Or have I misunderstood how this is meant to work ?
I have noticed that whether a VM is started with fixed memory, or dynamic memory it starts with the same CLI string.
e.g.
VM with 16GB fixed memory:
Code:
root 6237 1 4 14:21 ? 00:20:26 /usr/bin/kvm -id 247 -chardev socket,id=qmp,path=/var/run/qemu-server/247.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/247.vnc,x509,password -pidfile /var/run/qemu-server/247.pid -daemonize -name Test-win7 -smp 2,sockets=2,cores=1,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga std -no-hpet -cpu kvm64,hv_spinlocks=0xffff,hv_relaxed,+lahf_lm,+x2apic,+sep -m 16384 -k en-us -device piix3-usb-uhci
,id=uhci,bus=pci.0,addr=0x1.0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:5b78872efe6c -device virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive file=rbd:tier2-rbd/vm-247-disk-1:mon_hos
t=10.233.202.11\:6789\;10.233.202.12\:6789\;10.233.202.13\:6789:id=admin:auth_supported=cephx:keyring=/etc/pve/priv/ceph/tier2-rbd.keyring,if=none,id=drive-scsi0,cache=writeback,discard=on,aio=native,detect-zeroes=unmap -device scsi-hd,bus=scsihw0.0,ch
annel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100 -drive if=none,id=drive-ide3,media=cdrom,aio=native -device ide-cd,bus=ide.1,unit=1,drive=drive-ide3,id=ide3,bootindex=200 -drive if=none,id=drive-ide2,media=cdrom,aio=native -device ide-
cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=201 -netdev type=tap,id=net0,ifname=tap247i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=52:F7:12:E9:54:7E,netdev=net0,
bus=pci.0,addr=0x12,id=net0,bootindex=300 -rtc driftfix=slew,base=localtime -global kvm-pit.lost_tick_policy=discardVM with 16GB/8GB dynamic
Code:
root 16584 1 71 21:35 ? 00:00:07 /usr/bin/kvm -id 247 -chardev socket,id=qmp,path=/var/run/qemu-server/247.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/247.vnc,x509,password -pidfile /var/run/qemu-server/247.pid -daemonize -name Test-win7 -smp 2,sockets=2,cores=1,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga std -no-hpet -cpu kvm64,hv_spinlocks=0xffff,hv_relaxed,+lahf_lm,+x2apic,+sep -m 16384 -k en-us -device piix3-usb-uhci
,id=uhci,bus=pci.0,addr=0x1.0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:5b78872efe6c -device virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive file=rbd:tier2-rbd/vm-247-disk-1:mon_hos
t=10.233.202.11\:6789\;10.233.202.12\:6789\;10.233.202.13\:6789:id=admin:auth_supported=cephx:keyring=/etc/pve/priv/ceph/tier2-rbd.keyring,if=none,id=drive-scsi0,cache=writeback,discard=on,aio=native,detect-zeroes=unmap -device scsi-hd,bus=scsihw0.0,ch
annel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100 -drive if=none,id=drive-ide3,media=cdrom,aio=native -device ide-cd,bus=ide.1,unit=1,drive=drive-ide3,id=ide3,bootindex=200 -drive if=none,id=drive-ide2,media=cdrom,aio=native -device ide-
cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=201 -netdev type=tap,id=net0,ifname=tap247i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=52:F7:12:E9:54:7E,netdev=net0,
bus=pci.0,addr=0x12,id=net0,bootindex=300 -rtc driftfix=slew,base=localtime -global kvm-pit.lost_tick_policy=discardI would have thought the "fixed" memory configuration VM would not have a balloon device, e.g. would be started with "-balloon none"
Have I found a bug? Or have I misunderstood how this is meant to work ?