On Tue, 16 Feb 2021 18:39:50 +0000
g4sra via Dng <dng@???> wrote:

> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Tuesday, February 16, 2021 12:55 PM, Steve Litt
> <slitt@???> wrote:
>
> > On Tue, 16 Feb 2021 20:29:46 +1100
> > Ralph Ronnquist via Dng dng@??? wrote:
> >
> > > On 16/02 03:24, Steve Litt wrote:
> > >
> > > > Hi all,
> > > > My ultimate goal is to have a Devuan VM guest on my Void Linux
> > > > Daily Driver Desktop (DDD) that acts like just another metal
> > > > computer on my LAN at 192.168.0.0/24. I want it to have address
> > > > 192.168.0.66. I've tried to do this sporadically over the past
> > > > 2 years, never with success. ...
> > > > I tried setting the VM guest's /etc/network/interfaces to static
> > > > with address 192.168.0.66, with the gateway, netmask etc set
> > > > accordingly, but after doing that, ip addr on the VM showed no
> > > > IP address at all.
> > >
> > > It all looks fine, and static setup should work. Possibly you
> > > left out the "auto eth0" or "allow-hotplug eth0" line?
> >
> > Thanks Ralph,
> >
> > I had left them both out, but putting them in didn't change the
> > symptom. I tried with only auto eth0, and that didn't change the
> > symptom either.
> >
> > Thanks,
> >
> > SteveT

>
> I gave up doing things this way as Qemu kept changing under me,
> voiding my scripts. I now use 'virt-manager' relatively painlessly.

Thanks g4sra,

I tried virt-manager but became disallusioned. First, a look at the man
page told me that although virt-manager can be used without systemd,
systemd is invading. Worse, you can't use virt-manager without dbus. I
consider dbus the ultimate anti-encapsulation thing ever invented: On
troubleshooting, you have to chase *everything* through dbus. When
encountering a "no dbus" error with virt-manager, I found out that I'd
never run the dbus daemon, which is why every time I start LXDE on a
Void Linux machine, I get a "no dbus" error, which I always just
ignored.

Also, even after I ran the dbus daemon, virt-manager didn't work. I'd
have troubleshot it, but at that point I figured if I were going to
troubleshoot anything, it would be pure qemu, because the end result
would be a script that would work every time, not a set of clicks. This
is also the reason I didn't run Gnome-Boxes or VirtualBox.

>
> That IP may have been issued by a Qemu dhcp server.

Yes.

> The first step is to confirm Qemu is not messing with stuff it
> shouldn't... Spin up the VM and confirm that your host network
> settings have not been altered/added to. You must do this when the VM
> is running.

I've read that tap devices are DOWN until something actually uses them.
But yeah, I'll do an ip link and ip addr before, and after I run the
qemu guest, and do a diff on the results. That should shed some light
on it. Thanks for the suggestion!

SteveT

Steve Litt
Autumn 2020 featured book: Thriving in Tough Times
http://www.troubleshooters.com/thrive