[clug] VM initiated VMotion

[Stephen Hocking]

HI Hugh & Steve,

THere are issues with some of the hosts in the cluster, where they don't
have full access to the VLAN they advertise, usually manifesting by VMs
being able to talk to anything else on the network, including the default
route.

So sending network messages to an external process to initiate the transfer
won't work.

I was hoping for a way to communicate with the hypervisor via the kernel
module. The boxes get migrated around the cluster a fair bit, as part of
VMWare's internal load-balancing process.

Ideally, the dodgy  hosts and their VLAN issues should get fixed, but the
VMWare team is overloaded and we keep on getting hammered by reports of VMs
that are seemingly down.


On Wed, 14 Dec 2022 at 22:52, Hugh Fisher <hugo.fisher at gmail.com> wrote:

> On Wed, 14 Dec 2022 at 16:28, Stephen Hocking via linux
> <linux at lists.samba.org> wrote:
> >
> > Hi all,
> >
> > My googling skills have fallen short - I've wondered if there's a way
> for a
> > VM to initiate its own VMotion to another physical host in the cluster.
> > There's one or two physicals in the cluster which are having problems
> with
> > some VLANs, so that a VM that uses them can't even ping its default
> route.
> > Am loath to use affinity rules, as it's possible the VLAN issues might go
> > away without me being told.
>
> You want to give your VMs the ability to move themselves across the
> network?
>
> Many bad science fiction stories have taught me that this will only
> lead to your VMs escaping onto the Internet, where they will
> undoubtedly acquire a GPT-3 AI and become fully sentient threats to
> all of humanity.
>
> Seriously, this could lead to some ... interesting ... Sorcerer's
> Apprentice type incidents.
> --
>
>         cheers,
>         Hugh (Hugo) Fisher
>


-- 

  "I and the public know
  what all schoolchildren learn
  Those to whom evil is done
  Do evil in return"		W.H. Auden, "September 1, 1939"