You are not logged in.

Pages: 1

#1 2023-11-01 10:52:26

Wolfje the wolf
Member
Registered: 2023-10-23
Posts: 6

cant start a vm

like title I cant start a vm, I have it enabled in the bios and the other steps but it doesn't work.
side note i don't use grub, but i don't remember what it was called.
error massage

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 923, 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/lib/python3.11/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

kernel 6.5.9-arch2-1
de Plasma 5.27.9
CPU: AMD Ryzen 9 7950X (32) @ 5.881GHz
GPU: AMD ATI Radeon RX 7900 XT/7900 XT
GPU: AMD ATI 12:00.0 Raphael

Offline

#2 2023-11-01 11:15:36

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,987

Re: cant start a vm

You have followed https://wiki.archlinux.org/title/Libvirt , especially chapter 2.1 & 2.2 ?

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2023-11-01 11:29:22

Wolfje the wolf
Member
Registered: 2023-10-23
Posts: 6

Re: cant start a vm

so 1 of the issues i have is that when i enable libvirtd.service it immediately deactivates.
I can activate it it is installed but will not stay on.

here is message

○ libvirtd.service - Virtualization daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled)
     Active: inactive (dead) since Wed 2023-11-01 12:31:22 CET; 3s ago
   Duration: 11ms
TriggeredBy: ● libvirtd.socket
             ● libvirtd-ro.socket
             ● libvirtd-admin.socket

Last edited by Wolfje the wolf (2023-11-01 11:32:19)

Offline

#4 2023-11-01 12:26:05

loqs
Member
Registered: 2014-03-06
Posts: 18,877

Re: cant start a vm

Wolfje the wolf wrote:

so 1 of the issues i have is that when i enable libvirtd.service it immediately deactivates.

What command did you use to enable the service?

Wolfje the wolf wrote:

I can activate it it is installed but will not stay on.

Please post the journal for libvirtd.service in code tags.  You did not answer Lone_Wolf's question.

Offline

#5 2023-11-01 14:45:06

Wolfje the wolf
Member
Registered: 2023-10-23
Posts: 6

Re: cant start a vm

loqs wrote:

What command did you use to enable the service?

sudo systemctl start libvirtd.service

Loqs wrote:

Please post the journal for libvirtd.service in code tags.

[WolfjeTheWolf@WolfLinuxPc ~]$ sudo systemctl status libvirtd.service
○ libvirtd.service - Virtualization daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled)
     Active: inactive (dead) since Wed 2023-11-01 12:31:22 CET; 3s ago
   Duration: 11ms
TriggeredBy: ● libvirtd.socket
             ● libvirtd-ro.socket
             ● libvirtd-admin.socket
       Docs: man:libvirtd(8)
             https://libvirt.org
    Process: 5575 ExecStart=/usr/bin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS)
   Main PID: 5575 (code=exited, status=0/SUCCESS)
        CPU: 30ms

Nov 01 12:31:22 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 12:31:22 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 12:31:22 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
[WolfjeTheWolf@WolfLinuxPc ~]$ systemctl status virt
Unit virt.service could not be found.
[WolfjeTheWolf@WolfLinuxPc ~]$ systemctl status virt*
● virtlockd.socket - Virtual machine lock manager socket
     Loaded: loaded (/usr/lib/systemd/system/virtlockd.socket; enabled; preset: 
disabled)
     Active: active (listening) since Wed 2023-11-01 13:07:33 CET; 33
min left
   Triggers: ● virtlockd.service
     Listen: /run/libvirt/virtlockd-sock (Stream)
     CGroup: /system.slice/virtlockd.socket

Nov 01 13:07:33 WolfLinuxPc systemd[1]: Listening on Virtual machine lock manage
r socket.

● virtlogd.socket - Virtual machine log manager socket
     Loaded: loaded (/usr/lib/systemd/system/virtlogd.socket; enabled; preset: 
disabled)
     Active: active (listening) since Wed 2023-11-01 13:07:33 CET; 33
min left
   Triggers: ● virtlogd.service
     Listen: /run/libvirt/virtlogd-sock (Stream)
     CGroup: /system.slice/virtlogd.socket

Nov 01 13:07:33 WolfLinuxPc systemd[1]: Listening on Virtual machine log manager
 socket.
Loqs wrote:

You did not answer Lone_Wolf's question.

I went through those step multiple times.

Last edited by Wolfje the wolf (2023-11-01 14:46:00)

Offline

#6 2023-11-01 15:17:55

loqs
Member
Registered: 2014-03-06
Posts: 18,877

Re: cant start a vm

Wolfje the wolf wrote:
loqs wrote:

What command did you use to enable the service?

sudo systemctl start libvirtd.service

That starts the service which is not the same as enabling the service see Systemd#Basic_systemctl_usage.

Wolfje the wolf wrote:
Loqs wrote:

Please post the journal for libvirtd.service in code tags.

[WolfjeTheWolf@WolfLinuxPc ~]$ sudo systemctl status libvirtd.service
○ libvirtd.service - Virtualization daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled)
     Active: inactive (dead) since Wed 2023-11-01 12:31:22 CET; 3s ago
   Duration: 11ms
TriggeredBy: ● libvirtd.socket
             ● libvirtd-ro.socket
             ● libvirtd-admin.socket
       Docs: man:libvirtd(8)
             https://libvirt.org
    Process: 5575 ExecStart=/usr/bin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS)
   Main PID: 5575 (code=exited, status=0/SUCCESS)
        CPU: 30ms

Nov 01 12:31:22 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 12:31:22 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 12:31:22 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
[WolfjeTheWolf@WolfLinuxPc ~]$ systemctl status virt
Unit virt.service could not be found.
[WolfjeTheWolf@WolfLinuxPc ~]$ systemctl status virt*
● virtlockd.socket - Virtual machine lock manager socket
     Loaded: loaded (/usr/lib/systemd/system/virtlockd.socket; enabled; preset: 
disabled)
     Active: active (listening) since Wed 2023-11-01 13:07:33 CET; 33
min left
   Triggers: ● virtlockd.service
     Listen: /run/libvirt/virtlockd-sock (Stream)
     CGroup: /system.slice/virtlockd.socket

Nov 01 13:07:33 WolfLinuxPc systemd[1]: Listening on Virtual machine lock manage
r socket.

● virtlogd.socket - Virtual machine log manager socket
     Loaded: loaded (/usr/lib/systemd/system/virtlogd.socket; enabled; preset: 
disabled)
     Active: active (listening) since Wed 2023-11-01 13:07:33 CET; 33
min left
   Triggers: ● virtlogd.service
     Listen: /run/libvirt/virtlogd-sock (Stream)
     CGroup: /system.slice/virtlogd.socket

Nov 01 13:07:33 WolfLinuxPc systemd[1]: Listening on Virtual machine log manager
 socket.

That is not the journal for libvirtd.service

Wolfje the wolf wrote:

I went through those step multiple times.

What other configuration steps did you perform for libvirt?  Please also post the contents of any configuration files you have modified.

Offline

#7 2023-11-01 18:39:48

Wolfje the wolf
Member
Registered: 2023-10-23
Posts: 6

Re: cant start a vm

loqs wrote:

That starts the service which is not the same as enabling the service see Systemd#Basic_systemctl_usage.

[WolfjeTheWolf@WolfLinuxPc ~]$ systemctl is-enabled libvirtd.service
enabled
Loqs wrote:

Please post the journal for libvirtd.service in code tags.

[WolfjeTheWolf@WolfLinuxPc ~]$ journalctl --since="2023-11-1" --grep=libvirtd.service
Nov 01 10:09:04 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service
: Start request repeated too quickly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service
: Failed with result 'start-limit-hit'.
-- Boot 6be185c6183c450bbaf7465cf5c71b9c --
Nov 01 13:07:43 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 12:26:02 WolfLinuxPc sudo[4998]: WolfjeTheWolf : TTY=pts/1 ; PWD=
/home/WolfjeTheWolf ; USER=root ; COMMAND=/usr/bin/systemctl status libv
irtd.service
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Start request repeated too quickly.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Failed with result 'start-limit-hit'.
Nov 01 12:31:22 WolfLinuxPc sudo[5571]: WolfjeTheWolf : TTY=pts/1 ; PWD=/home/WolfjeTheWolf ; USER=root ; COMMAND=/usr/bin/systemctl start lib
virtd.service
Nov 01 12:31:22 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:31:25 WolfLinuxPc sudo[5600]: WolfjeTheWolf : TTY=pts/1 ; PWD=/home/WolfjeTheWolf ; USER=root ; COMMAND=/usr/bin/systemctl status li
bvirtd.service
-- Boot 22d425acf439470788c822b6c3cae408 --
Nov 01 16:48:21 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Start request repeated too quickly.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Failed with result 'start-limit-hit'.
-- Boot 6d16a35c2eda4f0f9ed443ba00530e97 --
Nov 01 19:18:51 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 19:28:10 WolfLinuxPc sudo[3545]: WolfjeTheWolf : TTY=pts/1 ; PWD=/home/WolfjeTheWolf ; USER=root ; COMMAND=/usr/bin/systemctl enable li
bvirtd.service
Nov 01 19:28:26 WolfLinuxPc sudo[3622]: WolfjeTheWolf : TTY=pts/1 ; PWD=/home/WolfjeTheWolf ; USER=root ; COMMAND=/usr/bin/systemctl status li
bvirtd.service
Nov 01 19:28:34 WolfLinuxPc sudo[3627]: WolfjeTheWolf : TTY=pts/1 ; PWD=/home/WolfjeTheWolf ; USER=root ; COMMAND=/usr/bin/systemctl start lib
virtd.service
Nov 01 19:28:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 19:28:37 WolfLinuxPc sudo[3656]: WolfjeTheWolf : TTY=pts/1 ; PWD=/home/WolfjeTheWolf ; USER=root ; COMMAND=/usr/bin/systemctl status li
bvirtd.service
loqs wrote:

What other configuration steps did you perform for libvirt?  Please also post the contents of any configuration files you have modified.

I will need to look into it and remember, I do know there there was some issue as people use grub which i don't have.

Offline

#8 2023-11-01 18:56:11

loqs
Member
Registered: 2014-03-06
Posts: 18,877

Re: cant start a vm

Does the following return any more output than --grep?

# journalctl --since="2023-11-1" -u libvirtd.service

Offline

#9 2023-11-02 11:04:48

Wolfje the wolf
Member
Registered: 2023-10-23
Posts: 6

Re: cant start a vm

loqs wrote:

Does the following return any more output than --grep?

# journalctl --since="2023-11-1" -u libvirtd.service
[WolfjeTheWolf@WolfLinuxPc ~]$ journalctl --since="2023-11-1" -u libvirtd.service
Nov 01 10:09:04 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 10:09:04 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 10:09:04 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successful
ly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Start request repeated too quickly.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: libvirtd.service: Failed with result 'start-limit-hit'.
Nov 01 11:45:34 WolfLinuxPc systemd[1]: Failed to start Virtualization daemon.
-- Boot 6be185c6183c450bbaf7465cf5c71b9c --
Nov 01 13:07:43 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 13:07:43 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 13:07:43 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Start request repeated too quickly.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: libvirtd.service: Failed with result 'start-limit-hit'.
Nov 01 12:29:50 WolfLinuxPc systemd[1]: Failed to start Virtualization daemon.
Nov 01 12:31:22 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 12:31:22 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 12:31:22 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
-- Boot 22d425acf439470788c822b6c3cae408 --
Nov 01 16:48:21 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 16:48:21 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 16:48:21 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Start request repeated too quickly.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: libvirtd.service: Failed with result 'start-limit-hit'.
Nov 01 15:59:00 WolfLinuxPc systemd[1]: Failed to start Virtualization daemon.
-- Boot 6d16a35c2eda4f0f9ed443ba00530e97 --
Nov 01 19:18:51 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 19:18:51 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 19:18:51 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.
Nov 01 19:28:34 WolfLinuxPc systemd[1]: Starting Virtualization daemon...
Nov 01 19:28:34 WolfLinuxPc systemd[1]: Started Virtualization daemon.
Nov 01 19:28:34 WolfLinuxPc systemd[1]: libvirtd.service: Deactivated successfully.

Offline

#10 2023-11-03 09:58:40

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,987

Re: cant start a vm

from /usr/lib/systemd/system/libvirtd.service

[Service]
Type=notify
Environment=LIBVIRTD_ARGS="--timeout 120"
EnvironmentFile=-/etc/conf.d/libvirtd
ExecStart=/usr/bin/libvirtd $LIBVIRTD_ARGS
ExecReload=/bin/kill -HUP $MAINPID

Disable libvirtd.service , reboot, 
try /usr/bin/libvirtd --timeout 120 directly from a root-terminal*  and post the output .

Note that opening  a terminal as user in GUI and then using su - to switch to root qualifies as 'using a root terminal' in my opinion.


* anything under /usr/lib/systemd/system/ is typically run as root.

Last edited by Lone_Wolf (2023-11-03 10:02:55)

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#11 2023-11-03 14:00:22

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,422

Re: cant start a vm

How about we look at the entire jouranal ofthe boot to identify pot. side-issues bleeding over
Please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Also have we seen /etc/libvirt/libvirtd.conf and /etc/conf.d/libvirtd ?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2023-11-03 14:37:00

loqs
Member
Registered: 2014-03-06
Posts: 18,877

Re: cant start a vm

Also the output of `pacman -Qikk libvirt` for the version and modified files.

Offline

Pages: 1

Board footer

Powered by FluxBB