The script should be run from an Ubuntu 12.04 machine otherwise chroot will not 
work right. 

On Sep 9, 2013, at 3:20 AM, France <mailingli...@isg.si> wrote:

> That fixed the first error, but there are two more:
> --
> Saving to: `cloud-set-guest-password-ubuntu'
> 
> 100%[============================================================================================================================>]
>  4,153       --.-K/s   in 0s
> 
> 2013-09-09 08:59:45 (50.8 MB/s) - `cloud-set-guest-password-ubuntu' saved 
> [4153/4153]
> 
> cp: cannot stat `/run/resolvconf/resolv.conf': No such file or directory
> FATAL: kernel too old
> rm: cannot remove 
> `ubuntu-12.04-server-cloudimg-amd64/run/resolvconf/resolv.conf': No such file 
> or directory
> Done creating image. You can mount it to check it out using:
> mount -o loop ubuntu-12.04-server-cloudimg-amd64.fs 
> ubuntu-12.04-server-cloudimg-amd64
> 
> If you are happy with it, copy ubuntu-12.04-server-cloudimg-amd64.fs to one 
> of your XenServer hosts and create the vhd file using createVHD.sh
> --
> 
> First is about resolv.conf which is at /etc/resolv.conf in my CentOS install. 
> I can work around that by creating softlink, even thou resolv.conf is 
> normally populated using DHCP client.
> 
> The other "FATAL: kernel too old" might be in relation to CentOS kernel, once 
> script chroots into Ubuntu install. I'm just going to leave this for now and 
> install xen tools or guest utilities once i have the first Ubuntu VM running 
> in case if they weren't already.
> 
> Now it's time to test .vhd creation.
> 
> Regards,
> F.
> 
> On 9/9/13 12:00 PM, France wrote:
>> I just found the first error:
>> 
>> Script downloads ubuntu-12.04-server-cloudimg-amd64-root.tar.gz (actually 
>> ubuntu-12.04.3-server-cloudimg-amd64-root.tar.gz redirects to 
>> ubuntu-12.04-server-cloudimg-amd64-root.tar.gz), but then tries to 
>> uncompress ubuntu-12.04.3-server-cloudimg-amd64-root.tar.gz:
>> 
>> ---
>> This filesystem will be automatically checked every 34 mounts or
>> 180 days, whichever comes first.  Use tune2fs -c or -i to override.
>> Untar file system
>> tar: ubuntu-12.04.3-server-cloudimg-amd64-root.tar.gz: Cannot open: No such 
>> file or directory
>> tar: Error is not recoverable: exiting now
>> tar: Child returned status 2
>> tar: Error exit delayed from previous errors
>> Extract done
>> Begin customizing image
>> ./createUbuntuCSimageXen.sh: line 66: etc/init/hvc0.conf: No such file or 
>> directory
>> sed: can't read boot/grub/menu.lst: No such file or directory
>> sed: can't read etc/fstab: No such file or directory
>> sed: can't read boot/grub/grub.cfg: No such file or directory
>> sed: can't read etc/fstab: No such file or directory
>> sed: can't read etc/fstab: No such file or directory
>> sed: can't read etc/cloud/cloud.cfg: No such file or directory
>> ./createUbuntuCSimageXen.sh: line 80: etc/cloud/cloud.cfg.d/90_dpkg.cfg: No 
>> such file or directory
>> can't find file to patch at input line 3
>> Perhaps you used the wrong -p or --strip option?
>> The text leading up to this was:
>> --------------------------
>> |--- /usr/lib/python2.7/dist-packages/cloudinit/DataSourceCloudStack.py.old 
>> 2012-04-11 03:54:56.000000000 +0000
>> |+++ /usr/lib/python2.7/dist-packages/cloudinit/DataSourceCloudStack.py 
>> 2013-09-07 01:01:02.482498743 +0000
>> --------------------------
>> File to patch:
>> ---
>> 
>> I'll just change that LINK variable to: 
>> http://cloud-images.ubuntu.com/releases/precise/release/ubuntu-12.04-server-cloudimg-amd64-root.tar.gz
>> 
>> On 9/9/13 11:14 AM, France wrote:
>>> Carlos,
>>> 
>>> just one quick question. Which OS type should be used when registering this 
>>> Ubuntu created VHD on CS 4.1.1 with XS 6.0.2?
>>> https://github.com/creategui/CloudStackImageScripts
>>> 
>>> Tnx.
>>> F.
> 

Reply via email to