Specifications

alias oramp2
}
multipath {
wwid 3600a0b80001327510000015427b625e
alias oramp3
}
multipath {
wwid 3600a0b80001327510000015427b625e
alias oramp4
}
This defines 4 luns: /dev/mpath/oramp1, /dev/mpath/oramp2, /dev/mpath/oramp3, and
dev/mpath/oramp4. The devices will reside in the /dev/mpath directory. These lun names are
persistent over reboots as it creates the alias names on the wwid of the luns.
10. SELinux Considerations
This sections contains things to you must consider when you implement SELinux into your Red
Hat Virtualization environment. When you deploy system changes or add devices, you must
update your SELinux policy accordingly. To configure an LVM volume for a guest, you must
modify the SELinux context for the respective underlying block device and volume group.
# semanage fcontext -a -t xen_image _t -f -b /dev/sda2
# restorecon /dev/sda2
The boolean parameter xend_disable_trans put xend in unconfined mode after restarting the
daemon. It is better to disable protection for a single daemon than the whole system. It is
advisable that you should not re-label directories as xen_image_t that you will use elsewhere.
11. Accessing Data on Guest Disk Image
You can use two separate applications that assist you in accessing data from within a guest
disk image. Before using these tools, you must shut down the guests. Accessing the file system
from the guest and dom0 could potentially harm your system.
You can use the kpartx application to handle partitioned disks or LVM volume groups:
yum install kpartx
kpartx -av /dev/xen/guest1
add map guest1p1 : 0 208782 linear /dev/xen/guest1 63
add map guest1p2: 0 16563015 linear /dev/xen/guest1 208845
To access LVM volumes on a second partiton, you must rescan LVM with vgscan and activate
the volume group on the partition (called VolGroup00 by default) by using the vgchange -ay
command:
Chapter 18. Red Hat Virtualization Troubleshooting
88