<div dir="ltr">Hi Dan,<br><div><div class="gmail_extra"><br><div class="gmail_quote">On 8 February 2017 at 18:10, Dan Yasny <span dir="ltr"><<a href="mailto:dyasny@gmail.com" target="_blank">dyasny@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Feb 8, 2017 at 4:07 PM, Doug Ingham <span dir="ltr"><<a href="mailto:dougti@gmail.com" target="_blank">dougti@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Guys,<br></div><div> 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.<br></div><div><br>The problem is vdsClient is giving me an "Unexpected exception", without much more info as to why it's failing.<br><br></div><div>Any idea?<br></div><div><br>[root@v0 ~]# vdsClient -s 0 list table | grep georep<br>9d1c3fef-498e-4c20-b124-01364d<wbr>4d45a8 30455 georep-proxy Down<br><br>[root@v0 ~]# vdsClient -s 0 continue 9d1c3fef-498e-4c20-b124-01364d<wbr>4d45a8<br>Unexpected exception<br><br></div>/var/log/vdsm/vdsm.log<br><div>periodic/1063::WARNING::2017-0<wbr>2-08 17:57:52,532::periodic::276::v<wbr>irt.periodic.VmDispatcher::(__<wbr>call__) could not run <class 'vdsm.virt.periodic.DriveWater<wbr>markMonitor'> on ['65c9807c-7216-40b3-927c-5fd9<wbr>3bbd42ba', u'9d1c3fef-498e-4c20-b124-0136<wbr>4d4d45a8']<br clear="all"><br></div></div></blockquote><div><br></div></span><div>continue meane un-pause, not "start from a stopped state"</div></div></div></div></blockquote><div><br></div><div>I search the manual for start/init/resume syntax, and "continue" was the closest thing I found.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>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</div><div></div></div></div></div></blockquote><div><br></div><div>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.<br><br></div><div>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?<br><br></div><div>Thanks,<br></div></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Doug</div>
</div></div></div>