search for: drvqemu

reading KVM/QEMU hypervisor driver page here: http://libvirt.org/drvqemu.html and one reads, "KVM hypervisor: The driver will probe /usr/bin for the presence of qemu-kvm ...". on my RHEL 6.5 system, qemu-kvm is in /usr/libexec, not /usr/bin. am i misreading something? rday

...>> parameters using libvirt? > > I'm not aware of similar functionality in libvirt. You would need to > customize the domXML before feeding it to 'virsh create'. Qemu domains have that ability, via an XML namespace that adds <qemu:commandline>: http://libvirt.org/drvqemu.html#qemucommand but no one has yet implemented that for Xen domains. If you want to add it, the src/qemu code would be the obvious starting point to copy from. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

...>> feature 'true' >> by default as i am using libvirt to start the VMs. >> Is there a way to pass the newly added feature bit 'standby' to qemu >> via libvirt >> XML file? >> Maybe you can try qemu command line passthrough: https://libvirt.org/drvqemu.html#qemucommand The patch looks good to me. Let's see if Michael have any comment. Thanks >> Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> >> --- >> ? hw/net/virtio-net.c???????????????????????? | 2 ++ >> ? include/standard-headers/linux/vir...

...>> feature 'true' >> by default as i am using libvirt to start the VMs. >> Is there a way to pass the newly added feature bit 'standby' to qemu >> via libvirt >> XML file? >> Maybe you can try qemu command line passthrough: https://libvirt.org/drvqemu.html#qemucommand The patch looks good to me. Let's see if Michael have any comment. Thanks >> Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> >> --- >> ? hw/net/virtio-net.c???????????????????????? | 2 ++ >> ? include/standard-headers/linux/vir...

...qemu='http://libvirt.org/schemas/domain/qemu/1.0 > '> > ... > <qemu:commandline> > <qemu:arg value='-device'/> > <qemu:arg value='edu'/> > </qemu:commandline> > </domain> > > More reference: https://libvirt.org/drvqemu.html#qemucommand > >> >> > -- >> Regards, >> Bharath >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users@redhat.com >> https://www.redhat.com/mailman/listinfo/libvirt-users > > > > -- &gt...

I use libvirt to manage a QEMU/KVM system. Starting a VM only by using > virsh start vmname What I want to know is how to add an option to virsh vm's start script, in my case I want to add QEMU logging option (-d and -D). I can see from > ps aux | grep qemu that current VM started using virsh not including those options ~ady

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

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

milos.blazevic wrote: > A VM can have spice console listen only on the loopback interface, so the only way to connect would be to tunnel the spice connection via SSH. This is so 'by design'. I specified to listen on all addresses --- in my understanding, that are the addresses of the host rather than those of any particular VM. > You'll certainly need an SSH keypair for

hi, using the cockpit web ui and with these instructions: https://libvirt.org/dbus.html#usage we allow successfully that a group of users can access the console of the system vms in different kvm hosts. Oddly enough, in the same cockpit web interface I can use a terminal, and if I run virsh list --all I get an empty listing. So using cockpit I can manage the system vms, but I cannot use virsh.

.... Either you can passthrough > it onto qemu commandline [1] or use locked memoryBacking [2]. I advocate > for the latter though. Not only it will allocate all the memory at qemu > startup it will also lock it so it won't get swapped off. > > Michal > > 1: http://libvirt.org/drvqemu.html#qemucommand > 2: http://libvirt.org/formatdomain.html#elementsMemoryBacking > I tried memoryBacking: I added this to the domain xml: <memoryBacking> <locked/> </memoryBacking> And got an error when attempting to start the vm: memory locking no supported by QEMU bina...

...> > <qemu:commandline> > > <qemu:arg value='-set'/> > > <qemu:arg value='device.drive-virtio-disk0.x-data-plane=on'/> > > </qemu:commandline> > > Did you also remember to declare the namespace? Per > http://libvirt.org/drvqemu.html#qemucommand > > it is essential to have something like: > > <domain type='qemu' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0 > '> > > before any other <qemu:...> will be recognized. (The namespace does not > have to be named 'q...

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,

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 <instance-id>" on the hyprvisor node, and adding below into instance xml just before

...line [1] or use locked memoryBacking [2]. I advocate > >> for the latter though. Not only it will allocate all the memory at qemu > >> startup it will also lock it so it won't get swapped off. > >> > >> Michal > >> > >> 1: http://libvirt.org/drvqemu.html#qemucommand > >> 2: http://libvirt.org/formatdomain.html#elementsMemoryBacking > >> > > > > I tried memoryBacking: I added this to the domain xml: > > <memoryBacking> > > <locked/> > > </memoryBacking> > > > > And...

...9;t recognized by libvirt. > > <qemu:commandline> > <qemu:arg value='-set'/> > <qemu:arg value='device.drive-virtio-disk0.x-data-plane=on'/> > </qemu:commandline> Did you also remember to declare the namespace? Per http://libvirt.org/drvqemu.html#qemucommand it is essential to have something like: <domain type='qemu' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> before any other <qemu:...> will be recognized. (The namespace does not have to be named 'qemu:', but it makes it easier to s...

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.

...e option I see, use -mem-prealloc. Either you can passthrough it onto qemu commandline [1] or use locked memoryBacking [2]. I advocate for the latter though. Not only it will allocate all the memory at qemu startup it will also lock it so it won't get swapped off. Michal 1: http://libvirt.org/drvqemu.html#qemucommand 2: http://libvirt.org/formatdomain.html#elementsMemoryBacking

...lowing: <domain type='qemu' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> ... <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='edu'/> </qemu:commandline> </domain> More reference: https://libvirt.org/drvqemu.html#qemucommand > > -- > Regards, > Bharath > _______________________________________________ > libvirt-users mailing list > libvirt-users@redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users -- Best regards, ----------------------------------- Han Han Q...

...rg/schemas/domain/qemu/1.0'> >> ... >> <qemu:commandline> >> <qemu:arg value='-device'/> >> <qemu:arg value='edu'/> >> </qemu:commandline> >> </domain> >> >> More reference: https://libvirt.org/drvqemu.html#qemucommand >> >>> >>> >> -- >>> Regards, >>> Bharath >>> _______________________________________________ >>> libvirt-users mailing list >>> libvirt-users@redhat.com >>> https://www.redhat.com/mailman/listinfo/...