• View Communities
    • Citrix Developer Network
      The place for unfiltered straight talk on Citrix products. Blogs, code downloads, best practices, APIs, and more can all be found here.
    • Citrix Ready Community Verified
      Does it work with Citrix? Application compatibility questions are a thing of the past with the new Citrix Community Verified site.
    • Blogs
      Learn the latest from the Citrix employees who are building application delivery infrastructure technologies.
    • Blogosphere
      The Citrix Blogosphere is a window into the thousands of conversations taking place about Citrix and Application Delivery.
  •  Sign In
The Citrix Blog
Blogs for tag 'merchandising server'

Permalink | Twitter Post to Twitter | Comments (5) | Views (1890) |

posted by Brian Ehlert

Courtesy of the Citrix Project Kensho work over the past 18 months we have spent a good deal of time looking at the interoperability of virtual machines between hypervisors.

If you didn't already know: Kensho uses the still evoloving OVF Standard from the DMTF and has given rise to the Citrix OVF Tool; that can export multi-vm workloads from XenServer and/or Hyper-V, as well as import OVF content from VMware into XenServer or Hyper-V. Kensho has also added the OVF capabilities into XenConvert.

Before we outline the steps below, Hyper-V was chosen for this first example because the publically available tools are Hyper-V specific, and because Citrix is using VHD as its OVF package standard. There will be more later about taking this same VM to ESX.

The Tools:
We need to obtain (download) a few things and a couple need to be installed.

Explanation of the Tools:
The Merchandising Server is the appliance used for the example. XenConvert is to convert the XVA (XenServer export format) into an OVF based appliance. The Kensho OVF Tool is to import the OVF into Hyper-V. The Linux distribution "Live CD" is to mount the virtual disk of the appliance to modify the Grub boot loader and copy some files. And the v1 Linux Integration Components have the magic PV kernel shim that is needed.

The process:

  1. Expand the Merchandising Server bz2 zip archive. (WinRAR can do this, and others as well)
  2. Use Citrix XenConvert 2.x to convert from "Xen Virtual Appliance" to "Open Virtualization Format (OVF) Package"
    • Do not create an OVA, just an OVF.
  3. Use Citrix Kensho OVF Tool to Import the OVF Package from step 2 to a Hyper-V host.
    • Do not boot the VM at this time.
  4. Attach the Live CD ISO to the VM
  5. Set the boot order to boot from DVD first
  6. Remove the default Network Adapter and add a Legacy Network Adapter
  7. Add a second DVD drive
  8. attach the Hyper-V (v1) Linux IC ISO to the second DVD drive of the VM
  9. Boot the VM into the Live CD and log in to its console
    • Debian will auto logon as 'user'.
  10. switch to root: sudo -i
    • This command is specific to Debian Live
  11. Discover the IDE disks:
    1. cd /dev
    2. ls hd*
  12. Mount the virtual disk (the vhd)
    1. make a mount point folder: mkdir /mnt/mine
    2. mount the disk to the folder: mount /dev/hda1 /mnt/mine
  13. explore the volume
    1. cd /mnt/mine
    2. ls
  14. /mine looks like a common Linux /boot volume:
  15. Mount the Linux IC DVD drive (mine is the second dvd on controller 2):
    1. mkdir /mnt/cdrom
    2. mount /dev/hdd /mnt/cdrom
  16. Copy the kernel shims from the ISO to the virtual disk
    1. cd /mnt/cdrom/shim
    2. cp . /mnt/mine
  17. Edit the device.map
    1. cd /mnt/mine/grub
    2. nano device.map

  18. Edit the GRUB bootloader to load the shim and the kernel.
    1. nano menu.lst
  19. Comment the 'hiddenmenu' option and increase the timeout so I can test.
  20. Create a new entry specific to the shim and the distribution kernel-xen
    • Notice that the kernel is the shim file copied from the previous step and the existing kernel and initrd load as modules of the shim.
  21. Modify the default selection to point to my new entry.
    • The default entry begins counting at "0"
  22. Unmount the virtual disk and the cdrom
    1. cd /
    2. umount /dev/hda1
    3. umount /dev/hdd
  23. Shutdown the virtual machine and remove the ISOs from the DVD drive (also remove the second virtual dvd drive).
  24. Boot the virtual machine, note the new menu selection that was created - this is the kernel that should boot. Select it if you did not set it as the default.
Expand Blog Post