This bug was fixed in the package qemu - 2.0.0+dfsg-2ubuntu1.5
---
qemu (2.0.0+dfsg-2ubuntu1.5) trusty-proposed; urgency=medium
* move reload of kvm_intel qemu-system-x86.postinst. (LP: #1324174)
qemu (2.0.0+dfsg-2ubuntu1.4) trusty-proposed; urgency=medium
* reload kvm_intel
Hello Serge, or anyone else affected,
Accepted qemu into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks, the new version fixed the bug.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1324174
Title:
qemu should
No need to wait. Just upload the new one.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1324174
Title:
qemu should attempt to re-load kvm_intel to enable nesting at first
install
Sadly this fix isn't quite right. The reason is that the modprobe
file is qemu-system-x86.modprobe, but the postinst doing the reload
of kvm_intel is qemu-system-common.postinst.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in
I've 'fixed' the fix in utopic, so can post a new fix to trusty once
2.0.0+dfsg-2ubuntu1.4 is kicked out of the archive.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Hello Serge, or anyone else affected,
Accepted qemu into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- Otherwise user may be confused as to why nesting is not enabled until a
+ Otherwise user may be confused as to why nesting is not enabled until a
reboot.
+
+ SRU Justification:
+ 1. Impact: Users who install a new intel-baesd machine and immediately start
+ a VM will
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Trusty)
Status: New = Confirmed
** Changed in: qemu (Ubuntu Trusty)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package qemu - 2.1+dfsg-2ubuntu2
---
qemu (2.1+dfsg-2ubuntu2) utopic; urgency=medium
* reload kvm_intel if needed to set the nested=Y flag (LP: #1324174)
-- Serge Hallyn serge.hal...@ubuntu.com Mon, 11 Aug 2014 12:58:50 -0500
** Changed in: qemu
Perhaps the best way to achieve this would be to rmmod kvm_intel || true
in qemu-system-x86.preinst ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1324174
Title:
qemu should attempt
11 matches
Mail list logo
