similar to: Reply: Fail in virDomainUpdateDeviceFlags (libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10)

Hello Everyone, My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10 ALL-in-One. I use python-sdk with libvirt and run [self.domain.updateDeviceFlags(xml, libvirt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). However, I enable libvirt debug log , the log as below: "2018-02-26 13:09:13.638+0000: 50524: debug :

On Tue, Feb 27, 2018 at 09:53:00 +0100, Michal Privoznik wrote: > On 02/27/2018 03:06 AM, Star Guo wrote: > > Hello Everyone, > > > > > > > > My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph > > 10.2.10 ALL-in-One. > > > > > > > > I use python-sdk with libvirt and run [self.domain.updateDeviceFlags(xml,

On 02/27/2018 03:06 AM, Star Guo wrote: > Hello Everyone, > > > > My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph > 10.2.10 ALL-in-One. > > > > I use python-sdk with libvirt and run [self.domain.updateDeviceFlags(xml, > libvirt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). > However, I enable libvirt debug log

On Fri, Mar 02, 2018 at 15:32:44 -0500, John Ferlan wrote: > > > On 03/02/2018 08:28 AM, Peter Krempa wrote: > > On Tue, Feb 27, 2018 at 09:53:00 +0100, Michal Privoznik wrote: > >> On 02/27/2018 03:06 AM, Star Guo wrote: > >>> Hello Everyone, > >>> > >>> > >>> > >>> My pc run in CentOS 7.4 and install

On 03/02/2018 08:28 AM, Peter Krempa wrote: > On Tue, Feb 27, 2018 at 09:53:00 +0100, Michal Privoznik wrote: >> On 02/27/2018 03:06 AM, Star Guo wrote: >>> Hello Everyone, >>> >>> >>> >>> My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph >>> 10.2.10 ALL-in-One. >>> >>> >>>

On 03/05/2018 03:47 AM, Peter Krempa wrote: > On Fri, Mar 02, 2018 at 15:32:44 -0500, John Ferlan wrote: >> >> >> On 03/02/2018 08:28 AM, Peter Krempa wrote: >>> On Tue, Feb 27, 2018 at 09:53:00 +0100, Michal Privoznik wrote: >>>> On 02/27/2018 03:06 AM, Star Guo wrote: >>>>> Hello Everyone, >>>>> >>>>>

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

On 11/15/2017 06:54 AM, Holger Schranz wrote: > Thread 1 (Thread 0x7f4a069cc700 (LWP 10178)): > #0 0x00007f49ff969170 in qemuDomainChangeEjectableMedia ( > driver=driver@entry=0x7f49f841b700, vm=vm@entry=0x7f49ec02fbd0, > disk=disk@entry=0x7f49ec0375d0, newsrc=0x7f49e8014d10, force=force@entry=false) > at qemu/qemu_hotplug.c:303 This is fixed in current upstream by

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:

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

On Tue, Nov 14, 2017 at 07:19:01PM +0100, Holger Schranz wrote: > Ups ... my fault ... > > libvirtd instead libvirt .... > > > etcsvms5:/var/lib/systemd/coredump # coredumpctl info libvirtd >            PID: 10177 (libvirtd) >            UID: 0 (root) >            GID: 0 (root) >         Signal: 11 (SEGV) >      Timestamp: Tue 2017-11-14 10:11:32 CET (9h ago)

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

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

Here is v11. Fixed comments/bugs and updated against the latest libvirt.git. Changes v10->v11: - fixed comments on each patches - fixed cgroup handling in patch 3. - fixed MODIFY_CURRENT handling in patch 4. most of diff comes from refactoring qemu/qemu_driver.c -- conf/domain_conf.c | 40 ++ conf/domain_conf.h | 5 libvirt_private.syms | 3 qemu/qemu_driver.c | 727

Hi Michal, Looking in the logs, it looks like the libvirt process sent a sigkill to the qemu process: 2013-10-11 19:59:22.132+0000: 10212: debug : virLockManagerAcquire:358 : lock=0x7f6bc80de170 state='(null)' flags=3 action=0 fd=0x7f6bdf3bf074 2013-10-11 19:59:22.132+0000: 10212: debug : virLockManagerFree:395 : lock=0x7f6bc80de170 2013-10-11 19:59:22.132+0000: 10212: debug :

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

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

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