Issue


The VS built from some older templates, before Xen 4 support was added, fail to boot under Xen 4 in some cases.

Resolution


We can update these virtual servers to allow them to boot under Xen 4. The steps below have been completed on a clean installation, so there may be specific considerations needed depending on the running software. As a precaution, we suggest taking a backup before completing these steps on the production virtual servers.

This is likely to be due to an issue with grub and can be resolved by removing the grub.cfg file:

  1. SSH into the virtual server.
  2. Run rm /boot/grub/grub.cfg
  3. Stop the virtual server.
  4. Migrate to XEN4 compute resource.
  5. Start the virtual server.

OR

  1. Stop the virtual server.
  2. Migrate to a Xen 4 compute resource.
  3. Start the virtual server in recovery mode.
  4. SSH into the virtual server.
  5. Mount /dev/sdb1 /mnt
  6. Run rm -rf /mnt/boot/grub/grub.cfg
  7. Reboot the virtual server.


If it doesn't work, upgrade from Debian6 to Debian7:

  1. Run:

    # root@OnApp:~# uname -a
    CODE

    Linux OnApp 2.6.32-24-server #43-Ubuntu SMP Thu Sep 16 16:05:42 UTC 2010 x86_64 GNU/Linux

  2. Run:

    # cat /etc/issue
    CODE

    Debian GNU/Linux 6.0 \n \l

  3. Run:

    # sed -i 's/squeeze/wheezy/g' /etc/apt/sources.list
    CODE
  4. Run:

    # apt-get update
    CODE
  5. Run:

    # apt-get upgrade
    CODE
  6. Run:

    # apt-get dist-upgrade
    CODE
  7. Run:

    # cp /boot/grub/menu.lst /boot/grub/menu.lst.old
    CODE
  8. Edit /boot/grub/menu.lst by removing the previous entries.
  9. Run:

    # halt
    CODE
  10. Migrate the virtual server to XEN4 compute resource and start it.
  11. Run:

    # root@OnApp:~# uname -a
    CODE

    Linux OnApp 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux

  12. Run:

    # cat /etc/issue
    CODE

    Debian GNU/Linux 7 \n \l