similar to: <qemu:commandline> domain XML tag is not working?

Hi Eric, Thanks! You are right, I missed declaring namespace, now, the <qemu:commandline> is saved after virsh edit. However, both namespace and <qemu:commandline> tag are lost after I run "nova start" to launch the VM. Any idea that how could I make this qemu command take effect ? Regards, CY. On Mon, Apr 20, 2015 at 11:41 PM, Eric Blake <eblake@redhat.com> wrote:

Hi Kashyap, Here I want to test and see how much I/O performance could be improved by virtio-blk data plane feature. Yes, this is a dirty way to enable it :-), You mentioned using newer libvirt, is there parameter similar "x-data-plane=on" in new version libvirt? Please let know me you if you have better solution. Regards, CY. On Mon, Apr 20, 2015 at 10:51 PM, Kashyap Chamarthy

On 04/20/2015 08:37 AM, Chengyuan Li wrote: > Hi, > > I tried to enable virtio-blk data plane feature for VMs in my openstack > environment, the hypervisor is ubuntu 14.04, libvirt 1.2.2 and QEMU 2.0. > As nova doesn't support that parameter yet, I did belows > > 1. nova boot a VM with raw disk image. > 2. nova stop the VM. > 3. run "virsh edit

On Mon, Apr 20, 2015 at 10:37:13PM +0800, Chengyuan Li wrote: > Hi, > > I tried to enable virtio-blk data plane feature for VMs in my openstack > environment, the hypervisor is ubuntu 14.04, libvirt 1.2.2 [I haven't tested the virtio-blk data plane myself.] This libvirt version seems a little old (from March 2014), you might want to move to a bit newer. > and QEMU 2.0.

Hi Team, I am exploring "edu" device in QEMU to add my own custom device. I am able to add the device using the command line. Would it be possible to add the device using XML file through libvirt? -- Regards, Bharath

Hi, My nova-compute nodes was running libvirt 0.9.13 and QEMU 1.0, after libvirt was upgraded to 1.2.2, the VMs launched by libvirt 0.9.13 can't attach volume any more, i.e. "nova volume-attach <vm-uuid> <volume-uuid>" doesn't work. But before the libvirt upgrade, the same VM can attach volume disk. I did some debuging and find that, it failed in QEMU when try to

Hi, When I'm trying to run qemu-kvm command on RHEL6(linux kernel 2.6.32) then I get following errors which I think related to tap devices in my setup. Any idea why is that? bash$ LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-00000027 -uuid

Hello Han, Thanks for the response. The XML option with qemu:commandline works if the device is added during the VM creation. But I would like to hot-plug the device to the running VM. I can add the device using the command line <virsh qemu-monitor-command --hmp VM-Name device_add edu,id=edu0> But I would like to add the device using the XML file, like <virsh attach-device VM-Name

On 05/18/2015 01:02 PM, Jim Fehlig wrote: > On 05/18/2015 11:35 AM, Emma Anderson wrote: >> hi, >> >> I use xl toolstack to manage vms on a Xen machine, and also pass some >> custom parameters when creating a vm, for example: >> >> xl create vm.cfg ' param="xyz" ' > > Documentation on create subcommand in the xl man page describes the

?Hi, ?I've installed libvirt-0.9.13 on RHEL6.2 from the source code. I cannot make sVirt working with LXC. (sVirt works well with KVM, though.) I can start an LXC instance, but the label of the process is not right. Can someone help me? I tried to change /etc/libvirtd/lxc.conf file to explicitly enable security_driver = "selinux". But it ends up with error saying "error :

On 2018?06?05? 09:41, Samudrala, Sridhar wrote: > Ping on this patch now that the kernel patches are accepted into > davem's net-next tree. > https://patchwork.ozlabs.org/cover/920005/ > > > On 5/7/2018 4:09 PM, Sridhar Samudrala wrote: >> This feature bit can be used by hypervisor to indicate virtio_net >> device to >> act as a standby for another device

On 2018?06?05? 09:41, Samudrala, Sridhar wrote: > Ping on this patch now that the kernel patches are accepted into > davem's net-next tree. > https://patchwork.ozlabs.org/cover/920005/ > > > On 5/7/2018 4:09 PM, Sridhar Samudrala wrote: >> This feature bit can be used by hypervisor to indicate virtio_net >> device to >> act as a standby for another device

Hi all, I am running KVM on a 3.18 kernel. The system runs and Atom processor with 2Gb RAM. Using KVM you obviously can over allocate your resources: say you have 4 guests each configured with 1GB ram. Running all four at the same time, depending on the workload, can crash the system - I get a kernel trace when this happens. But let's consider a simpler case: one guest with 1.5 Gb RAM,

On Tue, Jan 26, 2016 at 12:39 PM, Michal Privoznik <mprivozn@redhat.com> wrote: > On 26.01.2016 12:30, Andrei Perietanu wrote: > > Hi all, > > > > I am running KVM on a 3.18 kernel. The system runs and Atom processor > with > > 2Gb RAM. > > > > Using KVM you obviously can over allocate your resources: say you have 4 > > guests each configured

Hi, We've run into a problem with libvirt 1.1.2 and are looking for some comments on whether this is a bug or design intent. We're trying to use migrateToURI() but we're using a few things (numatune, vcpu mask, etc.) that may need adjustment during the migration. We found that migrateToURI2() mostly works if we use XML created by copying the domain XML from the running instance

Hello, I have a custom QEMU which requires some non-standard command line arguments to launch a VM. e.g., "--proc-type=secondary" option is always required to launch a QEMU VM. To launch the VM through libvirt (virsh) "How do I specify these non-standard options in XML? OR if thats not possible ,Can you guide me at which point (code file) libvirt converts the XML to QEMU command

On 02/11/2014 04:45 PM, Cole Robinson wrote: > On 02/10/2014 06:46 PM, Chris Friesen wrote: >> Hi, >> >> We've run into a problem with libvirt 1.1.2 and are looking for some comments >> on whether this is a bug or design intent. >> >> We're trying to use migrateToURI() but we're using a few things (numatune, >> vcpu mask, etc.) that may need

This is not a libvirt/redhat question… With your method you can only revert to versions which are available in the standard repositories. You’ll have to download the packages manually to force a different version. Use with caution. There is a reason why the version isn’t in the standard repositories. Van: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] Namens Keyur

hi, I use xl toolstack to manage vms on a Xen machine, and also pass some custom parameters when creating a vm, for example: xl create vm.cfg ' param="xyz" ' I am moving to libvirt for vm management. How I can pass those extra parameters using libvirt? Thanks.

Libvirt Version: 0.9.8 Hi: I added a new api for qemu_driver. and both added libvirt.c and remote. I tested it and it worked well. the function of this new api was add a new field in xml config of domain. (I added it like qemudDomainSetMemoryFlags)at the same time, I added a new member to struct virDomainDef. then I tested xml config converted to virDomaindef and virDomainDef converted to xml