Trying to install KVM via Yast fails.

English Virtualization
#1

Clean installation of Tumbleweed Gnome, trying to install KVM via the ‘Install Hypervisor and Tools’ option in yast, leads to an immediate error

Error! package Installation failed.

I’ve run KVM before on this PC so I’m not sure what the issue is?

#2

Not sure if this is any use, however, when I try to install KVM via Yast, in dmesg I see:

Jun 29 17:02:01 beano YaST.desktop[12198]: Qt: Session management error: None of the authentication protocols specified are supported
Jun 29 17:02:05 beano YaST.desktop[12198]: Run command: /sbin/yast2 virtualization &
Jun 29 17:02:06 beano org.gnome.Shell.desktop[1760]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2800005 specified for 0x2800009 (YaST2 - vi).
Jun 29 17:02:12 beano YaST.desktop[12198]: /sbin/yast2: line 448: 12267 Aborted (core dumped) $ybindir/y2start $module “$@” “$SELECTED_GUI” $Y2_GEOMETRY $Y2UI_ARGS

#3

Unless you’re unlucky enough to be subject to TW’s periodic unreliability due to a new modification,

  1. You should always fully update your system before installing virtualization. In rolling release (TW), this means you should execute(I have mixed feelings about any “no vendor change” settings)
zypper dup
  1. After updating, reboot. Then try installing virtualization through YaST again.

TSU

#4

Unfortunately, this is the second installation I’v tried installing KVM, with the same results. The most recent install, as mentioned in the OP, is a standard Gnome install from the latest snapshot and with a zypper dup prior to trying the KVM install. Do you have any idea why yast may be core dumping when trying to run this installer?

#5

The error messages you posted suggest a permissions problem,
And, ordinarily installing virtualization using YaST has nothing to do with the Desktop.

Am mystified why you might see that error if you’re launching YaST “normally.”

Out of curiosity, you night try this…

  1. Launch an elevated console by first opening a console then “su”
    2a. Launch yast (GUI) by entering the following
yast2 virtualization %

2b. If the above doesn’t work which should closely mirror ordinarily launching YaST… Then try launching YaST in text mode. Instead of “yast2” type the same command invoking “yast” as follows

yast virtualization %

TSU

#6

Searching the forums for “$@” “$SELECTED_GUI” $Y2_GEOMETRY $Y2UI_ARGS I found that this could be wayland related. Try opening a terminal window and do

su -c /sbin/yast2

.

#7

Running Yast in an su terminal, with either command, results in the same message:

root@beano
 /home/puk --> $ yast2 virtualization %
YaST2 vm
--------

Install Hypervisor and Tools

This YaST2 module does not support the command line interface.

Warning: unable to close filehandle properly: Bad file descriptor, <STDIN> line
    7 during global destruction (#1)
    (S io) There were errors during the implicit close() done on a filehandle
    when its reference count reached zero while it was still open, e.g.:
    
        {
            open my $fh, '>', $file  or die "open: '$file': $!
";
            print $fh $data or die "print: $!";
        } # implicit close here
    
    Because various errors may only be detected by close() (e.g. buffering could
    allow the print in this example to return true even when the disk is full),
    it is dangerous to ignore its result. So when it happens implicitly, perl will
    signal errors by warning.
    
    Prior to version 5.22.0, perl ignored such errors, so the common idiom shown
    above was liable to cause silent data loss.
    
root@beano
 /home/puk --> $ yast virtualization %
YaST2 vm
--------

Install Hypervisor and Tools

This YaST2 module does not support the command line interface.

Warning: unable to close filehandle properly: Bad file descriptor, <STDIN> line
    7 during global destruction (#1)
    (S io) There were errors during the implicit close() done on a filehandle
    when its reference count reached zero while it was still open, e.g.:
    
        {
            open my $fh, '>', $file  or die "open: '$file': $!
";
            print $fh $data or die "print: $!";
        } # implicit close here
    
    Because various errors may only be detected by close() (e.g. buffering could
    allow the print in this example to return true even when the disk is full),
    it is dangerous to ignore its result. So when it happens implicitly, perl will
    signal errors by warning.
    
    Prior to version 5.22.0, perl ignored such errors, so the common idiom shown
    above was liable to cause silent data loss.

I can enter the text based Yast UI with sudo yast/yast2 and run the virtualisation installer but the result is the same.

#8

This command runs yast but the KVM install still fails.

The console output is:

 ~ --> $ su -c /sbin/yast2
Password: 
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
Qt: Session management error: None of the authentication protocols specified are supported