ERROR: "Error: Kernel image does not exist: /tmp/kernel.SUMgkq"
NOTE: In this example our guest is named SLES10. For this TID, replace SLES10 with the name of the virtual machine ("xm list" will show the names of all the virtual machines installed).
- Navigate to a temporary directory.
- Extract the python file:xm list -l SLES10> sles10.py
- Create a backup copy of the sles10.py; it may be needed later on.
- Open sles10.py for editing.
- Locate the bootloader_args parameter. It will most likely look like this:( bootloader_args )
- Replace it with( bootloader_args'--entry=xvda1:/boot/vmlinuz-xen,/boot/initrd-xen')
- Locate the bootloader parameter. It will most likely look like this:( bootloader )
- Replace it with( bootloader /usr/lib/xen/boot/domUloader.py )
- Reload the new configuration file by typingxm new -F sles10.py
- Start the Xen guestxm start SLES10
- Go to /etc/xen/vm
- Locate the file with the guest's name (not the .xml file)
- Open the file for editing
- Change bootloader="" tobootloader="/usr/lib/xen/boot/domUloader.py"
- Change bootloaderargs="" tobootargs="--entry=xvda1:/boot/vmlinuz-xen,/boot/initrd-xen"
- Save the file
- Import the new filexm new -f sles10
- Start the Xen Guestxm start sles10
- This is a trial and error process. Because the configuration files were not made correctly, some errors may be seen. Review the configuration file and repeat steps 4 through 10 (method 1) or steps 4-8 (method 2) as needed. The most common item that will need review is the location of the kernel image. In ths example we used the first virtual disk (xvda) on the first partition (xvda1)
- If after typing "xm start...", the command hangs, pass it "control-C". Restart Xend ("rcxend restart"). Note that restarting Xend will not affect running Xen guests.
- If the Xen guest is in any sort of clustering or if the physical host is in a cluster, shutdown the cluster or turn off clustering for the node at hand. If not, strange things can happen with clustering as a result.
- ERROR: "Error: Boot loader didn't return any data!": This means that the bootloader was pointing at the wrong virtual disk and/or partition. Change the xvda1 to xvda2, etc, or to the virtual device where /boot was installed. "xvda" refers to the first disk, either physical or file that is presented to the guest as the first disk.
- ERROR: "Error: Kernel image does not exist....": Step 7 or 8 was done incorrectly. Review and test.
This error has been observed when the "virt-manager.py" program (this is the same program that is run by YaST's "Virtual Machine Manager" has been closed before the installation is complete. This only applies to paravirtualized guests.
Other Linux vendors recommend method 2, however in the Novell Documentation, the use of method 1 is preferred. When using method 2, be careful NOT to use xm create in step 7. Also, note that the Python file is imported using xm new -F while the simple text is imported using xm new -f