rbowman wrote:
a clean, up to date document on creating a bridge for QEMU would be
nice. Screwing around with 'sudo ip link ....' makes me nervous. It
took a bit to get rid of the bridge on the Fedora box.
What's wrong with bridged networking (for wired ethernet)?
Adding a switch is exactly what you'd do in the world of physical
networks, a L2 switch is just a multi-port bridge ...
c186282 wrote:
All docs about RPMFusion are now behind a > "Let's See If You Are
Human" wall
I see a glimpse of an anubis interstitial screen, but it doesn't ask me
to interact in any way.
3GB id what is assigned to windows XP to run. I tried 4 but it (XP) fell
over in amazement that such a quantity of memory even existed.
On Mon, 22 Jun 2026 10:20:01 +0100, The Natural Philosopher wrote:
3GB id what is assigned to windows XP to run. I tried 4 but it (XP) fell
over in amazement that such a quantity of memory even existed.
I wonder if that's related to vfat refusing to believe a file can be over
4 GB?
On 21/06/2026 18:49, Charlie Gibbs wrote:
On my two Deb/VBox machines (one running VBox 7.0.12,
the other one 7.2.0), VBox takes up about 5% CPU.
Mind you, that might be their XP VMs twiddling their thumbs...
Similar here (XP VM)
CPU no issue. RAM however is a fixed 3GB loss
Amiga kind of tried ... but by then Commodore was
losing momentum. And the A-1000 ... SO many "Guru
Meditation" messages I basically threw it away.
On 6/21/26 13:49, Charlie Gibbs wrote:
On 2026-06-21, rbowman <bowman@montana.com> wrote:
Perhaps if someone really wanted to use VirtualBox they could make it
work. Having a VM that can be reached by other machines on the LAN isn't >>> that important.
It is for me - it's my preferred method for moving files around.
I've made my peace with VirtualBox - I've managed to get it running
and keep it that way. I'm running Debian Bookworm, and have been
using VBox for the past <mumble> Debian releases.
I used to use SAMBA for everything - then IT got weird.
None of my usual setups worked right. Had to use No File
Security for my little home 'NAS'. Works, but NOT nearly
as fine-tweakable as SAMBA.
Made some 'standard' lines for 'fstab' and always use the
same dir/subdirs for NFS. Quick to install. This CAN be used
with VBox VMs if you can't get the damned 'extension pack'
and such working.
Used to have an XP VM ... dunno what's become of it.
Liked Win2K better, but a lot of software now won't
run on it.
Yes, I always figured that Windows' usability peaked somewhere between
2K and XP and has been going downhill ever since.
But 2K, as you said, wouldn't run a lot of stuff. I had a MIDI-to-USB converter that would crash 2K the instant I plugged it in; it worked
fine under XP though.
On 2026-06-22, The Natural Philosopher <tnp@invalid.invalid> wrote:
On 21/06/2026 18:49, Charlie Gibbs wrote:
On my two Deb/VBox machines (one running VBox 7.0.12,
the other one 7.2.0), VBox takes up about 5% CPU.
Mind you, that might be their XP VMs twiddling their thumbs...
Similar here (XP VM)
CPU no issue. RAM however is a fixed 3GB loss
I guess I'm running simpler stuff on my XP VMs;
they're quite happy with the 512MB I give them.
On 22/06/2026 18:07, Charlie Gibbs wrote:
On 2026-06-22, The Natural Philosopher <tnp@invalid.invalid> wrote:
On 21/06/2026 18:49, Charlie Gibbs wrote:
On my two Deb/VBox machines (one running VBox 7.0.12,
the other one 7.2.0), VBox takes up about 5% CPU.
Mind you, that might be their XP VMs twiddling their thumbs...
Similar here (XP VM)
CPU no issue. RAM however is a fixed 3GB loss
I guess I'm running simpler stuff on my XP VMs;
they're quite happy with the 512MB I give them.
My XP VM does real work using CAD software. It needs all it can get
I used Samba to transfer files back and forth between my Amiga and
Windows boxes. It worked well, but I haven't had occasion to use it
since. Microsoft issued a patch to Windows which would send an
invalid command to Samba servers on initial connection; if the error
message that came back wasn't formatted exactly the way a Windows
server did it, it would refuse to connect. It took Amiga programmers
only a few days to issue a patch for that one.
What's wrong with bridged networking (for wired ethernet)?
On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote:
rbowman wrote:
a clean, up to date document on creating a bridge for QEMU would be
nice. Screwing around with 'sudo ip link ....' makes me nervous. It
took a bit to get rid of the bridge on the Fedora box.
What's wrong with bridged networking (for wired ethernet)?
Adding a switch is exactly what you'd do in the world of physical
networks, a L2 switch is just a multi-port bridge ...
Nothing would be wrong if it had worked. Perhaps I didn't create the
bridge correctly.
On Mon, 22 Jun 2026 17:07:25 GMT, Charlie Gibbs wrote:
I used Samba to transfer files back and forth between my Amiga and
Windows boxes. It worked well, but I haven't had occasion to use it
since. Microsoft issued a patch to Windows which would send an
invalid command to Samba servers on initial connection; if the error
message that came back wasn't formatted exactly the way a Windows
server did it, it would refuse to connect. It took Amiga programmers
only a few days to issue a patch for that one.
Are you running an Amiga-specific Samba fork?
That doesn’t sound very healthy ...
On 22/06/2026 18:07, Charlie Gibbs wrote:
On 2026-06-22, The Natural Philosopher <tnp@invalid.invalid> wrote:My XP VM does real work using CAD software. It needs all it can get
On 21/06/2026 18:49, Charlie Gibbs wrote:
On my two Deb/VBox machines (one running VBox 7.0.12,
the other one 7.2.0), VBox takes up about 5% CPU.
Mind you, that might be their XP VMs twiddling their thumbs...
Similar here (XP VM)
CPU no issue. RAM however is a fixed 3GB loss
I guess I'm running simpler stuff on my XP VMs;
they're quite happy with the 512MB I give them.
HAD to go to NFS on my little home 'NAS' ...
but don't LIKE it.
On 6/22/26 09:46, rbowman wrote:
On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote:
rbowman wrote:
a clean, up to date document on creating a bridge for QEMU would be
nice. Screwing around with 'sudo ip link ....' makes me nervous. It
took a bit to get rid of the bridge on the Fedora box.
What's wrong with bridged networking (for wired ethernet)?
Adding a switch is exactly what you'd do in the world of physical
networks, a L2 switch is just a multi-port bridge ...
Nothing would be wrong if it had worked. Perhaps I didn't create the
bridge correctly.
VBox, it Just Works first time :-)
However, the past couple years, SOME shit about the config files has
CHANGED. Even following strict instructions it WON'T WORK. Yea, maybe
I could set up symlinks ... but always have to TEST those to make
sure they haven't dropped due to some micro-glitch. Easy with a
Python or Pascal or 'C' custom app, but SAMBA is kinda supposed to be
the WHOLE THING.
On 23/06/2026 10:03, c186282 wrote:
HAD to go to NFS on my little home 'NAS' ...
but don't LIKE it.
I use NFS because I run the exact environment it was designed for - a
fully trusted unix/linux only local area network .
I also use it WAN behind a carefully set up firewall.
Samba was fine when running windows or MAC clients with less
sophisticated users.
On Tue, 23 Jun 2026 04:32:24 -0400, c186282 wrote:
On 6/22/26 09:46, rbowman wrote:
On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote:
rbowman wrote:
a clean, up to date document on creating a bridge for QEMU would be
nice. Screwing around with 'sudo ip link ....' makes me nervous. It
took a bit to get rid of the bridge on the Fedora box.
What's wrong with bridged networking (for wired ethernet)?
Adding a switch is exactly what you'd do in the world of physical
networks, a L2 switch is just a multi-port bridge ...
Nothing would be wrong if it had worked. Perhaps I didn't create the
bridge correctly.
VBox, it Just Works first time :-)
After you find a distro where it will work at all...
On Tue, 23 Jun 2026 04:32:24 -0400, c186282 wrote:
On 6/22/26 09:46, rbowman wrote:
On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote:
rbowman wrote:
a clean, up to date document on creating a bridge for QEMU would be
nice. Screwing around with 'sudo ip link ....' makes me nervous. It
took a bit to get rid of the bridge on the Fedora box.
What's wrong with bridged networking (for wired ethernet)?
Adding a switch is exactly what you'd do in the world of physical
networks, a L2 switch is just a multi-port bridge ...
Nothing would be wrong if it had worked. Perhaps I didn't create the
bridge correctly.
VBox, it Just Works first time :-)
After you find a distro where it will work at all...
On 23/06/2026 18:26, rbowman wrote:
On Tue, 23 Jun 2026 04:32:24 -0400, c186282 wrote:As usual Linux Mint seems to be OK
On 6/22/26 09:46, rbowman wrote:
On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote:
rbowman wrote:
a clean, up to date document on creating a bridge for QEMU would be >>>>>> nice. Screwing around with 'sudo ip link ....' makes me nervous. It >>>>>> took a bit to get rid of the bridge on the Fedora box.
What's wrong with bridged networking (for wired ethernet)?
Adding a switch is exactly what you'd do in the world of physical
networks, a L2 switch is just a multi-port bridge ...
Nothing would be wrong if it had worked. Perhaps I didn't create the
bridge correctly.
VBox, it Just Works first time :-)
After you find a distro where it will work at all...
Although I haven't installed it recently
On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote:
Interesting that it builds the modules for the 6.17.0.14-generic kernel
while it seems to be a DIY process for Leap 16. Among other things the
error dialog on Leap 16 says it requires make, gcc, and kernel-devel
headers. The Mint box does not have make.
On 2026-06-24 03:34, rbowman wrote:
On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote:
Interesting that it builds the modules for the 6.17.0.14-generic kernel
while it seems to be a DIY process for Leap 16. Among other things the
error dialog on Leap 16 says it requires make, gcc, and kernel-devel
headers. The Mint box does not have make.
There is a new iso, announced yesterday.
On Wed, 24 Jun 2026 11:51:24 +0200, Carlos E. R. wrote:
On 2026-06-24 03:34, rbowman wrote:
On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote:
Interesting that it builds the modules for the 6.17.0.14-generic kernel
while it seems to be a DIY process for Leap 16. Among other things the
error dialog on Leap 16 says it requires make, gcc, and kernel-devel
headers. The Mint box does not have make.
There is a new iso, announced yesterday.
I got further with 7.0.16 on Mint but it still wasn't a success. My first attempt was TrixiePup64. The VM started up but was a terminal, not a
desktop and reported it had exited from labwc. startlabwc also exited immediately.
Next up was the Leap 16 offline iso. The initial screen had 4 options,
boot from a DVD, install Leap, safely install Leap or exit. Choosing
install brought up the familiar Agama installer. I selected Xfce for
variety and started the install. The Mint machine isn't the fastest so
that took a while before the screen announced it had been successfully installed and to reboot. Rebooting brought up the initial installation screen, not Leap 16.
To make sure the new VB modules hadn't affected kvm_intel I created a TrixiePup64 VM which started up with labwc.
So in my experience the RPMFusion version on Fedora 44 is the only one
that installs correctly and works. It is 7.2.8, not the 7.0.16 Ubuntu version. fwiw lsmod on Fedora also shows the vbox* modules.
2026-06-24 20:07, rbowman wrote:
On Wed, 24 Jun 2026 11:51:24 +0200, Carlos E. R. wrote:
On 2026-06-24 03:34, rbowman wrote:
On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote:
Interesting that it builds the modules for the 6.17.0.14-generic
kernel while it seems to be a DIY process for Leap 16. Among other
things the error dialog on Leap 16 says it requires make, gcc, and
kernel-devel headers. The Mint box does not have make.
There is a new iso, announced yesterday.
I got further with 7.0.16 on Mint but it still wasn't a success. My
first attempt was TrixiePup64. The VM started up but was a terminal,
not a desktop and reported it had exited from labwc. startlabwc also
exited immediately.
Next up was the Leap 16 offline iso. The initial screen had 4 options,
boot from a DVD, install Leap, safely install Leap or exit. Choosing
install brought up the familiar Agama installer. I selected Xfce for
variety and started the install. The Mint machine isn't the fastest so
that took a while before the screen announced it had been successfully
installed and to reboot. Rebooting brought up the initial installation
screen, not Leap 16.
Did you remove the DVD/USB first?
On 2026-06-24 20:07, rbowman wrote:
On Wed, 24 Jun 2026 11:51:24 +0200, Carlos E. R. wrote:
On 2026-06-24 03:34, rbowman wrote:
On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote:
Interesting that it builds the modules for the 6.17.0.14-generic kernel >>>> while it seems to be a DIY process for Leap 16. Among other things the >>>> error dialog on Leap 16 says it requires make, gcc, and kernel-devel
headers. The Mint box does not have make.
There is a new iso, announced yesterday.
I got further with 7.0.16 on Mint but it still wasn't a success. My first
attempt was TrixiePup64. The VM started up but was a terminal, not a
desktop and reported it had exited from labwc. startlabwc also exited
immediately.
Next up was the Leap 16 offline iso. The initial screen had 4 options,
boot from a DVD, install Leap, safely install Leap or exit. Choosing
install brought up the familiar Agama installer. I selected Xfce for
variety and started the install. The Mint machine isn't the fastest so
that took a while before the screen announced it had been successfully
installed and to reboot. Rebooting brought up the initial installation
screen, not Leap 16.
Did you remove the DVD/USB first?
On Thu, 25 Jun 2026 12:02:52 +0200, Carlos E. R. wrote:
2026-06-24 20:07, rbowman wrote:
On Wed, 24 Jun 2026 11:51:24 +0200, Carlos E. R. wrote:
On 2026-06-24 03:34, rbowman wrote:
On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote:
Interesting that it builds the modules for the 6.17.0.14-generic
kernel while it seems to be a DIY process for Leap 16. Among other
things the error dialog on Leap 16 says it requires make, gcc, and
kernel-devel headers. The Mint box does not have make.
There is a new iso, announced yesterday.
I got further with 7.0.16 on Mint but it still wasn't a success. My
first attempt was TrixiePup64. The VM started up but was a terminal,
not a desktop and reported it had exited from labwc. startlabwc also
exited immediately.
Next up was the Leap 16 offline iso. The initial screen had 4 options,
boot from a DVD, install Leap, safely install Leap or exit. Choosing
install brought up the familiar Agama installer. I selected Xfce for
variety and started the install. The Mint machine isn't the fastest so
that took a while before the screen announced it had been successfully
installed and to reboot. Rebooting brought up the initial installation
screen, not Leap 16.
Did you remove the DVD/USB first?
That's the fun part. There never was a DVD/USB. The first screen of
creating a new VM in VirtualBox asks for an ISO image. That image is in a directory on the host machine.
I tried to create a Leap 16 VM on the Fedora box. I got as far as the
Agama screen where you select the Leap 16 install. VB was using 100% of
the CPU and I ran out of patience waiting for the button to become active.
I then tried TrixiePup64. Like on the Mint machine it comes up as a
terminal session because labwc won't start.
Both work with kvm/QEMU. As I said before if VirtualBox works for someone they should use it. For me it fails to cleanly install on Leap 16, and doesn't work on Fedora or Mint.
Ok, same thing. You have to disconnect that ISO from VB.
On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote:
Ok, same thing. You have to disconnect that ISO from VB.
However you're supposed to do that. I'm done. I don't need VB.
On 26/06/2026 18:58, rbowman wrote:
On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote:
Ok, same thing. You have to disconnect that ISO from VB.
However you're supposed to do that. I'm done. I don't need VB.
That is sad. It's actually extremely good at what it does
I never had any trouble with it
On Fri, 26 Jun 2026 21:59:35 +0100, The Natural Philosopher wrote:
On 26/06/2026 18:58, rbowman wrote:
On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote:
Ok, same thing. You have to disconnect that ISO from VB.
However you're supposed to do that. I'm done. I don't need VB.
That is sad. It's actually extremely good at what it does
I never had any trouble with it
You are fortunate. Unlike kvm/QEMU I have had difficulty even getting it installed on various distros, and once installed it is quirky. Apparently
it can handle labwc at all. MX starts but never gets past the splash
screen.
otoh virt-manager works on all distros including Raspberry Pi OS.
On Fri, 26 Jun 2026 21:59:35 +0100, The Natural Philosopher wrote:
On 26/06/2026 18:58, rbowman wrote:
On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote:
Ok, same thing. You have to disconnect that ISO from VB.
However you're supposed to do that. I'm done. I don't need VB.
That is sad. It's actually extremely good at what it does
I never had any trouble with it
You are fortunate. Unlike kvm/QEMU I have had difficulty even getting it installed on various distros, and once installed it is quirky. Apparently
it can handle labwc at all. MX starts but never gets past the splash
screen.
otoh virt-manager works on all distros including Raspberry Pi OS.
On 26/06/2026 23:04, rbowman wrote:
On Fri, 26 Jun 2026 21:59:35 +0100, The Natural Philosopher wrote:Back in the day those options did not exist. QEMU was a way to run
On 26/06/2026 18:58, rbowman wrote:
On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote:
Ok, same thing. You have to disconnect that ISO from VB.
However you're supposed to do that. I'm done. I don't need VB.
That is sad. It's actually extremely good at what it does
I never had any trouble with it
You are fortunate. Unlike kvm/QEMU I have had difficulty even getting it
installed on various distros, and once installed it is quirky. Apparently
it can handle labwc at all. MX starts but never gets past the splash
screen.
windows on a power PC!
otoh virt-manager works on all distros including Raspberry Pi OS.
Well, as long as you have what works for you, that's all right
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,126 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 50:03:09 |
| Calls: | 14,414 |
| Calls today: | 2 |
| Files: | 186,400 |
| D/L today: |
10,397 files (2,824M bytes) |
| Messages: | 2,548,892 |
| Posted today: | 1 |