Debootstrap-ing Dapper on Fiesty

Discussion in 'HOWTO-Related Questions' started by ashutosh, Sep 18, 2007.

  1. ashutosh

    ashutosh New Member

    Hi all,
    i am trying to debootstrap dapper distribution on fiesty, but everytime i issue debootstrap command, i get this error message:

    W: Failure trying to run: chroot /xen-image/mnt mount -t proc proc /proc

    i followed the following procedure...

    #>dd if=/dev/zero of=guest_base.img bs=1024k count=2000
    //this is to create a file of size approx 2GB that will hold my dapper base

    #> mkfs.ext3 guest_base.img
    //this is to format the above file with ext3 partition

    #>mount -o loop guest_base.img mnt
    //loopback mounted file

    #> debootstrap --arch i386 --verbose dapper /xen-image/mnt/ file:/media/cdrom/ubuntu/

    After the last command this is the output i get:
    *************************************************************
    I: Retrieving Release
    I: Retrieving Packages
    I: Validating Packages
    I: Resolving dependencies of required packages...
    I: Resolving dependencies of base packages...
    I: Checking component main on file:/media/cdrom/ubuntu...
    I: Retrieving libatm1
    I: Validating libatm1
    W: Failure trying to run: chroot /xen-image/mnt mount -t proc proc /proc
    *************************************************************

    A log file was also created by debootstrap in the target directory (here it is: /xen-images/mnt/debootstrap/debootstrap.log). Contents of this logfile are:

    *************************************************************
    ar: /xen-image/mnt/: File format not recognized

    zcat: stdin: unexpected end of file
    chroot: cannot run command `mount': No such file or directory
    *************************************************************

    I tried to google this msg and also searched several forums. In this forum also, this problem has been discussed, but i couldn't get the solution.
    I changed my fiesty debootstrap program to dapper debootstrap program but the error persists.
    Essentially i am clueless about why is it giving file format no recognized error...

    If anyone has any idea plzzz share it
     
  2. falko

    falko Super Moderator ISPConfig Developer

    It seems that this command is wrong:

    Code:
    chroot /xen-image/mnt mount -t proc proc /proc
    I think it should be something like
    Code:
    chroot /xen-image/mnt && mount -t proc proc /proc
     
  3. ashutosh

    ashutosh New Member

    to falko:

    The chroot comman you mentioned is not given by me but is executed by debootstrap program itself...I can't change this command according to what you have specified....
    Can you suggest some other alternative?
     
  4. falko

    falko Super Moderator ISPConfig Developer

    Do you get the same error when you try to debootstrap another version, e.g. Feisty or Edgy?
     
  5. ashutosh

    ashutosh New Member

    I tried debootstrapping edgy, it completed successfully, but i got stuck while creating guest domain using following command:

    xm create baseimage -c

    It generates following error message:
    Error 22: Invalid arguments

    The contents of log generated by xm log are:
    [2007-09-20 15:43:54 xend.XendDomainInfo 29373] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'xen1.example.com'], ['memory', '128'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', 1], ['image', ['linux', ['kernel', '/boot/xen-3.gz'], ['ramdisk', '/boot/initrd.img-2.6.18-xen'], ['root', '/dev/sda1 ro']]], ['device', ['vbd', ['uname', 'file:/home/xen/domains/xen1.example.com/disk.img'], ['dev', 'sda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'file:/home/xen/domains/xen1.example.com/swap.img'], ['dev', 'sda2'], ['mode', 'w']]], ['device', ['vif', ['ip', '192.168.12.150']]]])
    [2007-09-20 15:43:54 xend.XendDomainInfo 29373] DEBUG (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'xen1.example.com'], ['memory', '128'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', 1], ['image', ['linux', ['kernel', '/boot/xen-3.gz'], ['ramdisk', '/boot/initrd.img-2.6.18-xen'], ['root', '/dev/sda1 ro']]], ['device', ['vbd', ['uname', 'file:/home/xen/domains/xen1.example.com/disk.img'], ['dev', 'sda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'file:/home/xen/domains/xen1.example.com/swap.img'], ['dev', 'sda2'], ['mode', 'w']]], ['device', ['vif', ['ip', '192.168.12.150']]]]
    [2007-09-20 15:43:54 xend.XendDomainInfo 29373] DEBUG (XendDomainInfo:395) parseConfig: result is {'shadow_memory': None, 'uuid': None, 'on_crash': 'restart', 'on_reboot': 'restart', 'localtime': None, 'image': ['linux', ['kernel', '/boot/xen-3.gz'], ['ramdisk', '/boot/initrd.img-2.6.18-xen'], ['root', '/dev/sda1 ro']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'xen1.example.com', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 128, 'device': [('vbd', ['vbd', ['uname', 'file:/home/xen/domains/xen1.example.com/disk.img'], ['dev', 'sda1'], ['mode', 'w']]), ('vbd', ['vbd', ['uname', 'file:/home/xen/domains/xen1.example.com/swap.img'], ['dev', 'sda2'], ['mode', 'w']]), ('vif', ['vif', ['ip', '192.168.12.150']])], 'bootloader': None, 'cpu': None, 'maxmem': None}
    [2007-09-20 15:43:54 xend.XendDomainInfo 29373] DEBUG (XendDomainInfo:1262) XendDomainInfo.construct: None
    [2007-09-20 15:43:54 xend.XendDomainInfo 29373] ERROR (__init__:1021) Domain construction failed
    Traceback (most recent call last):
    File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 194, in create
    vm.construct()
    File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 1266, in construct
    handle = uuid.fromString(self.info['uuid']))
    Error: (22, 'Invalid argument')
    [2007-09-20 15:43:54 xend.XendDomainInfo 29373] DEBUG (XendDomainInfo:1458) XendDomainInfo.destroy: domid=None
    [2007-09-20 15:43:54 xend 29373] ERROR (__init__:1021) (22, 'Invalid argument')
    Traceback (most recent call last):
    File "/usr/lib/python2.5/site-packages/xen/util/xmlrpclib2.py", line 162, in _marshaled_dispatch
    response = self._dispatch(method, params)
    File "SimpleXMLRPCServer.py", line 415, in _dispatch
    return func(*params)
    File "/usr/lib/python2.5/site-packages/xen/xend/server/XMLRPCServer.py", line 64, in domain_create
    info = XendDomain.instance().domain_create(config)
    File "/usr/lib/python2.5/site-packages/xen/xend/XendDomain.py", line 228, in domain_create
    dominfo = XendDomainInfo.create(config)
    File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 194, in create
    vm.construct()
    File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 1266, in construct
    handle = uuid.fromString(self.info['uuid']))
    Error: (22, 'Invalid argument')

    ********************************************************
    Here are the contents of the configuratio file I used to create gues domain(edgy):

    # -*- mode: python; -*-
    kernel = "/boot/vmlinuz-2.6.18-xen"
    ramdisk = "/boot/initrd.img-2.6.18-xen"
    memory = 128
    name = "baseimage"
    #vif = ['bridge=xenbr0']
    disk = ['file:/xen-images/guest_base.img,hda1,w','file:/xen-images/guest_base-swap.img,hda2,w']
    ip = "192.168.0.101"
    netmask = "255.255.255.0"
    gateway = "192.168.0.1"
    hostname = "baseimage"
    root = "/dev/hda1 ro"
    extra = "4"

    Since dapper is not working for me, I switched to edgy...but it seems this ride iis not going to be smooth.
    If you have any suggestions regarding this problem, plz let me know.
    Thanks in advance.
     
  6. falko

    falko Super Moderator ISPConfig Developer

    Can you try this in the domain configuration?

    Code:
    memory = [B][COLOR="Red"]"[/COLOR][/B]128[B][COLOR="Red"]"[/COLOR][/B]
    Also, can you try the xm create command without the -c switch?
     
  7. ashutosh

    ashutosh New Member

    to falko:

    The changes you mentioned are not working...any other suggestion???
     
  8. falko

    falko Super Moderator ISPConfig Developer

    Do you still get the same error message?
     
  9. ashutosh

    ashutosh New Member

    Yes, error messages are still the same.
     

Share This Page