- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Virtual partition monitor
Operating System - HP-UX
1758859
Members
3212
Online
108876
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
02-04-2007 12:21 PM
02-04-2007 12:21 PM
# vparboot -p vpar2.abc
vparboot: Error: Virtual partition monitor not running.
How can i restart my vpar monitoring ?
vparboot: Error: Virtual partition monitor not running.
How can i restart my vpar monitoring ?
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2007 12:50 PM
02-04-2007 12:50 PM
Solution
I understand you have not booted from the vpar because vpmon starts before loading kernel as vpmon itself loads the kernel...
I hope this is not the first time you are booting this vpar and AUTO file is updated using the following command:
mkboot -a â hpux /stand/vpmon -a" /dev/rdsk/cXtYdZ
(It's not possible to start vpmon and if it is not running that means system has not booted under a vpar)
Do check the AUTO file string before rebooting else system will boot normally. This can be checked using the following command:
lifcp /dev/dsk/cXtYdZ:AUTO -
where cXtYdZ is the root disk.
I hope this is not the first time you are booting this vpar and AUTO file is updated using the following command:
mkboot -a â hpux /stand/vpmon -a" /dev/rdsk/cXtYdZ
(It's not possible to start vpmon and if it is not running that means system has not booted under a vpar)
Do check the AUTO file string before rebooting else system will boot normally. This can be checked using the following command:
lifcp /dev/dsk/cXtYdZ:AUTO -
where cXtYdZ is the root disk.
Time has a wonderful way of weeding out the trivial
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP