similar to: Unable to decode message length

Displaying 20 results from an estimated 600 matches similar to: "Unable to decode message length"

2018 Nov 15
1
libvirt call qemu to create vm need more than 10 seconds
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
2013 Sep 18
0
libvirt report error "error: End of file while reading data: Input/output error" when start domain
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
2016 Mar 18
0
Fwd: [Issue]: Regarding client socket getting closed from the server once the lxc container is started
Hi Folks, Using libvirt python bindings we are creating an lxc container.Here is the problem that we see sometimes (say 20 % of the time) when we create a new container. 1.container gets created, and also starts.However the we are not able to enter the namepace of the container.It throws an error initPid not available.We see that the using netstat command , socket connection is closed. 2.To
2015 Oct 02
0
virsh with OSX and virtualbox
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
2016 Apr 12
0
CentOS 6 and 1.3.3
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 :
2013 Jul 14
0
OSX: trying to use libvirt 1.1.0 with VirtualBox 4.2
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
2013 Oct 06
0
libvirt crash when using libxl (xen 4.3)
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
2015 Apr 21
0
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
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. >> >
2015 Apr 21
2
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
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:
2013 Mar 11
1
QEMU+SSH login issue on RHEL 4
Hi All, I am trying to compile libvirt tools from source on RHEL 4. I could get the sources compiled, but when I try to connect to libvirtd using QEMU+SSH I get the following error: error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 With root as the user, I could login, rest other users get the error. All authentication related settings
2013 Feb 07
0
Failed to to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused
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 :
2018 Feb 27
1
Reply: Fail in virDomainUpdateDeviceFlags (libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10)
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
2020 Jul 16
1
Re: Unable to decode message length
Thank you for the help. But here I get exactly the same data as you. So I suppose the issue is on the server side only. I will try with gdb now. On Wed, Jul 15, 2020 at 16:02, Michal Privoznik <mprivozn@redhat.com> wrote: > On 7/14/20 7:42 PM, Valentin David wrote: >> Hello all, >> >> I have been trying to get libvirtd to work but when I connect to it >> with
2019 Feb 08
1
libvirtd (4.9) version takes a long time to start
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
2019 Feb 07
0
libvirtd (4.9) version takes a long time to start
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
2013 Sep 18
1
problem with sheepdog backend when creating a pool
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
2018 Apr 17
0
Re: can't find how to solve "QEMU guest agent is not connected"
On Tue, Apr 17, 2018 at 07:54:14PM +0900, Matt wrote: > I am trying to make Qemu agent work with libvirt thanks to > https://github.com/NixOS/nixops/pull/922 with libvirt 4.1.0. I've been > trying to make it work for quite some time but I still haven't the > slightest idea of what is wrong, I keep seeing "Guest agent is not > responding: QEMU guest agent is not
2018 Apr 17
2
can't find how to solve "QEMU guest agent is not connected"
I am trying to make Qemu agent work with libvirt thanks to https://github.com/NixOS/nixops/pull/922 with libvirt 4.1.0. I've been trying to make it work for quite some time but I still haven't the slightest idea of what is wrong, I keep seeing "Guest agent is not responding: QEMU guest agent is not connected" as the program I use (nixops) calls the libvirt python API. I
2014 Sep 23
0
libvirt crashed by restore of xen vm
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
2007 Jun 28
0
[1095] trunk/wxruby2: Remove useless methods from Wx::Object and add wx_class method for info; document
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!-- #msg dl { border: 1px #006 solid; background: #369; padding: