similar to: Fwd: [Issue]: Regarding client socket getting closed from the server once the lxc container is started

Hi, When I want to start a VM by virsh, report error: virsh start vm1 2013-09-18 05:52:06.809+0000: 12324: info : libvirt version: 1.1.1, package: 1.mcp8_0.1 (Koji, 2013-08-09-07:55:01, lnxmcp1) 2013-09-18 05:52:06.809+0000: 12324: debug : virLogParseOutputs:1334 : outputs=1:file:/var/log/virsh.log error: Failed to start domain vm1 error: End of file while reading data: Input/output error

Hi all: It takes more than 10 seconds to create a vm on a Dell R830 machine, but it takes less than 2 seconds on other machines. This is not normal, so I turned on the debug log for libvirtd. I analyzed the log and found that the time was spent on libvirtd calling qemu. Thread 95225 calls the qemuProcessLaunch interface at 14:22:30.129 and then builds the emulator command line, but the

Hello all, I have been trying to get libvirtd to work but when I connect to it with virsh, I get "error : virNetMessageDecodeLength:131 : Unable to decode message length" This happens with libvirt 6.1.0, libtirpc 1.2.6, rpcsvc-proto 1.4.1. I have tried with other versions, but I still get the same error. If anybody has any tip on what to try next, that would be helpful. Thank you

`virsh list` hangs on my server that hosts a bunch of VMs. This might be due to the Debian upgrade I did on Feb 15, which upgrades `libvirt` from 2.4.0-1 to 3.0.0-2. I have tried restarting libvirtd for a few times, without luck. Attached below are some relevant logs; let me know if you need some more for debugging. Thanks for your help!! root@vm-host:~# uname -a Linux vm-host 4.6.0-1-amd64 #1

I see that libvirt 1.1.0 should now support virtualbox 4.2, but I'm having problems getting it to work in OSX. I have built it using homebrew, which now has 1.1.0 in its formulae. The error I get when tying to connect is shown below. Any suggestions for where I should look next? The error about "Failed to find user record for uid 'NNNNN'" is odd. libvirtd *is* started

Hi I was trying out the libxl backend of xen 4.3 with libvirt, but I found it very unstable and unusable. I'm in xen 4.3 dom0 and starting: 1. xen stuff: echo "Starting Xen..." /etc/init.d/xencommons start #/etc/init.d/xend start . /etc/rc.d/rc.xen_bridge start /etc/init.d/xendomains start #libvirtd -l -d hsflowd 2. Starting libvirt -v to see what is going on. After that

I have freshly installed Virtualbox (5.04) and have installed libvirt (1.2.19) using brew. When i attempt to run virsh it does not work with the following outputs. # virsh -c vbox:///session error: failed to connect to the hypervisor error: internal error: unable to initialize VirtualBox driver API Any pointers on what to try next or where to investigate to get more info. Has anyone got virsh

I'm trying the following command on the source machine: virsh migrate --live --copy-storage-all --verbose TEST qemu+ssh:// 10.30.76.66/system If I ssh into the destination machine when this command is running, I can see NBD copying data as expected, and if I wait long enough it completes and succeeds. However if I ctrl+c this command above before it completes, it causes virsh commands

Hi, I have installed libvirt 4.9. libvirtd 4.9 takes a long time to come up. I enabled debug prints and also put my own prints Logs are below 2019-02-06 05:55:49.082+0000: 377: info : libvirt version: 4.9.0 2019-02-06 05:55:49.082+0000: 377: info : hostname: draco 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782d8bb0 classname=virAccessManager

Hi, I have installed libvirt 4.9. libvirtd 4.9 takes a long time to come up. I enabled debug prints and also put my own prints Logs are below 2019-02-06 05:55:49.082+0000: 377: info : libvirt version: 4.9.0 2019-02-06 05:55:49.082+0000: 377: info : hostname: draco 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782d8bb0 classname=virAccessManager

Hi, I tried to build and run libvirt-1.0.1 on FSL PowerPC platform. The connection to '/var/run/libvirt/libvirt-sock' is always refused. # libvirtd -d # export LIBVIRT_DEBUG=1 # export LIBVIRT_LOG_OUTPUTS="1:file:virsh.log" # virsh -c qemu:///system list 2013-01-10 04:55:20.409+0000: 2574: info : libvirt version: 1.0.1 2013-01-10 04:55:20.409+0000: 2574: debug :

Dear Michal After I fix the local libvirt master branch follow your patch, and build rpm for CentOS 7.4. virDomainUpdateDeviceFlags as bellow: ================================================ 2018-02-27 09:27:43.782+0000: 16656: debug : virDomainUpdateDeviceFlags:8326 : dom=0x7f2084000c50, (VM: name=6ec499397d594e f2a64fcfc938f38225, uuid=6ec49939-7d59-4ef2-a64f-cfc938f38225), xml=<disk

libvirt 1.3.3 seems to have introduced some kind of issue on CentOS 6 (no systemd). After upgrading, libvirt would take an incredibly long time to get to a state where it would actually respond to a simple 'virsh list' command. Looking at verbose output showed this repeating at exactly 30s intervals 2016-04-12 19:40:57.142+0000: 14929: info : virEventPollDispatchHandles:507 :

Hi there! I'm building libvirt-1.1.4 on Tizen. I had to modify the spec file: 1. Comment out requirements: xhtml1, scrub, shadow-utils 2. Added defines: %define _without_selinux 1 %define _without_hal 1 %define _without_libnl 1 %define _without_macvtap 1 %define _without_storage_fs 1 %define _without_network 1 %define _without_sasl 1 %define _without_qemu 1 %define

On 04/20/2015 09:28 PM, Matthew Schumacher wrote: > > On 04/20/2015 05:12 PM, Laine Stump wrote: >> On 04/20/2015 08:45 PM, Matthew Schumacher wrote: >>> List, >>> >>> I was under the impression that I could restart libvirtd without it >>> destroying my VMs, but am not finding that to be true. >> If not, then something is wrong. >> >

Hello everybody, i oberserve a strange behavior of libvirtd. I have an xen vm (HVM, windows xp) that i restore from an statefile. If i do so, it works. But if i do that in an loop, where i restore the vm, let it run 60 seconds, destroy it, wait 30 second, and then i restore again, it runs 91 times and then libvirt crashed and the give me in the syslog logs the messages after "from

i did the debugging as you said. Kindly refer the following logs: (gdb) c Continuing. thread apply all bt [New Thread 0x7fc337c6b700 (LWP 29520)] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) thread apply all bt Thread 12 (Thread 0x7fc337c6b700 (LWP 29520)): #0 0x00007fc33509f18d in read () from /lib/x86_64-linux-gnu/libpthread.so.0 #1

On 04/20/2015 05:12 PM, Laine Stump wrote: > On 04/20/2015 08:45 PM, Matthew Schumacher wrote: >> List, >> >> I was under the impression that I could restart libvirtd without it >> destroying my VMs, but am not finding that to be true. > If not, then something is wrong. > Here are the logs from the vm: 2015-04-20 23:50:20.387+0000: shutting down qemu:

centos6.3,libvirt 0.9.10. [root at ovirtdev private]# virsh -c qemu+tls://ovirtdev.localhost/system list 2013-04-22 03:37:09.362+0000: 9898: info : libvirt version: 0.9.10, package: 21.el6_3.8 (CentOS BuildSystem <http://bugs.centos.org>, 2013-01-28-19:24:16, c6b10.bsys.dev.centos.org) 2013-04-22 03:37:09.362+0000: 9898: warning : virNetClientIncomingEvent:1665 : Something went wrong during

Hello all, I am getting a error, when creating a sheepdog pool via libvirt. libvirt is compiled as: ./configure --prefix=/opt/libvirt --without-xen --with-yajl --with-storage-sheepdog=/opt/sheepdog Sheepdog is functional, when creating manually a vdi via "qemu-img" and than using as disk in libvirt. The error looks like this: internal error missing backend for pool type 9 The