<?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: Moving bound CPUs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-bound-cpus/m-p/4993949#M422908</link>
    <description>You need to shutdown the vpar to adjust the questionable CPUs from bound to unbound using the vparmodify command. &lt;BR /&gt;Once this is done, you can assing the unbound cpu to another vpar.</description>
    <pubDate>Fri, 28 Jul 2006 15:24:10 GMT</pubDate>
    <dc:creator>Torsten.</dc:creator>
    <dc:date>2006-07-28T15:24:10Z</dc:date>
    <item>
      <title>Moving bound CPUs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-bound-cpus/m-p/4993948#M422907</link>
      <description>I have five vpars running on an RP8420.  Obviously I can move unbound CPUs around dynamically.  I have one vpar on there that is a sandbox and is only used occasionally.  When it is not in use, I would like to shut it down and make use of its one bound CPU on another vpar.  Can this be done easily and without trashing the sandbox partition?</description>
      <pubDate>Fri, 28 Jul 2006 15:09:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-bound-cpus/m-p/4993948#M422907</guid>
      <dc:creator>Chuck Kohnen</dc:creator>
      <dc:date>2006-07-28T15:09:17Z</dc:date>
    </item>
    <item>
      <title>Re: Moving bound CPUs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-bound-cpus/m-p/4993949#M422908</link>
      <description>You need to shutdown the vpar to adjust the questionable CPUs from bound to unbound using the vparmodify command. &lt;BR /&gt;Once this is done, you can assing the unbound cpu to another vpar.</description>
      <pubDate>Fri, 28 Jul 2006 15:24:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-bound-cpus/m-p/4993949#M422908</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2006-07-28T15:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: Moving bound CPUs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-bound-cpus/m-p/4993950#M422909</link>
      <description>NO iws the simple answer&lt;BR /&gt;If you have the "sandbox" vpar configued and in the vpdb, that bound cpu is used, and cannot be used anywhere else.&lt;BR /&gt;You would need to delete the vpar, and then recreate it when you needed it again</description>
      <pubDate>Fri, 28 Jul 2006 15:27:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-bound-cpus/m-p/4993950#M422909</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2006-07-28T15:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: Moving bound CPUs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/moving-bound-cpus/m-p/4993951#M422910</link>
      <description>The only way to do what I want to do is to destroy the partition.</description>
      <pubDate>Mon, 31 Jul 2006 10:59:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/moving-bound-cpus/m-p/4993951#M422910</guid>
      <dc:creator>Chuck Kohnen</dc:creator>
      <dc:date>2006-07-31T10:59:24Z</dc:date>
    </item>
  </channel>
</rss>

