[dss-developer] Trying to build dss11-vm-image

[Sergey 'Jin' Bostandzhyan]

Hello Lukas,

On Thu, Sep 27, 2012 at 11:11:48PM +0200, Lukas Zeller wrote:
> The VM image in feeds works fine and is great for experimenting (you showed it to me at the devDays already, thanks!)
> 
> However the VM is only an intermediate step for me, my real target is the ALIX box. I just thought that the VM image is closest to that (x86 build), so I wanted to make sure I can build the VM and then start to adapt for the ALIX as needed.
> 
> I'll try to delete and bake w/o clean in between and see how far I get.

in this case you do not really need the VM image - it's only "special"
thing is the SYSLINUX installation which makes it bootable and the
conversion to vmdk.

Try building a dss11-image  (bitbake dss11-image) for the VM configuration,
it should spit out an ext3 and a tar.bz2 rootfs which is probably enough for
you. I do not know much about the ALIX box, but I would assume that you can
tell the bootloader where the rootfs is.

Kind regards,
Sergey

 
> On 27.09.2012, at 12:09, Sergey 'Jin' Bostandzhyan <jin at mediatomb.cc> wrote:
> 
> > Hi,
> > 
> > On Thu, Sep 27, 2012 at 12:02:37PM +0200, Lukas Zeller wrote:
> >> I'm trying to bake the dss11-vm-image target, but it always fails at the very end (do_rootfs) with:
> >> 
> >> ln: failed to create symbolic link `/home/luz/Code/digitalSTROM/dss-oe/angstrom-production-build-eglibc/deploy/images/qemux86/dss11-production-image-1.3.0-qemux86.tar.bz2': File exists
> >> 
> >> which leads to:
> >> 
> >> ERROR: Function 'do_rootfs' failed (see /home/luz/Code/digitalSTROM/dss-oe/angstrom-production-build-eglibc/work/qemux86-angstrom-linux/dss11-image-1.0-r0/temp/log.do_rootfs.29799 for further information)
> >> 
> >> 
> >> The thing is, that symlink does NOT exist when I look for it after the error occurs, but every time I retry I get the same message again, so it seems it is created in the process and cleaned up afterwards.
> >> 
> >> I tried to re-build a few times with
> >> 
> >>  bitbake -c clean dss11-vm-image
> >>  bitbake dss11-vm-image
> >> 
> >> but it always stops with this error.
> > 
> > this is a known problem, since the vm image is not officially supported it
> > was kind of a low priority and I did not have time to fix it yet.
> > 
> > You can try to remove /home/luz/Code/digitalSTROM/dss-oe/angstrom-production-build-eglibc/deploy/images/qemux86/dss11-production-image-1.3.0-qemux86.tar.bz2
> > and bitbake dss11-vm-image again (without cleaning), in most cases it works
> > then.
> > 
> > As an alternative (if you need production), take one of the images here:
> > http://feedback.aizo.com/feeds/dss11-production-eglibc/images/qemux86/
> > 
> > And then simply do a regular system update via the web UI in order to get
> > the latest version. Again, nothing guaranteed since the VM stuff is
> > unofficial and thus untested, but even if you run into some troubles it will
> > most likely be possible to fix them on the console.
> > 
> >> Before I dig deep into the mechanisms, I'd like to ask if building dss11-vm-image should just work (I tried in -devel and -production modes) like dss11-image does, or if there are precautions or manual steps to take before building.
> > 
> > I need to change the way how those live images are generated, I think it's
> > done differently these times in OE, while I still use an older method.
> > 
> > Kind regards,
> > Sergey
> > 
> > _______________________________________________
> > dss-developer mailing list
> > dss-developer at forum.digitalstrom.org
> > http://forum.digitalstrom.org/cgi-bin/mailman/listinfo/dss-developer
> 
>