<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: VM's still selected after vMotion... in VMware vCenter™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944557#M47029</link>
    <description>&lt;P&gt;reproduced, filed a bug for it.&lt;/P&gt;</description>
    <pubDate>Mon, 19 Dec 2022 09:45:28 GMT</pubDate>
    <dc:creator>depping</dc:creator>
    <dc:date>2022-12-19T09:45:28Z</dc:date>
    <item>
      <title>VM's still selected after vMotion...</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944435#M47016</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;today i had a bad experience in my current vSphere 8.0 environment...&lt;BR /&gt;&lt;BR /&gt;To install the latest patches i was on one host, on the tab with all VM's on that host i selected all running VM's except 3 with local devices.&lt;BR /&gt;&lt;BR /&gt;This VM's i moved with drag/drop to a other host.&lt;BR /&gt;&lt;BR /&gt;After this was finished i selected the 3 other VM's to shutdown the VM's.&lt;BR /&gt;&lt;BR /&gt;But what i missed, at the status line at the bottom of the VM list window, still shows that more than 20 VM's are selected. So i have shutdown manny of the VM's i just moved. Not all, because the vCenter was one of them.&lt;BR /&gt;&lt;BR /&gt;This behavior can't be correct and is very dangerous!&lt;BR /&gt;&lt;BR /&gt;Has someone seen this too? Is this a known issue and on the list to be fixed? Or must i open here a SR? The problem, we have only 5 SR in a year, and it is bad to waste this for bugs...&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Stefan&lt;/P&gt;</description>
      <pubDate>Sat, 17 Dec 2022 14:06:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944435#M47016</guid>
      <dc:creator>Raudi</dc:creator>
      <dc:date>2022-12-17T14:06:10Z</dc:date>
    </item>
    <item>
      <title>Re: VM's still selected after vMotion...</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944554#M47027</link>
      <description>&lt;P&gt;I will try to replicate it in my lab, and file a bug...&lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2022 09:32:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944554#M47027</guid>
      <dc:creator>depping</dc:creator>
      <dc:date>2022-12-19T09:32:10Z</dc:date>
    </item>
    <item>
      <title>Re: VM's still selected after vMotion...</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944555#M47028</link>
      <description>&lt;P&gt;Hi, that will be great, thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2022 09:34:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944555#M47028</guid>
      <dc:creator>Raudi</dc:creator>
      <dc:date>2022-12-19T09:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: VM's still selected after vMotion...</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944557#M47029</link>
      <description>&lt;P&gt;reproduced, filed a bug for it.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2022 09:45:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944557#M47029</guid>
      <dc:creator>depping</dc:creator>
      <dc:date>2022-12-19T09:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: VM's still selected after vMotion...</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944635#M47038</link>
      <description>&lt;P&gt;I noticed this behavior after the 7.0 update 3h update so the behavior exists on 7.0.3 as well.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2022 18:45:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944635#M47038</guid>
      <dc:creator>fgl</dc:creator>
      <dc:date>2022-12-19T18:45:35Z</dc:date>
    </item>
    <item>
      <title>Re: VM's still selected after vMotion...</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944704#M47047</link>
      <description>&lt;P&gt;Fix is being worked on I have been told.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Dec 2022 07:49:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VM-s-still-selected-after-vMotion/m-p/2944704#M47047</guid>
      <dc:creator>depping</dc:creator>
      <dc:date>2022-12-20T07:49:29Z</dc:date>
    </item>
  </channel>
</rss>

