I have some unclear about how VIOS uses its resources.
Assume that VIOS lpar has only 1 physical FC, and we use that to connect to the Lun. Then we install VIOS for the lpar on that Lun.
So my question is, afterward, we can still use that physical FC for the virtual FC we create later?
This can be same mechanism with virtual ethernet?
I have 1 physical ethernet assigned to vios, and configure IP on that, everything is fine until I tried to map another virtual ethernet to it and got the issue below:
Code:
$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 2
Adapter ent0 has an interface configured over it, or it belongs to another SEA, VLAN or EtherChannel
Command did not complete.
All of these mean that we have to use another physical device (FC, ethernet) for virtual devices??
Hey
May be a dumb question
Can I use a SPOT which is at 5.3 TL6 to boot an LPAR (with 5.3 TL8) in to maintenance mode? Will it work ?
Is it mandatory that SPOT should be of same or higher version in such case?
Bala (1 Reply)
I am trying to script and came up with a conclusion that I need a do while loop in my statement. I am stuck with the
do while syntax. I need to use it alongwith the if then else statement. Can I use it is a big question? I actually need to get all the files
that are there from within run_dt to... (1 Reply)
1.Write an automated shell program(s) that can create, monitor the log files and report the issues for matching pattern.
(i) Conditions for creating log files.
Log file is created with date (example 2010_03_27.log). If the log file size is 10 Mb for a particular day then automatically the log... (3 Replies)
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Hi All,
I have a p520 box running 3 LPARs, 1 x VIOS, 1 x AIX 6.1 and 1 x AIX 7.1 and no HMC, all configuration is performed via VIOS/IVM
Until recently the box did not have the AIX7.1 LPAR and everything was fine with the box.
We needed to use AIX 7.1 for a new project, so I created a... (11 Replies)
Hi All,
I have a source file with data
Name ~ Groups
Muni~abc,was,USA_ax,123
Chaitanya~USA_12,was
Balaji~123,xyz,was
Ramu~123,xyz
From the second column i want to extract only the groups that matches the pattern 'USA_%' or if the group = 'was', and ignore any other columns.
... (8 Replies)
Please help in creating script for below requirement.
I will be running 1 command and will get below entries in a text file say file44.txt
*******************************
DFDL1005 06:30 00:05
ABFL2003 10/22 01:10
CFTL1256 10/24 00:10
10/25 09:20 PM
********************************
.... (3 Replies)
Discussion started by: Vinay_3308
3 Replies
LEARN ABOUT OSF1
svatophys
svatophys(9r)svatophys(9r)NAME
svatophys - General: Converts a system virtual address to a physical address
SYNOPSIS
kern_return_t svatophys(
vm_offset_t kern_addr,
vm_offset_t *phys_addr );
ARGUMENTS
Specifies the kernel virtual address. Specifies a pointer to the physical address to be filled in.
DESCRIPTION
The svatophys routine converts a system virtual address to the corresponding physical address. All address and data structure manipulation
done within the kernel is performed using system virtual addresses. Typically, system virtual addresses are a means of mapping physical
memory and I/O space, which often consists of device registers and DMA buffers. In contrast to this, devices are usually unaware of any
virtual addressing and for this reason use physical addresses. You use the svatophys routine to perform this address translation.
As an example of where you can use this address translation, a disk device driver can use DMA buffers to transfer blocks of data to the
disk (for the case of a write operation). The data to be written to disk is present in system memory at a system virtual address known to
the driver. To initiate the DMA operation, the disk driver can set up a command packet to specify a write operation to the underlying disk
controller hardware. This write command packet contains (among other things) the location of the DMA buffer as a physical address and the
length of the buffer. Here, the driver calls the svatophys routine to translate the system virtual address of the DMA buffer to a physical
address in the command packet issued to the disk driver.
RETURN VALUES
The svatophys routine returns the following: The address translation has been completed successfully. Unable to perform address transla-
tion. This value indicates that the address specified by the kern_addr argument is not a valid kernel or system virtual address.
svatophys(9r)
01-16-2020
