You are not logged in.
Pages: 1
I've been having a little trouble getting QEMU working right for some reason. Every time I try to start the virtual machine, I get this error:
Error starting domain: internal error: qemu unexpectedly closed the monitor: 2019-05-08T06:39:43.100267Z qemu-system-x86_64: system firmware block device pflash0 has invalid size 56832
2019-05-08T06:39:43.100361Z qemu-system-x86_64: info: its size must be a non-zero multiple of 0x1000
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1420, in startup
self._backend.create()
File "/usr/lib/python3.7/site-packages/libvirt.py", line 1080, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: 2019-05-08T06:39:43.100267Z qemu-system-x86_64: system firmware block device pflash0 has invalid size 56832
2019-05-08T06:39:43.100361Z qemu-system-x86_64: info: its size must be a non-zero multiple of 0x1000
I've tried to look around online on how to change the size of pflash0 or get around this somehow but I just haven't had any luck.
Does anyone know what this means and what I should do to get it working? Thanks so much for the help! I really appreciate it!
Offline
Welcome to the arch linux forums BitHappy. Where did this 56832 sized file come from?
ovmf 1:r25737.89910a39dc-1 provides OVMF_CODE.fd 2 MB and OVMF_VARS.fd 32 KB both multiples of 4KB.
Offline
Thanks a lot! Well, I'm trying to get OsX to work and downloaded the OVMF_CODE.fd and OVMF_VARS.fd files from https://github.com/kholia/OSX-KVM . Although now that I'm looking at it, that file is supposed to be 3.5mb haha, so maybe it was a corrupted download somehow?
Yep looks like that was it! Thanks for the help! Never would have realized that the download screwed up haha. Thanks a lot!
Offline
Pages: 1