Tue, 18 Apr 2023 19:07:57 -0400 bent fender <ksusup@trixtar.org> :

Wed, 19 Apr 2023 00:04:22 +0200 Predrag Ivanović <predivan@mts.rs> :

...

On Tue, 18 Apr 2023 16:31:13 -0400 bent fender wrote:

...

As far as I can tell everything needed is installed and up to date but when I click Yast>Virtualizastion>Create-VM (OR command virt-manager) all I get is the virt-manager GUI popup saying

"Unable to connect to libvirt qemu:///system Failed to Connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory"

Check if virtqemud.socket service is enabled, perhaps? FWIW, I am using libvirt on Leap, and that one is disabled, but virt-manager works without issues.

...

"NetworkManager is being used. Bridge configuration must be done manually" (I use usb wifi adapters exclusively)

AFAIK, using wifi for qemu/libvirt networking is possible, but not really recommended. I use 'regular' bridge, as recommended by SUSE docs :)

...

Other related qieuestion:

If my mobo does not support UEFI, does that limit UEFI in a VM i.e. win-11 required TPM and EFI?

Nope, I had Win10,Win11 and some server Windows versions VM's using UEFI/SecureBoot and TPM(with swtpm) on a legacy BIOS machine.

HTH Pedja

Thanks! I found something (way over my head and maybe systemd related) here (down around the last 3rd of the page):

https://libvirt.org/daemons.html

The author suggests a test and the running of virtqemud instead of libvirtd. These tests show that NEITHER is running, which is surprising though it's all chinese to me:

/ # systemctl is-active virtqemud.socket inactive / # systemctl is-active virtqemud.service inactive / # systemctl is-active libvirtd.socket inactive / # systemctl is-active libvirtd.service inactive

So, I suppose I should take some to be doiscovered steps to set virtqemud up to be started each boot?

As for the USB wifi the setup doesn't seem to bother Oracle's VirtualBox under which win-7 connects the internet with a usb-wifi. Initially though I just want to run win-11 deferring sundries until after.

Addendum via answer to my last: # systemctl start virtqemud.service # systemctl is-active virtqemud.service active # virt-manager "Error: No active connection to install on"

Tue, 18 Apr 2023 19:21:15 -0500 Mark Petersen via openSUSE Users <users@lists.opensuse.org> :

On Tuesday, April 18, 2023 3:31:13 PM CDT bent fender wrote:

...

As far as I can tell everything needed is installed and up to date but when I click Yast>Virtualizastion>Create-VM (OR command virt-manager) all I get is the virt-manager GUI popup saying

"Unable to connect to libvirt qemu:///system Failed to Connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory"

The deails blurb says: Unable to connect to libvirt qemu:///system. Failed to connect socket to '/var/run/libvirt/virtqemud-sock': 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: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory

I can launch KVM no probs in Leap-15.4 though

Background: I'm trying to run win-11 and one Yast popup cought my eye:

"NetworkManager is being used. Bridge configuration must be done manually" (I use usb wifi adapters exclusively)

Other related qieuestion:

If my mobo does not support UEFI, does that limit UEFI in a VM i.e. win-11 required TPM and EFI?

Is libvirtd running?

user@computer:~> systemctl status libvirtd

# systemctl status libvirtd Unit libvirtd.service could not be found. # systemctl status virtqemud ○ virtqemud.service - Virtualization qemu daemon Loaded: loaded (/usr/lib/systemd/system/virtqemud.service; disabled; preset: disabled) Active: inactive (dead) TriggeredBy: ○ virtqemud-ro.socket ○ virtqemud.socket ○ virtqemud-admin.socket Docs: man:virtqemud(8) https://libvirt.org Wild guess, package upgrades out of step?

Sorry, some answers keep going out to wrong address This went only to sender: ------------------------------------------ Wed, 19 Apr 2023 10:38:55 -0000 "stefan wannemacher" <swannema@posteo.de> :

You are probably missing the libvirtd-daemon package or one of the libvirtd-daemon subpackages.

Installed everything *libvirt*, no joy, same error :-( I think (BIG mistake) that virtqemu is wanted but don't work? ---------------------------------------------- addendum I *am* having a minor 'locale' issue as well: # virt-manager ~ # (virt-manager:3597): Gtk-WARNING **: 07:30:56.374: Locale not supported by C library. Using the fallback 'C' locale. (virt-manager:3597): Gtk-WARNING **: 07:30:56.384: Theme parsing error: gtk-contained.css:32:432: negative values are not allowed. (virt-manager:3597): Gtk-WARNING **: 07:30:56.393: Theme parsing error: gtk-contained.css:1512:157: Unit is missing. maybe related? # locale locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME=Default.UTF-8 LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=

Wed, 19 Apr 2023 14:41:33 +0300 Andrei Borzenkov <arvidjaar@gmail.com> :

On Wed, Apr 19, 2023 at 2:35 PM bent fender <ksusup@trixtar.org> wrote:

...

LC_TIME=Default.UTF-8

This most certainly does not exist. Let me guess - you are using KDE and tried to configure individual categories in KDE settings. Do not do it :)

I'm on Leap right now where it's the same story, I don't remember what I set manually. I do use kde and do have *recurrent freakin' issues* with me setting en.US* but the system regularly sniffing the box and then inserting Canada into things ...and that often leads to no end of bilinguial keyboards and other such crap! Can this impact on virt-manager?

Have you enabled the libvirtd service to run on systemstart? There was a change in the libvirtd-daemon package when it was updated to 9.1.0, the package was divided into several single packages. I got hit by the same issue and I had to re-enable to service to run automatically.

Wed, 19 Apr 2023 16:47:11 -0000 "stefan wannemacher" <swannema@posteo.de> :

Have you enabled the libvirtd service to run on systemstart? There was a change in the libvirtd-daemon package when it was updated to 9.1.0, the package was divided into several single packages. I got hit by the same issue and I had to re-enable to service to run automatically.

sudo systemctl start libvirtd did it, thanks. Now virt-manager also requires root pwd, which I suppose is normal, but which it didn't before. Should this be a part of launching VM i.e. to check if it's running and start it if not?

Wed, 19 Apr 2023 20:20:03 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> :

On 4/19/23 18:33, bent fender wrote:

...

Wed, 19 Apr 2023 16:47:11 -0000 "stefan wannemacher" <swannema@posteo.de> :

...

Have you enabled the libvirtd service to run on systemstart? There was a change in the libvirtd-daemon package when it was updated to 9.1.0, the package was divided into several single packages. I got hit by the same issue and I had to re-enable to service to run automatically.

sudo systemctl start libvirtd

did it, thanks. Now virt-manager also requires root pwd, which I suppose is normal, but which it didn't before.

Should this be a part of launching VM i.e. to check if it's running and start it if not?

To configure for access as a normal user, see the "Configuration" section of:

https://wiki.archlinux.org/title/Virt-Manager

It's a 'disputed' doc, tried it anyway but it didn't change having to enter root pwd. Not a problem, Yast needs a root pwd too. I'm trying to compose a Suse-KVM-Win11 how2 while at it, I get as far as launching virt-manager and creating a "New VM" with only two other minor stumbles up to that point - having to manually start virt-manager - when done creating, having to also manually start the 'virtual network' (1 click button) So I create a new Win11 virtual machine with the 5/5 steps, on the last page (5) I check the box that says "Customize configuration before instatall" BEFORE continuing with "Finish" which leads to necessairly clicking "Start Virtual Network". I think it's at this point that I'd need to set up TPM as well as Secure-Boot and the "Add Hardware" button in the following and large Prefconfiguration dialog does have a TPM entry with (presumably) good defaults: (Emulated/CRB/Hypervisor default). But how do I set up SecureBoot on this precofig page? Once past TPM/SB bit is when the real cathouse will begin with the rest of the "Pre-Configuration" page which I think will need a LOT of reading/guidance.

Fri, 21 Apr 2023 16:29:35 +0200 Predrag Ivanović <predivan@mts.rs> :

On Thu, 20 Apr 2023 10:45:41 -0400 bent fender wrote:

...

But how do I set up SecureBoot on this precofig page?

IIRC, there is a OS detection when you add the ISO at initial steps, which will set some sane defaults, with UEFI/Secure Boot firmware for Windows 10/11.

...

Once past TPM/SB bit is when the real cathouse will begin with the rest of the "Pre-Configuration" page which I think will need a LOT of reading/guidance.

SUSE Virtualization guide might come in handy for that :) And https://kevinlocke.name/bits/2021/12/10/windows-11-guest-virtio-libvirt/ is one of the better guides I've seen on the matter, FWIW.

Pedja

Thank you very much for the moral support :-) If UEFI/SecureBoot are really taken care of that would in deed be a huge help already! Win-11 is in fact very nicely recognized by pointing the manager to the iso but not so for win-7. I can run 7 very well now on vBox and am trying (K?)VM mainly with win-11 in mind. Win-10 would do also but I figure why not row the front of the line IF I can and be done with it? With this species I get to the point where the first Win-11 window coughs up a bootability problem, I'm just guessing that it doesn't know where the created image-file is? Neither do I because the dialog never asked me where I want to keep it :-) Where is the config file for the newly-created or to-be-created virtual system? Looking at that might tell me something.

Sat, 22 Apr 2023 16:41:12 +0200 Predrag Ivanović <predivan@mts.rs> :

On Sat, 22 Apr 2023 06:33:06 -0400 bent fender wrote:

<snip>

...

With this species I get to the point where the first Win-11 window coughs up a bootability problem, I'm just guessing that it doesn't know where the created image-file is? Neither do I because the dialog never asked me where I want to keep it :-)

It's one of the steps, virt-manager either creates the default size disk image at the default pool, or lets user create it somewhere else. Default pool is at /var/lib/libvirt/images, IIRC.

Yes, found it. When I try to specify the directory where I want the virtual disk image stowed I was expecting vBox-like behavior: like I would set the directory and kvm would set the file-name based on the VM name given it earlier. But there being no file name yet if I just set the directory via this dialog I get an error saying the the filesystem has to be fat. It works if I set not only the directory but also the file-name (with the proper extension) editing it directly into the dialog box.

...

Where is the config file for the newly-created or to-be-created virtual system? Looking at that might tell me something.

XML tab in Overview, for the whole thing, and at every section, for its snippet of configuration. It's read-only by default in the UI.

Where is the complete editable file? It would have helped to look it over in the above situation. Other than this detail I didn't get any further, no time, the launched VM still coughs up a bootiong problem. Later