similar to: Error in launching chasis

On Mon, Oct 17, 2016 at 02:29:10PM +0200, Marina Danial wrote: >I have a predetermined set of commands that I want to launch qemu with: > >sudo `which qemu-system-x86_64` -m 4G $(IMAGE) -enable-kvm \ >-nographic \ >-net nic,model=virtio,netdev=net0,macaddr=$(MAC),vlan=0 \ >-netdev tap,id=net0,ifname=tap01,vhost=on,script=no,downscript=no \ >-net

Hello, In my C++ code, I generate my own domain XML file and I use virDomainCreateXML or virDomainDefineXML to launch my qemu VM. However, when I get to check which commands are sent to the qemu commandline, I find that libvirt has added so many extra parameters to the ones I have already set. How can I prevent libvirt from adding any extra parameters to the ones I originally defined in the

Thanks Martin. I can only use RHEL6 so upgrading libvirt Version is not a choice. RegardsAbhishek From: Martin Kletzander <mkletzan@redhat.com> To: abhishek jain <abhish_jain@yahoo.com> Cc: "libvirt-users@redhat.com" <libvirt-users@redhat.com> Sent: Wednesday, 15 February 2017 2:33 PM Subject: Re: [libvirt-users] Error in libvirt-GUI On Wed, Feb 15, 2017

I have a predetermined set of commands that I want to launch qemu with: sudo `which qemu-system-x86_64` -m 4G $(IMAGE) -enable-kvm \ -nographic \ -net nic,model=virtio,netdev=net0,macaddr=$(MAC),vlan=0 \ -netdev tap,id=net0,ifname=tap01,vhost=on,script=no,downscript=no \ -net nic,model=virtio,netdev=net1,macaddr=$(MANAGE_MAC),vlan=1 \ -netdev

I need write the domain XML in libvirt to eventually convert it into these qemu commands.. I don't want to call qemu directly with these commands. So I needed assistance with that On Oct 17, 2016 9:34 PM, "Martin Kletzander" <mkletzan@redhat.com> wrote: > On Mon, Oct 17, 2016 at 02:29:10PM +0200, Marina Danial wrote: > >> I have a predetermined set of commands

Hi, I am using libvirt --> 0.10.2  and virt-manager --> 0.9.0 version (RHEL 6). Very rare I get following error message dialogue box. (Image is attached for the error dialogue box ) Error saysError polling connection:'qemu+ssh......' Internal error client socket is closed TraceBack (most recent calls)engine.py: 440  conn.tickconnection.py: 1433   self.hostinfo() = self.vmm.getinfo()

I can only use RHEL6. Is it a bug in libvirt ?? RegardsAbhishek From: 王李明 <wanglm@certusnet.com.cn> To: 'abhishek jain' <abhish_jain@yahoo.com>; libvirt-users@redhat.com Sent: Tuesday, 21 February 2017 11:54 AM Subject: 答复: [libvirt-users] Virsh command hanging #yiv0252501574 #yiv0252501574 -- _filtered #yiv0252501574 {font-family:Helvetica;panose-1:2 11 6 4 2 2

On Thu, Apr 04, 2019 at 11:52:46AM -0400, Michael S. Tsirkin wrote: > I simply love it that you have analysed the individual impact of > each patch! Great job! Thanks! I followed Stefan's suggestions! > > For comparison's sake, it could be IMHO benefitial to add a column > with virtio-net+vhost-net performance. > > This will both give us an idea about whether the

On Thu, Apr 04, 2019 at 11:52:46AM -0400, Michael S. Tsirkin wrote: > I simply love it that you have analysed the individual impact of > each patch! Great job! Thanks! I followed Stefan's suggestions! > > For comparison's sake, it could be IMHO benefitial to add a column > with virtio-net+vhost-net performance. > > This will both give us an idea about whether the

Currently in the VM XML, I am passing the following command line argument as a passthrough argument: -netdev type=tap,id=net1,script=no,downscript=no,ifname=port3,vhost=on -device virtio-net-pci,netdev=net1,mac=00:00:00:00:00:01,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off Is there another way to represent this in the XML file? maybe that may solve the problem. On 24 July 2014

​The qemu that I am using isn't modified at all. It's the VHOST drivers that are mounted elsewhere i.e., not on default /dev/vhost-net. Here is the command that I use to launch my qemu VM: qemu-system-x86_64 -cpu host -boot order=c -hda /root/Disks/ubuntu1.qcow2 -m 1024M -smp 2 --enable-kvm -name 'client 1' -nographic -vnc :2 -net none -no-reboot -mem-path /dev/hugepages

On Thu, Apr 04, 2019 at 02:04:10PM -0400, Michael S. Tsirkin wrote: > On Thu, Apr 04, 2019 at 06:47:15PM +0200, Stefano Garzarella wrote: > > On Thu, Apr 04, 2019 at 11:52:46AM -0400, Michael S. Tsirkin wrote: > > > I simply love it that you have analysed the individual impact of > > > each patch! Great job! > > > > Thanks! I followed Stefan's

On Thu, Apr 04, 2019 at 02:04:10PM -0400, Michael S. Tsirkin wrote: > On Thu, Apr 04, 2019 at 06:47:15PM +0200, Stefano Garzarella wrote: > > On Thu, Apr 04, 2019 at 11:52:46AM -0400, Michael S. Tsirkin wrote: > > > I simply love it that you have analysed the individual impact of > > > each patch! Great job! > > > > Thanks! I followed Stefan's

HI, I have a small problem with libvirt / qemu. I have created a guest and when I start it from the command-line the guests starts OK, but when I start the guest through libvirt with "virsh start" I get "Booting from Hard Disk... Boot failed: not a bootable disk No bootable device" This is the command-line I use to start the guest (which works) "cd /var/lib/kvm/Wilmer;

Hi, I started the VMs with libvirt 3 days ago (17th Feb).  Now when I am trying to shutdown the domain, all my virsh command is hanging even  virt-manager remains in "connecting.."  mode and is not showing active domains.When   I set  the libvirt debug env and call "virsh list"  it hangs in poll. Here is the logsetenv LIBVIRT_DEBUG 1 virsh list 2017-02-21 05:31:09.241+0000:

I am using a custom qemu to launch a vhost enabled VM. The qemu doesn't use the default "/dev/vhost-net" directory as character device. Due to this I am getting the error: qemu-system-x86_64: -netdev type=tap,id=net1,script=no,downscript=no,ifname=port3,vhost=on: vhost-net requested but could not be initialized ​Is there a way to tell libvirt to ​avoid using the default

Thanks Wangkai but libvirt infact pre-configures network tap devices and pre-opens /dev/vhost-net file and passes these to qemu as open, ready to use file descriptors. My issue is that my qemu requires that /dev/vhost-net directory is removed and it's kernel module be unloaded. Then it creates a vhost -net device using its own configuration. On 24 July 2014 07:35, Wangkai (Kevin,C)

Let me clarify my question, I am using unmodified stock qemu (1.4.0) and only the location of vhost file descriptor is different from default (I don't remove the default /dev/vhost-net directory) The VHOST file descriptor is present in "/dev/vhost-0" directory instead of the default "/dev/vhost-net". When I try to give vhostfd in the XML I get a different error:

Hello all, hope all is well Was wondering if I'm doing something wrong/missing something. I have pxe+tftp+uefi working between 2 vms. However after the build is done and I reboot, I still come up to pxe b/c tianocore always starts, from what I've seen, with trying PXE first. Great for initial builds :) but I would like to it stop after. In the xml I am pointing to the disk to boot first.

I am seeing a problem with domain renames which I think affects everything running with the upstream qemu xen DM. If I create a domain, and then rename it, it renames in the xenstore, but it does not rename in qemu. This means that (interalia) the name on a VNC connection is incorrect. I am seeing this with a migration (where a libxl_domain_rename is done from "name--incoming" to