similar to: Xend and libvirt

Hello, On Mon, Aug 3, 2020 at 12:08 PM Daniel P. Berrangé <berrange@redhat.com> wrote: > On Sat, Aug 01, 2020 at 04:51:57PM +0300, David K. Kahurani wrote: > > Hello > > > > On a probably a few days old build of libvirt, it is not possible to > connect to my local system. > > > > The command used is: > > > > $virsh -c xen:///system >

On Mon, Aug 03, 2020 at 01:44:30PM +0300, K. Kahurani wrote: > Hello, > > On Mon, Aug 3, 2020 at 12:08 PM Daniel P. Berrangé <berrange@redhat.com> > wrote: > > > On Sat, Aug 01, 2020 at 04:51:57PM +0300, David K. Kahurani wrote: > > > Hello > > > > > > On a probably a few days old build of libvirt, it is not possible to > > connect to

On Sat, Aug 01, 2020 at 04:51:57PM +0300, David K. Kahurani wrote: > Hello > > On a probably a few days old build of libvirt, it is not possible to connect to my local system. > > The command used is: > > $virsh -c xen:///system > > The errors can be seen from libvirtd logs[1] an interesting part being: > " > Aug 01 16:30:13 metal libvirtd[1680]:

I'm setting up for libvirt remote access on a xend host. On the host, xl info | egrep "release|xen_version" release : 5.6.10-24.gde48f93-default xen_version : 4.13.0_12-lp151.700 systemctl --version systemd 234 I've installed rpm -qa libvirt-daemon-xen libvirt-daemon-xen-6.2.0-lp151.890.1.x86_64 libvirtd --version libvirtd (libvirt)

---------- Forwarded message --------- From: K. Kahurani <k.kahurani at gmail.com> Date: Sun, May 31, 2020 at 2:26 PM Subject: Hello To: <eblake at redhat.com> Hello, Hopefully this finds you well. This is not a bug report but more or less an inquiry as based on the information acquired from Jim Fehlig a while back, it is possible you would have some important information regarding

Hi all, I think it's a bug, when call virDomainGetState after "service libvirtd stop", I receive signal SIGPIPE. I want to know how to avoid this problem? And Other interfaces will also encounter this problem？ Below the bt information: Below some information about my hypervisor: root@ubuntu-05:/datapool/zhuohf# virsh -v 3.4.0 root@ubuntu-05:/datapool/zhuohf# qemu-x86_64 -version

Hi all, I'm getting started with hacking around with libvirt and am trying to familiarize myself with launching and running an instance of libvirtd I built from source on Centos 7.6. Following the instructions from https://libvirt.org/compiling.html to launch my built versions of libvirtd and virsh, I get the following error with no other context when trying to start a domain using

Hi all, KubeVirt uses libvirtd to manage qemu VMs represented as Kubernetes API resources. In this case, libvirtd is running inside an unprivileged pod, with some host mounts / capabilities added to the pod, needed by libvirtd and other services. One of the capabilities libvirtd requires for successful startup inside a pod is SYS_RESOURCE. This capability is used to adjust RLIMIT_MEMLOCK ulimit

On Tue, 30 Apr 2019 at 10:40, Michal Privoznik <mprivozn@redhat.com> wrote: > Is there any problem running libvirtd as root? > > Yes, in the regulated environment in which I work! I have to do far more thorough threat analysis than I would do if I knew which capabilities it had. So far, we've accepted the extra work; but it would be wonderful to be able to run a locked-down

Hi, I am currently facing an issue with libvirt w.r.t a guest's state and reason code. Precisely following are steps: 1. I have a running guest named *linux-test *on KVM 2. I do a * $> virsh save linux-test linux-saved.dat* 3. At this point * $> virsh domstate --reason linux-test *shows *shutoff(saved)* 4. I restarted the libvirtd daemon * $>systemctl

Hey, Over in KubeVirt we're investigating a use case where we'd like to perform a live migration within a network namespace that does not provide libvirtd with network access. In this scenario we would like to perform a live migration by proxying the migration through a unix socket to a process in another network namespace that does have network access. That external process would live

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

On Tue, Jul 14, 2020 at 3:33 PM Daniel P. Berrangé <berrange@redhat.com> wrote: > On Tue, Jul 14, 2020 at 03:21:17PM +0300, Ram Lavi wrote: > > Hello all, > > > > tl;dr, can you point me to the point in the libvirt repo where it's > trying > > to change a tap-device's SELinux label? > > > > I am trying to create a tap device with libvirt on

Hi all, I'm using libvirt-go and I following code to listen for lifecycle events: func event_listen() { log.Printf("event_listen %s", conf.Libvirt.LocalUrl) hv, err := libvirt.NewConnect(conf.Libvirt.LocalUrl) lifecycleCallback := func(c *libvirt.Connect, d *libvirt.Domain, event *libvirt.DomainEventLifecycle) { event_message(c, d, "lifecycle", event)

Hello all, tl;dr, can you point me to the point in the libvirt repo where it's trying to change a tap-device's SELinux label? I am trying to create a tap device with libvirt on a super-privileged container, and then use it on another, unprivileged container with libvirt. User wise, I know I need the super-privileged container to open the tap device with the user of the unprivileged one -

On Wed, Aug 29, 2018 at 4:55 AM, Daniel P. Berrangé <berrange@redhat.com> wrote: > On Tue, Aug 28, 2018 at 05:07:18PM -0400, David Vossel wrote: > > Hey, > > > > Over in KubeVirt we're investigating a use case where we'd like to > perform > > a live migration within a network namespace that does not provide > libvirtd > > with network access.

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

No, I'm not, I'm calling it sooner: func libvirt_start() { libvirt.EventRegisterDefaultImpl() event_listen() } S pozdravom / Best regards Daniel Kucera. 2017-05-17 15:47 GMT+02:00 Daniel P. Berrange <berrange@redhat.com>: > On Wed, May 17, 2017 at 03:41:09PM +0200, Daniel Kučera wrote: > > Hi Daniel, > > > > I tried that but it doesn't

Hi! I found little semantics bug: [13:53:40] root@dedicated-04:~ # LC_ALL=C libvirtd -h libvirtd: invalid option -- 'h' Usage: libvirtd [options] Options: -v | --verbose Verbose messages. -d | --daemon Run as a daemon & write PID file. -l | --listen Listen for TCP/IP connections. -t | --timeout <secs> Exit after timeout period. -f |

Hello, We are currently facing a strange situation. One of our VM is shown by 'virsh list' as in state "in shutdown" but there is no more a qemu-kvm process linked to it. So we have a few questions: 1. What does means the state in shutdown (I have not found much information about it)? 2. How to cleanly "shutdown" the vm, or more correctly, clean the status in