Hi,
I define 2 new LV on the vio server and run a cfgmgr on the partition and see my 2 new hdisk (hdisk6 and hdisk7).
I extend my vg vg000 (on the partition) and add the 2 hdisks.
I had a filesystem on the vg000 and when I added the disk I would like to increase the filesystem. But I cannot do a... (0 Replies)
Question is on setting of Physical and Virtual processors for LPARs to make proper use of virtualization capabilities.
Environment is a 8-way p570 with 4 LPARs.
lparVIO1 and lparVIO2:
AIX 5300-04-01
Mode/Type= Shared-SMT/Capped
Minimum Processors= 0.10
Desired Processors= 0.50
Maximum... (1 Reply)
I have clean installed AIX6.1 in this partition.
I want to run xclock but it fail to run :(
I have launch export DISPLAY=10.23.17.60:0
Then launch xclock but it will produce some error saying it failed.
Error: Can't open display: 10.23.177.60:0
When i try to google around, some say... (5 Replies)
I just wondering if there are ways to open multiple virtual terminal to a single LPAR.
After I have use putty to login to the VIOS. I will use mkvt -id <LPAR id> to open console but if my friend want to open 2 second one, it will say, VT already connected.
IS there a way to work this around ? ... (1 Reply)
Hi all,
I have the following configuration
2 ds3524 storage disk systems located over 2 locations
2 P720 server located over 2 locations
DS3524 are connected to san switch.
Each vio server has 1 fc adapter attached to a san switch.
per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Hello, hopefully someone can help me out with this, I have created a virtual Ethernet adapter on the VIO but would like to add it to my new LPAR.
On my VIO only my disk is mapped.
$ lsmap -all
SVSA Physloc Client Partition ID
--------------- --------------------------------------------... (5 Replies)
This is where I am getting stuck and I am wondering if I can get some help from the community.
I log into putty with X11 forward enable
echo $DISPLAY
DISPLAY=localhost:10.0
export DISPLAY
xclock ( I do see a clock)
:)
I am happy that I finally get to install Oracle 11g on solaris... (2 Replies)
Hello,
VIOS 2.2.1.4 using IVM.
I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user.
Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
There can be configurations in IBM Server wherein a
standalone partition is created on some supported IBM Server
Or
A VIOS - VIOC LPARs created.
Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..?
On a... (2 Replies)
Note: Newbie to IBM virtualization :-)
Query: Created a new AIX7.1 lpar on a system with same config as one before however the new one is having issues going out to physical network.
Now on comparison the only thing which differs between these two machines is an additional en1 and ent1 shown... (7 Replies)
Discussion started by: max
7 Replies
LEARN ABOUT HPUX
systemd-halt.service
SYSTEMD-HALT.SERVICE(8) systemd-halt.service SYSTEMD-HALT.SERVICE(8)NAME
systemd-halt.service, systemd-poweroff.service, systemd-reboot.service, systemd-kexec.service, systemd-shutdown - System shutdown logic
SYNOPSIS
systemd-halt.service
systemd-poweroff.service
systemd-reboot.service
systemd-kexec.service
/lib/systemd/systemd-shutdown
/lib/systemd/system-shutdown/
DESCRIPTION
systemd-halt.service is a system service that is pulled in by halt.target and is responsible for the actual system halt. Similarly,
systemd-poweroff.service is pulled in by poweroff.target, systemd-reboot.service by reboot.target and systemd-kexec.service by kexec.target
to execute the respective actions.
When these services are run, they ensure that PID 1 is replaced by the /lib/systemd/systemd-shutdown tool which is then responsible for the
actual shutdown. Before shutting down, this binary will try to unmount all remaining file systems, disable all remaining swap devices,
detach all remaining storage devices and kill all remaining processes.
It is necessary to have this code in a separate binary because otherwise rebooting after an upgrade might be broken -- the running PID 1
could still depend on libraries which are not available any more, thus keeping the file system busy, which then cannot be re-mounted
read-only.
Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in
/lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen
action. All executables in this directory are executed in parallel, and execution of the action is not continued before all executables
finished.
Note that systemd-halt.service (and the related units) should never be executed directly. Instead, trigger system shutdown with a command
such as "systemctl halt" or suchlike.
SEE ALSO systemd(1), systemctl(1), systemd.special(7), reboot(2), systemd-suspend.service(8)systemd 237SYSTEMD-HALT.SERVICE(8)