Hi Dan,
On 8 February 2017 at 18:10, Dan Yasny <dyasny(a)gmail.com> wrote:
On Wed, Feb 8, 2017 at 4:07 PM, Doug Ingham <dougti(a)gmail.com> wrote:
> Hi Guys,
> My Hosted-Engine has failed & it looks like the easiest solution will be
> to install a new one. Now before I try to re-add the old hosts (still
> running the guest VMs) & import the storage domain into the new engine, in
> case things don't go to plan, I want to make sure I'm able to bring up the
> guests on the hosts manually.
>
> The problem is vdsClient is giving me an "Unexpected exception", without
> much more info as to why it's failing.
>
> Any idea?
>
> [root@v0 ~]# vdsClient -s 0 list table | grep georep
> 9d1c3fef-498e-4c20-b124-01364d4d45a8 30455 georep-proxy Down
>
> [root@v0 ~]# vdsClient -s 0 continue 9d1c3fef-498e-4c20-b124-01364d4d45a8
> Unexpected exception
>
> /var/log/vdsm/vdsm.log
> periodic/1063::WARNING::2017-02-08 17:57:52,532::periodic::276::v
> irt.periodic.VmDispatcher::(__call__) could not run <class
> 'vdsm.virt.periodic.DriveWatermarkMonitor'> on
> ['65c9807c-7216-40b3-927c-5fd93bbd42ba', u'9d1c3fef-498e-4c20-b124-0136
> 4d4d45a8']
>
>
continue meane un-pause, not "start from a stopped state"
I search the manual for start/init/resume syntax, and "continue" was the
closest thing I found.
now having said that, if you expect the VMs not to be able to start
after
you rebuild the engine and the VMs exist on the hosts, I'd collect a virsh
-r dumpxml VMNAME for each - that way you have the disks in use, and all
the VM configuration in a file, and with some minor LVM manipulation you'll
be able to start the VM via virsh
My main concern is that I might have to halt the VMs or VDSM services for
some reason when trying to migrate to the new engine. I just want to make
sure that no matter what happens, I can still get the VMs back online.
I'm still getting myself acquainted with virsh/vdsClient. Could you provide
any insight into what I'd have to do to restart the guests manually?
Thanks,
--
Doug