aarch64: logfile not supported in this QEMU binary
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Medium
|
Unassigned | ||
Ocata |
Fix Released
|
Medium
|
Unassigned | ||
Pike |
Fix Released
|
Medium
|
Unassigned | ||
libvirt (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Zesty |
Fix Released
|
Medium
|
Unassigned | ||
Artful |
Fix Released
|
Medium
|
Unassigned | ||
nova (Ubuntu) |
Fix Released
|
Medium
|
James Page | ||
Zesty |
Fix Released
|
Medium
|
James Page | ||
Artful |
Fix Released
|
Medium
|
James Page |
Bug Description
[Impact]
arm64 based openstack clouds can't boot instances with OpenStack Ocata or later.
[Test Case]
Deploy OpenStack
Boot instance
Instance fails to boot with "logfile not supported in the QEMU binary" error message
[Regression Potential]
Low; the proposed patch reverts to using the pre-ocata code path, skipping
use of virtlogd for arm based architectures.
[Original Bug Report]
This is a spin-off to bug 1673467 as it is a different issue:
Got this today via Mail, linking here:
none:
https:/
host-model:
https:/
host-passthrough
https:/
@admcleod - While my system is preparing to test this I think the logs you added are already kind of proving that the issue this bug was reported about is kind of solved.
In regard to your logs - the related error:
none:
-> Passes the initialization but then breaks on logfile
host-model:
-> Fails due to host-model being broken
host-passthrough
-> Passes the initialization but then breaks on logfile
That said it seems to me the config overall is broken in regard to the logfile in some sort.
When host-model is selected it fails earlier on init (this is the actual bug that was discussed in comments #1-#20), if called without host-model the init goes on.
But then in general this seems to have issues around the logfile in some way.
"libvirtError: unsupported configuration: logfile not supported in this QEMU binary"
To reproduce I took the recommende "host-passthrough" case and made the following modifications to run without a real openstack around it:
#0 packages that drag in all dependencies
sudo apt install uvtool-libvirt nova-compute
#1 create nvram vars from template to match XML
sudo cp /usr/share/
sudo chown libvirt-qemu:kvm /var/lib/
#2 Replace openstack disks with something local that boots
wget https:/
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/
<target dev='hdc' bus='virtio'/>
<address type='virtio-
</disk>
#3 since we don't have the OS created net, replace with the default network
<interface type='network'>
<mac address=
<source network='default'/>
<model type='virtio'/>
</interface>
#4 Create the logdir that nova specified in the "real" case
sudo mkdir /var/lib/
sudo chown nova:nova /var/lib/
With the above I was able to get your new bug around "logfile not supported in this QEMU binary".
Ok, that certainly is a different bug - I can switch between host-model (old issue) and host-passthrough and be good.
The logfile issue is a different one, so we track it in a new bug = Here.
tags: | added: arm64 uosci |
Changed in nova (Ubuntu Zesty): | |
status: | Triaged → In Progress |
assignee: | nobody → James Page (james-page) |
description: | updated |
tags: | added: libvirt-3.6 |
tags: |
added: verification-zesty-done removed: verification-needed-zesty |
Query Qemu the way Libvirt does to detect QEMU_CAPS_ CHARDEV_ LOGFILE:
virsh qemu-monitor- command instance-00000010 --pretty '{ "execute": "query- command- line-options" }'
Has:
"parameters": [
[...]
{
"name": "logfile",
"type": "string"
},
],
"option": "chardev"
},
So the chardev should have the logfile option as it always had IMHO.