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

    vMotion causing glitches on moved machines

    IT Discussion
    vmware vmware esxi virtualization storage vmotion
    10
    28
    4.3k
    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.
    • scottalanmillerS
      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 CooperR
        Reid Cooper
        last edited by

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

        travisdh1T 1 Reply Last reply Reply Quote 1
        • travisdh1T
          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
          • scottalanmillerS
            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-ITGuyW
              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.

              travisdh1T 1 Reply Last reply Reply Quote 0
              • travisdh1T
                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-ITGuyW 1 Reply Last reply Reply Quote 0
                • WLS-ITGuyW
                  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.

                  travisdh1T 1 Reply Last reply Reply Quote 0
                  • travisdh1T
                    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-ITGuyW 1 Reply Last reply Reply Quote 0
                    • WLS-ITGuyW
                      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?

                      travisdh1T JaredBuschJ NetworkNerdN 3 Replies Last reply Reply Quote 0
                      • travisdh1T
                        travisdh1 @WLS-ITGuy
                        last edited by

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

                        DustinB3403D 1 Reply Last reply Reply Quote 0
                        • DustinB3403D
                          DustinB3403 @travisdh1
                          last edited by

                          @travisdh1 I believe you can create a new VM from a snap, just like what can be done with XS.

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

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

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

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

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

                                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-ITGuyW 1 Reply Last reply Reply Quote 2
                                • WLS-ITGuyW
                                  WLS-ITGuy @WLS-ITGuy
                                  last edited by

                                  @WLS-ITGuy No issues. Wasn't required to fsck after a reboot.

                                  1 Reply Last reply Reply Quote 1
                                  • 1
                                  • 2
                                  • 2 / 2
                                  • First post
                                    Last post