One of my zone is stuck in down state, not able to boot it or halt it .. not even detach .. is there any way to recover without rebooting the whole system ( global zone ) ? (3 Replies)
Hi All,
I'm preparing to migrate some servers from vscsi to pass-thru NPIV. I am planning to have the SAN team move the exact LUNs from vio1/vio2 to those two VWWN through NPIV.
My question is on the partition itself.. right now, let's say I have hdisk0/1/2/3/4 that are part of datavg. They... (2 Replies)
Hi,
I want to change from vscsi to npiv. Is it possible to use both on the same adapter, so we can change the systems one by one, or must we place a second FC adapter in the VIO servers?
Thanks,
Ronald (2 Replies)
Hello,
I have a VIOS System and would like to do mapping some hdisks, hdisk160 until hdisk165 to a vSCSi Adapter. I try to do this in the oem_setup_env like the following:
for i in $(lspv | grep hdisk* | awk {'print $1'};
do
mkdev -V $i -p vhost20
done
There where a mapping with... (4 Replies)
If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is... (3 Replies)
Hello,
When I assigned CDROM from IVM (VIOS) to LPAR and then running cfgmgr i get the following message on the client lpar
#cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed.
devices.vscsi.disk
searching... (0 Replies)
Hi everybody,
I have Power5 server with 4 internal hdisks each of 70Gb.
VIOS server was installed via Virtual I/O Server Image Repository on the HMC.
HMC release - 7.7.0
VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
LEARN ABOUT XFREE86
xchangekeyboarddevice
XChangeKeyboardDevice(3X11) X FUNCTIONS XChangeKeyboardDevice(3X11)NAME
XChangeKeyboardDevice - change which device is used as the X keyboard
SYNTAX
Status XChangeKeyboardDevice(Display *display, XDevice *device);
ARGUMENTS
display Specifies the connection to the X server.
device Specifies the device to be used as the X keyboard.
DESCRIPTION
The XChangeKeyboardDevice request causes the server to use the specified device as the X keyboard. The device must have been previously
opened by the requesting client via XOpenDevice or a BadDevice error will result. The device must support input class Keys, or a BadMatch
error will result. If the server implementation does not support using the requested device as the X keyboard, a BadDevice error will
result.
If the specified device is grabbed by another client, AlreadyGrabbed is returned. If the specified device is frozen by a grab on another
device, GrabFrozen is returned. If the request is successful, Success is returned.
If the request succeeds, a ChangeDeviceNotify event is sent to all clients that have selected that event. A MappingNotify event with
request = MappingKeyboard is sent to all clients. The specified device becomes the X keyboard and the old X keyboard becomes accessible
through the input extension protocol requests.
XChangeKeyboardDevice can generate a BadDevice or a BadMatch error.
DIAGNOSTICS
BadDevice An invalid device was specified. The specified device does not exist, has not been opened by this client via XOpenInputDevice,
or is already one of the core X device (pointer or keyboard). This error may also occur if the server implementation does not
support using the specified device as the X keyboard.
BadMatch This error may occur if an XChangeKeyboardDevice request was made specifying a device that has no keys.
SEE ALSO
XChangePointerDevice
Programming With Xlib
XFree86 Version 4.7.0 XChangeKeyboardDevice(3X11)