Hi Christopher
I found the easiest way to create a AstLinux VMware image is to create a second
drive on a existing working Windows/Linux VM, Boot the Windows/Linux vm and
then use either dd or physdiskwrite to write the AstLinux image to the second
drive (as described in http://doc.astlinux.org/userdoc:new-install). Then I
detach the second drive from the Windows/Linux VM and create a new VM using the
existing second drive..
this alternative way of creating a AstLinux VM works for me
Regards Guy
On 18/06/2010, at 1:10 AM, Chris Abnett wrote:
> Ok so im here banging my head against the wall trying to get astlinux to run
> under VMWare.. I know there used ot be images created for it so I know it can
> be done…
>
> Here is what I want..
>
> I want to be able to work on my Astrlinux development while im say on an
> airplane with no internet access.. (be able to write dialplan and test with
> my softphone)….. I have VMware server on my very capable dual core laptop so
> no issues there….
>
> So I have my custom builds of astlinux.. one is for a net5501 and one is for
> a standard i586 generic (I run astlinux on both)…
>
> So I took a custom build, and did makerunnix.sh on it to create an image…. I
> can take that image and ddrescue it to a flash drive and it boots fine and
> works…
>
> So I found a program called qemu-img and ran that on the image makerunnix
> created.. this turned it into a vmdk..
>
> Created a virtual machine.. copied the vmdk over to the directory.. powered
> on the virtual machine…
>
> I get the following:
>
> Boot:
> Loading Runnix…………………………………………………………….
> Loading Runnix.img……………………
> Ready.
> Uncompressing Linux… Ok, booting the kernel.
>
> Decompressing Linux… Parsing ELF… done.
>
>
>
> And then no more output to the console afterwords… this is using the PC
> version (not the net5501)
>
> I figure im missing something dumb and that…
>
> Ok so I got past that error.. turns out I had it set up for a serial console…
> bad…
>
> ****
>
> So now I get all the way to where it says
>
> Copying AstLinux files to RAM…
> Unmounting /cdrom
> Pivoting…
> INIT: version 2.86 booting
> INIT: /etc/inittab[7]: id field too long (max 4 characters)
> INIT: /etc/inittab[8]: id field too long (max 4 characters)
> INIT: /etc/inittab[14]: missing id field
> INIT: /etc/inittab[15]: missing id field
> Enter runlevel:
>
> And that’s where it bombs… I don’t want to use an ISO because I want to make
> changes.. I really just want to run my astlinux just like I do on my PC in
> my VMware…
>
> Anything special I need to do?
> -Christopher
>
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo_______________________________________________
> Astlinux-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> [email protected].
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
