Installation guide

# mknod /dev/xvdd b $major 32
# mknod /dev/xvdd1 b $major 33
Now you should verify the partitions which you have created are available.
[root@rhel3]# cat /proc/partitions
major minor #blocks name
3 0 10485760 hda
3 1 104391 hda1
3 2 10377990 hda2
202 16 64000 xvdb
202 17 32000 xvdb1
202 18 32000 xvdb2
253 0 8257536 dm-0
253 1 2031616 dm-1
In the above output, you can observe that the partitioned device “ xvdb” is available to the system.
The procedure below adds the new device to the guest and makes it persistent after rebooting. All
these commands are executed on the guest.
1. Create directories to mount the block device image in.
[root@rhel3]# mkdir /mnt/pvdisk_p1
[root@rhel3]# mkdir /mnt/pvdisk_p2
2. Mount the devices to the new folders.
[root@rhel3]# mount /dev/xvdb1 /mnt/pvdisk_p1
[root@rhel3]# mount /dev/xvdb2 /mnt/pvdisk_p2
3. Verify the devices are mounted correctly.
[root@rhel3]# df /mnt/pvdisk_p1
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/xvdb1 32000 15 31985 1% /mnt/pvdisk_p1
4. Update the /etc/fstab file inside the guest to mount the devices during the boot sequence.
Add the following lines:
/dev/xvdb1 /mnt/pvdisk_p1 ext3 defaults 1 2
/dev/xvdb2 /mnt/pvdisk_p2 ext3 defaults 1 2
Note
Using a Red Hat Enterprise Linux 5.1 host (dom0), the "noapic" parameter should be added
to the kernel boot line in your virtual guest's /boot/grub/grub.conf entry as seen below.
Keep in mind your architecture and kernel version may be different.
kernel /vmlinuz-2.6.9-67.EL ro root=/dev/VolGroup00/rhel4_x86_64 rhgb
noapic
A Red Hat Enterprise Linux 5.2 dom0 will not need this kernel parameter for the guest.
⁠Chapt er 1 2 . Xen Para- virt ualiz ed Drivers
155