Differences between version 30 and previous revision of XenNotes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 30 | Last edited on Thursday, February 10, 2011 6:57:46 am | by WikiWorld | Revert |
| Older page: | version 29 | Last edited on Thursday, February 10, 2011 6:54:07 am | by WikiWorld | Revert |
@@ -2,8 +2,9 @@
Xen by default just uses the dom0's clock, which isn't updated within the domU's. Either set <tt>/proc/xen/independent_wallclock</tt> to 1 (so that this domU has an indepedent clock from the host dom0, or set the clock in the dom0.
!!!Making a tape drive available to a guest via iSCSI Xenserver5.6
+<verbatim>
Making a tape drive available to a guest via iSCSI
This is specifically for Citrix XenServer, although the principles will of course work in other Xen implementations
I recently had a scenario where I was replacing two Windows servers with XenServer guests. This was fine, but we needed a way to backup to the existing SCSI DDS4 DAT drive. After failing to make PCI passthrough work, I settled on the much nicer method of providing the tape drive via an iSCSI target on the XenServer Host (Dom0). Here is how I achieved this.
@@ -35,22 +36,8 @@
'tar -zxf scstadmin-1.0.6.tar.gz'
'tar -zxf iscsi-scst-1.0.1.1.tar.gz'
•Edit the scst-1.0.1.1/src/Makefile and uncomment the line EXTRA_CFLAGS += -DCONFIG_SCST_STRICT_SERIALIZING
-
-Here's where it gets a little ugly, and I'd welcome suggestions (just edit this wiki) for how to do this the "right" way. This is necessary because the make install part of the build depends on having the kernel-dev skeleton installed, and this can't be installed on a XenServer Host (to my knowledge).
-
-•tar up the devel tree - example (the dir will change depending on the XenServer/kernel version):
-cd /usr/src/kernels/2.6.18-128.1.6.el5.xs5.5.0.505.1024xen-i686
-tar -czvpf /opt/build/build.tar.gz .
-cd /opt/buildOK, you're now ready to install on your target XenServer? host
-
-Here's where it gets a little ugly, and I'd welcome suggestions (just edit this wiki) for how to do this the "right" way. This is necessary because the make install part of the build depends on having the kernel-dev skeleton installed, and this can't be installed on a XenServer Host (to my knowledge).
-
-•tar up the devel tree - example (the dir will change depending on the XenServer/kernel version):
-cd /usr/src/kernels/2.6.18-128.1.6.el5.xs5.5.0.505.1024xen-i686
-tar -czvpf /opt/build/build.tar.gz .
-cd /opt/buildOK, you're now ready to install on your target XenServer? host
Here's where it gets a little ugly, and I'd welcome suggestions (just edit this wiki) for how to do this the "right" way. This is necessary because the make install part of the build depends on having the kernel-dev skeleton installed, and this can't be installed on a XenServer Host (to my knowledge).
•tar up the devel tree - example (the dir will change depending on the XenServer/kernel version):
@@ -109,17 +96,9 @@
•Finally, set the relevant daemons to start on boot with chkconfig scst on && chkconfig iscsi-scst on (and start them with service scst start && service iscsi-scst start)
You should now be able to discover and connect to the target.
Tested using MS iSCSI initiator on Windows Server 2008 against the above config on XenServer 5.6.
-
-
-
-
-
-
-
-
-
+</verbatim>
!!!Making a tape drive available to a guest via iSCSI
__This is specifically for Citrix ~XenServer, although the principles will of course work in other Xen implementations__
