similar to: libvirtError: this function is not supported by the connection driver: virDomainSnapshotNum

On 06/17/2015 03:32 AM, Robert Heller wrote: > If host is using LVM for disk partitioning and uses logical volumes for VM > disks, it is possible to do LVM 'snapshots' and these snapshots can then be > backed up, all without shutting down the VMs. Note that making an LVM snapshot, alone, will not provide a consistent image for a backup. If you want to back up a snapshot of a

After reading the following articles, it doesn''t sound very hopeful for Xen. [1] Xen vs. KVM: Verdict still out on dueling hypervisors http://searchdatacenter.techtarget.com/news/article/0,289142,sid80_gci1368664,00.html [2] Xen vs. KVM Linux virtualization hypervisors http://searchservervirtualization.techtarget.com/generic/0,295582,sid94_gci1371226,00.html [3] Xen vs. KVM: The Linux

After reading the following articles, it doesn''t sound very hopeful for Xen. [1] Xen vs. KVM: Verdict still out on dueling hypervisors http://searchdatacenter.techtarget.com/news/article/0,289142,sid80_gci1368664,00.html [2] Xen vs. KVM Linux virtualization hypervisors http://searchservervirtualization.techtarget.com/generic/0,295582,sid94_gci1371226,00.html [3] Xen vs. KVM: The Linux

QUESTION: What, if anything, can I do so that I can use xl (in place of xm) with libvirt 1.0.2 and Xen 4.2.1 in Ubuntu 13.04? BACKGROUND: I am testing a fully updated (as of March 27) installation of Ubuntu 13.04 that includes the following packages: libvirt - version 1.0.2-0ubuntu9 xen-hypervisor-4.2-amd64 - version 4.2.1-0ubuntu1 Upon setting TOOLSTACK=xm in /etc/default/xen (as well as

hope this help some one else --as it helped me, in undertanding contributions to * wiki pages... Regards! Samuel ----- Original Message ----- From: "whatis.com" <WhatIs-BAD63EB5A68046E1@lists.techtarget.com> To: "whatis.com" <WhatIs@lists.techtarget.com> Sent: Tuesday, January 06, 2004 10:31 AM Subject: Word-of-the-Day: wiki > THE

On 12.03.2014 14:41, Sijo Jose wrote: > > > > Hi, > Could anyone help I'm getting the following error when I tried to add a > new network interface. > > DETAILS > > > Connection > --------------------------- > import libvirt > conn = libvirt.open('qemu:///system') > > Interface XML > ---------------------- > > <interface

Hi, Could anyone help I'm getting the following error when I tried to add a new network interface. DETAILS Connection --------------------------- import libvirt conn = libvirt.open('qemu:///system') Interface XML ---------------------- <interface type="bridge" name="br0"> <start mode="onboot"/> <mtu size="1500"/>

Hello everyone I have solved the problem(LibvirtError: Operation not supported : JSON monitor is required). yajl-devel package must be intalled before compile and install libvirt 1.2.4 ..... then rebuild and install libvirt-python 1.2.4 every thing is OK..... Hi Thanks for chenhanxiao@cn.fujitsu.com help , I have resole the problem (libvirt 1.2.4 and

Hi Thanks for chenhanxiao@cn.fujitsu.com help , I have resole the problem (libvirt 1.2.4 and virt-manager 0.9.0 are not incompatible)..but when I created VM by virt-manager ,it reported : unable to complete install: 'Opertation not supported: JSON monitor is required.' Traceback(most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py",line

On Wed, Oct 16, 2013 at 01:52:57PM +0200, Maciej Gałkiewicz wrote: > Hi > > I am using Libvirt 1.1.2 with Openstack Havana (RC2, nova-network) and > openvswitch 1.4.2+git20120612-9.1. Libvirt vif driver ( > nova.virt.libvirt.vif.LibvirtGenericVIFDriver) generates config likes this: > > <interface type='bridge'> > <mac

On 16 October 2013 13:55, Daniel P. Berrange <berrange@redhat.com> wrote: > > Sounds like a host mis-configuration related to kernel bridge support > to me. > Could you tell me what might be mis-configured? I am using kernel 3.10.11, modules openvswitch, bridge, stp and llc are loaded. regards -- Maciej Gałkiewicz Shelly Cloud Sp. z o. o., Sysadmin http://shellycloud.com/,

On Wed, Oct 16, 2013 at 02:04:47PM +0200, Maciej Gałkiewicz wrote: > On 16 October 2013 13:55, Daniel P. Berrange <berrange@redhat.com> wrote: > > > > Sounds like a host mis-configuration related to kernel bridge support > > to me. > > > > Could you tell me what might be mis-configured? I am using kernel 3.10.11, > modules openvswitch, bridge, stp and llc

Hi I am using Libvirt 1.1.2 with Openstack Havana (RC2, nova-network) and openvswitch 1.4.2+git20120612-9.1. Libvirt vif driver ( nova.virt.libvirt.vif.LibvirtGenericVIFDriver) generates config likes this: <interface type='bridge'> <mac address='fa:16:3e:44:30:a4'/> <source bridge='br0'/> <model type='virtio'/>

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.

I have built on clean system with xen-unstable 25374 and stops with this error: gcc -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -D__XEN_TOOLS__ -MMD -MF .libxl.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls -Werror -Wno-format-zero-length

This adds a backend_domname field in libxl devices that contain a backend_domid field, allowing either a domid or a domain name to be specified in the configuration structures. The domain name is resolved into a domain ID in the _setdefault function when adding the device. This change allows the backend of the block devices to be specified (which previously required passing the libxl_ctx down

Adds support for assigning a label to domains, obtaining and setting the current enforcing mode, and loading a policy with xl command and libxl header when the Flask XSM is in use. Adheres to the changes made by the patch to remove exposure of libxenctrl/libxenstore headers via libxl.h. tools/libxl/libxl_flask.c | 71 ++++++++++++++++++ tools/libxl/Makefile | 2

Usage: spicevdagent=1|0 (default=0) Enables spice vdagent. The Spice vdagent is an optional component for enhancing user experience and performing guest-oriented management tasks. Its features includes: client mouse mode (no need to grab mouse by client, no mouse lag), automatic adjustment of screen resolution, copy and paste (text and image) between client and domU. It also requires vdagent

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.

vif interfaces allows the user to specify the domain that should run the backend (also known as driver domain) using the ''backend'' parameter. This is not compatible with run_hotplug_scripts=1, since libxl can only run the hotplug scripts from the Domain 0. Signed-off-by: Roger Pau Monne <roger.pau@citrix.com> --- docs/misc/xl-network-configuration.markdown | 6 ++++--