Thanks to everyone who contributed to this fix. I confirm that it works
for me in testing with Ussuri and Ubuntu Bionic on vmx-enabled GCP VMs;
with fixed qemu packages coming from cloud-archive:ussuri.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
The fix for the cloud-archive looks to have successfully backported from
the distro changes
** Changed in: cloud-archive
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
This bug was fixed in the package qemu - 1:4.2-3ubuntu6.3
---
qemu (1:4.2-3ubuntu6.3) focal; urgency=medium
* debian/patches/ubuntu/lp-1878973-*: fix assert in qemu-guest-agent that
crashes it on shutdown (LP: #1878973)
* d/p/ubuntu/lp-1882774-*: fix issues with VMX subfeature
All autppkgtest errors resolved and verification done - ready once it is
long enough in proposed without an issue found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882774
Title:
issues with seco
Thank you Matthew!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882774
Title:
issues with secondary VMX execution controls
To manage notifications about this bug go to:
https://bugs.launchpad.net
Also verifying this on Azure Cloud.
I enabled -proposed and installed qemu 4.2-3ubuntu6.3 on a Focal
instance.
$ sudo apt-cache policy qemu-kvm | grep Installed
Installed: 1:4.2-3ubuntu6.3
>From there I executed the following:
$ sudo -s
# apt install qemu-kvm bridge-utils
# BR_NAME="br0"
# BR
Prior to the fix starting a host-model guest on GCE:
ubuntu@nested-vm:~$ virsh start focal
error: Failed to start domain focal
error: internal error: process exited while connecting to monitor:
2020-06-23T09:54:47.062832Z qemu-system-x86_64: warning: host doesn't support
requested feature: MSR(4
I've started to look into the autpkgtest fails, so far all look like
unreliable tests not triggered by the upload. I have re-triggered
accordingly and will investigate in case one stays unresolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hello Christian, or anyone else affected,
Accepted qemu into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu6.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Hi Christian, I have tested the exact same patch on Azure over on bug
1884470 and I can confirm that it fixes the issue. I will be eagerly
awaiting your upload to hit -proposed.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ok, the other SRU is released and the MP reviewed.
Uploaded this one to F-unapproved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882774
Title:
issues with secondary VMX execution controls
To man
Complete in groovy, preparing for SRUs - SRU-Template ready, MPs are up.
@SRU Team - already ahead as hint please release qemu
1:4.2-3ubuntu6.2/1:4.0+dfsg-0ubuntu9.7 of bug 1805256 which is ready,
before accepting this one.
--
You received this bug notification because you are a member of Ubuntu
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/385876
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882774
Title:
issues with secondary VMX e
This bug was fixed in the package qemu - 1:4.2-3ubuntu9
---
qemu (1:4.2-3ubuntu9) groovy; urgency=medium
* debian/patches/ubuntu/lp-1878973-*: fix assert in qemu-guest-agent that
crashes it on shutdown (LP: #1878973)
* d/p/ubuntu/lp-1882774-*: fix issues with VMX subfeatures o
FYI: Uploaded to Groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882774
Title:
issues with secondary VMX execution controls
To manage notifications about this bug go to:
https://bugs.launchpa
FYI I'm waiting for the fix to bug 1878973 to be committed and then plan
to roll both together into groovy.
** Also affects: qemu (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Focal)
Status: New => Triaged
** Changed in: qemu (Ubuntu)
Importance
@Neil - it isn't too easy, but I was able to confirm myself in the
meantime and it works well.
The usual flow is that I bring this fix into the affected Groovy and Focal and
then the cloud-archive would rebase onto those versions.
But I'll add a ubuntu-cloud-archive task.
Maybe they can pre-build
I have tested this with a GCE instance with nested enabled
here the domcapabilities for the type:
Skylake-Client-IBRS
Intel
I set the guest (on Bionic) to use host-model:
Due to that it got on first ex
Christian, would it be easy for you to build this for Bionic as well? I
run tests with GCP instances as the OpenStack hypervisors, and have hit
this bug, so am keen to test your fix.
(http://lists.openstack.org/pipermail/openstack-
discuss/2020-June/015343.html)
--
You received this bug notific
** Description changed:
[Impact]
In qemu 4.2 was a change [1] meant to improve the handling of MSRs vs CPUID.
It was later identified [2] as an issue and fixed.
This has to be backported to Focal to resolve that issue on several platforms.
An example where this occurs is:
- Azure
FYI there is an older build in the PPA, only >=qemu -
1:4.2-3ubuntu6.3~ppa2 will have the proposed fix for this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882774
Title:
issues with second
Test fix started to build in PPA (for Focal):
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4081/
It would be great if one with GCP or Azure instances affected could give
this a try.
** Changed in: qemu (Ubuntu)
Status: New => Triaged
--
You received this bug notification b
22 matches
Mail list logo
