Warning : Failed to set up UEFI / The Libvirt version does not support UEFI / Install options are limited...
Mario Marietto
marietto2008 at gmail.com
Mon Aug 28 19:22:45 UTC 2023
Two packages were missing : gir1.2-vte-2.91 ; girl1.2-gtk-vnc-2.0
and I have reached the same point that pushed me to follow your advice to
recompile libvirt. Do you remember where we started ? What was the error
that I needed to fix ? well,I walked a long road to meet him again :
[Mon, 28 Aug 2023 18:57:46 virt-manager 2664] DEBUG (createvm:494)
UEFI found, setting it as default.
[Mon, 28 Aug 2023 18:57:46 virt-manager 2664] DEBUG (createvm:728)
Guest type set to os_type=hvm, arch=armv7l, dom_type=kvm
[Mon, 28 Aug 2023 18:57:46 virt-manager 2664] DEBUG (guest:546) Prefer
EFI => True
[Mon, 28 Aug 2023 18:57:47 virt-manager 2664] DEBUG
(domcapabilities:250) Error fetching domcapabilities XML
Traceback (most recent call last):
File "/usr/local/share/virt-manager/virtinst/domcapabilities.py", line
245, in build_from_params
xml = conn.getDomainCapabilities(emulator, arch,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/libvirt.py", line 4612, in
getDomainCapabilities
raise libvirtError('virConnectGetDomainCapabilities() failed')
libvirt.libvirtError: KVM is not supported on this platform: Function
not implemented
[Mon, 28 Aug 2023 18:57:48 virt-manager 2664] DEBUG
(domcapabilities:250) Error fetching domcapabilities XML
Traceback (most recent call last):
File "/usr/local/share/virt-manager/virtinst/domcapabilities.py", line
245, in build_from_params
xml = conn.getDomainCapabilities(emulator, arch,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/libvirt.py", line 4612, in
getDomainCapabilities
raise libvirtError('virConnectGetDomainCapabilities() failed')
libvirt.libvirtError: KVM is not supported on this platform: Function
not implemented
[Mon, 28 Aug 2023 18:57:48 virt-manager 2664] DEBUG (createvm:497)
Error checking for UEFI default
Traceback (most recent call last):
File "/usr/local/share/virt-manager/virtManager/createvm.py", line
491, in _set_caps_state
guest.enable_uefi()
File "/usr/local/share/virt-manager/virtinst/guest.py", line 589, in enable_uefi
path = self._lookup_default_uefi_path()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/share/virt-manager/virtinst/guest.py", line 848, in
_lookup_default_uefi_path
raise RuntimeError(_("Libvirt version does not support UEFI."))
RuntimeError: Libvirt version does not support UEFI.
[Mon, 28 Aug 2023 18:57:48 virt-manager 2664] DEBUG (storage:136)
Found default pool name=default target=/var/lib/libvirt/images
[Mon, 28 Aug 2023 18:57:48 virt-manager 2664] DEBUG (storage:136)
Found default pool name=default target=/var/lib/libvirt/images
[Mon, 28 Aug 2023 18:57:48 virt-manager 2664] DEBUG (engine:316)
window counter incremented to 2
[Mon, 28 Aug 2023 18:57:49 virt-manager 2664] DEBUG (connection:691)
storage pool refresh event: pool=default
[Mon, 28 Aug 2023 18:57:49 virt-manager 2664] DEBUG (connection:691)
storage pool refresh event: pool=default
On Mon, Aug 28, 2023 at 8:11 PM Mario Marietto <marietto2008 at gmail.com>
wrote:
> I've appended the parameter debug to understand which error could be
> behind and I found it...please scroll until the end,because as soon as
> virt-manager is launched,I don't see errors. But I see the error in the
> exact moment when I press on "create a new virtual machine",but for clarity
> I have pasted all the error message that I've got :
>
>
> root at chromarietto:/home/marietto/Desktop# virt-manager --debug
> >virt-manager_debug
>
> [Mon, 28 Aug 2023 18:03:06 virt-manager 2305] DEBUG (cli:204) Version
> 4.1.0 launched with command line: /usr/l
> ocal/bin/virt-manager --debug
> [Mon, 28 Aug 2023 18:03:06 virt-manager 2305] DEBUG (virtmanager:167)
> virt-manager version: 4.1.0
> [Mon, 28 Aug 2023 18:03:06 virt-manager 2305] DEBUG (virtmanager:168)
> virtManager import: /usr/local/share/vir
> t-manager/virtManager
> [Mon, 28 Aug 2023 18:03:06 virt-manager 2305] DEBUG (virtmanager:205)
> PyGObject version: 3.42.2
> [Mon, 28 Aug 2023 18:03:06 virt-manager 2305] DEBUG (virtmanager:209) GTK
> version: 3.24.37
> [Mon, 28 Aug 2023 18:03:07 virt-manager 2305] DEBUG (systray:84) Imported
> AppIndicator3=<IntrospectionModule '
> AyatanaAppIndicator3' from
> '/usr/lib/arm-linux-gnueabihf/girepository-1.0/AyatanaAppIndicator3-0.1.typelib'>
>
> [Mon, 28 Aug 2023 18:03:07 virt-manager 2305] DEBUG (systray:86)
> AppIndicator3 is available, but didn't find a
> ny dbus watcher.
> [Mon, 28 Aug 2023 18:03:32 virt-manager 2305] DEBUG (systray:476) Showing
> systray: False
> [Mon, 28 Aug 2023 18:03:32 virt-manager 2305] DEBUG (inspection:206)
> python guestfs is not installed
> [Mon, 28 Aug 2023 18:03:32 virt-manager 2305] DEBUG (engine:113) Loading
> stored URIs:
> qemu:///system
> [Mon, 28 Aug 2023 18:03:32 virt-manager 2305] DEBUG (engine:461)
> processing cli command uri= show_window=manag
> er domain=
> [Mon, 28 Aug 2023 18:03:32 virt-manager 2305] DEBUG (engine:464) No cli
> action requested, launching default wi
> ndow
> [Mon, 28 Aug 2023 18:03:32 virt-manager 2305] DEBUG (manager:185) Showing
> manager
> [Mon, 28 Aug 2023 18:03:32 virt-manager 2305] DEBUG (engine:316) window
> counter incremented to 1
> [Mon, 28 Aug 2023 18:03:32 virt-manager 2305] DEBUG (engine:211) Initial
> gtkapplication activated
> [Mon, 28 Aug 2023 18:03:32 virt-manager 2305] DEBUG (connection:482)
> conn=qemu:///system changed to state=Conn
> ecting
> [Mon, 28 Aug 2023 18:03:32 virt-manager 2305] DEBUG (connection:903)
> Scheduling background open thread for qem
> u:///system
> [Mon, 28 Aug 2023 18:03:34 virt-manager 2305] DEBUG (connection:128)
> libvirt URI versions library=9.7.0 driver
> =9.7.0 hypervisor=5.1.0
> [Mon, 28 Aug 2023 18:03:36 virt-manager 2305] DEBUG (connection:109)
> Fetched capabilities for qemu:///system:
> <capabilities>
>
> <host>
> <uuid>0e585e61-2cd2-4823-9130-1548b0aac8d6</uuid>
> <cpu>
> <arch>armv7l</arch>
> <topology sockets='1' dies='1' cores='2' threads='1'/>
> <pages unit='KiB' size='4'/>
> </cpu>
> <power_management>
> <suspend_mem/>
> </power_management>
> <iommu support='yes'/>
> <migration_features>
> <live/>
> <uri_transports>
> <uri_transport>tcp</uri_transport>
> <uri_transport>rdma</uri_transport>
> </uri_transports>
> </migration_features>
> <topology>
> <cells num='1'>
> <cell id='0'>
> <memory unit='KiB'>1012436</memory>
> <cpus num='2'>
> <cpu id='0' socket_id='0' die_id='0' core_id='0' siblings='0'/>
> <cpu id='1' socket_id='0' die_id='0' core_id='1' siblings='1'/>
> </cpus>
> </cell>
> </cells>
> </topology>
> <secmodel>
> <model>none</model>
> <doi>0</doi>
> </secmodel>
> <secmodel>
> <model>dac</model>
> <doi>0</doi>
> <baselabel type='kvm'>+1002:+1002</baselabel>
> <baselabel type='qemu'>+1002:+1002</baselabel>
> </secmodel>
> </host>
>
> <guest>
> <os_type>hvm</os_type>
> <arch name='armv6l'>
> <wordsize>32</wordsize>
> <emulator>/usr/local/bin/qemu-system-arm</emulator>
> <machine maxCpus='512'>virt-5.1</machine>
> <machine canonical='virt-5.1' maxCpus='512'>virt</machine>
> <machine maxCpus='2'>ast2600-evb</machine>
> <machine maxCpus='1'>borzoi</machine>
> <machine maxCpus='1'>spitz</machine>
> <machine maxCpus='255'>virt-2.7</machine>
> <machine maxCpus='2'>nuri</machine>
> <machine maxCpus='2'>mcimx7d-sabre</machine>
> <machine maxCpus='1'>romulus-bmc</machine>
> <machine maxCpus='512'>virt-3.0</machine>
> <machine maxCpus='512'>virt-5.0</machine>
> <machine maxCpus='255'>virt-2.10</machine>
> <machine maxCpus='2'>musca-b1</machine>
> <machine maxCpus='255'>virt-2.8</machine>
> <machine maxCpus='4'>realview-pbx-a9</machine>
> <machine maxCpus='1'>versatileab</machine>
> <machine maxCpus='1'>kzm</machine>
> <machine maxCpus='2'>musca-a</machine>
> <machine maxCpus='512'>virt-3.1</machine>
> <machine maxCpus='1'>mcimx6ul-evk</machine>
> <machine maxCpus='2'>smdkc210</machine>
> <machine maxCpus='1'>sx1</machine>
> <machine maxCpus='4'>raspi2</machine>
> <machine maxCpus='255'>virt-2.11</machine>
> <machine maxCpus='1'>imx25-pdk</machine>
> <machine maxCpus='255'>virt-2.9</machine>
> <machine maxCpus='4'>orangepi-pc</machine>
> <machine maxCpus='1'>z2</machine>
> <machine maxCpus='1'>xilinx-zynq-a9</machine>
> <machine maxCpus='1'>tosa</machine>
> <machine maxCpus='255'>virt-2.12</machine>
> <machine maxCpus='2'>mps2-an521</machine>
> <machine maxCpus='4'>sabrelite</machine>
> <machine maxCpus='1'>mps2-an511</machine>
> <machine maxCpus='1'>canon-a1100</machine>
> <machine maxCpus='1'>realview-eb</machine>
> <machine maxCpus='1'>emcraft-sf2</machine>
> <machine maxCpus='1'>realview-pb-a8</machine>
> <machine maxCpus='512'>virt-4.0</machine>
> <machine maxCpus='1'>palmetto-bmc</machine>
> <machine maxCpus='1'>sx1-v1</machine>
> <machine maxCpus='1'>n810</machine>
> <machine maxCpus='2'>tacoma-bmc</machine>
> <machine maxCpus='1'>n800</machine>
> <machine maxCpus='512'>virt-4.1</machine>
> <machine maxCpus='1'>versatilepb</machine>
> <machine maxCpus='1'>terrier</machine>
> <machine maxCpus='1'>mainstone</machine>
> <machine maxCpus='4'>realview-eb-mpcore</machine>
> <machine maxCpus='1'>integratorcp</machine>
> <machine maxCpus='512'>virt-4.2</machine>
> <machine maxCpus='1'>witherspoon-bmc</machine>
> <machine maxCpus='1'>swift-bmc</machine>
> <machine maxCpus='4'>vexpress-a9</machine>
> <machine maxCpus='4'>midway</machine>
> <machine maxCpus='1'>musicpal</machine>
> <machine maxCpus='1'>lm3s811evb</machine>
> <machine maxCpus='1'>lm3s6965evb</machine>
> <machine maxCpus='1'>microbit</machine>
> <machine maxCpus='1'>mps2-an505</machine>
> <machine maxCpus='1'>mps2-an385</machine>
> <machine maxCpus='1'>cubieboard</machine>
> <machine maxCpus='1'>verdex</machine>
> <machine maxCpus='1'>netduino2</machine>
> <machine maxCpus='4'>vexpress-a15</machine>
> <machine maxCpus='1'>sonorapass-bmc</machine>
> <machine maxCpus='1'>cheetah</machine>
> <machine maxCpus='255'>virt-2.6</machine>
> <machine maxCpus='1'>ast2500-evb</machine>
> <machine maxCpus='4'>highbank</machine>
> <machine maxCpus='1'>akita</machine>
> <machine maxCpus='1'>connex</machine>
> <machine maxCpus='1'>netduinoplus2</machine>
> <machine maxCpus='1'>collie</machine>
> <domain type='qemu'/>
> <domain type='kvm'/>
> </arch>
> <features>
> <cpuselection/>
> <deviceboot/>
> <disksnapshot default='on' toggle='no'/>
> <externalSnapshot/>
> </features>
> </guest>
>
> <guest>
> <os_type>hvm</os_type>
> <arch name='armv7l'>
> <wordsize>32</wordsize>
> <emulator>/usr/local/bin/qemu-system-arm</emulator>
> <machine maxCpus='512'>virt-5.1</machine>
> <machine canonical='virt-5.1' maxCpus='512'>virt</machine>
> <machine maxCpus='2'>ast2600-evb</machine>
> <machine maxCpus='1'>borzoi</machine>
> <machine maxCpus='1'>spitz</machine>
> <machine maxCpus='255'>virt-2.7</machine>
> <machine maxCpus='2'>nuri</machine>
> <machine maxCpus='2'>mcimx7d-sabre</machine>
> <machine maxCpus='1'>romulus-bmc</machine>
> <machine maxCpus='512'>virt-3.0</machine>
> <machine maxCpus='512'>virt-5.0</machine>
> <machine maxCpus='255'>virt-2.10</machine>
> <machine maxCpus='2'>musca-b1</machine>
> <machine maxCpus='255'>virt-2.8</machine>
> <machine maxCpus='4'>realview-pbx-a9</machine>
> <machine maxCpus='1'>versatileab</machine>
> <machine maxCpus='1'>kzm</machine>
> <machine maxCpus='2'>musca-a</machine>
> <machine maxCpus='512'>virt-3.1</machine>
> <machine maxCpus='1'>mcimx6ul-evk</machine>
> <machine maxCpus='2'>smdkc210</machine>
> <machine maxCpus='1'>sx1</machine>
> <machine maxCpus='4'>raspi2</machine>
> <machine maxCpus='255'>virt-2.11</machine>
> <machine maxCpus='1'>imx25-pdk</machine>
> <machine maxCpus='255'>virt-2.9</machine>
> <machine maxCpus='4'>orangepi-pc</machine>
> <machine maxCpus='1'>z2</machine>
> <machine maxCpus='1'>xilinx-zynq-a9</machine>
> <machine maxCpus='1'>tosa</machine>
> <machine maxCpus='255'>virt-2.12</machine>
> <machine maxCpus='2'>mps2-an521</machine>
> <machine maxCpus='4'>sabrelite</machine>
> <machine maxCpus='1'>mps2-an511</machine>
> <machine maxCpus='1'>canon-a1100</machine>
> <machine maxCpus='1'>realview-eb</machine>
> <machine maxCpus='1'>emcraft-sf2</machine>
> <machine maxCpus='1'>realview-pb-a8</machine>
> <machine maxCpus='512'>virt-4.0</machine>
> <machine maxCpus='1'>palmetto-bmc</machine>
> <machine maxCpus='1'>sx1-v1</machine>
> <machine maxCpus='1'>n810</machine>
> <machine maxCpus='2'>tacoma-bmc</machine>
> <machine maxCpus='1'>n800</machine>
> <machine maxCpus='512'>virt-4.1</machine>
> <machine maxCpus='1'>versatilepb</machine>
> <machine maxCpus='1'>terrier</machine>
> <machine maxCpus='1'>mainstone</machine>
> <machine maxCpus='4'>realview-eb-mpcore</machine>
> <machine maxCpus='1'>integratorcp</machine>
> <machine maxCpus='512'>virt-4.2</machine>
> <machine maxCpus='1'>witherspoon-bmc</machine>
> <machine maxCpus='1'>swift-bmc</machine>
> <machine maxCpus='4'>vexpress-a9</machine>
> <machine maxCpus='4'>midway</machine>
> <machine maxCpus='1'>musicpal</machine>
> <machine maxCpus='1'>lm3s811evb</machine>
> <machine maxCpus='1'>lm3s6965evb</machine>
> <machine maxCpus='1'>microbit</machine>
> <machine maxCpus='1'>mps2-an505</machine>
> <machine maxCpus='1'>mps2-an385</machine>
> <machine maxCpus='1'>cubieboard</machine>
> <machine maxCpus='1'>verdex</machine>
> <machine maxCpus='1'>netduino2</machine>
> <machine maxCpus='4'>vexpress-a15</machine>
> <machine maxCpus='1'>sonorapass-bmc</machine>
> <machine maxCpus='1'>cheetah</machine>
> <machine maxCpus='255'>virt-2.6</machine>
> <machine maxCpus='1'>ast2500-evb</machine>
> <machine maxCpus='4'>highbank</machine>
> <machine maxCpus='1'>akita</machine>
> <machine maxCpus='1'>connex</machine>
> <machine maxCpus='1'>netduinoplus2</machine>
> <machine maxCpus='1'>collie</machine>
> <domain type='qemu'/>
> <domain type='kvm'/>
> </arch>
> <features>
> <cpuselection/>
> <deviceboot/>
> <disksnapshot default='on' toggle='no'/>
> <externalSnapshot/>
> </features>
> </guest>
>
> </capabilities>
>
> [Mon, 28 Aug 2023 18:03:36 virt-manager 2305] DEBUG (connection:739) Using
> domain events
> [Mon, 28 Aug 2023 18:03:36 virt-manager 2305] DEBUG (connection:778) Using
> network events
> [Mon, 28 Aug 2023 18:03:36 virt-manager 2305] DEBUG (connection:797) Using
> storage pool events
> [Mon, 28 Aug 2023 18:03:36 virt-manager 2305] DEBUG (connection:822) Using
> node device events
> [Mon, 28 Aug 2023 18:03:36 virt-manager 2305] DEBUG (connection:691)
> storage pool refresh event: pool=default
> [Mon, 28 Aug 2023 18:03:36 virt-manager 2305] DEBUG (connection:1072)
> network=default status=Active added
> [Mon, 28 Aug 2023 18:03:36 virt-manager 2305] DEBUG (connection:1072)
> pool=default status=Active added
> [Mon, 28 Aug 2023 18:03:36 virt-manager 2305] DEBUG (storage:136) Found
> default pool name=default target=/var/lib/libvirt/images
> [Mon, 28 Aug 2023 18:03:36 virt-manager 2305] DEBUG (connection:482)
> conn=qemu:///system changed to state=Active
> [Mon, 28 Aug 2023 18:03:46 virt-manager 2305] DEBUG (xmleditor:12) Using
> GtkSource 4
>
>
> *This is the error that happens when I press on Start a new virtual machine :*
>
>
>
> [Mon, 28 Aug 2023 18:03:47 virt-manager 2305] DEBUG (cli:195) Uncaught
> exception:
> Traceback (most recent call last):
> File "/usr/local/share/virt-manager/virtManager/details/serialcon.py",
> line 16, in <module>
> gi.require_version("Vte", "2.91")
> File "/usr/lib/python3/dist-packages/gi/__init__.py", line 126, in
> require_version
> raise ValueError('Namespace %s not available' % namespace)
> ValueError: Namespace Vte not available
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/usr/local/share/virt-manager/virtManager/manager.py", line 451, in
> new_vm
> from .createvm import vmmCreateVM
> File "/usr/local/share/virt-manager/virtManager/createvm.py", line 31, in
> <module>
> from .vmwindow import vmmVMWindow
> File "/usr/local/share/virt-manager/virtManager/vmwindow.py", line 15, in
> <module>
> from .details.console import vmmConsolePages
> File "/usr/local/share/virt-manager/virtManager/details/console.py", line
> 13, in <module>
> from .serialcon import vmmSerialConsole
> File "/usr/local/share/virt-manager/virtManager/details/serialcon.py",
> line 19, in <module>
> gi.require_version("Vte", "2.90")
> File "/usr/lib/python3/dist-packages/gi/__init__.py", line 126, in
> require_version
> raise ValueError('Namespace %s not available' % namespace)
> ValueError: Namespace Vte not available
>
>
>
> On Mon, Aug 28, 2023 at 7:31 PM Mario Marietto <marietto2008 at gmail.com>
> wrote:
>
>> Hello.
>>
>> I made another progress. I've recompiled the kernel again,I have enabled
>> more iptables options and now virt-manager has been able to create the
>> bridge for me :
>>
>> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
>> inet 192.168.122.1 netmask 255.255.255.0 broadcast
>> 192.168.122.255
>> ether 52:54:00:bc:6c:69 txqueuelen 1000 (Ethernet)
>> RX packets 0 bytes 0 (0.0 B)
>> RX errors 0 dropped 0 overruns 0 frame 0
>> TX packets 0 bytes 0 (0.0 B)
>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>
>> So,now network works,qemu and kvm works,but now I don't know what to do
>> because when I try to create a new virtual machine going in FIle / New
>> Virtual Machine,nothing happens. There could be an additional problem,but I
>> don't see errors. What can I do to see which kind of problem there could be
>> under the hood ?
>>
>> PS : I've accessed the chromebook using : ssh -Y root at 192.168.1.6 and
>> then I ran "virt-manager" as root. Is this wrong ?
>>
>>
>> On Mon, Aug 28, 2023 at 4:27 PM Mario Marietto <marietto2008 at gmail.com>
>> wrote:
>>
>>> Thanks very much. You are very gentle and helpful.
>>>
>>> I've fixed the PolicyKit problem in this way :
>>>
>>> In :
>>>
>>> /usr/share/polkit-1/actions/org.libvirt.unix.policy
>>>
>>>
>>> I have changed this :
>>>
>>> <action id="org.libvirt.unix.manage">
>>> <description>Manage local virtualized systems</description>
>>> <message>System policy prevents management of local virtualized systems</message>
>>> <defaults>
>>> <!-- Any program can use libvirt in read/write mode if they
>>> provide the root password -->
>>> <allow_any>auth_admin_keep</allow_any>
>>> <allow_inactive>auth_admin_keep</allow_inactive>
>>> <allow_active>auth_admin_keep</allow_active>
>>> </defaults>
>>> </action>
>>>
>>>
>>>
>>> to this :
>>>
>>> <action id="org.libvirt.unix.manage">
>>> <description>Manage local virtualized systems</description>
>>> <message>System policy prevents management of local virtualized systems</message>
>>> <defaults>
>>> <!-- Any program can use libvirt in read/write mode if they
>>> provide the root password -->
>>> <allow_any>yes</allow_any>
>>> <allow_inactive>yes</allow_inactive>
>>> <allow_active>yes</allow_active>
>>> </defaults>
>>> </action>
>>>
>>>
>>> and boom : QEMU and KVM are connected now. Now,another problem has
>>> emerged. When I click on "File / New Virtual Machine",nothing happens.
>>> At this point,I did :
>>>
>>>
>>> sudo virsh net-info default
>>>
>>> then :
>>>
>>> sudo virsh net-start default
>>>
>>>
>>> and a lot of shit came out from the manhole [image: :D]:
>>>
>>> Error starting network 'default': internal error:
>>> Failed to apply firewall rules /usr/sbin/iptables -w --table mangle --list-rules: iptables v1.8.9 (legacy):
>>> can't initialize iptables table `mangle': Table does not exist (do you need to insmod?)
>>> Perhaps iptables or your kernel needs to be upgraded.
>>>
>>>
>>> Traceback (most recent call last):
>>> File "/usr/local/share/virt-manager/virtManager/asyncjob.py", line 71, in cb_wrapper
>>> callback(asyncjob, *args, **kwargs)
>>> File "/usr/local/share/virt-manager/virtManager/asyncjob.py", line 107, in tmpcb
>>> callback(*args, **kwargs)
>>> File "/usr/local/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
>>> ret = fn(self, *args, **kwargs)
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^
>>> File "/usr/local/share/virt-manager/virtManager/object/network.py", line 69, in start
>>> self._backend.create()
>>> File "/usr/lib/python3/dist-packages/libvirt.py", line 3547, in create
>>> raise libvirtError('virNetworkCreate() failed')
>>> libvirt.libvirtError: internal error: Failed to apply firewall rules /usr/sbin/iptables -w --table mangle --list-rules: iptables v1.8.9 (legacy): can't initialize iptables table `mangle': Table does not exist (do you need to insmod?)
>>> Perhaps iptables or your kernel needs to be upgraded.
>>>
>>> and :
>>>
>>> *marietto at chromarietto*:*~*$ sudo virsh net-info default
>>>
>>> Name: default
>>>
>>> UUID: 7c4408b7-5125-4c98-9d53-f1fe109371e3
>>>
>>> Active: no
>>>
>>> Persistent: yes
>>>
>>> Autostart: yes
>>>
>>> Bridge: virbr0
>>>
>>> *marietto at chromarietto*:*~*$ sudo virsh net-start default
>>>
>>> error: Failed to start network default
>>>
>>> error: internal error: Failed to apply firewall rules /usr/sbin/iptables
>>> -w --table mangle --list-rules: iptables v1.8.9 (legacy): can't
>>> initialize iptables table `mangle': Table does not exist (do you need to
>>> insmod?). Perhaps iptables or your kernel needs to be upgraded.
>>>
>>>
>>> I tried to fix it with this :
>>>
>>>
>>> $ modprobe iptable_mangle
>>> modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/5.4.244-stb-cbe
>>>
>>>
>>> so,some options should be enabled inside the kernel,for sure.
>>>
>>> I have configured the option "MANGLE" to yes when I have recompiled the kernel the last time :
>>>
>>> CONFIG_IP_NF_MANGLE=y
>>> CONFIG_IP_NF_ARP_MANGLE=y
>>> CONFIG_IP6_NF_MANGLE=y
>>>
>>>
>>> "unfortunately" I'd configured it correctly,so the error should depend
>>> on something else.
>>> It would have been too easy to fix the error so fast. Suggestions ?
>>>
>>> On Mon, Aug 28, 2023 at 1:16 PM Pavel Hrdina <phrdina at redhat.com> wrote:
>>>
>>>> On Sun, Aug 27, 2023 at 06:06:59PM +0200, Mario Marietto wrote:
>>>> > If I don't launch virtqemud,this is what I have :
>>>>
>>>> Yeah you never want to run libvirtd and virtqemud at the same time, more
>>>> info here <https://libvirt.org/daemons.html>.
>>>>
>>>> > marietto at chromarietto:~$ libvirtd &
>>>>
>>>> This will not work as expected. If you want to use system connection you
>>>> need to run libvirtd as root user.
>>>>
>>>> > [1] 2083
>>>> >
>>>> > marietto at chromarietto:~$ virt-manager
>>>> >
>>>> >
>>>> > A new error comes out :
>>>> >
>>>> > Unable to connect to libvirt qemu:///system.
>>>> >
>>>> > error from service:
>>>> GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed:
>>>> > Action org.libvirt.unix.manage is not registered
>>>> >
>>>> > Libvirt URI is: qemu:///system
>>>> >
>>>> > Traceback (most recent call last):
>>>> > File "/usr/local/share/virt-manager/virtManager/connection.py", line
>>>> > 923, in _do_open
>>>> > self._backend.open(cb, data)
>>>> > File "/usr/local/share/virt-manager/virtinst/connection.py", line
>>>> 171, in open
>>>> > conn = libvirt.openAuth(self._open_uri,
>>>> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>> > File "/usr/lib/python3/dist-packages/libvirt.py", line 147, in
>>>> openAuth
>>>> > raise libvirtError('virConnectOpenAuth() failed')
>>>> > libvirt.libvirtError: error from service:
>>>> > GDBus.Error:org.freedesktop.PolicyKit1.
>>>> > Error.Failed: Action org.libvirt.unix.manage is not registered
>>>>
>>>> This is polkit trying to authenticate that your user can connect to
>>>> system connection, libvirt running with root privileges, but you started
>>>> libvirtd as normal user.
>>>>
>>>> The error that "org.libvirt.unix.manage is not registered" means there
>>>> is no process handling that polkit action as there is no libvirtd
>>>> running as root.
>>>>
>>>> Pavel
>>>>
>>>> > On Sun, Aug 27, 2023 at 1:00 AM Mario Marietto <
>>>> marietto2008 at gmail.com>
>>>> > wrote:
>>>> >
>>>> > > Is there someone that can help me ? thanks.
>>>> > >
>>>> > > # sudo usermod -a -G libvirt root
>>>> > > # sudo usermod -a -G libvirtd root
>>>> > > # sudo usermod -a -G libvirt-qemu libvirt-qemu
>>>> > > # sudo usermod -a -G libvirt marietto
>>>> > > # sudo adduser libvirt-qemu
>>>> > > # sudo groupadd --system libvirt
>>>> > > # sudo groupadd --system libvirt-qemu
>>>> > > # sudo newgrp libvirt-qemu
>>>> > > # newgrp libvirt
>>>> > >
>>>> > > # /usr/local/sbin# libvirtd &
>>>> > > [1] 2875
>>>> > >
>>>> > > # virtqemud &
>>>> > > [2] 2906
>>>> > >
>>>> > > # /usr/local/sbin# 2023-08-26 22:53:10.190+0000: 2923: info :
>>>> libvirt version: 9.7.0
>>>> > >
>>>> > > 2023-08-26 22:53:10.190+0000: 2923: info : hostname: chromarietto
>>>> > > 2023-08-26 22:53:10.190+0000: 2923: error :
>>>> virPidFileAcquirePathFull:409 :
>>>> > > Failed to acquire pid file '/var/local/run/libvirt/qemu/driver.pid':
>>>> > > Resource temporarily unavailable
>>>> > > 2023-08-26 22:53:10.192+0000: 2923: error : virStateInitialize:672 :
>>>> > > Initialization of QEMU state driver failed: Failed to acquire pid
>>>> file
>>>> > > '/var/local/run/libvirt/qemu/driver.pid': Resource temporarily
>>>> unavailable
>>>> > > 2023-08-26 22:53:10.192+0000: 2923: error : daemonRunStateInit:617 :
>>>> > > Driver state initialization failed
>>>> > >
>>>> > > # /usr/local/sbin# ps ax | grep libvirt
>>>> > > 2875 pts/0 Sl 0:00 libvirtd
>>>> > >
>>>> > > # /usr/local/sbin# ps ax | grep virtqemu
>>>> > >
>>>> > >
>>>> > > On Fri, Aug 25, 2023 at 11:43 PM Mario Marietto <
>>>> marietto2008 at gmail.com>
>>>> > > wrote:
>>>> > >
>>>> > >> The real problem seems to be that the libvirtd process won't start
>>>> :
>>>> > >>
>>>> > >> marietto at chromarietto:~$ systemctl enable libvirtd
>>>> > >>
>>>> > >> ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files
>>>> ====
>>>> > >> Authentication is required to manage system service or unit files.
>>>> > >> Multiple identities can be used for authentication:
>>>> > >> 1. linux
>>>> > >> 2. mario,,, (marietto)
>>>> > >> Choose identity to authenticate as (1-2): 2
>>>> > >> Password:
>>>> > >> ==== AUTHENTICATION COMPLETE ====
>>>> > >>
>>>> > >> marietto at chromarietto:~$ systemctl start libvirtd
>>>> > >>
>>>> > >> ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
>>>> > >> Authentication is required to start 'libvirtd.service'.
>>>> > >> Multiple identities can be used for authentication:
>>>> > >> 1. linux
>>>> > >> 2. mario,,, (marietto)
>>>> > >> Choose identity to authenticate as (1-2): 2
>>>> > >> Password:
>>>> > >> ==== AUTHENTICATION COMPLETE ====
>>>> > >>
>>>> > >> marietto at chromarietto:~$ systemctl status libvirtd
>>>> > >>
>>>> > >> ○ libvirtd.service - Virtualization daemon
>>>> > >> Loaded: loaded (/usr/local/lib/systemd/system/libvirtd.service;
>>>> > >> enabled; preset: enabled)
>>>> > >> Active: inactive (dead) since Fri 2023-08-25 21:04:37 UTC; 2s
>>>> ago
>>>> > >> Duration: 88ms
>>>> > >> TriggeredBy: ● libvirtd-admin.socket
>>>> > >> ● libvirtd-ro.socket
>>>> > >> ● libvirtd.socket
>>>> > >> Docs: man:libvirtd(8)
>>>> > >> https://libvirt.org
>>>> > >> Process: 3488 ExecStart=/usr/local/sbin/libvirtd $LIBVIRTD_ARGS
>>>> > >> (code=exited, status=0/SUCCESS)
>>>> > >> Main PID: 3488 (code=exited, status=0/SUCCESS)
>>>> > >> CPU: 252ms
>>>> > >>
>>>> > >> As you can see,it says "inactive". This is the reason :
>>>> > >>
>>>> > >> Aug 25 21:22:59 chromarietto libvirtd[3663]: invalid argument:
>>>> Failed to
>>>> > >> parse user 'libvirt-qemu'
>>>> > >> Aug 25 21:22:59 chromarietto libvirtd[3663]: Initialization of QEMU
>>>> > >> state driver failed: invalid argument: Failed to parse user
>>>> 'libvirt-qemu'
>>>> > >> Aug 25 21:22:59 chromarietto libvirtd[3663]: Driver state
>>>> initialization
>>>> > >> failed
>>>> > >> Aug 25 21:22:59 chromarietto systemd[1]: libvirtd.service:
>>>> Deactivated
>>>> > >> successfully.
>>>> > >>
>>>> > >> On Fri, Aug 25, 2023 at 10:27 PM Mario Marietto <
>>>> marietto2008 at gmail.com>
>>>> > >> wrote:
>>>> > >>
>>>> > >>> I think that what I found is very interesting :
>>>> > >>>
>>>> > >>> marietto at chromarietto:~/Desktop/Dati/new/libvirt/build$
>>>> systemctl start
>>>> > >>> virtqemud
>>>> > >>>
>>>> > >>> ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
>>>> > >>> Authentication is required to start 'virtqemud.service'.
>>>> > >>> Multiple identities can be used for authentication:
>>>> > >>> 1. linux
>>>> > >>> 2. mario,,, (marietto)
>>>> > >>> Choose identity to authenticate as (1-2): 2
>>>> > >>> Password:
>>>> > >>> ==== AUTHENTICATION COMPLETE ====
>>>> > >>>
>>>> > >>> marietto at chromarietto:~/Desktop/Dati/new/libvirt/build$ systemctl
>>>> > >>> enable virtqemud
>>>> > >>>
>>>> > >>> ==== AUTHENTICATING FOR
>>>> org.freedesktop.systemd1.manage-unit-files ====
>>>> > >>> Authentication is required to manage system service or unit files.
>>>> > >>> Multiple identities can be used for authentication:
>>>> > >>> 1. linux
>>>> > >>> 2. mario,,, (marietto)
>>>> > >>> Choose identity to authenticate as (1-2): 2
>>>> > >>> Password:
>>>> > >>> ==== AUTHENTICATION COMPLETE ====
>>>> > >>>
>>>> > >>> marietto at chromarietto:~/Desktop/Dati/new/libvirt/build$ ls
>>>> > >>> /var/local/run/libvirt/virtqemud-sock
>>>> > >>> /var/local/run/libvirt/virtqemud-sock
>>>> > >>>
>>>> > >>> but when I launch virt-manager :
>>>> > >>>
>>>> > >>> marietto at chromarietto:~/Desktop/Dati/new/libvirt/build$
>>>> > >>> /usr/local/bin/./virt-manager
>>>> > >>>
>>>> > >>> It tries to connect,but it gets disconnected after a couple of
>>>> seconds
>>>> > >>> and the error "Failed to connect socket to
>>>> > >>> '/var/run/libvirt/virtqemud-sock': No such file or directory' is
>>>> shown
>>>> > >>> again.
>>>> > >>>
>>>> > >>> In addition,virtqemud-sock is deleted :
>>>> > >>>
>>>> > >>> marietto at chromarietto:~/Desktop/Dati/new/libvirt/build$ ls
>>>> > >>> /var/local/run/libvirt/virtqemud-sock
>>>> > >>> ls: cannot access '/var/local/run/libvirt/virtqemud-sock': No
>>>> such file
>>>> > >>> or directory
>>>> > >>>
>>>> > >>>
>>>> > >>> The same problem I have has been found here and solved :
>>>> > >>>
>>>> > >>>
>>>> > >>>
>>>> https://unix.stackexchange.com/questions/715726/virsh-list-throw-error-failed-to-connect-socket-to-var-run-libvirt-virtqemud
>>>> > >>>
>>>> > >>> On Fri, Aug 25, 2023 at 8:34 PM Mario Marietto <
>>>> marietto2008 at gmail.com>
>>>> > >>> wrote:
>>>> > >>>
>>>> > >>>> I don't agree with some of your assumptions,for example :
>>>> > >>>>
>>>> > >>>> 1) to send a screenshot is most of the time more informative
>>>> than copy
>>>> > >>>> and paste text,because it contains more information. To describe
>>>> > >>>> complicated situations using only words takes a LOT of
>>>> time,sometimes.
>>>> > >>>> Especially for the newbies,that aren't so skilled and they may
>>>> have some
>>>> > >>>> difficulty in including or not some information. And even for
>>>> the lack of a
>>>> > >>>> technical language.
>>>> > >>>>
>>>> > >>>> 2) From my experience, going to irc to ask for help can be a
>>>> problem
>>>> > >>>> for the time zone. Every time I tried to go to an IRC
>>>> channel,I've always
>>>> > >>>> found bots and not talking users.
>>>> > >>>>
>>>> > >>>> 3) The rejection of emails happens even if I don't attach any
>>>> > >>>> screenshots (a thing that I do rarely),and my messages are also
>>>> rejected
>>>> > >>>> because when I hit reply also all the story is attached. I think
>>>> that it's
>>>> > >>>> important to attach the story because it may contains important
>>>> details
>>>> > >>>> that could be missed
>>>> > >>>>
>>>> > >>>> On Fri, Aug 25, 2023 at 8:24 PM Eric Blake <eblake at redhat.com>
>>>> wrote:
>>>> > >>>>
>>>> > >>>>> On Fri, Aug 25, 2023 at 07:13:26PM +0200, Mario Marietto wrote:
>>>> > >>>>> > I've sent you an email on your personal email address because
>>>> the ML
>>>> > >>>>> does
>>>> > >>>>> > not accept pictures,but I need to show you a picture to help
>>>> you to
>>>> > >>>>> > understand well. I don't approve this rule of the ML,it does
>>>> not
>>>> > >>>>> help those
>>>> > >>>>> > who want to learn and for this reason need to be exhaustive
>>>> when
>>>> > >>>>> there is a
>>>> > >>>>> > strong need to explain well.
>>>> > >>>>>
>>>> > >>>>> The list has a cap at 300k for a reason. Sending larger
>>>> attachments
>>>> > >>>>> to the list then multiplies out to gigabytes of network data
>>>> when
>>>> > >>>>> counting the number of subscribers, even though many of those
>>>> > >>>>> subscribers are not actively participating in the thread.
>>>> Sending a
>>>> > >>>>> URL to an image hosted externally uses much less bandwidth.
>>>> Also, if
>>>> > >>>>> the problem is something that happens in a terminal window, it
>>>> is less
>>>> > >>>>> bandwidth-intensive to just copy/paste the contents of the
>>>> terminal
>>>> > >>>>> (as text) instead of attaching a screenshot to your email, and
>>>> no less
>>>> > >>>>> informative.
>>>> > >>>>>
>>>> > >>>>> You may also try IRC; there, you can probably get faster
>>>> turnaround
>>>> > >>>>> times than waiting for emails to bounce back and forth.
>>>> > >>>>> https://libvirt.org/contact.html#irc
>>>> > >>>>>
>>>> > >>>>> although at the end of the day, email is more persistent and
>>>> reaches a
>>>> > >>>>> larger audience whereas IRC only reaches whoever is online at
>>>> the time.
>>>> > >>>>>
>>>> > >>>>> --
>>>> > >>>>> Eric Blake, Principal Software Engineer
>>>> > >>>>> Red Hat, Inc.
>>>> > >>>>> Virtualization: qemu.org | libguestfs.org
>>>> > >>>>>
>>>> > >>>>>
>>>> > >>>>
>>>> > >>>> --
>>>> > >>>> Mario.
>>>> > >>>>
>>>> > >>>
>>>> > >>>
>>>> > >>> --
>>>> > >>> Mario.
>>>> > >>>
>>>> > >>
>>>> > >>
>>>> > >> --
>>>> > >> Mario.
>>>> > >>
>>>> > >
>>>> > >
>>>> > > --
>>>> > > Mario.
>>>> > >
>>>> >
>>>> >
>>>> > --
>>>> > Mario.
>>>>
>>>
>>>
>>> --
>>> Mario.
>>>
>>
>>
>> --
>> Mario.
>>
>
>
> --
> Mario.
>
--
Mario.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/virt-tools-list/attachments/20230828/a44bd882/attachment.htm>
More information about the virt-tools-list
mailing list