On 06/08/2010 05:13, Ken Woolard wrote:
I'm slightly confused reading about setting up an IO Domain on a
T5240.
I know how to set it up grabbing one of the 2 buses via ldm add-io
and I can also install an OS on it using the the VDS on the primary
domain.
What confuses me is the next stage when I go to create a Guest
domain. Which commands are required when creating the Guest domain so
that it can access the storage via the IO Domain.
It's the relationship between the IO domain and the Guest domain that
I want to understand
Hi Ken
A second I/O domain is usually created to provide guests an independent
route to I/O from the primary domain.
It also usually means that the second I/O domain itself is independent
from the primary domain, otherwise a failure of the primary would also
cause a failure in the second I/O domain.
What you have described above is perfectly valid, but does not provide
redundancy in case the primary domain fails, as the boot disk for the
second I/O domain is provided by the primary domain ( via the primary's
VDS service).
What we would normally expect is the second I/O to have its own boot
disks that are on the PCI bus that you are assigning to the second I/O
domain. In this case the disks will be external to the T5240.
If, however, you are happy with the above arrangement of the primary
supplying the disk to the second I/O domain you would need to create
services in the second i/O domain in order for the guests to use those.
You mention storage, so in that case you would create ( from the primary
domain ) a vds service in the second I/O domain
primary domain # ldm add-vds <new-service-name> <second I/O domain name>
If you also have network also add a network service.
Then you can add devices to the vds service and export those to the guests.
Note that all of these commands are run from the primary domain as that
is where the SUNWldm package is installed.
T
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
