<?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 CPU scheduler &amp;quot;automatic relation removal&amp;quot;  causing vm freeze, esxi 6.7U2, threadripper, gpu in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-scheduler-quot-automatic-relation-removal-quot-causing-vm/m-p/1836435#M19679</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Interesting problem, I can't find another example of it listed anywhere.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4 win 10 vm's on esxi 6.7U2 host, each with a GPU pass through and therefore reserved memory.&amp;nbsp; NUMA enabled in BIOS. 8 vcpu's per vm on&amp;nbsp; a 16 core threadripper 1950x.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each vm gets occasional (every few hours of use) freezes where the running application becomes unresponsive. Task manager is still accessible but you can't actually do anything from it.&amp;nbsp; If the vm is power cycled from the host it reboots normally. Host does not freeze or crash and other vm's unaffected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The host error log always gives something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2019-06-26T23:51:42.491Z cpu26:2097396)WARNING: CpuSched: 996: Automatic relation removal from 2100712(vmx-vcpu-0:VM3, VM1) to 2100713(PVSCSI-2100577:1)&lt;/P&gt;&lt;P&gt;2019-06-26T23:51:51.491Z cpu22:2097396)WARNING: CpuSched: 996: Automatic relation removal from 2100566(vmx-vcpu-0:VM2, VM1) to 2100567(LSI-2100430:0)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where "VM1" is the name of a vm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; VM1 is always involved, others may or may not be; and the second listing is always PVSCI or LSI&amp;nbsp; (which are virtual SCSI adapters.) The freezes can happen on ANY of the 4 vm's, but vm1 is the least stable. Freezes only occur when the VM (that freezes) is under load, and not at idle.&amp;nbsp; VM1 load doesn't seem to freeze the other vm's, only itself, but with freezes this intermittent it's hard to be sure of.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven't changed the default vm cpu scheduler. Latest BIOS / AGESA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since these warnings always accompany a freeze I assume they are related, but I can't find any documentation of what they mean let alone how to resolve them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone have a clue?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;LT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 28 Jun 2019 14:58:44 GMT</pubDate>
    <dc:creator>Memnarch</dc:creator>
    <dc:date>2019-06-28T14:58:44Z</dc:date>
    <item>
      <title>CPU scheduler "automatic relation removal"  causing vm freeze, esxi 6.7U2, threadripper, gpu</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-scheduler-quot-automatic-relation-removal-quot-causing-vm/m-p/1836435#M19679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Interesting problem, I can't find another example of it listed anywhere.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4 win 10 vm's on esxi 6.7U2 host, each with a GPU pass through and therefore reserved memory.&amp;nbsp; NUMA enabled in BIOS. 8 vcpu's per vm on&amp;nbsp; a 16 core threadripper 1950x.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each vm gets occasional (every few hours of use) freezes where the running application becomes unresponsive. Task manager is still accessible but you can't actually do anything from it.&amp;nbsp; If the vm is power cycled from the host it reboots normally. Host does not freeze or crash and other vm's unaffected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The host error log always gives something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2019-06-26T23:51:42.491Z cpu26:2097396)WARNING: CpuSched: 996: Automatic relation removal from 2100712(vmx-vcpu-0:VM3, VM1) to 2100713(PVSCSI-2100577:1)&lt;/P&gt;&lt;P&gt;2019-06-26T23:51:51.491Z cpu22:2097396)WARNING: CpuSched: 996: Automatic relation removal from 2100566(vmx-vcpu-0:VM2, VM1) to 2100567(LSI-2100430:0)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where "VM1" is the name of a vm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; VM1 is always involved, others may or may not be; and the second listing is always PVSCI or LSI&amp;nbsp; (which are virtual SCSI adapters.) The freezes can happen on ANY of the 4 vm's, but vm1 is the least stable. Freezes only occur when the VM (that freezes) is under load, and not at idle.&amp;nbsp; VM1 load doesn't seem to freeze the other vm's, only itself, but with freezes this intermittent it's hard to be sure of.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven't changed the default vm cpu scheduler. Latest BIOS / AGESA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since these warnings always accompany a freeze I assume they are related, but I can't find any documentation of what they mean let alone how to resolve them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone have a clue?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;LT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Jun 2019 14:58:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-scheduler-quot-automatic-relation-removal-quot-causing-vm/m-p/1836435#M19679</guid>
      <dc:creator>Memnarch</dc:creator>
      <dc:date>2019-06-28T14:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: CPU scheduler "automatic relation removal"  causing vm freeze, esxi 6.7U2, threadripper, gpu</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-scheduler-quot-automatic-relation-removal-quot-causing-vm/m-p/1836436#M19680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all-- in case anyone else ever runs into this--&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the VM in question had bad USB driver&amp;nbsp;&amp;nbsp;&amp;nbsp; that was causing it to hang.&amp;nbsp; The vmware warnings above happened on rebooting the hanged vm, not and the crash itself.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jul 2019 16:00:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-scheduler-quot-automatic-relation-removal-quot-causing-vm/m-p/1836436#M19680</guid>
      <dc:creator>Memnarch</dc:creator>
      <dc:date>2019-07-05T16:00:26Z</dc:date>
    </item>
  </channel>
</rss>

