Re: Virtual Machine Network Connection Confusion

2023-04-04 Thread Peter Boy


> Am 04.04.2023 um 17:51 schrieb Robert McBroom via users 
> :
> 
> Fedora 37 with four qemu/kvm virtual machines. Trying to get internet access 
> from the vm's. Found some advice about using systemd-networkd instead of 
> NetworkManager.

Following „some advice“ is usually a good chance for adventure. What was wrong 
with using Fedora documentation?


>  Lost internet connection with the host. Restored with NetworkManager. 
> Further research on NetworkManager gets into a tangle with ifcfg scripts and 
> the apparent migration to keyfiles.
> 
> Totally confused.
> 
> Can only start the virtual machines if the network device is removed. 
> 
> --
> 
> VM centos8 failed to start
> 
> Requested operation is not valid: network 'default' is not active
> -
> From cockpit on the web interface tried some of the options with bond looking 
> like a possibility
> -
> 11:37 AM
>  [1680622647.3084] dhcp6 (bond0): state changed new lease, 
> address=2600:1702:4860:9dd0::34
> NetworkManager
> 11:27 AM
>  [1680622058.5768] manager: (vnet4): new Tun device 
> (/org/freedesktop/NetworkManager/Devices/9)
> NetworkManager
> 11:07 AM
>  [1680620850.7934] dhcp6 (bond0): state changed new lease, 
> address=2600:1702:4860:9dd0::34
> NetworkManager
> 11:02 AM
>  [1680620556.1938] manager: (vnet3): new Tun device 
> (/org/freedesktop/NetworkManager/Devices/8)
> NetworkManager
> 11:01 AM
>  [1680620475.6234] manager: (vnet2): new Tun device 
> (/org/freedesktop/NetworkManager/Devices/7)
> NetworkManager
> 10:40 AM
>  [1680619204.0043] dhcp6 (bond0): state changed new lease, 
> address=2600:1702:4860:9dd0::34
> NetworkManager
> 
> but
> 
> VM centos8 failed to start
> 
> Unable to add bridge bond0 port vnet5: Operation not supported
> --
> 
> The options seem to be endless with no success. 
> Advice?
> 

All these messages are nice, but meaningless for troubleshooting. The first 
thing is how the host was installed and how the network was configured, as a 
first start the output of „ip a“. The second one is, how you configured the 
virtual internet connection of a vm.








--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
p...@fedoraproject.org

Timezone: CET (UTC+1) / CEST (UTC+2)


Fedora Server Edition Working Group member
Fedora docs team contributor
Java developer and enthusiast


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Virtual Machine Network Connection Confusion

2023-04-04 Thread Robert McBroom via users
Fedora 37 with four qemu/kvm virtual machines. Trying to get internet 
access from the vm's. Found some advice about using systemd-networkd 
instead of NetworkManager. Lost internet connection with the host. 
Restored with NetworkManager. Further research on NetworkManager gets 
into a tangle with ifcfg scripts and the apparent migration to keyfiles.


Totally confused.

Can only start the virtual machines if the network device is removed.


   --


   VM centos8 failed to start

Requested operation is not valid: network 'default' is not active
-
From cockpit on the web interface tried some of the options with bond 
looking like a possibility

-
11:37 AM
 [1680622647.3084] dhcp6 (bond0): state changed new lease, 
address=2600:1702:4860:9dd0::34

NetworkManager
11:27 AM
 [1680622058.5768] manager: (vnet4): new Tun device 
(/org/freedesktop/NetworkManager/Devices/9)

NetworkManager
11:07 AM
 [1680620850.7934] dhcp6 (bond0): state changed new lease, 
address=2600:1702:4860:9dd0::34

NetworkManager
11:02 AM
 [1680620556.1938] manager: (vnet3): new Tun device 
(/org/freedesktop/NetworkManager/Devices/8)

NetworkManager
11:01 AM
 [1680620475.6234] manager: (vnet2): new Tun device 
(/org/freedesktop/NetworkManager/Devices/7)

NetworkManager
10:40 AM
 [1680619204.0043] dhcp6 (bond0): state changed new lease, 
address=2600:1702:4860:9dd0::34

NetworkManager

but



   VM centos8 failed to start

Unable to add bridge bond0 port vnet5: Operation not supported
--

The options seem to be endless with no success.
Advice?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: GNOME interface is too bulky

2023-04-04 Thread Ranjan Maitra
On Mon Apr03'23 09:24:57PM, Tom Horsley wrote:
> From: Tom Horsley 
> Date: Mon, 3 Apr 2023 21:24:57 -0400
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: GNOME interface is too bulky
> 
> On Tue, 04 Apr 2023 10:39:25 +0930
> Tim via users wrote:
> 
> > Icons, icons, icons!  I can't find a damn thing by icons.
> 
> Yes! A stop sign and an envelope are pretty much it for icons that
> make some sense, after those two it is all guesswork (and I wonder how
> the envelope will age with no one sending physical letters
> any longer :-).
> 
> Personally, I use the FVWM window manager and my own custom .fvwmrc
> file which doesn't completely change my interface every six months.

Wow, I used to use twm for a while, pre-Fedora, and then fvwm2, and then went 
to xfce briefly before pekwm and then settling on openbox. I make my own remix, 
and my wife who used to make fun of my desktop environment (shunya/zero) 
eventually adopted it, and does not want to go back. She went kde -> xfce -> 
lxde -> openbox. (She still makes fun of it though.)

There is something to be said for stability and backwards compatibility, which 
seems to be missing from at least a few modern software -- I was long ago given 
to understand that achieving 1.0 in a software version meant that backwards 
compatibility would be maintained in the future, however this does not seem to 
be the case anymore.

Unfortunately, I have read that openbox and other such window managers will 
stop working as wayland progresses without more development. I hope that is too 
long into the future.

Ranjan

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue