On Friday, 19-07-2024 at 10:15 s...@swampdog.co.uk wrote:
> On Wednesday, 17 July 2024 21:31:00 BST Jeffrey Walton wrote:
> > On Tue, Jul 16, 2024 at 1:35 PM jeremy ardley <jeremy.ard...@gmail.com>
> wrote:
> > > On 16/7/24 19:31, Tom Browder wrote:
> > > > I haven't looked at VB in a long time, but I have a real need for a
> > > > Windows host
> > > > to port some Linux libraries to Windows in order to support the Raku
> > > > language.
> > > >
> > > > I now have lots of memory and disk space which was always a significant
> > > > issue when I used it before, and my use case is much different. Then I
> > > > was trying to show Windows users how they could run Linux, now I want to
> > > > help Windows folks to use a new programming language that was developed
> > > > on *nix systems.
> > > >
> > > > Thus my question is: Has anyone use a recent version of VB to run
> > > > Windows with satisfactory results? (Note I still have a legal copy of
> > > > Win 10 on a CD as well as a portable DVD player with a USB connector.)
> > > >
> > > > Thank you my fellow Debian users!
> > >
> > > VirtualBox is not supported on Debian 12.
> > >
> > > There are alternatives that include:
> > >
> > > - KVM/QEMU
> > >
> > > - VMWare Workstation Pro (which is now free for private use)
> > >
> > > In my experience KVM/QEMU is fairly stable. The VMWare product not so
> > > much.
> > >
> > > Given everything is virtual you can easily try all options in an hour or
> > > two.
> >
> > Add a "mee too" for KVM/QEMU/libvirt. The components are managed by
> > the kernel, so there are usually no technical problems, like unsigned
> > modules. Virt Manager takes a little getting used to, but everything
> > you need is there.
> >
> > The only downside to KVM/QEMU/libvirt is networking in some cases.
> > Configuring a VM to use your local DHCP server is a pain because you
> > have to setup and configure the bridging yourself. And the
> > documentation to do it does not exist.
>
> Out of interest, how is one supposed to do it now? I set mine up ages ago via
> /etc/network/interfaces - eg..
>
> auto br0
> iface br0 inet dhcp
> bridge_ports enp4s0
> bridge_stp off
> bridge_fd 0
> bridge_maxwait 0
>
> ..but I have no idea how to do it now. Manpage says 'brctl' is obsolete and
> points to 'bridge' which I've never used.
After I uninstalled Network Manager, I found this page very useful for setting
up a bridge:
https://wiki.debian.org/BridgeNetworkConnections#Manual_bridge_setup
Configuring bridging in /etc/network/interfaces
If you like static IP’s, then you can just add the static IP options under the
br0 interface setup. For example:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo br0
iface lo inet loopback
# Set up interfaces manually, avoiding conflicts with, e.g., network manager
iface eth0 inet manual
iface eth1 inet manual
# Bridge setup
iface br0 inet static
bridge_ports eth0 eth1
address 192.168.1.2
broadcast 192.168.1.255
netmask 255.255.255.0
gateway 192.168.1.1
One day I would like to learn all that this page explains, but I think the
above is easier:
https://wiki.debian.org/NetworkConfiguration#Bridging
Bridging
I keep trying to convince myself that I should learn and then use
systemd-networkd :
https://wiki.debian.org/SystemdNetworkd
bridging over a bond
https://wiki.archlinux.org/title/systemd-networkd
https://major.io/p/creating-a-bridge-for-virtual-machines-using-systemd-networkd/
Creating a bridge for virtual machines using systemd-networkd
3.1 Network bridge with DHCP
Yet another way (just how many network configuration systems does Linux have?)
https://wiki.archlinux.org/title/Network_bridge
I guess you had found these web pages or ones like them yourself, but in case
you had not, hope they are a help?
I use the first example that uses "/etc/network/interfaces" which appears to
work for servers when Network Manager is not installed but on systems that have
Network Manager I have experience some delay issues with networking when
starting up the computer. And I gave up on setting up Bridges on Wireless
network interfaces as I think each wireless connection is treated as a new
network interface.
George.
>
>
>
>
>
