vMotion causing glitches on moved machines
-
@WLS-ITGuy said in vMotion causing glitches on moved machines:
The ReadyNAS is set up as iSCSI and is certified to work with vSphere. Why is it risky?
None of the "pieces" are risky, it's the fundamental design that you have. Would you buy the biggest, baddest server and then run it without RAID on a single consumer hard drive? That's what you have here - loads of high end parts and protection all resting on a single point of failure that should never be used in this way.
Certified means "tested as compatible" and in no way tells you it is safe to use or less.... that it is safe to use as you have used it. Your setup is significantly more costly but less safe than just running a single server.
-
-
Doesn't vMotion move the memory state? Should not corrupt as the VM never stops, I thought.
-
@Reid-Cooper said in vMotion causing glitches on moved machines:
Doesn't vMotion move the memory state? Should not corrupt as the VM never stops, I thought.
Yeah, that's why I'm wondering if this is something corrupt in the inodes or the like. Moving the VM between hosts shouldn't effect that at all.
-
I agree, the memory should be protecting it from corruption. Not sure what stage would expose the storage here. Possible it is a bug, but that's unlikely in VMware.
-
I can tell you that we are on the latest build version of 5.5. I run the move from the web client and I select the reserve for optimal performance on the migration. I am just moving the VM from one host to another.
-
@WLS-ITGuy said in vMotion causing glitches on moved machines:
I can tell you that we are on the latest build version of 5.5. I run the move from the web client and I select the reserve for optimal performance on the migration. I am just moving the VM from one host to another.
Have you run an fsck before doing the vmotion? I'm wondering if it's something pre-existing that just isn't caught.
-
@travisdh1 I did one after because it required it to get it working again. I cannot recall if I have done one since doing the fsck.
-
@WLS-ITGuy said in vMotion causing glitches on moved machines:
@travisdh1 I did one after because it required it to get it working again. I cannot recall if I have done one since doing the fsck.
Now we're getting somewhere at least. We just don't know weather doing the vmotion is causing the issue. Can you make a temp image of the machine (no networking), and do an fsck on it before and after doing a vmotion? That'll help us eliminate one cause at least.
-
@travisdh1 Even though I may get slammed for asking this, How would I make a temp image, Clone to VM?
-
@WLS-ITGuy said in vMotion causing glitches on moved machines:
@travisdh1 Even though I may get slammed for asking this, How would I make a temp image, Clone to VM?
I'm not used to ESXi, so possibly different. Take snapshot -> restore from snapshot -> remove all network interfaces during the restore options.
-
@travisdh1 I believe you can create a new VM from a snap, just like what can be done with XS.
-
@WLS-ITGuy said in vMotion causing glitches on moved machines:
@travisdh1 Even though I may get slammed for asking this, How would I make a temp image, Clone to VM?
We won't slam you for saying you don't know and asking.
-
@WLS-ITGuy said in vMotion causing glitches on moved machines:
@travisdh1 Even though I may get slammed for asking this, How would I make a temp image, Clone to VM?
If you have vCenter, you should be able to right-click and clone the VM in question to a new VM or to a template. I cannot remember, however, if the VM must be powered off to clone to a new VM.
-
Was able to make the vm clone. When I booted up I didn't have any issue so I wasn't required to fsck anything. Moving it now and I'll check it and post again.
-
@WLS-ITGuy No issues. Wasn't required to fsck after a reboot.
