ganeti falha ao instalar instâncias do debootstrap no squeeze

Question

A configuração do

ganeti 2.4-rc3 no meu servidor squeeze correu bem e consegui criar instâncias com sucesso:

$ gnt-instance add -t plain -s 5G -o debootstrap+default -n obi-wan vm01
Wed Mar  2 17:12:51 2011 * disk 0, vg xenvg, name fdc7fa9e-19ac-405c-adad-f72da34d6682.disk0
Wed Mar  2 17:12:51 2011 * creating instance disks...
Wed Mar  2 17:12:51 2011 adding instance vm01.physcip.uni-stuttgart.de to cluster config
Wed Mar  2 17:12:51 2011  - INFO: Waiting for instance vm01.physcip.uni-stuttgart.de to sync disks.
Wed Mar  2 17:12:51 2011  - INFO: Instance vm01.physcip.uni-stuttgart.de's disks are in sync.
Wed Mar  2 17:12:51 2011 * running the instance OS create scripts...
Wed Mar  2 17:13:03 2011 * starting instance... 
$

Diz-me que a instância está a funcionar bem:

$ gnt-instance list
Instance                      Hypervisor OS                  Primary_node                     Status  Memory
vm01.physcip.uni-stuttgart.de xen-pvm    debootstrap+default obi-wan.physcip.uni-stuttgart.de running   128M

No entanto, o debootstrap não pode instalar um sistema operacional porque não consegue montar um dispositivo raiz. Este é um instantâneo do console da vm:

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... [    0.491828] device-mapper: uevent: version 1.0.3
[    0.492487] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: [email protected]
done.
Begin: Waiting for root file system ... done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/sda1 does not exist.  Dropping to a shell!

O que está instalado:

• debian squeeze com xen 4 e lvm2
• kernel 2.6.32-5-xen-amd64
• ganeti 2.4 rc3

informação do cluster ganeti: Cluster com um único nó (chamado obi-wan)

gnt-cluster info
Cluster name: vmcluster.physcip.uni-stuttgart.de
Cluster UUID: 2ae3377c-8682-486d-9ac2-cdac43a136f7
Creation time: 2011-03-01 12:05:10
Modification time: 2011-03-02 14:12:48
Master node: obi-wan.physcip.uni-stuttgart.de
Architecture (this node): 64bit (x86_64)
Tags: (none)
Default hypervisor: xen-pvm
Enabled hypervisors: xen-pvm
Hypervisor parameters:
  - xen-pvm:
      blockdev_prefix: sd
      bootloader_args: 
      bootloader_path: 
      initrd_path: /boot/initrd-2.6-xenU
      kernel_args: ro
      kernel_path: /boot/vmlinuz-2.6-xenU
      migration_mode: live
      migration_port: 8002
      root_path: /dev/sda1
      use_bootloader: False
OS-specific hypervisor parameters:
OS parameters:
Hidden OSes: 
Blacklisted OSes: 
Cluster parameters:
  - candidate pool size: 10
  - master netdev: xen-br0
  - lvm volume group: xenvg
  - lvm reserved volumes: (none)
  - drbd usermode helper: /bin/true
  - file storage path: /srv/ganeti/file-storage
  - maintenance of node health: False
  - uid pool: 
  - default instance allocator: 
  - primary ip version: 4
  - preallocation wipe disks: False
Default node parameters:
    oob_program: None
Default instance parameters:
  - default:
      auto_balance: True
      memory: 128
      vcpus: 1
Default nic parameters:
  - default:
      link: xen-br0
      mode: bridged

    

Answer 1

O root_path padrão definido para xen-pvm está errado. Eu mudei id via

gnt-cluster modify --hypervisor-parameter xen-pvm:root_path='/dev/xvda1'

e o debootstrap instalado aperta muito bem!

    

Answer 2

Este é o código de criação da minha instância:

-H xen-pvm:kernel_path=/boot/vmlinuz-2.6-xenU,initrd_path=/boot/initrd-2.6-xenU,blockdev_prefix=xvd,root_path=/dev/xvda1