Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #82323 > unrolled thread

Heh Heh - New Fedora, HUGE Updates Needed

Back to article view | Back to comp.os.linux.misc

Contents

  Heh Heh - New Fedora, HUGE Updates Needed c186282 <c186282@nnada.net> - 2026-03-01 01:40 -0500
    Re: Heh Heh - New Fedora, HUGE Updates Needed rbowman <bowman@montana.com> - 2026-03-01 18:13 +0000
      Re: Heh Heh - New Fedora, HUGE Updates Needed c186282 <c186282@nnada.net> - 2026-03-01 22:34 -0500
        Re: Heh Heh - New Fedora, HUGE Updates Needed rbowman <bowman@montana.com> - 2026-03-02 06:51 +0000
          Re: Heh Heh - New Fedora, HUGE Updates Needed c186282 <c186282@nnada.net> - 2026-03-02 03:58 -0500
            Re: Heh Heh - New Fedora, HUGE Updates Needed "Carlos E.R." <robin_listas@es.invalid> - 2026-03-03 19:51 +0100
              Re: Heh Heh - New Fedora, HUGE Updates Needed c186282 <c186282@nnada.net> - 2026-03-03 19:29 -0500
              Re: Heh Heh - New Fedora, HUGE Updates Needed rbowman <bowman@montana.com> - 2026-03-04 03:02 +0000
                Re: Heh Heh - New Fedora, HUGE Updates Needed c186282 <c186282@nnada.net> - 2026-03-04 00:09 -0500
                  Re: Heh Heh - New Fedora, HUGE Updates Needed rbowman <bowman@montana.com> - 2026-03-04 19:17 +0000
                Re: Heh Heh - New Fedora, HUGE Updates Needed "Carlos E.R." <robin_listas@es.invalid> - 2026-03-04 13:20 +0100
                  Re: Heh Heh - New Fedora, HUGE Updates Needed rbowman <bowman@montana.com> - 2026-03-04 19:20 +0000
                    Re: Heh Heh - New Fedora, HUGE Updates Needed "Carlos E.R." <robin_listas@es.invalid> - 2026-03-04 20:56 +0100
        Re: Heh Heh - New Fedora, HUGE Updates Needed jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-03-02 12:04 -0500
          Re: Heh Heh - New Fedora, HUGE Updates Needed rbowman <bowman@montana.com> - 2026-03-02 18:56 +0000
            Re: Heh Heh - New Fedora, HUGE Updates Needed c186282 <c186282@nnada.net> - 2026-03-02 20:11 -0500

#82323 — Heh Heh - New Fedora, HUGE Updates Needed

Hilarious ! Downloaded a fresh Fedora-XFCE from their
site yesterday. Got it installed as a KVM machine on
Trixie (big fight, not as straight a path as with VBox).

The FUNNY bit, despite being fresh off the press, it
is now installing *764* updates over my slow-ass
connection :-)

Tried AQEMU, which is nice, but it wouldn't RUN the
VM once I took the ISO CD out of the list. WAS able
to import the QCOW2 and run it using 'virt-manager'
however. Note that with AQUEMU you have to run it
sudo or it just PRETENDS to create the virtual disk.
MIGHT be fixable by adding 'disk' to the regular
users groups ???

AQUEMU, despite the fancy interface, does NOT seem
to be able to recognize the wifi or even a bridge
interface. Virt-manager MAYbe can if you set the
network to, on my box, 'virbr0' which network-manager
says is a bridge. I'll try that soon.

Note HUGE amounts of VM stuff/apps had to be installed
before virt-manager or AQEMU could find the QEMU
'connection'.

DID connect my box to the, oft shitty, hardwire
ports on the router. This DID give it internet
access, hence the updates. However it's not MY
damned subnet. More fooling around to do ...

Didn't things used to be a lot easier, like
just a few years ago ???

Was gonna go to sleep last night and then at the
last moment stuff about the Iran war started up.
Didn't sleep until maybe 8am ... major burn out :-)

[toc] | [next] | [standalone]

#82325

On Sun, 1 Mar 2026 01:40:58 -0500, c186282 wrote:


> AQUEMU, despite the fancy interface, does NOT seem to be able to
> recognize the wifi or even a bridge interface. Virt-manager MAYbe can if
> you set the network to, on my box, 'virbr0' which network-manager says
> is a bridge. I'll try that soon.

I've wondered about the schedule for creating isos. The B&N store is next 
to the gym and I got curious last week. Linux Magazine still exists in 
hardcopy and, blast from the past, it has DVDs for both Ubuntu and Fedora 
43.

In that model it's understandable the software will be stale, but with 
almost all isos it seems the first thing it does is look for a internet 
connection and phone home to update. 

I don't know about Xfce, but I'm running KDE which recently released 
Plasma 6. Both the Arch and Fedora boxes have been doing a lot of updates. 
The first round for Fedora was close to a GB. Yesterday's was also close 
to a GB, including the 6.18.13 kernel. The Arch box timed out but it was 
trying to get 6.18.13 too. Arch hadn't been updating the kernel as 
frequently and I believe they were waiting for 6.19. 

I used KVM and didn't have problems other than trying to use a img.zx. 
That didn't fly for some reason. I did VMs both on Fedora (Leap 16) and, 
for laughs, Ubuntu Server on the Raspberry Pi. Yeah, the Pi OS is based on 
Trixie and has KVM although some of the tests for it don't work as 
expected.

In both cases the VM created a virtual NAT, using the host's connection. 
The VMs worked fine although the IPs were something like 192.168.101.93, 
not on my subnet as you mention. Now comes the fly in the ointment. My 
whole system is wireless, not an ethernet connection in sight. Using a 
bridge supposedly allows you to get on the subnet, 192.168.1.x in this 
case -- but it doesn't work with wireless. A NIC can handle it but not 
wifi. I can ping the VMs IP from the host but that's it. No problem for 
trying various distros but if I were to serve up a webpage from the VM 
only the host would be able to see it.

The Linux users group met yesterday and the guy who had started it rolling 
(again) is a newbie (6 months) and tried the KVM route but it was too 
complex for him. He said he did get VirtualBox installed on Mint but 
didn't actually use it. 

fwiw, I think the Leap 16 VM would really like to do a bunch of updates 
but I'm not going to. I did KDE after an extremely brief GNOME install but 
with KDE on Arch and Fedora I really can't see what openSUSE has to offer 
except 'zypper' instead of apt, dnf, or pacman for updates.

[toc] | [prev] | [next] | [standalone]

#82327

On 3/1/26 13:13, rbowman wrote:
> On Sun, 1 Mar 2026 01:40:58 -0500, c186282 wrote:
> 
> 
>> AQUEMU, despite the fancy interface, does NOT seem to be able to
>> recognize the wifi or even a bridge interface. Virt-manager MAYbe can if
>> you set the network to, on my box, 'virbr0' which network-manager says
>> is a bridge. I'll try that soon.
> 
> I've wondered about the schedule for creating isos. The B&N store is next
> to the gym and I got curious last week. Linux Magazine still exists in
> hardcopy and, blast from the past, it has DVDs for both Ubuntu and Fedora
> 43.

   Wow ! Well done Linux Mag !

   Though a tiny packet with a mini SD card might be
   cheaper and at this point more accessible than an
   olde tyme DVD.

> In that model it's understandable the software will be stale, but with
> almost all isos it seems the first thing it does is look for a internet
> connection and phone home to update.
> 
> I don't know about Xfce, but I'm running KDE which recently released
> Plasma 6. Both the Arch and Fedora boxes have been doing a lot of updates.
> The first round for Fedora was close to a GB. Yesterday's was also close
> to a GB, including the 6.18.13 kernel. The Arch box timed out but it was
> trying to get 6.18.13 too. Arch hadn't been updating the kernel as
> frequently and I believe they were waiting for 6.19.
> 
> I used KVM and didn't have problems other than trying to use a img.zx.
> That didn't fly for some reason. I did VMs both on Fedora (Leap 16) and,
> for laughs, Ubuntu Server on the Raspberry Pi. Yeah, the Pi OS is based on
> Trixie and has KVM although some of the tests for it don't work as
> expected.

   I'm doing opposite, Fedora VM on Trixie.

   As said, the VM can only see the hardwire net port
   but not the wifi. There may be workarounds, but not
   as clean as straight-up access to the local wifi.

   Fedora does not seem to have anything as convenient
   as Debs 'net-manager' where you can micro-tweak all
   the important stuff. Yea, the info is in a config
   file (or two or three), but that's more work. Gonna
   try altering the XML file that KVM uses to set the
   net addresses.

   As said, this AQEMU app is even nicer than virt-manager
   but it does have a few tricks - like you set up the VM
   and QCOW2 virtual disk first, THEN use the interface
   and add the install CD (yer ISO or image) and set it
   to bootable. Alas you need to remove the CD after the
   install and that's where it gets unhappy. There IS a
   'boot order' thingie, with the CD ahead of the HDD,
   maybe if I alter that stuff ... ?

   Note that VBox sometimes also requires exterminating
   the CD ... sometimes moving the ISO to a different dir ...
   so this issue isn't unique.

> In both cases the VM created a virtual NAT, using the host's connection.
> The VMs worked fine although the IPs were something like 192.168.101.93,
> not on my subnet as you mention.

   'Zactly

> Now comes the fly in the ointment. My
> whole system is wireless, not an ethernet connection in sight. Using a
> bridge supposedly allows you to get on the subnet, 192.168.1.x in this
> case -- but it doesn't work with wireless. A NIC can handle it but not
> wifi. I can ping the VMs IP from the host but that's it. No problem for
> trying various distros but if I were to serve up a webpage from the VM
> only the host would be able to see it.

   There are a whole two physical plugs on the back
   of my Air router - and I've had mixed experiences
   with them. I did plug the box in question direct
   into the router and was thus able to install/update.
   However it's not the best solution - and the odd
   subnet is, well, odd ... DHCP should have picked
   my real subnet.

> The Linux users group met yesterday and the guy who had started it rolling
> (again) is a newbie (6 months) and tried the KVM route but it was too
> complex for him. He said he did get VirtualBox installed on Mint but
> didn't actually use it.

   I got VBox working on mint. Alas the VM, and then
   the Mint host, started acting weirder and weirder.
   More and more latency even crept into the keyboard
   and mouse inputs. No obvious stuff hogging the system.
   Thus, flushed and am trying Trixie again as the host.

   I suppose Centos might be the best VM host, it was
   kinda adjusted for hosting multiple VMs in the modern
   fashion after all. Alas the thought of dealing with
   that horrible Gnome interface again !  :-)

> fwiw, I think the Leap 16 VM would really like to do a bunch of updates
> but I'm not going to. I did KDE after an extremely brief GNOME install but
> with KDE on Arch and Fedora I really can't see what openSUSE has to offer
> except 'zypper' instead of apt, dnf, or pacman for updates.

   Well, OSuse used to have some good GUI tools ... are
   they gone ???

   If not GUI then, well, apt/zypper/pacman/dnf and such are
   pretty much the same and one is as 'good' as another.

   My Fedora - for some reason 'dnfdragora' is malfunctioning
   after the updates. I'll try a few things to unstick it
   (sez updating cache at the start but never does, hanging
   the whole thing). Could try manually deleting the cache
   so it'll start fresh ...

   Anyway, my immediate issue is wifi in the KVM machine.
   This is not hard in VBox, but I've had a number of
   issues installing/using VBox of late (as said here)
   so the paved road, KVM/QEMU, may need to be walked
   for now.

   Ah, 'future issue' ... there used to be serverS - mail,
   DB, etc ... then everybody (foolishly) tried to save
   a dollar and bought just ONE good box and ran all the
   servers as VMs. Great, until yer one box craps. NOW
   however, local servers are being rapidly replaced by
   cloud servers/suites. Maybe great until the net does
   not work or Vlad cyberattacks everything.

   Oh well, stuff to keep me busy ...

[toc] | [prev] | [next] | [standalone]

#82328

On Sun, 1 Mar 2026 22:34:14 -0500, c186282 wrote:


>> fwiw, I think the Leap 16 VM would really like to do a bunch of updates
>> but I'm not going to. I did KDE after an extremely brief GNOME install
>> but with KDE on Arch and Fedora I really can't see what openSUSE has to
>> offer except 'zypper' instead of apt, dnf, or pacman for updates.
> 
>    Well, OSuse used to have some good GUI tools ... are they gone ???
> 
>    If not GUI then, well, apt/zypper/pacman/dnf and such are pretty much
>    the same and one is as 'good' as another.

Yast was one of the big selling points but Myrlyn is the new GUI package 
manager. It' okay and it says you can install yast2. I tend to use the CLI 
tools like zypper or dnf rather than the GUI. In most cases I know what I 
want and don't need to go shopping.

I downloaded the offline iso. It's huge, 4.4 GB which led to the learning 
experience that you need to format the USB stick to exfat. vfat can't do 
over 4 GB. Admittedly it has both GNOME and KDE, maybe even Xfce, and the 
LibreOffice crap. What it doesn't have is gcc and friends. It does have 
Python.

The KDE version is pretty much KDE same as the Fedora and Arch boxes. 
Other than Myrlyn I didn't see any special openSUSE secret sauce. 

>    Anyway, my immediate issue is wifi in the KVM machine. This is not
>    hard in VBox, but I've had a number of issues installing/using VBox
>    of late (as said here)
>    so the paved road, KVM/QEMU, may need to be walked for now.

I didn't do anything special on Fedora or the Pi's Trixie version, just 
pointed it at the iso and accepted the defaults. When I look at the VM 
Info NIC entry it shows a Virtual NAT and the 192 IP address. I didn't 
mess with it after doing the research and finding br0 isn't going to fly 
over a wifi connection.  

That makes sense to me. You can go out through the NIC to the ethernet 
router and it's going to assign a IP on the subnet but the wireless router 
doesn't work like that. No big deal except I can't access it from anyplace 
other than the host.  I can ping machines on the 192.168.1.x subnet. I 
haven't tried it but I probably could mount the NFS export with my music 
since it's * in exportfs.

 
>    Oh well, stuff to keep me busy ...

Yeah, time to go back to the Pi. I've played around with the Picos but 
never did too much with the GPIO on the Pi. I doubt it is as fast as the 
Picos because of the Cortex-A architecture but it works. 

The PiDog does fine with a 3+ but it has a hat between the Pi and all the 
servos, sensors, and so forth.

[toc] | [prev] | [next] | [standalone]

#82329

On 3/2/26 01:51, rbowman wrote:
> On Sun, 1 Mar 2026 22:34:14 -0500, c186282 wrote:
> 
> 
>>> fwiw, I think the Leap 16 VM would really like to do a bunch of updates
>>> but I'm not going to. I did KDE after an extremely brief GNOME install
>>> but with KDE on Arch and Fedora I really can't see what openSUSE has to
>>> offer except 'zypper' instead of apt, dnf, or pacman for updates.
>>
>>     Well, OSuse used to have some good GUI tools ... are they gone ???
>>
>>     If not GUI then, well, apt/zypper/pacman/dnf and such are pretty much
>>     the same and one is as 'good' as another.
> 
> Yast was one of the big selling points but Myrlyn is the new GUI package
> manager. It' okay and it says you can install yast2. I tend to use the CLI
> tools like zypper or dnf rather than the GUI. In most cases I know what I
> want and don't need to go shopping.

   Yast/2 was GREAT. THE main selling point for OSuse.
   It was the Mark Above.

> I downloaded the offline iso. It's huge, 4.4 GB which led to the learning
> experience that you need to format the USB stick to exfat. vfat can't do
> over 4 GB. Admittedly it has both GNOME and KDE, maybe even Xfce, and the
> LibreOffice crap. What it doesn't have is gcc and friends. It does have
> Python.
> 
> The KDE version is pretty much KDE same as the Fedora and Arch boxes.
> Other than Myrlyn I didn't see any special openSUSE secret sauce.
> 
>>     Anyway, my immediate issue is wifi in the KVM machine. This is not
>>     hard in VBox, but I've had a number of issues installing/using VBox
>>     of late (as said here)
>>     so the paved road, KVM/QEMU, may need to be walked for now.
> 
> I didn't do anything special on Fedora or the Pi's Trixie version, just
> pointed it at the iso and accepted the defaults. When I look at the VM
> Info NIC entry it shows a Virtual NAT and the 192 IP address. I didn't
> mess with it after doing the research and finding br0 isn't going to fly
> over a wifi connection.

   Hmmm ... just spent an hour+ working on the KVM Fedora
   VM. Online instructions say you can do 'connections'
   and then choose 'bridged'. Well, there IS NO 'bridged'
   anymore ... a number of other, useless, options, but ...

   TRY to set whatever to the local net and you get an
   "in use by <enpxxx>" on the host and it won't work.
   Can't even boot the VM. Did save the orig def, but
   it didn't really deliver.

   Sorry, but this seems pretty much USELESS. The one good
   bit about KVM VMs was that you could set them so they'd
   be on your LOCAL net - same as a separate box plugged in.

   Spent hours trying all options.

   No, I'm NOT gonna use SSH connections ... that's retarded.


> That makes sense to me. You can go out through the NIC to the ethernet
> router and it's going to assign a IP on the subnet but the wireless router
> doesn't work like that. No big deal except I can't access it from anyplace
> other than the host.  I can ping machines on the 192.168.1.x subnet. I
> haven't tried it but I probably could mount the NFS export with my music
> since it's * in exportfs.
> 
>   
>>     Oh well, stuff to keep me busy ...
> 
> Yeah, time to go back to the Pi. I've played around with the Picos but
> never did too much with the GPIO on the Pi. I doubt it is as fast as the
> Picos because of the Cortex-A architecture but it works.
> 
> The PiDog does fine with a 3+ but it has a hat between the Pi and all the
> servos, sensors, and so forth.

   Well, I'm retired now ... so none of this is "for the money"
   anymore. However I'd really really LIKE it to work for some
   reasons I've mentioned.

   And no, ffmpeg STILL crashes or hangs on Mint, MX and Trixie
   after so many startups. Can NOT find any reason.

   Shit, all I want to do is make sequential rtsp captures
   with sound - scaled a bit so they don't use much space.
   The ffmpeg params are well documented and DO work - but
   now only for AWHILE. One hour, six hours, eight hours -
   then disaster. Really don't want to reboot the box every
   hour or two. This shit started around late December and
   PERSISTS. I feel betrayed.

   No, NOT gonna use Winder$ .......

[toc] | [prev] | [next] | [standalone]

#82354

On 2026-03-02 09:58, c186282 wrote:
>    And no, ffmpeg STILL crashes or hangs on Mint, MX and Trixie
>    after so many startups. Can NOT find any reason.

openSUSE has ffmepg in several versions, from 4 to 8. At least if you 
use the mature Leap 15.6

-- 
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;

[toc] | [prev] | [next] | [standalone]

#82363

On 3/3/26 13:51, Carlos E.R. wrote:
> On 2026-03-02 09:58, c186282 wrote:
>>    And no, ffmpeg STILL crashes or hangs on Mint, MX and Trixie
>>    after so many startups. Can NOT find any reason.
> 
> openSUSE has ffmepg in several versions, from 4 to 8. At least if you 
> use the mature Leap 15.6

   I'm attempting a Fedora install - same libs - VM
   within Trixie. It runs, but the networking scheme
   in KVM frustrates more than just me. VBox is better
   at that, easily finds/uses a bridge, but it does
   not run correctly in Trixie (yet).

[toc] | [prev] | [next] | [standalone]

#82366

On Tue, 3 Mar 2026 19:51:43 +0100, Carlos E.R. wrote:

> On 2026-03-02 09:58, c186282 wrote:
>>    And no, ffmpeg STILL crashes or hangs on Mint, MX and Trixie after
>>    so many startups. Can NOT find any reason.
> 
> openSUSE has ffmepg in several versions, from 4 to 8. At least if you
> use the mature Leap 15.6

That's beyond mature. EOL is next month.

[toc] | [prev] | [next] | [standalone]

#82371

On 3/3/26 22:02, rbowman wrote:
> On Tue, 3 Mar 2026 19:51:43 +0100, Carlos E.R. wrote:
> 
>> On 2026-03-02 09:58, c186282 wrote:
>>>     And no, ffmpeg STILL crashes or hangs on Mint, MX and Trixie after
>>>     so many startups. Can NOT find any reason.
>>
>> openSUSE has ffmepg in several versions, from 4 to 8. At least if you
>> use the mature Leap 15.6
> 
> That's beyond mature. EOL is next month.

   Um, yea, a bit old and wrinkly - and with
   that funny vitamin smell  :-)

   But, no doubt, it served well.

   HOPING that the latest Fedora VM will solve
   my ffmpeg problem - IF I can get it to
   attach to my local subnet ... working
   on it. DID order some USB WiFi dongles.
   A day or two and I'll have something to
   report. It MAY be that easy.

[toc] | [prev] | [next] | [standalone]

#82384

On Wed, 4 Mar 2026 00:09:14 -0500, c186282 wrote:

>    HOPING that the latest Fedora VM will solve my ffmpeg problem - IF I
>    can get it to attach to my local subnet ... working on it. DID order
>    some USB WiFi dongles.
>    A day or two and I'll have something to report. It MAY be that easy.

Hmmm. I've got a Panda dongle that I use to get around the Broadcom 
problem on the netbook. I assume the MAC address is determined by the wifi 
module or NIC so the wireless router will see a different MAC and assign 
an IP like it does for the TV, Kindles, etc. Now, how to get the VM, or 
actually the virtualization layer, to see it.

That could get interesting. I had to deal with one site that had a dual-
homed server with both NICs on the same subnet. There are valid reasons to 
do that but in this case it was a complete FUBAR. 

[toc] | [prev] | [next] | [standalone]

#82377

On 2026-03-04 04:02, rbowman wrote:
> On Tue, 3 Mar 2026 19:51:43 +0100, Carlos E.R. wrote:
> 
>> On 2026-03-02 09:58, c186282 wrote:
>>>     And no, ffmpeg STILL crashes or hangs on Mint, MX and Trixie after
>>>     so many startups. Can NOT find any reason.
>>
>> openSUSE has ffmepg in several versions, from 4 to 8. At least if you
>> use the mature Leap 15.6
> 
> That's beyond mature. EOL is next month.

So what? I do not intend to update it till 16.1. Maybe.
It is not going to disappear from the servers.

Wasn't the problem in a machine that captures and writes camera streams 
using ffmpeg? Why do you need to keep it updated? Even more if it is a 
virtual machine.

-- 
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;

[toc] | [prev] | [next] | [standalone]

#82385

On Wed, 4 Mar 2026 13:20:07 +0100, Carlos E.R. wrote:

> On 2026-03-04 04:02, rbowman wrote:
>> On Tue, 3 Mar 2026 19:51:43 +0100, Carlos E.R. wrote:
>> 
>>> On 2026-03-02 09:58, c186282 wrote:
>>>>     And no, ffmpeg STILL crashes or hangs on Mint, MX and Trixie
>>>>     after so many startups. Can NOT find any reason.
>>>
>>> openSUSE has ffmepg in several versions, from 4 to 8. At least if you
>>> use the mature Leap 15.6
>> 
>> That's beyond mature. EOL is next month.
> 
> So what? I do not intend to update it till 16.1. Maybe.
> It is not going to disappear from the servers.

No problemo. I ran 13.2 way beyond its EOL. You do get to the point where 
stuff stops working and then it's time to move on. In my case I moved on 
to Fedora to see what it was about. 

[toc] | [prev] | [next] | [standalone]

#82389

On 2026-03-04 20:20, rbowman wrote:
> On Wed, 4 Mar 2026 13:20:07 +0100, Carlos E.R. wrote:
> 
>> On 2026-03-04 04:02, rbowman wrote:
>>> On Tue, 3 Mar 2026 19:51:43 +0100, Carlos E.R. wrote:
>>>
>>>> On 2026-03-02 09:58, c186282 wrote:
>>>>>      And no, ffmpeg STILL crashes or hangs on Mint, MX and Trixie
>>>>>      after so many startups. Can NOT find any reason.
>>>>
>>>> openSUSE has ffmepg in several versions, from 4 to 8. At least if you
>>>> use the mature Leap 15.6
>>>
>>> That's beyond mature. EOL is next month.
>>
>> So what? I do not intend to update it till 16.1. Maybe.
>> It is not going to disappear from the servers.
> 
> No problemo. I ran 13.2 way beyond its EOL. You do get to the point where
> stuff stops working and then it's time to move on. In my case I moved on
> to Fedora to see what it was about.

The problem I foresee is some site saying FFx is too old.

-- 
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;

[toc] | [prev] | [next] | [standalone]

#82331

c186282 <c186282@nnada.net> writes:

>   As said, this AQEMU app is even nicer than virt-manager
>   but it does have a few tricks - like you set up the VM
>   and QCOW2 virtual disk first, THEN use the interface
>   and add the install CD (yer ISO or image) and set it
>   to bootable. Alas you need to remove the CD after the
>   install and that's where it gets unhappy. There IS a
>   'boot order' thingie, with the CD ahead of the HDD,
>   maybe if I alter that stuff ... ?
I'm not a fan of these "wrapper" applications for QEMU because QEMU is
already complex enough without having to deal with it with mittens on
besides. In plain QEMU, the -boot option sets the devices you want to
look to in order to boot. This way, it doesn't matter if the install
media is present or not after the initial install.

-boot order=cda,menu=on

That's usually, but depending on your guest OS:
Search first hard disk.
Look to cdrom.
Search removable media (floppy).

>> In both cases the VM created a virtual NAT, using the host's connection.
>> The VMs worked fine although the IPs were something like 192.168.101.93,
>> not on my subnet as you mention.
Messy and not very functional. Use a bridge and use -bridge mode with
the qemu-bridge-helper program (which must be SETRUID). br0 should exist
beforehand.


-rws--x--x 1 root root 2598232 Sep 10 18:33 /usr/libexec/qemu-bridge-helpe
 
This will plug a tap into your bridge and off you go, assuming DHCP,
SLAAC or similar on the brige and proper routing. The external device
does not exactly have to be in the bridge.

>   I suppose Centos might be the best VM host, it was
>   kinda adjusted for hosting multiple VMs in the modern
>   fashion after all.
Slackware - it doesn't try to be the system admin for you and assume
this and that nor does it change upstream so much that it's
unrecognizable. That's perfect for doing advanced stuff. Right now I
have 6 different hosts, with different networking technologies. 

Here's a networked FreeDOS with sound, able to reach the internet via
ip4:

qemu-system-i386 -cpu 486 -m 256M -rtc base=localtime\
-device pci-serial -vga vmware -device adlib \
-device pcnet,netdev=net0,mac=52:54:00:12:34:62 \
-netdev bridge,id=net0 -serial pty \
-drive file=c_harddisk_freedos_sf.img,format=qcow2,media=disk\
-cdrom FD14BNS.iso -boot order=cda,menu=on -daemonize

When it starts, it will tell you the device that will become the first
COM device in the guest. If it's a Unix guest, you can then, for
example, login with ttyS0, use kermit, or even run uucp.

-- 
PGP Key ID: 781C A3E2 C6ED 70A6 B356  7AF5 B510 542E D460 5CAE
       "The Internet should always be the Wild West!"

[toc] | [prev] | [next] | [standalone]

#82332

On Mon, 02 Mar 2026 12:04:25 -0500, jayjwa wrote:

> Messy and not very functional. Use a bridge and use -bridge mode with
> the qemu-bridge-helper program (which must be SETRUID). br0 should exist
> beforehand.

Once again -- no ethernet, no bridge. The host only uses wifi.

[toc] | [prev] | [next] | [standalone]

#82335

On 3/2/26 13:56, rbowman wrote:
> On Mon, 02 Mar 2026 12:04:25 -0500, jayjwa wrote:
> 
>> Messy and not very functional. Use a bridge and use -bridge mode with
>> the qemu-bridge-helper program (which must be SETRUID). br0 should exist
>> beforehand.
> 
> Once again -- no ethernet, no bridge. The host only uses wifi.

   Very vexing !

   Somewhere I saw an option to 'network' via SSH.
   That's awfully round-about and surely much slower
   than wifi, but it'd be SOME connection, enough
   to xfer files at least. There's also the 'shared
   folder' option - again unclean but in theory you
   can shuttle lots of files through it.

   When I used VMs on the job the boxes were always
   wired connections to the local net ... thus I
   never really noticed this lacking in KVM.

   VBox easily finds/uses bridged connections - but, as
   said, it's currently very flakey on the latest
   Deb-derived. Works fine on my last-year's MX, but not
   on the latest one. Hopefully Trixie will get it more
   together by the .1 version - may just have to wait.

   Hmmm ... somewhere I do have a wifi bridge/repeater.
   Plug the hardwire into that and set the adapter to
   my local wifi subnet ? They're not expensive.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.misc

csiph-web