On Wed, Aug 01, 2018 at 10:30:14AM -0400, Jason Andryuk wrote: > On Mon, Jul 30, 2018 at 11:56 PM, Marek Marczykowski-Górecki > <marma...@invisiblethingslab.com> wrote: > > The forced vkb device is meant for better performance of qemu access > > (at least according to ebbd2561b4cefb299f0f68a88b2788504223de18 "libxl: > > Add a vkbd frontend/backend pair for HVM guests"), which isn't used if > > there is no configured channel to actually access that keyboard. > > > > One can still add vkb device manually if needed. > > > > This is continuation of b053f0c4c9e533f3d97837cf897eb920b8355ed3 "libxl: do > > not start dom0 qemu for stubdomain when not needed". > > Prior to this change, was a dom0 qemu started for these entries?
AFAIR not for this device alone (unless some other condition in libxl__need_xenpv_qemu triggers it). But when it is created but backend not launched, it cause timeout on frontend side. > Reviewed-by: Jason Andryuk <jandr...@gmail.com> -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
signature.asc
Description: PGP signature
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
