similar to: permission denied when setting up VMchannel with libvirt

I am trying to connect a KVM-QEMU VM to OVS-DPDK vhostuser port. But, I am encountering a few errors. Since I am very new to libvrt and Linux I am not able to sort them out. Any guidance in this regard would be a great help. These are my System Logs: Mar 28 18:03:04 dpdk-OptiPlex-5040 libvirtd.service: 1529: debug : virCommandRunAsync:2429 : About to run LIBVIRT_LOG_OUTPUTS=3:stderr

Hi all. Having trouble figuring out the magic to set up VMChannel comms between EL6.x host/guests. My end goal is to enable fence_virt in the guest to talk to fence_virtd on the host via VMChannel. I'd prefer to use that instead of multicast because it is supposed to work even if networking in the guest is down/borked. My analysis is that there is a mismatch between what libvirt is feeding

> > Description of problem: > Guest get 'Call Trace' when loading module "virtio_console" and unloading > it frequently > > > Version-Release number of selected component (if applicable): > Guest > kernel-4.18.0-167.el8.x86_64 > seabios-bin-1.11.1-4.module+el8.1.0+4066+0f1aadab.noarch > # modinfo virtio_console >

Hello, I've running Ubuntu-14.04 as my host and my guest. I've been trying to get guest to host communication set up by configuring a virtio-serial device. My xml file contains: <channel type='unix'> <source mode='bind' path='/home/dave/vm1.agent'/> <target type='virtio' name='vm1'/> </channel> When I start up

Hi, I have created a VM with the option inside virt-manager to "start virtual machine on host boot up". It is the only VM on the host to be configured this way. However, I am getting this error in the log file when it attempts to start it on boot up: 2017-06-19 07:15:18.491+0000: starting up libvirt version: 2.0.0, package: 10.el7_3.9 (CentOS BuildSystem

Hello, I am trying to create a lucid guest VM with a vmchannel between the guest and the hypervisor. Details below: KERNEL: # uname -a Linux saurav-desktop 2.6.38-2-generic #29~lucid1-Ubuntu SMP Mon Feb 7 13:35:14 UTC 2011 i686 GNU/Linux QEMU: # /usr/bin/qemu --version QEMU emulator version 0.13.0, Copyright (c) 2003-2008 Fabrice Bellard LIBVIRT: # /usr/sbin/libvirtd --version

Libvirt doesn't care about security during hot add disk images. It even accepts addition of disk images of other guest running on the host. Steps followed to create this scenario : Started two VMs with following security configurations: vm1: <seclabel type='dynamic' model='selinux' relabel='yes'>

On Tue, Jun 20, 2017 at 06:23:39AM +0000, Andy Gibbs wrote: >Hi, > > >I have created a VM with the option inside virt-manager to "start virtual machine on host boot up". It is the only VM on the host to be configured this way. However, I am getting this error in the log file when it attempts to start it on boot up: > > >2017-06-19 07:15:18.491+0000: starting up

On 08/03/2015 10:47 PM, Martin Kletzander wrote: > On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>> Using: >>> >>> edk2.git-0-20150803.b1141.ga0973dc.x86_64 >>> edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch >>> >>> On Fedora 22. >>> >>> Provisioning

Am Donnerstag, 17. M?rz 2016, 08:57:40 CET schrieb Gordon Messmer: > On 03/17/2016 08:26 AM, G?nther J. Niederwimmer wrote: > > Have any a hint why ? The Problem is starting on three different Server, near to the same time ???? This is my Panic Situation. > You're going to have to provide logs, or error messages, or something. This is a a log from a client ? starting up

Hi, As I want to start qemu by adding following parameters : -device virtio-serial -chardev socket,path=/tmp/foo,server,nowait,id=test -device virtserialport,chardev=test,name=port.0 Is it possible to add them in the .xml configuration file of the guest , so they will be automatically added when the guest is started ? If yes , any doc describing the syntax ? Thx. Regards, J.P. Ribeauville

On Fri, Oct 18, 2019 at 06:47:18PM +0200, Laurent Vivier wrote: > When we hot unplug a virtserialport and then try to hot plug again, > it fails: > > (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait > (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ > chardev=serial0,id=serial0,name=serial0 > (qemu) device_del serial0 >

On 08/06/2015 08:08 AM, Martin Kletzander wrote: > On Tue, Aug 04, 2015 at 07:11:29AM -0700, Ryan Barry wrote: >> On 08/03/2015 10:47 PM, Martin Kletzander wrote: >>> On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >>>> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>>>> Using: >>>>> >>>>>

When we hot unplug a virtserialport and then try to hot plug again, it fails: (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\

When we hot unplug a virtserialport and then try to hot plug again, it fails: (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\

On 13/11/2019 16:22, Michael S. Tsirkin wrote: > On Wed, Nov 13, 2019 at 10:21:11AM -0500, Michael S. Tsirkin wrote: >> On Wed, Nov 13, 2019 at 04:00:56PM +0100, Laurent Vivier wrote: >>> When we hot unplug a virtserialport and then try to hot plug again, >>> it fails: >>> >>> (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait

On Tue, Dec 03, 2019 at 03:46:50PM +0100, Amit Shah wrote: > On Thu, 2019-11-14 at 13:25 +0100, Laurent Vivier wrote: > > When we hot unplug a virtserialport and then try to hot plug again, > > it fails: > > > > (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait > > (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ > >

On Wed, Nov 06, 2019 at 03:02:25PM +0100, Laurent Vivier wrote: > On 06/11/2019 14:56, Michael S. Tsirkin wrote: > > On Fri, Oct 18, 2019 at 06:47:18PM +0200, Laurent Vivier wrote: > >> When we hot unplug a virtserialport and then try to hot plug again, > >> it fails: > >> > >> (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait >

On Fri, Jul 18, 2014 at 11:58 PM, Andrey Korolyov <andrey@xdel.ru> wrote: > Hello, > > 2.0 model works fine > > 2.1 crashes with following: > > /tmp/buildd/qemu-2.0.92+rev1/hw/i386/smbios.c:825: smbios_get_tables: > Assertion `smbios_smp_sockets >= 1' failed > > Not sure if bisect will help much, but the commit which introduced > this platform works

On Wed, Nov 13, 2019 at 10:21:11AM -0500, Michael S. Tsirkin wrote: > On Wed, Nov 13, 2019 at 04:00:56PM +0100, Laurent Vivier wrote: > > When we hot unplug a virtserialport and then try to hot plug again, > > it fails: > > > > (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait > > (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >