[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v3 2/6] libxl: do not add a vkb backend to hvm guests
On Wed, Jun 10, 2015 at 11:09:50AM +0100, Stefano Stabellini wrote: > When QEMU restricts its xenstore connection, it cannot provide PV > backends. A separate QEMU instance is required to provide PV backends in > userspace, such as qdisk. With two separate instances, it is not > possible to take advantage of vkb for mouse and keyboard, as the QEMU > that emulates the graphic card (the device model), would be separate > from the QEMU running the vkb backend (PV QEMU). > The question is that how would this affect the non-split setup. But do I understand correctly we are moving towards a split setup regardlessly whether QEMU supports xsrestrict or not? I.e. there is no non-split setup in the future. Wei. > Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> > --- > tools/libxl/libxl_create.c | 5 ----- > 1 file changed, 5 deletions(-) > > diff --git a/tools/libxl/libxl_create.c b/tools/libxl/libxl_create.c > index f0da7dc..a74b340 100644 > --- a/tools/libxl/libxl_create.c > +++ b/tools/libxl/libxl_create.c > @@ -1275,17 +1275,12 @@ static void domcreate_launch_dm(libxl__egc *egc, > libxl__multidev *multidev, > { > libxl__device_console console; > libxl__device device; > - libxl_device_vkb vkb; > > init_console_info(gc, &console, 0); > console.backend_domid = state->console_domid; > libxl__device_console_add(gc, domid, &console, state, &device); > libxl__device_console_dispose(&console); > > - libxl_device_vkb_init(&vkb); > - libxl__device_vkb_add(gc, domid, &vkb); > - libxl_device_vkb_dispose(&vkb); > - > dcs->dmss.dm.guest_domid = domid; > if (libxl_defbool_val(d_config->b_info.device_model_stubdomain)) > libxl__spawn_stub_dm(egc, &dcs->dmss); > -- > 1.7.10.4 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |