From: Gottfried <gottfried@posteo.de>
To: Chris Keschnat <chris@catsu.it>, help-guix@gnu.org
Subject: Re: Virtualisation: Network problems
Date: Mon, 26 Sep 2022 18:05:31 +0000 [thread overview]
Message-ID: <35aae352-02cb-d346-4d61-9ac4650b2d84@posteo.de> (raw)
In-Reply-To: <8635cep00o.fsf@catsu.it>
[-- Attachment #1.1.1: Type: text/plain, Size: 7269 bytes --]
Hallo Chris,
I am writing in English, so that everybody can understand it.
> Hi Gottfried,
> is virtlogd running?
>
> I am not sure how it is/was started, but it is running on my system.
>
> #+begin_src sh
> ck@beehive ~ $ ps -ef | grep virtlog
> root 986 1 0 17:34 ? 00:00:00
> /gnu/store/v53l9k5badh84mf6arhhk76f0pa6ly46-libvirt-8.6.0/sbin/virtlogd
> - -f /gnu/store/7sd588q79rhdwvq8wypx5n2finsn8gsf-virtlogd.conf
> #+end_src
If I do a:
gfp@Tuxedo ~$ ps -ef | grep virtlog
it comes up with:
gfp 5233 5218 0 19:45 pts/0 00:00:00 grep --color=auto
virtlog (the word "virtlog" is in red colour)
root@Tuxedo ~# ps -ef | grep virtlog
root 5396 5392 0 19:55 pts/0 00:00:00 grep --color=auto
virtlog (the word "virtlog" is in red colour)
I don't know if that means virtlogd is running?
Gottfried
Am 26.09.22 um 18:29 schrieb Chris Keschnat:
>
> Gottfried <gottfried@posteo.de> writes:
>
>> [[PGP Signed Part:Undecided]]
>> Hi Chris,
>
>> thanks for your answer
>
>> does:
>>> ~sudo virsh net-list~ show a network?
>
>> yes, it shows a network: ("ja" means yes)
>
>> gfp@Tuxedo ~$ sudo virsh net-list
>> Name Status Automatischer Start Bleibend
>> ----------------------------------------------------
>> network Aktiv ja ja
>
>
>> Gottfried
>
>
>
>> ----------------------------------------------------
>> From: Chris Keschnat <chris@catsu.it>
>> To: help-guix@gnu.org
>> Subject: Re: Virtualisation: Network problems
>> Message-ID: <8635celpyy.fsf@catsu.it>
>> Content-Type: text/plain; charset=utf-8
>
>
>> Gottfried <gottfried@posteo.de> writes:
>
>> > [[PGP Signed Part:Undecided]]
>> > Hi Guixers,
>> >
>> > Basic details of my Virtualisation setup:
>> >
>> > Name: QEUMU/KVM
>> > Libvirt URL: qemu:///System
>> > Autoconnect yes
>> > -------------------------------------
>> > Network selection
>> > It gives me 3 options:
>> >
>> > 1. I added a virtual network
>> > Name: network
>> > Device: virbr0 is there
>> > IPv4 configuration is there
>> >
>> > Details:
>> >
>> > <network>
>> > <name>network</name>
>> > <uuid>e324aabf-6ad4-4407-9028-82c96be96e0c</uuid>
>> > <forward mode="nat">
>> > <nat>
>> > <port start="1024" end="65535"/>
>> > </nat>
>> > </forward>
>> > <bridge name="virbr0" stp="on" delay="0"/>
>> > <mac address="52:54:00:16:e9:74"/>
>> > <domain name="network"/>
>> > <ip address="192.168.100.1" netmask="255.255.255.0">
>> > <dhcp>
>> > <range start="192.168.100.128" end="192.168.100.254"/>
>> > </dhcp>
>> > </ip>
>> > </network>
>> >
>> > 2. Bridge device
>> > 3. Macvtap device
>> >
>> > I guess the 1. option is the one I need. May be I made a mistake in
>> > adding a virtual network
>> > -------------------------------------------------------------------
>> >
>> > When I want to set up the QEMU/KVM network connection for the VM
>> > and I want to run the last step(the 5/5 step) of installing an iso
>> > it says:
>> >
>> > Installation konnte nicht fertiggestellt werden/
>> > Installation could not be completed:
>> > Failed connect socket to
>> > '/var/run/libvirt/virtlogd-sock':
>> > No such file or directory
>> > -------------------------------------------------------------------
>> > Installation konnte nicht fertiggestellt werden: «Failed to connect
>> > socket to '/var/run/libvirt/virtlogd-sock': No such file or directory»
>> >
>> > Traceback (most recent call last):
>> > File
>> >
>> "/gnu/store/n3gyjzsylh2abc3ykxz9kf5335azgacr-virt-manager-3.2.0/share/virt-manager/virtManager/asyncjob.py",
>> > line 65, in cb_wrapper
>> > callback(asyncjob, *args, **kwargs)
>> > File
>> >
>> "/gnu/store/n3gyjzsylh2abc3ykxz9kf5335azgacr-virt-manager-3.2.0/share/virt-manager/virtManager/createvm.py",
>> > line 2001, in _do_async_install
>> > installer.start_install(guest, meter=meter)
>> > File
>> >
>> "/gnu/store/n3gyjzsylh2abc3ykxz9kf5335azgacr-virt-manager-3.2.0/share/virt-manager/virtinst/install/installer.py",
>> > line 701, in start_install
>> > domain = self._create_guest(
>> > File
>> >
>> "/gnu/store/n3gyjzsylh2abc3ykxz9kf5335azgacr-virt-manager-3.2.0/share/virt-manager/virtinst/install/installer.py",
>> > line 649, in _create_guest
>> > domain = self.conn.createXML(install_xml or final_xml, 0)
>> > File
>> >
>> "/gnu/store/anh3nz3qr46f0ds5i1pswisrc9s3cf3f-python-libvirt-8.6.0/lib/python3.9/site-packages/libvirt.py",
>> > line 4442, in createXML
>> > raise libvirtError('virDomainCreateXML() failed')
>> > libvirt.libvirtError: Failed to connect socket to
>> > '/var/run/libvirt/virtlogd-sock': No such file or directory
>> > --------------------------------------------------------------------
>> >
>> >
>> > But running the last step:
>> >
>> > Failed to find a suitable default network
>> > -----------------------------------------------
>> >
>> > What are the problems here?
>> > Any suggestions?
>> >
>> > Gottfried
>> >
>> > [2. OpenPGP public key --- application/pgp-keys;
>> OpenPGP_0x61FAF349C9FB7F94.asc]...
>> >
>> > [[End of PGP Signed Part]]
>> -------------------------------------------------------------------------------
>> Hello,
>> does ~sudo virsh net-list~ show a network? I remember having some issues
>> which I never solved "the guix way", only
>> manually.
>
>> If virsh doesn't show a network, you can try (locate a
>> =default.xml= on your machine):
>
>> #+begin_src sh
>
>> sudo virsh net-define
>> /gnu/store/47s1cs65izld791m38aa461s02q5ngb7-libvirt-8.6.0/etc/libvirt/qemu/networks/default.xml
>> sudo virsh net-autostart default
>> sudo virsh net-start default
>
>> #+end_src
>
>
>> Obviously I would prefer a cleaner way, but I haven't looked further
>> into this yet. If anyone knows the answer, I would appreciate it.
>
>> PS: Just for completeness, the =default.xml= looks like this:
>
>> #+begin_src conf
>
>> <network>
>> <name>default</name>
>> <bridge name='virbr0'/>
>> <forward/>
>> <ip address='192.168.122.1' netmask='255.255.255.0'>
>> <dhcp>
>> <range start='192.168.122.2' end='192.168.122.254'/>
>> </dhcp>
>> </ip>
>> </network>
>
>> #+end_src
>
>> [5. OpenPGP public key --- application/pgp-keys; OpenPGP_0x61FAF349C9FB7F94.asc]...
>
>> [[End of PGP Signed Part]]
>
> Hi Gottfried,
> is virtlogd running?
>
> I am not sure how it is/was started, but it is running on my system.
>
> #+begin_src sh
> ck@beehive ~ $ ps -ef | grep virtlog
> root 986 1 0 17:34 ? 00:00:00
> /gnu/store/v53l9k5badh84mf6arhhk76f0pa6ly46-libvirt-8.6.0/sbin/virtlogd
> -f /gnu/store/7sd588q79rhdwvq8wypx5n2finsn8gsf-virtlogd.conf
> #+end_src
>
> PS: I too am German, so I understand.
> PPS: I even use a Tuxedo too! Aura 15 Gen2, pretty happy with it (:
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-09-26 19:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 15:47 Virtualisation: Network problems Gottfried
2022-09-26 16:29 ` Chris Keschnat via
2022-09-26 18:05 ` Gottfried [this message]
2022-10-01 13:32 ` Andreas Enge
2022-10-02 12:47 ` Tobias Geerinckx-Rice
2022-09-27 4:26 ` Chris Keschnat via
2022-09-28 13:08 ` can not boot again VM with tails Gottfried
2022-09-28 14:27 ` Felix Lechner via
2022-09-28 20:59 ` Gottfried
-- strict thread matches above, loose matches on Subject: below --
2022-10-03 11:23 Virtualisation: Network problems Gottfried
2022-09-27 19:02 Gottfried
2022-09-25 17:58 Gottfried
2022-09-26 4:19 ` Chris Keschnat via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35aae352-02cb-d346-4d61-9ac4650b2d84@posteo.de \
--to=gottfried@posteo.de \
--cc=chris@catsu.it \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).