PC system firmware (pflash) must be a multiple of 0x1000

ONE FOTON

Member
Jun 30, 2017
35
0
11
40
Argentina, Cordoba
Hello
I had a vm win 10 running without problems!
but since yesterday I stop working and I throw this error
kvm: -drive if=pflash,unit=1,format=raw,id=drive-efidisk0,file=/var/lib/vz/images/107/vm-107-disk-2.qcow2: PC system firmware (pflash) must be a multiple of 0x1000
TASK ERROR: start failed: command '/usr/bin/kvm -id 107 -chardev 'socket,id=qmp,path=/var/run/qemu-server/107.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/107.pid -daemonize -smbios 'type=1,uuid=3bced6bc-f1a0-4454-a7a2-18b314505727' -drive 'if=pflash,unit=0,format=raw,readonly,file=/usr/share/kvm/OVMF_CODE-pure-efi.fd' -drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,file=/var/lib/vz/images/107/vm-107-disk-2.qcow2' -name WIN10PRO4 -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga none -nographic -no-hpet -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=proxmox,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,kvm=off' -m 6145 -k es -readconfig /usr/share/qemu-server/pve-q35.cfg -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10' -device 'vfio-pci,host=03:00.1,id=hostpci1,bus=pci.0,addr=0x11' -device 'vfio-pci,host=04:00.0,id=hostpci2,bus=pci.0,addr=0x1b' -device 'vfio-pci,host=04:00.1,id=hostpci3,bus=pci.0,addr=0x1c' -chardev 'socket,path=/var/run/qemu-server/107.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:d99d8bd2022' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/var/lib/vz/images/107/vm-107-disk-1.qcow2,if=none,id=drive-scsi0,discard=on,format=qcow2,cache=none,aio=native,detect-zeroes=unmap' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap107i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=AA:52:25:9A:89:87,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=q35' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1

someone will have some idea of how to solve it?
look for this error in the forum and I found nothing
 
ok I do not know how to explain this!
but for some reason proxmox distorted the start command of the vm
As I explained, the error he showed me was the following:
kvm: -drive if=pflash,unit=1,format=raw,id=drive-efidisk0,file=/var/lib/vz/images/107/vm-107-disk-2.qcow2: PC system firmware (pflash) must be a multiple of 0x1000

I hope someone from proxmox gives me a hand with this, for some reason proxmox, kvm or qemu change the disc format uefi.
the format of the original disk is .qcow2 and as it is shown in the error it changes the format to .raw 0_0. why?
ok now the machine is working again (see attached image)
to start what I did was the following:
1- copy the command path
2-modify the format of .raw to .qcow2
3- and enter

with that, the machine started and went to work.
I still have a lot of tests to do, but I would really appreciate it if some friendly person from Proxmox would give me a hand in a less rudimentary solution to this problem.:);)

please! please! please!
 

Attachments

  • Captura de pantalla de 2017-12-26 14-20-23.png
    Captura de pantalla de 2017-12-26 14-20-23.png
    131.2 KB · Views: 4
We seem to indeed be detecting the wrong format for efi disks currently. Will be fixed soon.
In the mean time, you should be able to fix this by appending `,format=qcow2` to the config line starting with `efidisk0:` to solve this.
Eg.
Code:
# /etc/pve/qemu-server/107.conf
(...)
efidisk0: local:107/vm-107-disk-2.qcow2,size=128K,format=qcow2
(...)
 
thanks for the support!
What I did was:
in the host> hardware> select hard disk efi> move disk
target storage: where you want to save it
format: raw disk

with that it was solved! °_°
 
Thanks for that information. Problem exists. So if i have Snapshots, and there are a lot... so that i can rollback... must i change on every efi-line this format? But this is only for existing VM's, not for new one?
 
Should be enough to use qemu-server>=5.0-19