similar to: VM creation using libvirtd for the qemu-KVM hypervisor

Hi, I am trying to migrate a running instance, but it fails with the following error: $ virsh migrate --live instance-00000008 qemu+tcp://10.2.3.150/system --verbose error: operation failed: migration job: unexpectedly failed I can see following in the instance specific qemu log directory (/var/log/libvirt/qemu/instance-00000008.log) on the destination host: 2012-04-12 03:57:26.211: starting up

Hi all. I run into trouble, while try to start libvirtd inside docker container (actually it is LXC container). During startup libvirtd can't load shared library libvirt-qemu.so.0 (and strace results looks very odd). * I run libvirtd as root. * libvirt-bin - 0.9.8-2ubuntu17 * selinux/apparmor both disabled. * No other security extension are used. * No sticky bits are set. * Required library

Hi, >From a KVM guest, I want to retrieve the hostname of the host on which the hypervisor is running. Before doing that by using libvirt API, I first try via virsh. So, I run virsh and the run hostname command.( got that in virsh help : .... hostname print the hypervisor hostname ....) Unfortunately, I got following error when starting virsh : error: Failed to

Thanks, I discovered I had wrong permissions for /var/lib/libvirt/qemu/, after setting them to drwxr-x--x. qemu qemu and executing daemon-reload libvirtd.service exists now on my vms :) However - I'm not able to get it to run. In the journal I see the message libvirtd[6800]: Unable to import CA certificate list /etc/pki/vdsm/certs/cacert.pem I have verified its permissions and that it's

On 5/13/20 12:59 PM, Dana Elfassy wrote: > Thanks, Michal, > On my laptop I do have libguestfs and libvirt-daemon-qemu. both > libvirtd.service and libvirtd.socket are running ok on my laptop > I just realized I haven't mentioned - my vms intend to serve as hosts > themselves, and that's why they, too, need to have libvirtd.service > running on them. > up to

Hi, This is what I tried : Y , how enter an answer in the thread ?) virsh -c qemu+ssh://127.0.0.1:22/system hostname root@127.0.0.1's<mailto:root@127.0.0.1's> password: error: End of file while reading data: : Input/output error error: failed to connect to the hypervisor In another hand ,as we have few information to share , I was thinking to use a virtio channel to

On 04/21/2015 05:53 PM, Matthew Schumacher wrote: > On 04/20/2015 05:42 PM, Laine Stump wrote: >> Well, this is when the qemu process is killed (I'm pretty clever, eh? :-) >> >> I have 3 questions: >> >> 1) what version of libvirt are you running and on what distro? >> >> 2) can you reproduce this reliably? >> >> 3) If the answer to 2 is

Thanks, Michal, On my laptop I do have libguestfs and libvirt-daemon-qemu. both libvirtd.service and libvirtd.socket are running ok on my laptop I just realized I haven't mentioned - my vms intend to serve as hosts themselves, and that's why they, too, need to have libvirtd.service running on them. up to recently I didn't have such a problem when I installed a vm on my laptop -

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. > When I killall > libvirtd then my VM's keep running, but then when I start libvirtd it > calls qemuDomainObjEndJob:1542 : Stopping job: modify

On Tue, May 12, 2020 at 01:00:06PM +0300, Dana Elfassy wrote: > Hi all, > Some background: > I recently has some issues with libvirt on my laptop when I got the error > 'operation failed: pool 'default' already exists with uuid > dd48b6ad-9a00-46eb-a3a4-c122d8a294a5' when I connected virt-manager. I was > finally able to resolve it yesterday, when I removed

On 5/12/20 1:41 PM, Dana Elfassy wrote: > if I understand correctly then I shouldn't have installed libvirt-daemon > on the guests VMs? > > Just a little background to Daniel's response. Libvirt and QEMU treat guests as black boxes, to some extent. There are some exceptions to this rule, when it comes to para-virtualization (that is when the guest knows it is running

On 04/28/2015 06:03 PM, Matthew Schumacher wrote: > > On 04/22/2015 08:19 AM, Laine Stump wrote: >> If you're compiling yourself, then you should be all set to run under >> gdb. libvirt-debuginfo is just a separate subpackage that contains all >> the symbol and line number info from the build so that backtraces in >> gdb make sense. Try attaching gdb to the

Hello, it is safe to use centos 7 qemu-kvm-ev repo with new one for libvirt 3.0 https://cbs.centos.org/repos/virt7-libvirt-latest-release/x86_64/os/Packages/? Anybody using it? Thanks. -- S pozdravem Kristi?n Feldsam -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Tue, May 12, 2020 at 02:25:29PM +0300, Dana Elfassy wrote: > Thanks, Daniel > I verified I had libvirt-daemon rpm on my laptop and reloaded its units, > but that didn't solve the issue. I then checked the vms- > libvirt-daemon rpm was indeed missing on my vms. After I installed it & > reloaded its unit files libvirtd.service was found, but as I started it, > the error

Thanks, Daniel I verified I had libvirt-daemon rpm on my laptop and reloaded its units, but that didn't solve the issue. I then checked the vms- libvirt-daemon rpm was indeed missing on my vms. After I installed it & reloaded its unit files libvirtd.service was found, but as I started it, the error 'operation failed: pool 'default' already exists with uuid

How can I disable libvirtd from attempting to suspend VMs on poweroff / reboot? It is slowly filling up our /var/ filesystem with save points at /var/lib/libvirt/qemu/save/<vm name>.save, even though I'm not initiating any suspend or restore functionality. I checked /etc/libvirt/libvirtd.conf and /etc/libvirt/qemu.conf but could not find anything. This is CentOS 5 with libvirt

Hi all, Some background: I recently has some issues with libvirt on my laptop when I got the error 'operation failed: pool 'default' already exists with uuid dd48b6ad-9a00-46eb-a3a4-c122d8a294a5' when I connected virt-manager. I was finally able to resolve it yesterday, when I removed libvirt and all its related content in /etc/libvirt, removed the pool by its UUID, deleted virbr0

Hi, In KubeVirt we are right now starting libvirt via a wrapper shell script. I want to remove that wrapper and directly start libvirtd from our golang code. This means that our golang code is PID 1 in the container and we start libvirtd as a fork from there. When I did this, strange things started to happen. Libvirt was still able to start and manage qemu processes, but stopping the qemu

On 04/22/2015 08:19 AM, Laine Stump wrote: > If you're compiling yourself, then you should be all set to run under > gdb. libvirt-debuginfo is just a separate subpackage that contains all > the symbol and line number info from the build so that backtraces in > gdb make sense. Try attaching gdb to the libvirtd process and do > something like "thread apply all bt" - if

Package: xen-hypervisor-4.6-amd64 Version: 4.6.0-1 Severity: normal Dear maintaners, I was using XEN 4.4 on that machine ("unstable") and want to switch to 4.6. All xen stuff was uninstalled (XEN 4.4), the machine restarted before installing 4.6. When I uninstall XEN 4.4 (libxenlight4.4) it deinstall also part of QEMU and when I reinstall QEMU libxenlight-4.4 aws reinstalled. First