This repository has been archived by the owner on May 12, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 375
Move to qemu vanilla #1397
Comments
btw, I have already took the task to test qemu 3.1.0 locally and all QA tests seem pretty stable. |
+1
Some items to fix to consider this complete are:
|
@jcvenegas yes for now NEMU relies on 3.1, but there is some ongoing work to rebase NEMU on top of 4.0. |
@jcvenegas et. al. I opened a similar issue and did some metrics measures last month ;-) - over at #1253 |
chavafg
added a commit
to chavafg/runtime-1
that referenced
this issue
Mar 21, 2019
Update qemu version to v3.1.0 Fixes: kata-containers#1397. Signed-off-by: Salvador Fuentes <[email protected]>
@jcvenegas can you have a list of out of tree QEMU patches we carry today? |
Assess the need for porting qemu-lite patches |
Metrics Data from @grahamwhaley |
chavafg
added a commit
to chavafg/runtime-1
that referenced
this issue
Apr 26, 2019
Update qemu version to v4.0.0 Fixes: kata-containers#1397. Signed-off-by: Salvador Fuentes <[email protected]>
chavafg
added a commit
to chavafg/runtime-1
that referenced
this issue
Apr 26, 2019
Update qemu version to v4.0.0 Fixes: kata-containers#1397. Signed-off-by: Salvador Fuentes <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In recent days we have talk about moving our default hypervisor from the 2.11
qemu-lite
to a newer version of the qemu, which could be qemu vanilla 3.1.0 or 4.0.0 (which is still in rc).Opening this issue to discuss further.
The text was updated successfully, but these errors were encountered: