<?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 Odd vPar issue regarding console in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837531#M272772</link>
    <description>We have a SuperDome with multiple nPars, and one nPar is carved up into multiple vPars.  I defined a new vPar in vparmgr, but whenever that vPar is brought up, console access to that nPar locks up!&lt;BR /&gt;&lt;BR /&gt;Rather, all keystrokes are queued up; if I shutdown that vPar, the console processes all the inputs from when it stopped responding.  &lt;BR /&gt;&lt;BR /&gt;I've reset the GSP/MP, no help.  I can't figure out what might be happening.  I've even redefined the vPar to entirely different hardware, but the same issue persists.  I've used a different vPar name (thought perhaps the vPar database might not like it for whatever reason), same result.&lt;BR /&gt;&lt;BR /&gt;I've toasted and recreated this new vPar from both the command line as well as the GUI, no change in behavior (I thought perhaps I was missing some option).&lt;BR /&gt;&lt;BR /&gt;Any ideas where to go with figuring this out?  We've opened a call with Support, but no luck so far.  I thought perhaps the 'hive mind' here might have a pointer or two.&lt;BR /&gt;&lt;BR /&gt;BTW - the vPar software is B.11.11.01.02.&lt;BR /&gt;&lt;BR /&gt;Thanks gang!</description>
    <pubDate>Fri, 04 Aug 2006 12:19:02 GMT</pubDate>
    <dc:creator>Eric Yruegas</dc:creator>
    <dc:date>2006-08-04T12:19:02Z</dc:date>
    <item>
      <title>Odd vPar issue regarding console</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837531#M272772</link>
      <description>We have a SuperDome with multiple nPars, and one nPar is carved up into multiple vPars.  I defined a new vPar in vparmgr, but whenever that vPar is brought up, console access to that nPar locks up!&lt;BR /&gt;&lt;BR /&gt;Rather, all keystrokes are queued up; if I shutdown that vPar, the console processes all the inputs from when it stopped responding.  &lt;BR /&gt;&lt;BR /&gt;I've reset the GSP/MP, no help.  I can't figure out what might be happening.  I've even redefined the vPar to entirely different hardware, but the same issue persists.  I've used a different vPar name (thought perhaps the vPar database might not like it for whatever reason), same result.&lt;BR /&gt;&lt;BR /&gt;I've toasted and recreated this new vPar from both the command line as well as the GUI, no change in behavior (I thought perhaps I was missing some option).&lt;BR /&gt;&lt;BR /&gt;Any ideas where to go with figuring this out?  We've opened a call with Support, but no luck so far.  I thought perhaps the 'hive mind' here might have a pointer or two.&lt;BR /&gt;&lt;BR /&gt;BTW - the vPar software is B.11.11.01.02.&lt;BR /&gt;&lt;BR /&gt;Thanks gang!</description>
      <pubDate>Fri, 04 Aug 2006 12:19:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837531#M272772</guid>
      <dc:creator>Eric Yruegas</dc:creator>
      <dc:date>2006-08-04T12:19:02Z</dc:date>
    </item>
    <item>
      <title>Re: Odd vPar issue regarding console</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837532#M272773</link>
      <description>SHOOT - hit 'submit' too soon.  We have a total of 10 vPars in this nPar.  The console behaves normally when booting all other vPars until I get to this new one.  Even if it's the only vPar loaded, still locks.</description>
      <pubDate>Fri, 04 Aug 2006 12:20:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837532#M272773</guid>
      <dc:creator>Eric Yruegas</dc:creator>
      <dc:date>2006-08-04T12:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: Odd vPar issue regarding console</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837533#M272774</link>
      <description>Gaah- vPar Manager is B.11.11.01.02. &lt;BR /&gt;&lt;BR /&gt;vPar software itself is A.03.02.04.&lt;BR /&gt;&lt;BR /&gt;Sorry gang - didn't mean to confuse anyone.</description>
      <pubDate>Fri, 04 Aug 2006 13:17:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837533#M272774</guid>
      <dc:creator>Eric Yruegas</dc:creator>
      <dc:date>2006-08-04T13:17:11Z</dc:date>
    </item>
    <item>
      <title>Re: Odd vPar issue regarding console</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837534#M272775</link>
      <description>You should be aware to never press CTRL S or Q by accident - this could cause some trouble.&lt;BR /&gt;&lt;BR /&gt;And btw, the version of your vPar software is probably V.02.xx or V.03.xx - run swlist to figure out.</description>
      <pubDate>Fri, 04 Aug 2006 13:19:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837534#M272775</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2006-08-04T13:19:47Z</dc:date>
    </item>
    <item>
      <title>Re: Odd vPar issue regarding console</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837535#M272776</link>
      <description>from the release notes:&lt;BR /&gt;&lt;BR /&gt;"While a virtual partition is shutting down, panicking, or booting, typing&lt;BR /&gt;control-s to suspend its console output may cause the virtual partition to&lt;BR /&gt;stop making forward progress. The virtual partition may appear to hang."&lt;BR /&gt;&lt;BR /&gt;Could this be related to your problem?&lt;BR /&gt;&lt;BR /&gt;"a" is very close to "s" (at least at my keyboard).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Aug 2006 13:57:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837535#M272776</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2006-08-04T13:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: Odd vPar issue regarding console</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837536#M272777</link>
      <description>I've checked the CTRL-S and CTRL-Q issues (there's references in the rel notes as well as the KB).  Not the issue here.  It's specific to a given vPar being online or off.</description>
      <pubDate>Fri, 04 Aug 2006 14:38:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/odd-vpar-issue-regarding-console/m-p/3837536#M272777</guid>
      <dc:creator>Eric Yruegas</dc:creator>
      <dc:date>2006-08-04T14:38:40Z</dc:date>
    </item>
  </channel>
</rss>

