Академический Документы
Профессиональный Документы
Культура Документы
Introduction
Hypervisor :
The SPARC hypervisor is a small firmware layer that provides a stable virtualized machine architecture to which an operating system can be written. Sun servers that use the hypervisor provide hardware features to support the hypervisor's control over a logical operating system's activities. Each logical domain is only permitted to observe and interact with those server resources that are made available to it by the hypervisor. The Logical Domains Manager enables you to specify what the hypervisor should do through the control domain.
Logical Domain :
A logical domain is a virtual machine comprised of a discrete logical grouping of resources. A logical domain has its own operating system and identity within a single computer system. Each logical domain can be created, destroyed, reconfigured, and rebooted independently, without requiring you to power cycle the server. You can run a variety of applications software in different logical domains and keep them independent for performance and security purposes.
The figure on previous slide shows the hypervisor supporting two logical domains. It also shows the following layers that make up the Logical Domains functionality: Applications, or user/services Kernel, or operating systems Firmware, or hypervisor Hardware, including CPU, memory, and I/O
The hypervisor software is responsible for maintaining the separation between logical domains. The hypervisor software also provides logical domain channels (LDCs) that enable logical domains to communicate with each other. LDCs enable domains to provide services to each other, such as networking or disk services. The service processor (SP), also known as the system controller (SC), monitors and runs the physical machine, but it does not manage the logical domains. The Logical Domains Manager manages the logical domains.
allocate virtual resources to other domains. You can have only one control domain per server. The control domain is the first domain created when you install the Logical Domains software. The control domain is named primary and also known as I/O domain or service domain.
Guest domain A guest domain is a non-I/O domain that consumes virtual device services that are provided by one or more service domains. A guest domain does not have any physical I/O devices, but only has virtual I/O devices, such as virtual disks and virtual network interfaces.
Dynamic Reconfiguration :
Dynamic reconfiguration (DR) is the ability to add or remove resources while the operating system is running. The ability to perform dynamic reconfiguration of a particular resource type is dependent on having support in the OS running in the logical domain. Dynamic reconfiguration is supported for the following resources: Virtual CPUs Supported in all versions of the Solaris 10 OS Virtual I/O devices Supported in at least the Solaris 10 10/08 OS
Memory Not supported Physical I/O devices Not supported To use the dynamic reconfiguration capability, the Logical Domains dynamic reconfiguration daemon (drd), must be running in the domain that you want to change.
10
Delayed Reconfiguration :
In contrast to dynamic reconfiguration operations that take place immediately, delayed reconfiguration operations take effect in the following circumstances: After the next reboot of the OS After a stop and start of the logical domain When a delayed reconfiguration is in progress on the control domain, other reconfiguration requests for the control domain are deferred until it is rebooted, or stopped and started. Also, when a delayed reconfiguration is outstanding for the control domain, reconfiguration requests for other logical domains are severely restricted and will fail with an appropriate error message.
11
Persistent Configurations :
You can use the ldm config command to store the current configuration of a logical domain on the service processor. You can add a configuration, specify a configuration to be used, remove a configuration, and list the configurations.
12
13
14
15
1. Create a virtual disk server (vds) to allow importing virtual disks into a logical domain. For example, the following command adds a virtual disk server (primary-vds0) to the control domain (primary). 2. Create a virtual console concentrator (vcc) service for use by the virtual network terminal server daemon (vntsd) and as a concentrator for all logical domain consoles. For example, the following command would add a virtual console concentrator service (primary-vcc0) with a port range from 5000 to 5100 to the control domain (primary).
16
3. Create a virtual switch service (vsw) to enable networking between virtual network (vnet) devices in logical domains. For example, the following command would add a virtual switch service (primary-vsw0) on network adapter driver e1000g0 to the control domain (primary). This command automatically allocates a MAC address to the virtual switch.You can specify your own MAC address as an option to the ldm add-vsw command.
17
4. Verify the services have been created by using the list-services subcommand. Your output should look some how similar to the following.
18
19
2. Assign virtual CPUs to the control domain. For example, the following command would assign 4 virtual CPUs to the control domain, primary. This leaves the remainder of the virtual CPUs available to a guest domain.
3. Assign memory to the control domain. For example, the following command would assign 4 gigabytes of memory to the control domain, primary. This leaves the remainder of the memory available to a guest domain.
20
4. Add a logical domain machine configuration to the service processor (SP). For example, the following command would add a configuration called initial.
21
Note: Before rebooting the server, rename the /etc/hostname.interface_name file to /etc/hostname.vsw0 (the name of the virtual switch).
22
23
24
2. Add CPUs to the guest domain. For example, the following command would add four virtual CPUs to guest domain ldg1. 3. Add memory to the guest domain. For example, the following command would add 2 gigabytes of memory to guest domain ldg1. 4. Add a virtual network device to the guest domain. For example, the following command would add a virtual network device with these specifics to the guest domain ldg1.
25
5. Specify the device to be exported by the virtual disk server as a virtual disk to the guest domain. You can export a physical disk, disk slice, volumes, or file as a block device. The following examples show a physical disk and a file. Physical Disk Example: The first example adds a physical disk with these specifics. File Example. This second example is exporting a file as a block device.
26
6. Add a virtual disk to the guest domain. The following example adds a virtual disk to the guest domain ldg1. 7. Set auto-boot and boot-device variables for the guest domain. The first example command sets auto-boot\? to true for guest domain ldg1. The second example command sets boot-device to vdisk for the guest domain ldg1.
27
8. Bind resources to the guest domain ldg1 and then list the domain to verify that it is bound.
10. Taking the console of guest domain from the control domain.
28
3. Stop and unbind the guest domain (ldg1).Then add the DVD with DVDROM media as a secondary volume (dvd_vol@primary-vds0) and virtual disk (vdisk_cd_media), for example c0t0d0s2 is where the Solaris OS media resides
29
4. Check to see that the DVD is added as a secondary volume and virtual disk.
30
31
6. Show the device aliases in the client OpenBoot PROM. In this example, see the device aliases for vdisk_cd_media, which is the SolarisDVD, and vdisk1, which is a virtual disk on which you can install the Solaris OS.
32
33
Thank You
Ankit Padegaonkar
Wipro System Integration (SI)Team ankit.padegaonkar@wipro.com