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]: Failed to connect socket to '/var/run/libvirt/virtxend-sock':> Aug 01 16:30:13 metal libvirtd[1680]: End of file while reading data: Input/output error ">From the log, libxl driver is trying to connect to a socket which is tagged xend.My host is running Xen 5.1+ release from which Xend has been removed. Xend was removed from Xen in 4.5+ release, at least according to the docs[2] "xl was introduced in the Xen 4.1 release, however xend remained the default. At the time of the Xen 4.2 release, xend was declared deprecated and xl became the default toolstack. xend has finally been removed from the Xen 4.5 release" Any ideas would be much appreciated! Sincerely, David 1. https://termbin.com/l1br 2. https://wiki.xen.org/wiki/XL
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]: Failed to connect socket to '/var/run/libvirt/virtxend-sock':> > Aug 01 16:30:13 metal libvirtd[1680]: End of file while reading data: Input/output error " > > From the log, libxl driver is trying to connect to a socket which is tagged xend.This is the new virtxend daemon provided by libvirt, not the old XenD of years gone by. What args did you pass to configure ? We shouldn't be trying to connect to this socket by default - we should be using libvirtd still - unless you changed args to configure. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
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 > > > > The errors can be seen from libvirtd logs[1] an interesting part being: > > " > > Aug 01 16:30:13 metal libvirtd[1680]: Failed to connect socket to > '/var/run/libvirt/virtxend-sock':> > > Aug 01 16:30:13 metal libvirtd[1680]: End of file while reading data: > Input/output error " > > > > From the log, libxl driver is trying to connect to a socket which is > tagged xend. > > This is the new virtxend daemon provided by libvirt, not the old XenD of > years > gone by. > > What args did you pass to configure ? We shouldn't be trying to connect to > this socket by default - we should be using libvirtd still - unless you > changed args to configure. >configure was not directly used but rather autogen. ./autogen --system Thanks a lot for the insight!> Regards, > Daniel > -- > |: https://berrange.com -o- > https://www.flickr.com/photos/dberrange :| > |: https://libvirt.org -o- > https://fstop138.berrange.com :| > |: https://entangle-photo.org -o- > https://www.instagram.com/dberrange :| > >