Rafael, I posted results of testing aarch64 xml example in bug 1832394.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630
Title:
aarch64: MSI is not supported by interrupt controller
To manage
Fully functional aarch64 (arm64) kvm xml definition example:
https://pastebin.ubuntu.com/p/jvN6SYHbtD/
Fully functional aarch32 (armhf) kvm xml definition example:
https://pastebin.ubuntu.com/p/nTmSQRf2CQ/
Both are running in an ARMv8 with KVM support for Aarch64 and Aarch32.
--
You received
> The most common related mistake is the lac of
This is what I found too, but it's seems like in my case something else
cause this error. Below is attempt to run
https://paste.ubuntu.com/25423471/ from Comment 9 which definitely have
:
~$ virsh start instance-0007
error: Failed to start dom
@RussianNeuromancer for aarch64 you need to tweak quite some things to work.
Openstack does so by default, but I doubt that virt-manager comes up with a
great default config.
The most common related mistake is the lac of
I'll reset this bug to the incomplete state that it was (as it was gone w
Getting same issue with both of libvirt 4.0.0/qemu 2.11 (18.04.2) and
libvirt 5.0.0/qemu 3.1 (19.04) on attempt to run AArch64 guest on
AArch64 host. Virtual machine setting is default generated by virt-
manager wizard, so there is no big changes to default devices, I just
filled iso, hdd and netwo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630
Title:
aa
No - with the hwe-kernel (4.10.0-42-generic from 4.10.0-42.46~16.04.1),
this doesn't happen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630
Title:
aarch64: MSI is not supported by interrupt c
Is this reproducible w/ the hwe kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630
Title:
aarch64: MSI is not supported by interrupt controller
To manage notifications about this bug go
I'm running qemu-system-arm 2.10+dfsg-0ubuntu3.1~cloud0 and still seeing
this issue.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => New
** Tags added: cdoqa-blocker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
@admcleod : Any updates on Pike testing with qemu2.10 mentioned in comm
#9 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630
Title:
aarch64: MSI is not supported by interrupt controller
To ma
>From the log:
hvm
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 w
Re the state of qemu ver, I've asked someone else to comment on that.
XML from before was:
==> nova/nova-compute.log <==
2017-08-28 13:15:46.413 23162 ERROR nova.virt.libvirt.guest
[req-e2fc9a90-7433-479c-9d96-c2818641fe45 b147293e0a7941899301c59b48068e51
18b9fc2bdb6b45a0a682d79d9130a975 - defau
Well the status of today should have qemu 2.10-rc3 right?
Is that in xenial-pike/proposed already?
If so the assumption of james that a fix was in qemu 2.9 was wrong and
we need a new theory.
Is the generated XML still the same as in comment #3 - could you please
on xenial-pike/proposed generate
Can confirm this bug exists as of today, with xenial-pike/proposed
Linux juju-25b69e-14 4.4.0-79-generic #100-Ubuntu SMP Wed May 17 19:58:30 UTC
2017 aarch64 aarch64 aarch64 GNU/Linux
libvirt0: 3.6.0
qemu: 2.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This does not match James finding of missing the gic version in the generated
XML.
Also the error is to not start the guest at all.
Yet still on the changed MSI interrupt behaviour the following change might be
related:
commit b4b9862b536f41fcdf6ad193a306a852c5b5b71a
Author: Michael S. Tsirkin
** Tags added: virt-fixed-by-2.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630
Title:
aarch64: MSI is not supported by interrupt controller
To manage notifications about this bug go to:
ht
I meet the same problem in AArch64, with latest Nova and qemu 2.8.1,
libvirt 3.0.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630
Title:
aarch64: MSI is not supported by interrupt controller
** Tags added: arm64 uosci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630
Title:
aarch64: MSI is not supported by interrupt controller
To manage notifications about this bug go to:
https://b
https://bugzilla.redhat.com/show_bug.cgi?id=1414081
** Bug watch added: Red Hat Bugzilla #1414081
https://bugzilla.redhat.com/show_bug.cgi?id=1414081
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
The attached xml is that returned from libvirt - the nova generated xml
does not include a gic version:
42c06630-1fe3-4fd0-8cec-549f809e0c46
instance-000d
1048576
1
http://openstack.org/xmlns/libvirt/nova/1.0";>
openstack-on-lxd-new-libvirt
2017-07-26 12:58:2
Attaching XML generated by OpenStack for the failed instance launch.
** Attachment added: "libvirt.xml"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1706630/+attachment/4921636/+files/libvirt.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
21 matches
Mail list logo
