You have to get your HMC involved because the vio server and your client LPAR can only see their own slot numbers for their adapters. I don't think either can see the other server's slot number, maybe they can but I'm not sure how.
Here is how it can be done though. In this example, slot 11 on the VIO server connects to slot C9 on the client.
Get the slot number of the vscsi0 from the client side using "lsslot -c slot":
Assuming your managed system's name is "MANAGEDSYSTEM", query your HMC with the 'lshwres' command and grep out your client LPAR's hostname and slot number. From this command you'll see the client slot to VIO slot association (make sure to put the comma inside the double-quotes of the grep):
You can verify the resulting VIO slot number information by looking at the 'lsmap -all' output on your VIO server:
We're using VIO (not an HMC) to manage our LPAR's We have 3 physical adapters and 4 LPARs. Through the VIO interface we assigned 2 virtual interfaces but require a 3rd interface assigned to these LPARs. I am experiencing issues understanding exactly how to create another virtual adapter, either... (1 Reply)
Hi,
I am little confused about the virtual Ethernet configuration on VIO and Client Partitions. There is alot of info on the internet but it gets more confusing....
If I have LHEA, it is very simple. Just assign LHEA (logical host ethernet adapter) to client partition -> run smitty tcpip and... (10 Replies)
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Hi,
I would like to reboot vio client but I am not able to access vio client(I am not able to get putty) , I am able to get putty of vio server,
is there any command by using which from vio server I can reboot vio client? (3 Replies)
Hi,
I am having single p series blade with Single Physcial CPU with dual core,
on that vio server is installed, I have created vio client allocate 0.9 each cpu , now when I am running prtconf command on vio client it is showing "2" no of processor,
My query using which command it will... (1 Reply)
Hi
I am facing very strange issue on my vio server 5 vio clients are confgured, now I am to connect 3 vio client , i am unable to connect 2 vio client my ip address,subnet mask,gateway is correct.
i have rebooted and reconfigured the ip address, but issue is persists.
Kindly suggest how to... (0 Replies)
Hi
im logged in to the vio servers now.
when i give
# lspv | wc -l
i get the count as 6246
how will i know if a lun has been already mapped to a vio client or it is left free without mapping to any of the vio client ? (1 Reply)
Hi
In my vio server I have the below output
$ lsvopt | grep -i SAPSITGS
sapsitgs_cdrom TL12UP.iso 3182
In my vio client lpar I have the below output
root@sapsitgs:/ # lsdev -Cc cdromcd0 Available Virtual SCSI Optical Served by VIO Server
cd1... (1 Reply)
I know the VIOs are generally to be treated as an appliance and one should never drop down to oem_setup_env. In reality however, oem is a very useful tool to get the job done. So that leads me into the question of using the Chef client on a VIO.
Currently a big push to manage all our *nix... (4 Replies)
I have a broken PV in a VIO VG that's used to support client LPARs using LVs. On the client LPAR, I reduced all PVs from the relevant client VG and thus deleted it. I.e. there is no client LPAR using the VIO VG. Yet when I try to reducevg the VIO VG, it complains that the LV hosted on the PV is... (2 Replies)
Discussion started by: maraixadm
2 Replies
LEARN ABOUT XFREE86
xsetdevicemodifiermapping
XGetDeviceModifierMapping(3X11) X FUNCTIONS XGetDeviceModifierMapping(3X11)NAME
XGetDeviceModifierMapping, XSetDeviceModifierMapping - query or change device modifier mappings
SYNTAX
int XSetDeviceModifierMapping(Display *display, XDevice *device, XModifierKeymap *modmap);
XModifierKeymap *XGetDeviceModifierMapping(Display *display, XDevice *device);
ARGUMENTS
display Specifies the connection to the X server.
device Specifies the device whose modifier mapping is to be queried or modified.
modmap Specifies a pointer to the XModifierKeymap structure.
DESCRIPTION
The XSetDeviceModifierMapping request specifies the KeyCodes of the keys (if any) that are to be used as modifiers for the specified
device. If it succeeds, the X server generates a DeviceMappingNotify event, and XSetDeviceModifierMapping returns MappingSuccess. X per-
mits at most eight modifier keys. If more than eight are specified in the XModifierKeymap structure, a BadLength error results.
The modifiermap member of the XModifierKeymap structure contains eight sets of max_keypermod KeyCodes, one for each modifier in the order
Shift, Lock, Control, Mod1, Mod2, Mod3, Mod4, and Mod5. Only nonzero KeyCodes have meaning in each set, and zero KeyCodes are ignored. In
addition, all of the nonzero KeyCodes must be in the range specified by min_keycode and max_keycode as returned by XListInputDevices, or a
BadValue error results. No KeyCode may appear twice in the entire map, or a BadValue error results.
An X server can impose restrictions on how modifiers can be changed, for example, if certain keys do not generate up transitions in hard-
ware, if auto-repeat cannot be disabled on certain keys, or if multiple modifier keys are not supported. If some such restriction is vio-
lated, the status reply is MappingFailed, and none of the modifiers are changed. If the new KeyCodes specified for a modifier differ from
those currently defined and any (current or new) keys for that modifier are in the logically down state, XSetDeviceModifierMapping returns
MappingBusy, and none of the modifiers is changed.
XSetDeviceModifierMapping can generate BadLengthP, BadDevice, BadMatch, BadAlloc, and BadValue errors.
The XGetDeviceModifierMapping request returns a pointer to a newly created XModifierKeymap structure that contains the keys being used as
modifiers. The structure should be freed after use by calling XFreeModifierMapping . If only zero values appear in the set for any modi-
fier, that modifier is disabled.
XGetDeviceModifierMapping can generate BadDevice and BadMatch errors.
STRUCTURES
The XModifierKeymap structure contains:
typedef struct {
int max_keypermod;
KeyCode *modifiermap;
} XModifierKeymap;
DIAGNOSTICS
BadLength More than eight keys were specified in the XModifierKeymap structure.
BadAlloc The server failed to allocate the requested resource or server memory.
BadDevice An invalid device was specified. The specified device does not exist or has not been opened by this client via XOpenInputDe-
vice. This error may also occur if the specified device is the X keyboard or X pointer device.
BadMatch This error may occur if an XGetDeviceModifierMapping or XChangeDeviceModifierMapping request was made specifying a device that
has no keys.
BadValue Some numeric value falls outside the range of values accepted by the request. Unless a specific range is specified for an
argument, the full range defined by the argument's type is accepted. Any argument defined as a set of alternatives can gener-
ate this error.
SEE ALSO XSetDeviceKeyMapping(3X11)XSetDeviceButtonMapping(3X11)
Programming With Xlib
XFree86 Version 4.7.0 XGetDeviceModifierMapping(3X11)