similar to: Adding timestamps for all emulator output

On Thu, Feb 26, 2015 at 5:36 PM, Daniel P. Berrange <berrange@redhat.com> wrote: > On Thu, Feb 26, 2015 at 06:29:49PM +0400, Andrey Korolyov wrote: >> Hello, >> >> I think it would be useful if libvirt will be able to prefix all >> messages from emulator pipes with the date stamping, for example I am >> trying to catch very rare and non-fatal race with

On Thu, Feb 26, 2015 at 06:29:49PM +0400, Andrey Korolyov wrote: > Hello, > > I think it would be useful if libvirt will be able to prefix all > messages from emulator pipes with the date stamping, for example I am > trying to catch very rare and non-fatal race with > > virtio-serial-bus: Guest failure in adding device virtio-serial0.0 > > which is specific to the

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

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

On Fri, Mar 13, 2015 at 12:35 PM, Daniel P. Berrange <berrange@redhat.com> wrote: > On Fri, Mar 13, 2015 at 10:32:14AM +0100, Dominique Ramaekers wrote: >> Dear Daniel, my XML's: >> >> Note: It seems I was to quick, the Windows 8.1 isn't fixed... >> >> Windows Server 2015 R2 >> >> <domain type='kvm' id='146'> >>

Hi, There is a quite annoying thing, don`t sure if I can call it a bug. How to reproduce: - start a bunch of VMs, - stop libvirt, - start libvirt and immediately issue any call, say, 'virsh version', - delay until call completion may be fitted nearly as quadratic function from number of running VMs, qemu-kvm in my case (see link below). After this delay passed, any calls executed

2014-08-26 19:11 GMT+04:00 Andrey Korolyov <andrey@xdel.ru>: > not, right now it is not possible. Why don`t you want to just assign > unique paths for socket name, derived, say, from VM` UUID? > In case of unix domain sockets paths not problem, but i want to connect to each qemu-ga address from central point. I don't want to use socat , as i see qemu have ability to specify

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 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 >> (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >>

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 >> (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >>

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,\ >

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,\ >

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,\

Small update: traceFlag T8038 => no improvement... -----Oorspronkelijk bericht----- Van: Dominique Ramaekers Verzonden: vrijdag 13 maart 2015 16:35 Aan: 'Daniel P. Berrange'; Andrey Korolyov CC: libvirt-users@redhat.com Onderwerp: RE: [libvirt-users] Processor usage of qemu process. Results ---------- First I want to show my appreciation to Daniel and Andrey. So thanks... I've

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,\ > >

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 Thu, Jan 31, 2013 at 12:11 AM, Marcelo Tosatti <mtosatti at redhat.com> wrote: > On Wed, Jan 30, 2013 at 11:21:08AM +0300, Andrey Korolyov wrote: >> On Wed, Jan 30, 2013 at 3:15 AM, Marcelo Tosatti <mtosatti at redhat.com> wrote: >> > On Tue, Jan 29, 2013 at 02:35:02AM +0300, Andrey Korolyov wrote: >> >> On Mon, Jan 28, 2013 at 5:56 PM, Andrey Korolyov