Tumbleweed: after reinstall of system: creation of connection KVM fails with error message.
particularity: I have the /var/lib/libvirt installed on a RAID 1 on separate hardware. entropy@linux:~> lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 119,2G 0 disk └─md126 9:126 0 119,2G 0 raid1 └─md126p1 259:0 0 119G 0 part /boot/efi sdb 8:16 0 119,2G 0 disk └─md126 9:126 0 119,2G 0 raid1 └─md126p1 259:0 0 119G 0 part /boot/efi sdc 8:32 0 3,6T 0 disk └─sdc1 8:33 0 3,6T 0 part └─md0 9:0 0 3,6T 0 raid1 /var/lib/libvirt sdd 8:48 0 7,3T 0 disk └─sdd1 8:49 0 7,3T 0 part └─md1 9:1 0 7,3T 0 raid1 └─md1p1 259:1 0 7,3T 0 part /home sde 8:64 0 7,3T 0 disk └─sde1 8:65 0 7,3T 0 part └─md1 9:1 0 7,3T 0 raid1 └─md1p1 259:1 0 7,3T 0 part /home sdf 8:80 0 232,9G 0 disk └─sdf1 8:81 0 232,9G 0 part └─md127 9:127 0 232,9G 0 raid1 /var /usr/local /root /srv /boot/grub2/x86_64-efi /boot/grub2/i386-pc /opt / sdg 8:96 0 3,6T 0 disk └─sdg1 8:97 0 3,6T 0 part └─md0 9:0 0 3,6T 0 raid1 /var/lib/libvirt sdh 8:112 1 0B 0 disk sdi 8:128 1 0B 0 disk sdj 8:144 1 0B 0 disk sdk 8:160 1 0B 0 disk sr0 11:0 1 1024M 0 rom normally I did not have any problem in setting up a new system after a reinstall. But now I get: Socket creation for '/var/run/libvirt/virtqemud-sock' failed: No such file or directory Libvirt URI is: qemu:///system Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 925, in _do_open self._backend.open(cb, data) File "/usr/share/virt-manager/virtinst/connection.py", line 171, in open conn = libvirt.openAuth(self._open_uri, File "/usr/lib64/python3.10/site-packages/libvirt.py", line 147, in openAuth raise libvirtError('virConnectOpenAuth() failed') libvirt.libvirtError: Socket creation for '/var/run/libvirt/virtqemud-sock' failed: No such file or directory I am puzzled. Has there been a change in directories of KVM, between var and run? What do I have to do to recover my images that are currently in /var/lib/ libvirt?
I am further getting this error when running "libvirt-manager" from the CLI: (virt-manager:14824): dbind-WARNING **: 20:06:01.359: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files As this is a fresh install, I am thinking that the permissions should be right, I am not really understanding the issue of the message. All I know I cannot establish a working connection in virt manager, the images are all there the files also. The program does not seem to have a permission problem for the images. sudo ls -lah /var/lib/libvirt/ [sudo] password di root: Riprovare. [sudo] password di root: totale 56K drwxr-xr-x 12 root root 4,0K 29 dic 13.26 . drwxr-xr-x 1 root root 836 24 gen 21.24 .. drwx--x--x 2 root root 4,0K 29 dic 13.26 boot drwxr-xr-x 2 root root 4,0K 29 dic 13.26 dnsmasq drwx--x--x 2 root root 4,0K 29 dic 13.26 filesystems drwx--x--x 5 root root 4,0K 29 dic 13.26 images drwx------ 5 root root 4,0K 29 dic 13.26 libxl drwx------ 2 root root 16K 21 dic 2020 lost+found drwx------ 2 root root 4,0K 5 mar 2022 lxc drwx------ 2 root root 4,0K 29 dic 13.26 network drwxr-x--x 13 qemu qemu 4,0K 29 dic 13.26 qemu drwx--x--x 2 root root 4,0K 29 dic 13.26 swtpm ntropy@linux:~> sudo ls -lah /var/lib/libvirt/images totale 2,4T drwx--x--x 5 root root 4,0K 29 dic 13.26 . drwxr-xr-x 12 root root 4,0K 29 dic 13.26 .. -rw------- 1 root root 21G 27 set 2021 android-x86-9.0-2.qcow2 -rw------- 1 root root 21G 17 apr 2021 android-x86-9.0.qcow2 -rw-------+ 1 qemu qemu 1001G 22 gen 21.13 Deepin20.qcow2 -rw------- 1 root root 21G 8 dic 19.53 fedora.qcow2 drwx------ 2 root root 4,0K 1 lug 2017 lost+found -rw------- 1 root root 61G 31 dic 16.08 mageia8.qcow2 drwxr-xr-x 5 root root 4,0K 14 nov 2019 migrated -rw------- 1 root root 501G 5 mag 2021 opensuse.qcow2 -rw------- 1 root root 14G 26 nov 17.17 opensusetumbleweed-clone1.qcow2 -rw------- 1 qemu qemu 49G 24 gen 00.59 opensusetumbleweed-clone.qcow2 -rw------- 1 root root 18G 19 gen 23.51 opensusetumbleweed-clone-update- test.qcow2 -rw------- 1 root root 101G 25 nov 21.54 opensusetumbleweed.qcow2 drwx--x--x 2 root root 4,0K 26 set 19.54 pool -rw------- 1 root root 501G 4 mag 2021 vm1.qcow2 -rw------- 1 root root 23G 20 gen 2020 Windows_7-cloneGarmin-clone.qcow2 -rw------- 1 root root 23G 28 dic 2020 Windows_7-cloneGarmin.qcow2 -rw------- 1 root root 26G 22 lug 2020 Windows_7-clone_OmnipagePro.qcow2 -rw------- 1 root root 23G 17 nov 2020 Windows_7_logitech.qcow2 -rw------- 1 qemu qemu 64G 7 gen 10.30 Windows_7.qcow2 Does anybody see something "A.B. normal" ?
On 2023-01-26 20:14, Stakanov wrote:
As this is a fresh install, I am thinking that the permissions should be right, I am not really understanding the issue of the message.
All I know I cannot establish a working connection in virt manager, the images are all there the files also. The program does not seem to have a permission problem for the images.
Very wild guess. Do the images need to be "run"? If so, maybe the partition must be mounted "exec". mount | grep /var/lib If it says "noexec", maybe you need to change that. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
In data giovedì 26 gennaio 2023 20:26:34 CET, Carlos E. R. ha scritto:
On 2023-01-26 20:14, Stakanov wrote:
As this is a fresh install, I am thinking that the permissions should be right, I am not really understanding the issue of the message.
All I know I cannot establish a working connection in virt manager, the images are all there the files also. The program does not seem to have a permission problem for the images.
Very wild guess. Do the images need to be "run"?
If so, maybe the partition must be mounted "exec".
mount | grep /var/lib
If it says "noexec", maybe you need to change that.
-- Cheers / Saludos,
Carlos E. R.
(from Elesar, using openSUSE Leap 15.4)
says: entropy@linux:~> mount | grep /var/lib /dev/md0 on /var/lib/libvirt type ext4 (rw,relatime,data=ordered) so, that cannot be it.
In data giovedì 26 gennaio 2023 21:31:13 CET, Stakanov ha scritto:
In data giovedì 26 gennaio 2023 20:26:34 CET, Carlos E. R. ha scritto:
On 2023-01-26 20:14, Stakanov wrote:
As this is a fresh install, I am thinking that the permissions should be right, I am not really understanding the issue of the message.
All I know I cannot establish a working connection in virt manager, the images
are all there the files also.
The program does not seem to have a permission problem for the images.
Very wild guess. Do the images need to be "run"?
If so, maybe the partition must be mounted "exec".
mount | grep /var/lib
If it says "noexec", maybe you need to change that.
says:
entropy@linux:~> mount | grep /var/lib /dev/md0 on /var/lib/libvirt type ext4 (rw,relatime,data=ordered)
so, that cannot be it.
This is actually plain stupid. If you use the "convenience pack, or install by "hand" you always end with this because the systemd dipendent services are not active and they have to apparently at systemstartup. Once marked them active, after restarting the system, it is finally possible to create a working connection and recover the former images. I am hesitating if to call that a bug at least for the scripts in the "convenience packet". Because if you install all that, why would you not want to start up the demon to be able to use it?
On 2023-01-27 02:01, Stakanov wrote:
In data giovedì 26 gennaio 2023 21:31:13 CET, Stakanov ha scritto:
In data giovedì 26 gennaio 2023 20:26:34 CET, Carlos E. R. ha scritto:
On 2023-01-26 20:14, Stakanov wrote:
This is actually plain stupid. If you use the "convenience pack, or install by "hand" you always end with this because the systemd dipendent services are not active and they have to apparently at systemstartup. Once marked them active, after restarting the system, it is finally possible to create a working connection and recover the former images.
I am hesitating if to call that a bug at least for the scripts in the "convenience packet". Because if you install all that, why would you not want to start up the demon to be able to use it?
At least, add a README file with the minimal instructions. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
In data venerdì 27 gennaio 2023 11:38:21 CET, Carlos E. R. ha scritto:
On 2023-01-27 02:01, Stakanov wrote:
In data giovedì 26 gennaio 2023 21:31:13 CET, Stakanov ha scritto:
In data giovedì 26 gennaio 2023 20:26:34 CET, Carlos E. R. ha scritto:
On 2023-01-26 20:14, Stakanov wrote:
This is actually plain stupid. If you use the "convenience pack, or install by
"hand" you always end with this because the systemd dipendent
services are not active and they have to apparently at systemstartup. Once marked them active, after restarting the system, it is finally possible to create a working connection and recover the former images.
I am hesitating if to call that a bug at least for the scripts in the "convenience packet". Because if you install all that, why would you not want to start up the demon to be able to use it?
At least, add a README file with the minimal instructions.
-- Cheers / Saludos,
Carlos E. R. (from 15.4 x86_64 at Telcontar)
I think this happens when you reinstall the system and some of the files do exist already (as with me in /var/lib/libvirt. Because AFAIK, the daemons you need are, at least in Leap, started when you install kvm/qemu
On 2023-01-26 19:01:27 Stakanov wrote:
|In data giovedì 26 gennaio 2023 21:31:13 CET, Stakanov ha scritto: |> In data giovedì 26 gennaio 2023 20:26:34 CET, Carlos E. R. ha scritto: |> > On 2023-01-26 20:14, Stakanov wrote: |> > > As this is a fresh install, I am thinking that the permissions |> > > should be |> > > right, I am not really understanding the issue of the message. |> > > |> > > All I know I cannot establish a working connection in virt manager, |> > > the images |> |> are all there the files also. |> |> > > The program does not seem to have a permission problem for the |> > > images. |> > |> > Very wild guess. Do the images need to be "run"? |> > |> > If so, maybe the partition must be mounted "exec". |> > |> > mount | grep /var/lib |> > |> > If it says "noexec", maybe you need to change that. |> |> says: |> |> entropy@linux:~> mount | grep /var/lib |> /dev/md0 on /var/lib/libvirt type ext4 (rw,relatime,data=ordered) |> |> so, that cannot be it. | |This is actually plain stupid. If you use the "convenience pack, or | install by "hand" you always end with this because the systemd dipendent | services are not active and they have to apparently at systemstartup. | Once marked them active, after restarting the system, it is finally | possible to create a working connection and recover the former images. | |I am hesitating if to call that a bug at least for the scripts in the |"convenience packet". Because if you install all that, why would you not | want to start up the demon to be able to use it?
Sounds more like an "INconvenience" pack. :-) Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 x86_64
participants (3)
-
Carlos E. R. -
J Leslie Turriff -
Stakanov