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


Groups > comp.os.linux.misc > #82331

Re: Heh Heh - New Fedora, HUGE Updates Needed

From jayjwa <jayjwa@atr2.ath.cx.invalid>
Newsgroups comp.os.linux.misc
Subject Re: Heh Heh - New Fedora, HUGE Updates Needed
Date 2026-03-02 12:04 -0500
Organization atr2net 2026
Message-ID <87y0kai2na.fsf@atr2.ath.cx> (permalink)
References <3hmcneRdZ-7oQj70nZ2dnZfqn_GdnZ2d@giganews.com> <n0jdtcFoi5hU1@mid.individual.net> <WJ2cnX6XhPmkmDj0nZ2dnZfqn_udnZ2d@giganews.com>

Show all headers | View raw


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!"

Back to comp.os.linux.misc | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

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

csiph-web