similar to: xen4.2 + qemu-upstream domain rename partial failure (& migration)

Anthony PERARD (3): libxl_qmp: Use GC instead of CTX as parameter for _initialize. Provide dm_vnc() as a in libxl helper. libxl: Set VNC password through QMP tools/libxl/libxl_create.c | 2 +- tools/libxl/libxl_dm.c | 32 ++++++++++++++---------- tools/libxl/libxl_internal.h | 7 ++++- tools/libxl/libxl_qmp.c | 55 ++++++++++++++++++++++++++++++----------- 4 files

Package: xen-utils-common Version: 4.4.1-6 Severity: normal Dear Maintainer, (There appear to be several reports on the BTS with concerns relating to this report. Some unarchiving/merging may be necessary. Reassignment may be needed as well since I'm not sure which package this problem would fall under. Ultimately decided to file with xen-utils-common with 'xl' being the frontend

Hello Xen Users, Been experimenting with upstream-qemu and wanted to try out the OVMF bios option, but I seem to be missing something. Are there additional steps to installing OVMF beyond compiling Xen? I saw notes on patching back in february, but I thought the package was included with Xen 4.2 on release. When I attempt to set it as my bios option, the machine boots then immediately closes.

Hi All, I'm seeing tapdisk processes not being terminated after a HVM vm is shutdown or migrated away. I don't see this problem with linux paravirt domu's, just windows hvm ones. xl.cfg: name = 'nathanwin' memory = 4096 vcpus = 2 disk = [ 'file:/mnt/gtc_disk_p1/nathanwin/drive_c,hda,w' ] vif = [ 'mac=00:16:3D:01:03:E0,bridge=vlan208' ] builder =

This patch provide the code to set the VNC password to QEMU upstream through VNC. The password is still stored in xenstore but will not be used by QEMU upstream. Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> --- tools/libxl/libxl_create.c | 3 +++ tools/libxl/libxl_dm.c | 21 ++++++++++++--------- tools/libxl/libxl_internal.h | 1 + tools/libxl/libxl_qmp.c

This patch series provides the facility to eject and insert a cdrom when the used device-model is qemu-xen. The only difference between both device-model is a call to a QMP command as `xl cd-insert ...` will still update xenstore, even if it''s not used by QEMU. Anthony PERARD (3): libxl_qmp, Introduce libxl__qmp_insert_cdrom. libxl_dm: Set an id to cdrom drives with qemuu. libxl:

Dom0 is Wheezy 64 bit with kernel 3.2.0-1-amd64 version 3.2.4-1, xen from xen-unstable.hg changeset 24858:a88ba599add1 plus these patch for not fail build: http://xen.1045712.n5.nabble.com/PATCH-0-of-2-rename-libxl-yajl-gen-alloc-td5469362.html And also this change for lib patch modified with multiarch support: vi config/StdGNU.mk LIBLEAFDIR_x86_64 ?= lib DomUs PV working, domUs with

On Fri, May 24, 2013 at 02:59:05AM +0000, Gonglei (Arei) wrote: > Hi, > > > > > On Thu, 23 May 2013, Gonglei (Arei) wrote: > > > Hi, all > > > > > > I use O_DIRECT to open disk images for IDE, but I'm failed. After debug, I get > > the below logs: > > > [2013-05-22 23:25:46] ide: CMD=c8 > > > [2013-05-22 23:25:46] bmdma:

Coding style has recently been changed for libxl. The convenience macro LOG() has been introduced, and invocations of the old macro LIBXL__LOG() are to be replaced with it. Change occurences of the old macro to the new one in the functions qmp_handle_response() and qmp_handle_error_response(). The new macros need access to a local libxl__gc *gc, so add it as a parameter to both these functions,

From 18344216b432648605726b137b348f28ef64a4ef Mon Sep 17 00:00:00 2001 From: Liu Jinsong <jinsong.liu@intel.com> Date: Fri, 23 Aug 2013 23:30:23 +0800 Subject: [PATCH V3] xl: HVM domain S3 bugfix Currently Xen hvm s3 has a bug coming from the difference between qemu-traditioanl and qemu-xen. For qemu-traditional, the way to resume from hvm s3 is via ''xl trigger'' command.

This patch exposes a generic interface which can be expanded in the future to implement USB for PVUSB, qemu, and stubdoms. It can also be extended to include other types of USB other than host USB (for example, tablets, mice, or keyboards). For each device removed or added, one of two protocols is available: * PVUSB * qemu (DEVICEMODEL) The caller can additionally specify "AUTO", in

To remove a pci passthough device from QEMU (upstream). Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> --- tools/libxl/libxl_internal.h | 2 ++ tools/libxl/libxl_qmp.c | 35 +++++++++++++++++++++++++++++++++++ 2 files changed, 37 insertions(+), 0 deletions(-) diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h index 1dff211..84da6b1 100644 ---

Commit 2b3072ed0cbeed8c0385f20e92ba0f1201db8a17 has the setting of obj->u.b Commit 6a2aca9fdef0499e613715baf107f2296b9007cf does not. This shows up by vnc-port and vnc-listen are missing in xenstore when they should not be. Signed-off-by: Don Slutz <dslutz@verizon.com> --- tools/libxl/libxl_json.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git

I''ve been trying to have all spice features working on xen domUs since the end of 2011. Basic functions were already working. Adding qemu parameters manually for vdagent and usbredirection was and is also working (I made the patches to support them directly on xl). Qxl was never working: one bug on xen and one on qemu about qxl are fixed, the other xen bug found months ago on the

Package: xen-system-amd64 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainer, after upgrading my bullseye server to bookworm I ran into the issue that all VMs of type hvm are not starting anymore. xl throws an error: libxl: error: libxl_qmp.c:1399:qmp_ev_fd_callback: Domain 8:error on QMP socket: Connection reset by peer libxl: error: libxl_qmp.c:1438:qmp_ev_fd_callback: Domain

This is problem 1 of 3 problems we are having with live migration and/or ACPI on Xen-4.3 and Xen-4.2. Any help would be appreciated. Detailed description of problem: We are using Xen-4.3-rc1 with dom0 running Ubuntu Precise and 3.5.0-23-generic kernel, and domU running Ubuntu Precise (12.04) cloud images running 3.2.0-39-virtual. We are using the xl.conf below on qemu-upstream-dm and HVM and

Usage: usbversion=1|2|3 (default=0, no usb controller defined) Specifies the type of an emulated USB bus in the guest. 1 for usb1, 2 for usb2 and 3 for usb3, it is available only with upstream qemu. The old usb and usbdevice parameters cannot be used with this. Changes from v6: - now usbversion cannot be used with usb and usbdevice parameters - now default is 0 (no usb controller defined) Will be

Hi All, One of our developers managed to trigger a kernel oops on a 4.4.2 dom0.. Oops text is attached. He was working on setting up network namespaces / bridging inside a centos domU, had activated the bridge and lost networking (probably config error) so he rebooted the VM. On reboot is when we saw the oops, along with various xen procs hanging: root 23388 0.0 1.6 132796 32264 ?

Usage: spiceusbredirection=NUMBER (default=0) Enables spice usbredirection. It requires an usb controller and creates NUMBER usbredirection channels for redirection of up to 4 usb devices from spice client to domU''s qemu. The default is disabled (0). Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> --- docs/man/xl.cfg.pod.5 | 6 ++++++ tools/libxl/libxl.h |

Usage: spiceusbredirection=NUMBER (default=0) Enables spice usbredirection. Creates NUMBER usbredirection channels for redirection of up to 4 usb devices from spice client to domU''s qemu. It requires an usb controller and if not defined will automatically adds an usb2 controller. Changes from v2: - updated for usbversion patch v7 - now usbredirection cannot be used with usb and