ML
    • Register
    • Login
    • Search
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups

    vMotion causing glitches on moved machines

    IT Discussion
    vmware vmware esxi virtualization storage vmotion
    10
    28
    2833
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • WLS-ITGuy
      WLS-ITGuy last edited by

      Vsphere ESXi Essentials Plus 5.5

      3 hosts are all HP Proliant gen 9 servers. Storage is Netgear ReadyNAS 3312.

      Nothing errors out when moving from one host to another. Nothing in the logs that I can see but I could be looking in the wrong place.

      F travisdh1 2 Replies Last reply Reply Quote 0
      • F
        Francesco Provino @WLS-ITGuy last edited by

        @WLS-ITGuy said in vMotion causing glitches on moved machines:

        3 hosts are all HP Proliant gen 9 servers. Storage is Netgear ReadyNAS 3312.

        WAT

        1 Reply Last reply Reply Quote 1
        • Dashrender
          Dashrender last edited by

          I summon the IPOD executioner - @scottalanmiller

          1 Reply Last reply Reply Quote 1
          • travisdh1
            travisdh1 @WLS-ITGuy last edited by

            @WLS-ITGuy said in vMotion causing glitches on moved machines:

            Vsphere ESXi Essentials Plus 5.5

            3 hosts are all HP Proliant gen 9 servers. Storage is Netgear ReadyNAS 3312.

            Nothing errors out when moving from one host to another. Nothing in the logs that I can see but I could be looking in the wrong place.

            That Netgear ReadyNAS is probably a good device for backup. As main storage for a cluster, not so much. Is this a lab?

            1 Reply Last reply Reply Quote 0
            • scottalanmiller
              scottalanmiller last edited by

              That setup is terrible, but it shouldn't be the cause of any issues here. vMotion should not cause corruption even with a highly risky setup like that.

              1 Reply Last reply Reply Quote 1
              • dafyre
                dafyre last edited by

                I wonder if we should tag @John-Nicholson ?

                1 Reply Last reply Reply Quote 0
                • WLS-ITGuy
                  WLS-ITGuy last edited by

                  The ReadyNAS is set up as iSCSI and is certified to work with vSphere. Why is it risky?

                  Dashrender DustinB3403 scottalanmiller 3 Replies Last reply Reply Quote 0
                  • Dashrender
                    Dashrender @WLS-ITGuy last edited by Dashrender

                    @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?

                    But you have an inverted pyramid setup.

                    Three servers going to (we hope) two switches going to one SAN.

                    If the SAN fails the whole thing fails.

                    Instead of making your system safer, it's actually, risk wise, noticeably less safe.

                    1 Reply Last reply Reply Quote 2
                    • DustinB3403
                      DustinB3403 @WLS-ITGuy last edited by DustinB3403

                      @WLS-ITGuy The issue that @Dashrender and @scottalanmiller have posted about are regarding the overall system design. Which isn't related (as far as we can tell) the root of your problem.

                      Since your VM's are using shared non-redundant storage the issue has to lye somewhere else.

                      vSphere 5.5 is quite out of date, and could be the cause of the problem.

                      1 Reply Last reply Reply Quote 2
                      • travisdh1
                        travisdh1 last edited by

                        Have you run an fsck on the drives/partitions and have it find something wrong?

                        1 Reply Last reply Reply Quote 0
                        • scottalanmiller
                          scottalanmiller @WLS-ITGuy last edited by

                          @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.

                          1 Reply Last reply Reply Quote 1
                          • scottalanmiller
                            scottalanmiller last edited by

                            https://mangolassi.it/topic/8821/risk-3-2-1-stock-inverted-pyramid-design/

                            1 Reply Last reply Reply Quote 0
                            • Reid Cooper
                              Reid Cooper last edited by

                              Doesn't vMotion move the memory state? Should not corrupt as the VM never stops, I thought.

                              travisdh1 1 Reply Last reply Reply Quote 1
                              • travisdh1
                                travisdh1 @Reid Cooper last edited by

                                @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.

                                1 Reply Last reply Reply Quote 0
                                • scottalanmiller
                                  scottalanmiller last edited by

                                  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.

                                  1 Reply Last reply Reply Quote 1
                                  • WLS-ITGuy
                                    WLS-ITGuy last edited by

                                    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.

                                    travisdh1 1 Reply Last reply Reply Quote 0
                                    • travisdh1
                                      travisdh1 @WLS-ITGuy last edited by

                                      @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.

                                      WLS-ITGuy 1 Reply Last reply Reply Quote 0
                                      • WLS-ITGuy
                                        WLS-ITGuy @travisdh1 last edited by WLS-ITGuy

                                        @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.

                                        travisdh1 1 Reply Last reply Reply Quote 0
                                        • travisdh1
                                          travisdh1 @WLS-ITGuy last edited by

                                          @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.

                                          WLS-ITGuy 1 Reply Last reply Reply Quote 0
                                          • WLS-ITGuy
                                            WLS-ITGuy @travisdh1 last edited by

                                            @travisdh1 Even though I may get slammed for asking this, How would I make a temp image, Clone to VM?

                                            travisdh1 JaredBusch NetworkNerd 3 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post