[Xen-ia64-devel] ramdisk generated by xm-test

[Matsumoto <n_matumoto@xxxxxxxxxxxxxxxx>]

Hi,

I started DomU in "tools/xm-test/ramdisk/initrd.img" which 
xm-test generated. However,The message of "Kernel panic - not 
syncing: No init found.  Try passing init= option to kernel." 
was output, and it was not possible to start.

When I confirm the contents of initrd.img, It seems to be the 
state that cannot start so that busybox is made in 32bit.
DomU was able to start in initrd-0.6.img which xm-test generated 
in the following procedures.

1.Config edit of busybox
  # cd tools/xm-test/ramdisk/buildroot/build_i386/busybox-1.01

  "make menuconfig","make"
  # make menuconfig
     Build Options  --->  
       [*] Build BusyBox as a static binary (no shared libs)

2.Edit of ramdisk that xm-test generated
  It is copied onto tools/xm-test/ramdisk/initrd-0.6.img. 

3.Edit of domain configuration file

  # Xen configuration generated by xm-test
  ramdisk = "tools/xm-test/ramdisk/initrd-0.6.img"
  kernel = "/boot/vmlinuz-2.6.12.6-xenU"
  name = "01_create_basic_pos"
  vcpus = 1
  memory = 256
  root = "/dev/ram0"
  extra = "nomca nosmp xencons=tty0 console=tty0 3"

Attention:
The system hardens in memory=64. 
Extra is not generated in xm-test. 

Best Regards,

Matsumoto



_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel