- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Some questiones about VPAR6.0
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2011 08:14 AM - edited 12-20-2011 07:22 PM
12-14-2011 08:14 AM - edited 12-20-2011 07:22 PM
Some questiones about VPAR6.0
Q1:According to the following output, how many MEMORY I can use to create a new vpar? 48000?
root@server[/] # vparhwmgmt -p memory -l System Memory Sizes LDOM# Size(MB) Free(MB) 0 14336 184 1 14336 943 2 14336 1295 3 14336 1265 4 14336 1356 5 14336 1395 6 14336 1384 7 14040 1119 -1 16361 2 Total: 130753 8943 vPar/VM Memory Pool Sizes LDOM# Size(MB) Free(MB) 0 12864 0 1 12864 0 2 12864 0 3 12800 0 4 12800 12032 5 12800 12032 6 12800 12096 7 12544 11840 -1 12032 0 Total: 114368 48000
Q2: When I reboot the VSP OS, the vpar boot up automatically. How can I change the "auto boot" setting ?
==================
Adding new questions
12.17 2011
Q3: one vpar has some LUNs which state are NO_HW in the VSP OS. I cannot boot it up and even modify the vpar. what should I do?
The output is:
# vparmodify -p rxna2 -a disk:avio_stor::disk:/dev/rdisk/disk8
vPar/VM rxna2 configuration problems:
Error 1 on item /dev/rdisk/disk5: '/dev/rdisk/disk5' backing device does not exist or is not currently available.
vparmodify: Unable to modify the vPar.
#vparboot -p rxna2
vparboot: ERROR (host): libIO error on function call 'io_is_legacy_dev': System call error. on device /dev/rdisk/disk112.
vPar/VM rxna2 configuration problems: Warning 1 on item /tmp/hpux31.1109.iso: '/tmp/hpux31.1109.iso' backing devic e does not exist or is not currently available.
These problems may prevent the vPar or VM rxna2 from starting.
vparboot: Unable to continue.
Because the Storage guy has delete the unused LUN, so the ioscan -fnNCdisk cannot show out the "disk112".
what should I do?
Q4: Where is the configuration file of every vpar?
Continue waiting.
Q5:
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2011 08:35 AM
12-14-2011 08:35 AM
Re: Some questiones about VPAR6.0
>> Q2: When I reboot the VSP OS, the vpar boot up automatically. How can I change the "auto boot" setting ?
VSP# hpvmmodify -P <vparname> -B manual
François
- Tags:
- hpvmmodify
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2011 09:10 AM
12-14-2011 09:10 AM
Re: Some questiones about VPAR6.0
Q1:According to the following output, how many MEMORY I can use to create a new vpar?
What does "hpvmstatus -s" show on your VSP? As an example:
# hpvmstatus -s
[HPVM Server System Resources]
vPar/VM types supported by this VSP = vPar
Processor speed = 1729 Mhz
Total physical memory = 261826 Mbytes
Total number of operable system cores = 32
CPU cores allocated for VSP = 1
CPU cores allocated for vPars and VMs = 31
CPU cores reserved for virtual partitions = 16
Available VSP memory = 18166 Mbytes
Available swap space = 31471 Mbytes
Total memory allocated for vPars and VMs = 231744 Mbytes
Memory in use by vPars and VMs = 98304 Mbytes
Available memory for vPars and VMs = 133440 Mbytes <<<
The "Available memory for vPars and VMs" line should give you a good idea of the memory available to dedicate to vPars.
Dave
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2011 08:22 PM
12-14-2011 08:22 PM
Re: Some questiones about VPAR6.0
hi Donze,
thanks!
But I cannot find out the -B option in vparmodify manpage. Later I will test this in the OS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2011 08:22 PM
12-14-2011 08:22 PM
Re: Some questiones about VPAR6.0
Dear Dave,
thanks a lot!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2011 08:23 PM
12-14-2011 08:23 PM
Re: Some questiones about VPAR6.0
I think if you check again you'll see Francois suggested using the hpvmmodify command, not the vparmodify command.
Dave
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2011 07:55 AM
12-17-2011 07:55 AM
Re: Some questiones about VPAR6.0
Sorry, I find it.
It's quite strange, VM's command can be used to set VPAR's attribute.
We need a VPAR6.0 CLI guide.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2011 08:26 AM - edited 12-17-2011 08:27 AM
12-17-2011 08:26 AM - edited 12-17-2011 08:27 AM
Re: Some questiones about VPAR6.0
Yes, the v6 CLI is a bit confusing because we needed to preserve as much of the vPar experience as possible for previous vPar customers and at the same time prepare for v6.1 where you'll be able to run either vPars or VMs on a VSP using a common set of commands.
To clarify - the plan for v6.1 is to allow you to run either VM's or vPars on a single VSP, but not both simultaneously. Simultaneous vPars and VMs on the same VSP is a future roadmap item.
Dave
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2011 09:13 AM
12-17-2011 09:13 AM
Re: Some questiones about VPAR6.0
Dear Dave:
Thanks!
Could you tell me the bigest difference between VPAR6.x and VM in our future planning?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2011 08:49 PM
12-17-2011 08:49 PM
Re: Some questiones about VPAR6.0
Hi Jack,
Here are a couple of slides from my vPars v6 presentation that compare vPars v6 against HPVM v4.3. If you have any questions about what any of these comparisons mean let me know.
Dave
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]