Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
export MGUID=`xe vm-install template=centos6 new-name-label="centos 6 test install 3"`
xe vm-disk-add disk-size=11GiB vm=$MGUID sr-uuid=$STORAGE_UID device=0
xe vm-param-set uuid="$MGUID" PV-args="ks= ksdevice=eth0"
xe vm-param-set uuid="$MGUID" other-config:install-repository=""
xe vm-start uuid=$MGUID

when i do this i get a error that there is no bootloader. if i add a disk to the template and omit the 2nd command everything works fine.

so the question: how can i boot into installation after adding disk(s)

share|improve this question

I'm trying to follow along here:

When I run the vm-disk-add line, i get

"A device with the name given already exists on the selected VM device: 0 "

Meaning that I already have a disk at position 0. This is true; my template includes a disk in slot 0 when it's made.

I guess my question is, why do you want to do it this way. What if you put a disk on the template with a small size, and then expand it to the size you want before doing the vm-start. Would this have the same desired effect?

Does this page help you at all?:

share|improve this answer
well it would somehow have the same effect. none the less i would like to figure out why this happens and how i can get into "installation from kickstart mode" – yawniek Oct 24 '11 at 17:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.