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 :| > >
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 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 --systemI expect you've not started libvirtd and it failed to conenct, as so tried falling back to virtxend which also isn't running. 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 :|
My cc'n you must have been a mistake! Apologies sir! On Mon, Aug 3, 2020 at 2:03 PM Daniel P. Berrangé <berrange@redhat.com> wrote:> 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 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 > > I expect you've not started libvirtd and it failed to conenct, as so tried > falling back to virtxend which also isn't running. > > > 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 :| > >