Thanks Serge!
--
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/1409308
Title:
Request: Please update to QEMU 2.2 in Vivid
To manage notifications about this bug go to:
https://bugs.lau
Thanks for the reply, Serge. No hurry. I'm currently using QEMU 2.2
from ppa:jacob/virtualisation on Utopic. It seems to be working well,
but I'd prefer to install it from the official repository when I upgrade
to Vivid. Thanks much!
--
You received this bug notification because you are a mem
Public bug reported:
If possible to do so, please update to QEMU 2.2 in Vivid before the
feature freeze. Thanks!
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed t
Serge, thanks so much for your hard work to get qemu 2.0 into the
repository. Much appreciated!
--
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/1284793
Title:
[FFE] Merge qemu 2.0
To
My previously reported issue with BSODs seems to be fixed in
2.0~git-20140327.3768d50-0ubuntu1.
--
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/1284793
Title:
[FFE] Merge qemu 2.0
To m
Yep, that seems to be it. I look forward to the patch.
--
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/1284793
Title:
[FFE] Merge qemu 2.0
To manage notifications about this bug go t
I attempted to start the VM using the commands listed in comment #9
above (with -M q35), which was working great until
2.0~git-20140325.7b770c7-0ubuntu1. I tried substituting -M pc-
i440fx-2.0 for -M q35 (Is that what you had in mind?), but got the
following error: "qemu-system-x86_64: -device
i
VFIO was workng great with the last two (or three) QEMU 2.0 test version
versions prior to 2.0~git-20140325.7b770c7-0ubuntu1. But with
2.0~git-20140325.7b770c7-0ubuntu1, I get a BSOD and an error stating
that "The Bios in this system is not fully ACPI compliant" when
attempting to start my Windows
Hi Serge,
Version 2.0~git-20140307.4c288ac-0ubuntu1 installed from ppa:ubuntu-
virt/candidat seems to be working great with VFIO. Thanks!
Regards,
GizmoChicken
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://b
Thanks Serge. Much appreciated! I'll test it later tonight or early
tomorrow.
By the way, the patch that you mentioned is from Igor Mammedov, who is
at RedHat. Alex Williamson, who is also at RedHat, plays a significant
role in implementing VFIO in qemu and the linux kernel, so he might also
b
Hi Serge,
I downloaded ALL of the test debs at
http://people.canonical.com/~serge/qemu-20140306-1/ and then installed
ALL of them using the "sudo dpkg -i *.deb" command. That's what you had
in mind, right?
Anyway, the good news is that the provided test version of Qemu 2.0.
seems to have fixed
Good news, bad news.
First the good news:
I have a few VMs that run under KVM using Virt-Manager. ALL of those
VMs are running great with Qemu 2.0.
The bad news:
I have one VM that runs under KVM with VGA passththrough using the VFIO
option. That VM, including VGA passthrough, works flawless
12 matches
Mail list logo