** Changed in: nova (Ubuntu Zesty)
Status: Triaged => In Progress
** Changed in: nova (Ubuntu Zesty)
Assignee: (unassigned) => James Page (james-page)
** Description changed:
+ [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://pastebin.canonical.com/190574/
host-model:
https://pastebin.canonical.com/190578/
host-passthrough
https://pastebin.canonical.com/190579/
-
- @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.
+ @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/AAVMF/AAVMF_VARS.fd
/var/lib/libvirt/qemu/nvram/instance-00000010_VARS.fd
sudo chown libvirt-qemu:kvm
/var/lib/libvirt/qemu/nvram/instance-00000010_VARS.fd
#2 Replace openstack disks with something local that boots
wget
https://cloud-images.ubuntu.com/zesty/current/zesty-server-cloudimg-arm64.img
<disk type='file' device='disk'>
- <driver name='qemu' type='raw'/>
- <source file='/home/ubuntu/zesty-server-cloudimg-arm64.img'/>
- <target dev='hdc' bus='virtio'/>
- <address type='virtio-mmio'/>
+ <driver name='qemu' type='raw'/>
+ <source file='/home/ubuntu/zesty-server-cloudimg-arm64.img'/>
+ <target dev='hdc' bus='virtio'/>
+ <address type='virtio-mmio'/>
</disk>
#3 since we don't have the OS created net, replace with the default network
<interface type='network'>
- <mac address='52:54:00:af:8f:2f'/>
- <source network='default'/>
- <model type='virtio'/>
+ <mac address='52:54:00:af:8f:2f'/>
+ <source network='default'/>
+ <model type='virtio'/>
</interface>
#4 Create the logdir that nova specified in the "real" case
sudo mkdir /var/lib/nova/instances/5f488b37-8906-4006-b736-70860856f290/
sudo chown nova:nova
/var/lib/nova/instances/5f488b37-8906-4006-b736-70860856f290/
-
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697610
Title:
aarch64: logfile not supported in this QEMU binary
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1697610/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
