similar to: disable-ticketing

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

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

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

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

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

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 all, sorry for being OT but would any of you recommend a ticketing system? We'd like something pretty comprehensive to cover helpdesk and HR stuff as well as software bugs/requests. There seems to be a million variations out there.

Dear All, do you have any experiences with trouble ticketing systems written for RoR? Best regards, Karl

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, I am using virsh 0.9.8 My qemu is 1.0 version. I would like to use Ivshmem device from virsh command line. It is possible to use ivshmem device from qemu command line.But its not working if I am giving -device ivshmem device in xml config file. Does virsh support ivshmem device.?? -- Mrugani Kurtadikar Btech IT College of Engineering, Pune. -------------- next part -------------- An HTML

Hello All, I want to use shared memory , but in virsh I am unable to provide the necessary options for use of shared memory. I want to have some scripts so that they can be included in the xml file so that each time the need is of shared memory , it can be directly used from there only. Thanks and Regards -------------- next part -------------- An HTML attachment was scrubbed... URL:

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.

On 25 September 2016 at 17:57, Leonard den Ottolander >> > >> Nested Virtualization will be a tech preview in RHEL 7.3 Beta, and so >> it'll be available after RHEL 7.3 is released and CentOS rebuilds it. > Officially its gonna be tech-preview in 7.3, but I can tell you we've been successfully using it for testing oVirt since 7.1... (For el7 on top of el7, see [1]

Thanks Ján! >What were the exact changes you were trying to make? I was following this guide: https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Passing_keyboard/mouse_via_Evdev Specifically, I was updating the domain tag to include `xmlns:qemu=' http://libvirt.org/schemas/domain/qemu/1.0'` >both call virDomainDefineXMLFlags under the hood. That is good to know,

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

On Tue, Jan 26, 2016 at 1:51 PM, Michal Privoznik <mprivozn@redhat.com> wrote: > On 26.01.2016 14:35, Andrei Perietanu wrote: > > 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

Hello! We are proudly announce that CerbNG-1.0 Release Candidate 2 is now avaliable. There are many changes from RC1 (many new functionalities, some bug fixes, new interesting policies, new regression tests and more). It seems that CerbNG is stable for now, so we hope that the next version is going to be final 1.0 series release. We count on feedback from FreeBSD community in founding bugs (if