Two things - the linux installers use either a cd image to install from or they 
use the network. By setting install-repository as you have implies a network 
install, and so for this to work your vm will need a vif (virtual network 
interface).

Secondly, installing from the linux templates is a bit like installing real 
Linux machines - you need to go through the install process, selecting what 
software to install, how to partition your disks etc. it sounds like what 
you've done is to effectively start the install procedure, then pull the plug. 
When you next try to start it, it's complaining quite rightly that you haven't 
got a kernel to boot from.

The best thing to do is to use a GUI (openxenmanager) to connect to the console 
after you've started the installation.

Jon

On 23 Dec 2011, at 11:02, "Medhavini Buchade" 
<[email protected]<mailto:[email protected]>> wrote:

Hello everyone,

I encountered some problems while working on XCP. Please suggest if I am doing 
something wrong. I also need to clarify certain concepts as I am using XCP for 
the first time.
<328.png>
1)
I was trying to install Debian Lenny 5.0 (32-bit). I did the following steps:
xe vm-install template=...
xe vm-param-set uuid=... 
other-config:install-repository=http://ftp.debian.org/debian
xe vm-start uuid=...

VM was created and it was in the running state. Then I did xe vm-shutdown after 
which the VM entered the halted state.
I then did the following steps:
xe vm-start uuid=...
Error: Unable to find partition containing kernel
To remove the above error, I did the following step
xe vm-param-set uuid=... PV-bootloader=eliloader

xe vm-start uuid=...
Error code:INVALID_SOURCE
Error parameters:Unable to access a required file in the specified repository:
http://ftp.debian.org/debian/isolinux/vmlinuz

2)
In which state should the VMs be when we need to shutdown the server that runs 
XCP?

3)
In which state should the VM be when it is not in use(Just like we shut down 
our PCs when they are not in use and the data on the PC remains intact.)?

Thank you.
_______________________________________________
xen-api mailing list
[email protected]<mailto:[email protected]>
http://lists.xensource.com/mailman/listinfo/xen-api
_______________________________________________
xen-api mailing list
[email protected]
http://lists.xensource.com/mailman/listinfo/xen-api

Reply via email to