From the log:
<type arch='aarch64' machine='virt-2.8'>hvm</type>
This is still running on the older qemu.
So the former assumption isn't checked yet.
It is assumed that 2.10 releases today [1].
I addressed some feedback of corecb in regard to your builds in the -rc4 I prepared already.
I'd have thought you have the -rc3 I made available a while ago in UCA already.
So we have to re-test with that once available in UCA as well.
to verify that it should work I took your XML and
- removed the disks I don't have (added a local img file as replacement)
- replaced the bridge I don't have with the default bridge (still a virtio net device)
All device init would still pass on this so I would trigger your bug, but it works just fine.
See xml [2] which gets live expanded to [3].
For now still assuming it is fixed in qemu 2.10 - please get back when it is tested on that in pike.
From the log: 'virt-2. 8'>hvm< /type>
<type arch='aarch64' machine=
This is still running on the older qemu.
So the former assumption isn't checked yet.
It is assumed that 2.10 releases today [1].
I addressed some feedback of corecb in regard to your builds in the -rc4 I prepared already.
I'd have thought you have the -rc3 I made available a while ago in UCA already.
So we have to re-test with that once available in UCA as well.
to verify that it should work I took your XML and
- removed the disks I don't have (added a local img file as replacement)
- replaced the bridge I don't have with the default bridge (still a virtio net device)
All device init would still pass on this so I would trigger your bug, but it works just fine.
See xml [2] which gets live expanded to [3].
For now still assuming it is fixed in qemu 2.10 - please get back when it is tested on that in pike.
[1]: https:/ /wiki.qemu. org/index. php/Planning/ 2.10 paste.ubuntu. com/25423471/ paste.ubuntu. com/25423472/
[2]: http://
[3]: http://