Chapter 9. Configuring RHEL 5.2 for cloning 145
If you forgot to grant access to the VSWITCH you will see an error message. Verify that you
have OSA devices at addresses 600-602:
==> q osa
00: OSA 0600 ON NIC 0600 UNIT 000 SUBCHANNEL = 0002
00: 0600 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE
...
Verify that you have two read/write devices at addresses 100-101 using the QUERY DASD
command:
==> q da
00: DASD 0100 3390 LXAE23 R/W 3338 CYL ON DASD AE23 SUBCHANNEL = 0000
00: DASD 0101 3390 LXAE24 R/W 3338 CYL ON DASD AE24 SUBCHANNEL = 0001
00: DASD 0190 3390 LX8RES R/O 107 CYL ON DASD CF31 SUBCHANNEL = 0009
00: DASD 0191 3390 LX8027 R/O 300 CYL ON DASD 8027 SUBCHANNEL = 000C
...
Logoff from LINUX02.
At this point you have cloned one Linux virtual server and defined three more user IDs that
should now be ready for cloning or kickstarting to. You will clone to these user IDs in the
chapters that follow.
9.5 Reviewing system status
Now you can view your system from a DASD point of view, as shown in Figure 9-2 on
page 146. If you have implemented the instructions in all sections in this book, you should
have used 24 3390-3 volumes: 10 for your z/VM system; 7 for the Linux controller and golden
image; and one for each of the seven virtual servers.
You can also view the system from an administrator’s perspective and from a user’s
perspective, as shown by the horizontal lines and the italicized text on the right side of
Figure 9-2 on page 146. The z/VM and Linux system administration roles may be performed
by the same person, but these roles can also be done by different administrators. The Linux
users may not care or be aware that their servers are virtual machines which might have been
cloned in a matter of minutes.
Komentarze do niniejszej Instrukcji