VMware Communities: Message List - Ubuntu 7.10 Just Enough OS appliance

Ubuntu eth0

Lance Rushing — Wed, 06 Aug 2008 19:11:09 GMT

For Ubuntu Hardy 8.04 I got eth0 working by doing the following:

sudo rm /etc/udev/rules.d/70-persistent-net.rules
sudo reboot

Also I went back and removed the 70-persistent-net.rules from my gold source used for cloning.

I suppose you could make a script that would remove 70-persistent-net.rules on each boot/halt. Then you can roll out the appliance and not worry about the eth0.

Re: virtual appliances .net

brugh — Fri, 04 Apr 2008 22:06:25 GMT

the whole purpose of creating the jeos appliance for me was to have a solid base to create other appliances on. i created several appliances on this one (like the Hasslefree download appliance). at the moment i'm working on a pure esx deployment appliance that we use at my company to role out esx servers by the 100s. i think i'll post that on the here some day soon, it's very intuitive and quick to setup and has built in script-building features which would probably help a lot of people setting up their environment in no time at all.

i know about the virtualappliances.net site. tested some of the appliances too. didn't check the forum yet but i think i'll have a look.

funny sidenote; i host http://virtualappliances.eu. no relation to their site

virtual appliances .net

avasseur — Fri, 04 Apr 2008 12:05:05 GMT

"Brugh"

you might be interested in http://virtualappliances.net/
I think it would make sense if you 'd join your expertise with the guys over there, although they seem to be more after "jeOS VM+something" than jeOS bare VM.

Re: Network problems in virtual appliances

gerbenh — Thu, 03 Apr 2008 12:53:19 GMT

Try adding ethernet0.virtualDev = "vlance" or try ethernet0.virtualDev = "e1000″ to the vmx config file.

When i test it local it is enough to delete the content of the 70-persistent-net.rules file, configuring a static ip address on eth0 and reboot the machine. But that doesn't work remote here.

Re: Network problems in virtual appliances

brugh — Wed, 02 Apr 2008 21:34:47 GMT

the post states that changing the device type in the vmx to vmxnet would help. but this appliance has that setting by default. do you have anything on udev perhaps? that's a bigger problem..

Re: Network problems in virtual appliances

gerbenh — Mon, 31 Mar 2008 14:07:38 GMT

How to fix ethernet0 enabling problems with Ubuntu JeOS 7.10 and maybe higher and some lower versions

Re: Ubuntu 7.10 Just Enough OS appliance

merlotsv — Wed, 26 Mar 2008 07:56:04 GMT

I was still having trouble getting my shared folders to automount at startup but after piecing together the steps in this thread with some external sources I worked it out.

First make this command works for you
vmware-hgfsmounter .host:/ /mnt
If that doesn't work then you will need to check your vmx settings as per OP

If that works then add the line to your /etc/fstab
./host:/ /mnt/hgfs vmhgfs defaults 0 0

Finally create a symlink
ln -s /usr/sbin/vmware-hgfsmounter /sbin/mount.vmhgfs

Thats it..

Re: Other format for EC2

brugh — Tue, 25 Mar 2008 14:47:48 GMT

this appliance is different in the fact that i removed all audio and multimedia related applications and some others that nobody needs in a virtual appliance. also, the harddisk has been repackaged and with some smart disk and filejuggling, manually defragmented. so instead of a default install and application removal which would leave you with a 300mb zipfile, this one is only 70mb.

as for canonical, i think they only add payed support to ubuntu and some tools to manage multiple servers at the same time. no specific appliance or jeos stuff.

Re: Other format for EC2

avasseur — Tue, 25 Mar 2008 11:06:11 GMT

How is this appliance different from the Canonical provided Ubuntu JeOS instal CD at http://www.ubuntu.com/news/ubuntu-jeos ?

(except that it is pre installed as a VMware appliance)

a related question if someone knows:how the canonical provided ubuntu-jeos is different from what a "deboostrap " call would produce ?

thanks

Re: Network problems in virtual appliances

deleta — Sun, 23 Mar 2008 20:55:38 GMT

I understand now. However, I prefer not to change the configuration now that it is working.

Thank you,

Diego

Re: Other format for EC2

brugh — Fri, 21 Mar 2008 16:45:35 GMT

i'm not familiar with amazon machine images but as far as i can tell it's just a matter of running some AMI tools inside the machine to capture it. if that's the case it should be quite straightforward to convert this VM to a AMI. just download player, run the vm, run the tools and voila. if not, please elaborate what would be needed to create AMI's.

Re: Network problems in virtual appliances

brugh — Fri, 21 Mar 2008 16:35:42 GMT

glad it worked for you. but you shouldn't have to edit /etc/network/interfaces.

what probably happened is that, once you start the appliance for the first time, it generates a new eth because the rules.d hasn't changed yet. if you just remark the line with eth0, the new eth1 line will still be in there. so a reboot doesn't help because it'll still have the eth1 line. if you edit the interfaces file, changing eth0 to eth1 will work but you'll end up with a eth1.

the way to go is to not only put a # in front of the eth0 lines in the file in /etc/udev/rules.d but in front of all of them. now if you reboot it'll generate a new eth and since it has no rules yet, it'll be eth0.

Re: Network problems in virtual appliances

deleta — Fri, 21 Mar 2008 07:59:06 GMT

I think I fixed my own problem. I am not sure if it is an error in brugh's previous post or just a misinterpretation on my part.

After following the instructions, I had the same problem as commented above. To solve it, after trying various things, I went to /etc/network/ interfaces and edited the lines with eth0, replacing eth0 with eth1. After that, everything worked.

I believe that by putting the # before the eth0 line as brugh sugested, it forced the system to create an eth1 interface, not an eth0 interface. That's why, when I changed the "interfaces" file as mentioned above, it worked.

Re: Network problems in virtual appliances

deleta — Fri, 21 Mar 2008 06:47:41 GMT

I have been following the thread about the network problems because I have the exact same problem.

I have followed the last instructions, gone to the /etc/udev/rules.d/70-persistent-net.rules and added a # before the line:

SUBSYSTEM=="NET" ..... NAME="eth0"

Unfortunately, when I rebooted, I got the exact same symptom as before, when I typed ifconfig, I could only see the lo interface, no eth0 or eth1.

Any ideas of what I might be doing wrong?

By the way, I am using VMware Server Version 1.0.4 running on a Ubuntu 7.10 host.

Greatly appreciate the help.

Other format for EC2

avasseur — Fri, 14 Mar 2008 15:54:50 GMT

I am wondering if someone would be interested in making that VM available on EC2 as an AMI (I apology - it does not directly relate to VMWare)
This VM sounds a very nice initiative to build some more complex VM atop - somewhat like rPath but with a more limited - thus hopefully simpler - scope, but having it available only in a single format is no fun.

Drop me a note if you are interested.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Wed, 12 Mar 2008 11:43:17 GMT

good question since it's built do work that way, it should work.. but perhaps the new kernel creates new UUIDs and a 'grub-install' after a reboot would solve the problem also. exactly why i dont like udev and UUIDs.

Re: Ubuntu 7.10 Just Enough OS appliance

srand — Wed, 12 Mar 2008 08:48:08 GMT

thanks, that's better

Why does the boot fail if the UUID are correct ??

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Wed, 12 Mar 2008 08:40:14 GMT

that's probably because the kernel installer 'conveniently' changed /boot/grub/menu.lst for you. it will want to use UUID's to identify the harddisks and somehow, despite the fact the UUID's are correct, boot will fail.

easy way to fix this is to hit 'esc' when you see the grub prompt, go to the kernel line, hit 'e' to edit it and change everything after 'root=' to '/dev/sda1'. now hit enter, 'b' to boot and you should be able to get it. now edit /boot/grub/menu.lst and do the same and all should be well again.

i do hate how linux tends to uniquely identify everything and give it a new name. i just want the first harddisk to be /dev/sda, the first network card eth0, and not have everything renamed if something changes. ohwell..

hope this helps

Re: Ubuntu 7.10 Just Enough OS appliance

srand — Wed, 12 Mar 2008 07:20:19 GMT

I can't boot anymore since I upgrade to the kernel 2.6.22-14-virtual

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Tue, 11 Mar 2008 22:42:14 GMT

what's your point?

Re: Ubuntu 7.10 Just Enough OS appliance

Larry_Vmware — Mon, 10 Mar 2008 13:16:07 GMT

测试 test this mmm

Re: Support for other locale

brugh — Wed, 05 Mar 2008 16:56:27 GMT

the jeos is pretty bare when it comes to keyboard and language support. but you can simply type:

apt-get install console-setup

to get the required package.

Support for other locale

avasseur — Wed, 05 Mar 2008 16:05:24 GMT

Hi
Can anyone give me instructions on how to switch the locale (esp. keyboard) to FR, or Azerty
"locale" is not installed, and so isn't "sudo dpkg-reconfigure console-setup"

thanks

Re: Jeos SCSI drive

brugh — Fri, 22 Feb 2008 21:34:03 GMT

reason i put in scsi is that you can use the appliance on esx also so the appliance uses buslogic drivers. it's common practice to have linux (and windows) run on lsilogic and i wonder why ubuntu people didn't include that in the jeos image but the buslogic driver works fine.

there's a problem with the virtual scsi layer in vmware server 1.0 so buslogic doesn't work well there but on other platforms like workstation, esx, player or server 2.0 beta it runs fine. if you have to run it on server 1.0, try loading it up in player, install the generic kernel and it'll run fine in server too (it'll just be a lot bigger). the generic kernel has a well working lsilogic driver onboard.

Jeos SCSI drive

apjo — Fri, 22 Feb 2008 15:54:19 GMT

Hi brugh,

I have found your Jeos build to be very reliable (bar the linux-image grub problem, which had me scratching my head!) and am using it to good success in production currently.

One question i did have was why the image is configured with SCSI not IDE, since the Jeos guide says that SCSI drivers are not fully installed/supported, and IDE should be used?

thanks

apjo

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Tue, 19 Feb 2008 01:04:59 GMT

thanks for the feedback. that'll help people to set things up for themselves.

Re: Ubuntu 7.10 Just Enough OS appliance

alexneg — Mon, 18 Feb 2008 12:53:13 GMT

finally it works!

you should add to .vmx file

sharedFolder.option = "alwaysEnabled"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.writeAccess = "TRUE"
sharedFolder0.hostPath = "C:\shared_folder"
sharedFolder0.guestName = "hgfs"
sharedFolder0.expiration = "never"
sharedFolder.maxNum = "1"

start the appliance then run
vmware-hgfsmounter .host:/ /mnt

and you'll find your shared_folder in /mnt/hgfs.

mount -t vmhgfs .host:/ /mnt/hgfs -- failed with an error 'wrong fs type, bad option, bad superblock on .host/'

thank you very much

Network problems in virtual appliances

brugh — Sat, 16 Feb 2008 23:12:18 GMT

omygawd, if i'd have known it was that simple . i read a bit into udev and it seems it's easier than i thought.

if you have network problems it's because your host generated a new mac address. default behavior these days in linux is that it will generate a new ethernet device (ie. eth1) which is not setup in /etc/network interfaces.

all you have to do to have linux stop doing this, is to just put a # in front of the eth0 line in /etc/udev/rules.d/70-persistent-net.rules. now if you reboot with a new mac address it will just call it eth0 again. for virtual appliances, that's exactly what we want

ohwell, took me half an hour of reading and googling. seems it's not written down somewhere obvious so i thought i'd share it with the rest of you.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Fri, 15 Feb 2008 22:31:56 GMT

i didn't enable it by default but the hgfs driver is in there. if you type

mount -t vmhgfs .host:/ /mnt/hgfs

you find all shared folders in /mnt/hgfs. to enable it at boot, add it to you /etc/fstab:

.host:/ /mnt/hgfs vmhgfs defaults 0 0

also, check 'vmware-hgfsmounter' for more options.

Re: Ubuntu 7.10 Just Enough OS appliance

alexneg — Thu, 14 Feb 2008 17:15:36 GMT

hi brugh,

is there any possibility to enable shared folders in your virtual appliance?

kind regards,
alec

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Thu, 07 Feb 2008 22:52:50 GMT

if you removed the package installer you can't fix it. apt-get is just a wrapper around dpkg and dpkg needs perl to do anything. so if dpkg is gone, you can't install anything anymore (the normal way). you could download them, unpack them on another machine and copy them over (with tar or cpio) but that's an awful lot of trouble. it's probably easier and faster to just start over and learn from the experience. (don't worry, happens to the best of us. it even happend to me once )

Re: Ubuntu 7.10 Just Enough OS appliance

Vadim Dorezuk — Thu, 07 Feb 2008 22:46:01 GMT

Hi Brugh, return to second question about removing unessential packages: I've tried to purge the "SELinux shared libraries" libselinux1 and agreed to remove a lot of depending stuff with it including "dpkg". But how can I get the dpkg-Package back to install minimal ubuntu-kernel now before reboot? The whole installation shines to be inconsistent and "apt-get install dpkg" says something about missing dependenses to perl5,locale and so on. Are there some tipp&tricks with options like "--irnore-missing" or something like that? Thank you in advance.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Thu, 07 Feb 2008 22:29:40 GMT

the kernel upgrade forces a rebuild of the initrd image. that also rewrites the menu.lst in /boot/grub. now the odd part is that dispite the UUID for the root fs is correct, it won't boot that way. try changing the 'root=UUID=someweirdnumber' to 'root=/dev/sda1' and try again.

just for reference; the regular appliance download should upgrade the virtual image, both HDA and JeOS. these work on buslogic. only the version specifically for VirtualServer 1.0x should upgrade the generic kernel. this is the one that's working with lsilogic (and has the bigger footprint).

Re: Ubuntu 7.10 Just Enough OS appliance

Mista_Eng — Thu, 07 Feb 2008 20:22:20 GMT

Hello Brugh, I just wanted to let you know that I didn't get to try out the network fix in your last reply to me. My regular JeOS install is working well and I am satisfied with it. However, thank you very much for your help and I hope to use your appliance in the future.

Re: Ubuntu 7.10 Just Enough OS appliance

Vadim Dorezuk — Thu, 07 Feb 2008 13:26:49 GMT

The appliance for VMServer 2 beta didn't survive the apt-upgrade with new linux-image-2.6.22-14-generic (version 14.51-i386 of 1.02.2008) for me, which contains new 2.6.22-14-virtual kernel. It's probably the same as :
https://bugs.launchpad.net/ubuntu/+bug/163227
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/164716

The appliance shows BusLogic SCSI and goes into BusyBox shell after upgrade/reboot. The same crash for DLappliance, which shows LSI-Logic -SCSI for me.
The full (not "purged" ) JeOS appliance 1124 (BusLogic) goes the upgrade through, and wants to install not linux-image-2.6.22-14-generic but only linux-image-2.6.22-14-virtual and
linux-headers-2.6.22-14-virtual.

Is the crash really due to SCSI? The SCSI issues should be fixed in JeOS 8.04 Hardy. Does it make sence to purge this one?
Does somebody know here , will the "apt-get upgrade" automaticaly upgrade 8.04 to alpha4 from alpha3 , beta1 from alpha4 and to rc from betaX or one should reinstall the whole jeos each time? Thank you very much in advance.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Thu, 07 Feb 2008 00:11:44 GMT

that disappearing network card keeps being a problem. the problem lies in the fact that linux fixes a mac address to a eth device. if an appliance starts for the first time it will generate a mac address if it doesnt have one.

the easiest way to fix it is to edit /etc/network/interfaces and copy the eth0 lines to eth1.

remember, on all hosts not being vmware server 1.0, you should have the ethernet0.virtualDev = "vmxnet" in your .vmx. only on vmware server 1.0 will you need to have 'vlance' in there (which will be a pcnet32 in linux).

Re: Ubuntu 7.10 Just Enough OS appliance

askwar — Wed, 06 Feb 2008 11:14:51 GMT

Hi!

Mista_Eng wrote:
Hi Brugh,

I tried your first suggestion, and typed "ifup eth1" and received: Ignoring unknown interface eth1-eth1.

"ifup eth0" resulted in: eth0: ERROR while getting interface flags: No such device.

The 70-persistend-net.rules file contained: SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:3a:1b:80", NAME="eth0"

"dmesg | grep eth0" resulted in: eth0: registered as PCnet/PCI II 79C970A

I think "lsmod | grep pcnet" did output a listing of pcnet32.

I have also tried reinstalling the network card from the applicance configuration but there was no change. It made no difference whether I uninstalled-installed while the VM was off or with a reboot between the steps; the appliance doesn't seem to see the network card despite traces of its existence.

"ifconfig" only shows the loopback adapter. Pings of course do not work. Hrmm, maybe I am the only one with this problem.

Thanks for the barebone process details. Since I do not know which packages are essential, I'll have to leave my other JeOS alone hehe. And "nano" is so much easier to use than "vi," much aggravation has been saved. Which reminds me, is there a way to have scrollable or prompted output from commands? For example, if I do a "ls --help" and get 3 screens worth of output, I only see the last screen. This is very annoying and I have been coping with this by doing "ls --help >foo" "less foo". I know in MS-DOS you can add the /p switch to a command, say "dir /p", and the output is controlled.

Thanks again, and hope to hear from you soon.

No, you're not alone. I've got the exact same problems getting the network card to work. I changed the ethernet0.virtualDev line in ub710jeos.vmx from vlance to vmxnet. But still no go :/

Regarding your "ls --help" question: You pipe the to-be-paged output to "less", like so:

ls --help | less

Regards,

Alexander

Re: Ubuntu 7.10 Just Enough OS appliance

askwar — Wed, 06 Feb 2008 10:49:59 GMT

Hello!

VadimDo wrote:as on Jan 30 2008 6:30AM the
http://virtualappliances.eu/ub710jeos-VS.zip
is still not the fixed one version for vmserver 1.0.4.
it contains only the files from 29.01.2008

The -VS version works fine for me on VMware Server 1.0.4 on Gentoo Linux.

-rwxrwxrwx 1 askwar users 175496899 6. Feb 11:15 ub710jeos-VS.zip
$ md5sum ub710jeos-VS.zip
30b3e77b7635058c9f2056a0f308cee7 ub710jeos-VS.zip

Best regards,

Alexander

Re: Ubuntu 7.10 Just Enough OS appliance

askwar — Wed, 06 Feb 2008 10:36:05 GMT

Hello!

I downloaded ub710jeos-1.021.zip and tried to run it in VMware Server 1.04 on Gentoo Linux. It does the "usual" SCSI scan thing (see attached screenshot). Example

http:// 54.642988 sd 2:0:1:3: rejecting I/O to offline device
http:// 54.643116 sd 2:0:1:3: rejecting I/O to offline device
http://...
http:// 54.643734 sd 2:0:1:3: sde Asking for cache data failed
http:// 54.643881 sd 2:0:1:3: sde Assuming drive cache: write through

This continues forever, as it seems.

According to Mista_Eng it should work, shouldn't it?

What to do?

Thanks,

Alexander

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Tue, 05 Feb 2008 08:46:12 GMT

it's strange that it sees your network card (dmesg) but won't start it. this is usually because it's bound to a hardware or MAC address. one more thing you could try is edit the /etc/network/interfaces and copy the two lines with eth0 and make it eth1. then try 'ifup eth1'. if that fails post your .vmx file here and the output of 'lspci'.

about less. you don't have to put output into a file first. you can simply type 'ls -h | less'. instead of a file it uses a pipe.

Re: Ubuntu 7.10 Just Enough OS appliance

Mista_Eng — Tue, 05 Feb 2008 01:50:18 GMT

Hi Brugh,

I tried your first suggestion, and typed "ifup eth1" and received: Ignoring unknown interface eth1-eth1.

"ifup eth0" resulted in: eth0: ERROR while getting interface flags: No such device.

The 70-persistend-net.rules file contained: SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:3a:1b:80", NAME="eth0"

"dmesg | grep eth0" resulted in: eth0: registered as PCnet/PCI II 79C970A

I think "lsmod | grep pcnet" did output a listing of pcnet32.

"ifconfig" only shows the loopback adapter. Pings of course do not work. Hrmm, maybe I am the only one with this problem.

Thanks again, and hope to hear from you soon.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Mon, 04 Feb 2008 22:53:15 GMT

if you dont have a network card in your appliance there's a few things you can check.

first, try typing 'ifup eth1', see if that gives you a link. if so, go to /etc/udev/rules.d and edit 70-persistent-net.rules, remove the line with 'eth0' and change the eth1 on the next line to eth0.

if this doesn't work, check the .vmx file and check the ethernet0.virtualDev = "vmxnet" line. it should also work with 'vlance' but in the appliance itself you need to do the above thing. to see which one it finds, type 'dmesg' and check for network card messages. or type 'lsmod' and check for 'pcnet32' or 'vmxnet' lines.

if this all fails, try removing the network card from the config and re-adding it. you can try either 'flexible' or 'vmxnet'.

second question is a bit harder to explain. removing packages is one thing, knowing which ones is another. but if you feel comfortable, try typing 'dpkg -l' and start removing with 'apt-get purge' (if you use 'remove' you'll not completely cleanup the configfiles etc). when you're done, type 'apt-get autoclean' to clear the caches and that's about it. just the diskfile is 3 times bigger than the actually used space because of all the adding and removing. therefor i created a second disk, copied all files onto that one and made it into the first one (bit of grubbing, bit of tweaking).

3rd question is easier if you dont like 'vi', i left 'nano' in there. it's a more intuitive editor with a lot less options but enough for basic configfile editing.

hope this helps.

Re: Ubuntu 7.10 Just Enough OS appliance

Mista_Eng — Mon, 04 Feb 2008 18:20:07 GMT

Hi, I downloaded and tried the appliance from your last link on VMware's Server 1.04 and while it did start without errors, there was no network connectivity. The Ethernet interface appeared to be disabled in the OS although there was one "installed" in the virtual machine configuration. I tried entering in static IP configuration information through the command "sudo vi /etc/networking/interfaces" "sudo /etc/init.d/networking restart" but it failed saying there was no hardware, or something like that.

I am a newbie when it comes to *nix and was wondering if you, or anyone for that matter, could help me. I just want a Dansguardian + adzapper + Squid server to transparently proxy, filter, and cache http requests with a small resource footprint. This particular appliance seems to fit my requirements exactly if only the networking was enabled, though the problem may be on my side.

Using the regular JeOS image, I have been able to create my own VM with everything I wanted installed, but I think the installation could be reduced in size. Can you detail what exactly you did to trim JeOS down to the "bare essentials"? If the process is too long, a summary will do, or if you have a link (I haven't found any guide or how-to information on the process), that would be fine as well.

In summary, I have three questions:

1. How do you enable eth0 so that I configure it with static IP settings?

2. How did you trim JeOS to it's bare essentials?

3. Also, is there an easier editor to use than "vi"? It seems to be a very cryptic program; I have managed to work with it reading some of the documentation online, but I continue to easily make mistakes during use.

Thank you very much in advance. While I did spend a bit of time getting my own JeOS creation going, and it appears to be working without issue, I wouldn't mind running your appliance instead. My home server only has 1GB of RAM and needs to be spent wisely hehe.

Re: Ubuntu 7.10 Just Enough OS appliance

VadimDo — Mon, 04 Feb 2008 15:44:00 GMT

thanks, it works now

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Sat, 02 Feb 2008 21:59:09 GMT

the total downloads of the appliance in januari stopped the counter at 27442. that's a huge number in just 25 days thanks everybody for their interest.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Thu, 31 Jan 2008 13:51:51 GMT

i redid the steps that i took to get the HDA to work and uploaded it again. please download it from here and let me know if it works. i can't test it myself because i dont have a VS1.0 host anymore. can't think of a reason why this one shouldn't work though since it's in core the exact same system as the HDA.

Re: Ubuntu 7.10 Just Enough OS appliance

VadimDo — Wed, 30 Jan 2008 15:46:08 GMT

as on Jan 30 2008 6:30AM the
http://virtualappliances.eu/ub710jeos-VS.zip
is still not the fixed one version for vmserver 1.0.4.
it contains only the files from 29.01.2008

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Wed, 30 Jan 2008 14:17:06 GMT

yes it is. available through the normal download link on http://www.vmware.com/appliances/directory/1136. it's not the vmware server 1.0 compatible one though. that one with "-VS.zip".

Re: Ubuntu 7.10 Just Enough OS appliance

VadimDo — Wed, 30 Jan 2008 12:56:36 GMT

thanks a lot! is the ub710jeos-1.021 ready for download?

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Wed, 30 Jan 2008 12:07:43 GMT

ah yes you did. i didnt realize it was a more common problem. fixed it and made ub710jeos-1.021 available with that and another small adjustment. if people run the appliance succesfully there's no need to download it again but if you ran into trouble you can give it a go.

please do post problems here if you see them though. i will try to help fix any issues out there to make this appliance work perfectly for everybody.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Wed, 30 Jan 2008 12:04:45 GMT

you sure you downloaded the right one? it should be 170mb in size and have a lsilogic scsi drive. because it runs a full kernel it's much bigger but the lsilogic driver in there should work perfectly. just in case, here's the link. the base is exactly the same as the DLappliance that works for you so it would be very strange if this one wouldn't.

appliance 1124 isn't mine. i tested that one too and it's way way too big for my taste. it's the reason i built this one though because i think an appliance should be small. also it should have added value, not just create a vm, install the os from iso and add vmware tools. anybody can do that.

Re: Ubuntu 7.10 Just Enough OS appliance

VadimDo — Wed, 30 Jan 2008 11:23:11 GMT

the vmserver version still doesn't work for me - again the full scsi scan. The same is with other appliance
http://www.vmware.com/appliances/directory/1124
which seems to be "unshrunked" version of JeOS.
But your new DLAppliance/JeOS for vmserver works fine, thanks!

As well as "French Ubuntu 7.10 JeOS Base"
http://www.vmware.com/appliances/directory/1150
but it has an IDE-disk.

Re: Ubuntu 7.10 Just Enough OS appliance

freemant — Wed, 30 Jan 2008 09:35:47 GMT

this is the screenshot.

Re: Ubuntu 7.10 Just Enough OS appliance

freemant — Wed, 30 Jan 2008 09:31:39 GMT

It occurs when you start the VM. I reported it on Jan 17 (see http://communities.vmware.com/message/842680#842680). A screen shot is attached.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Tue, 29 Jan 2008 22:51:49 GMT

OK, my quota got upped again so i put the JeOS appliance for VS online. So, for as long as quota lasts, go to this link and have a go.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Tue, 29 Jan 2008 21:11:37 GMT

what networkName error is that? and when does it occur? it's the first time i've heard this problem. can you post a screenshot?

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Tue, 29 Jan 2008 21:08:28 GMT

no problem. should be a quick fix. at the moment i have no place to put in on the internet though. my unlimited account has no space and my other account reached it quota a long time ago even after i doubled it. i'll put it online somewhere next week but can't promise 100% availability. if you're quick you can probably get it before the quota runs out again.

if anybody has a place to make it available and can do several TB of uploading a month please let me know

Re: Ubuntu 7.10 Just Enough OS appliance

VadimDo — Tue, 29 Jan 2008 17:02:23 GMT

Brugh,
the same as for ka9dgx for me on Vista with VM Server 1.0.4 , so I need vmware server 1.0 version of the appliance too. Thank you very much in advance.

Re: Ubuntu 7.10 Just Enough OS appliance

freemant — Tue, 29 Jan 2008 01:25:37 GMT

I can't give it a good rating due to the "networkName" error. In fact, it happens with my home computer (XP running the latest VMplayer, ie, 2.0.2). It is difficult to recommend it to people if it won't start unless you hand fix a config file.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Tue, 29 Jan 2008 00:41:08 GMT

cool, just saw a stats on the number of downloads. this appliance has been downloaded 25000 times since januari 6th. that's 22 days.

it would be nice if people voted though. the only one who voted was somebody who couldn't get it to work because he ran vmware server so the rating is a bit off compared to the number of downloads.. just go to http://www.vmware.com/appliances/directory/1140.

anyway, if there's anybody who needs a vmware server 1.0 version let me know. i got the hasslefree download appliance to work which is based on this one.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Fri, 25 Jan 2008 15:14:53 GMT

i was trying to make time to make a special vmware server 1.0 version (it works in server 2.0 beta). it's been too busy lately though.

if you're in a hurry, you could try downloading vmware player, run the appliance in there and run:

apt-get install linux-image

apt-get purge virtual*

and change the root=UUID=... bit in /boot/grub/menu.lst to read root=/dev/sda1 and things should work.

if you set the scsi driver to lsilogic and start the appliance in vmware server after that there's a good chance it will work. i'll try to build one in the near future (and do some specific cleanup up to keep the size down a bit) but you'll have to be patient.

Re: Ubuntu 7.10 Just Enough OS appliance

ka9dgx — Fri, 18 Jan 2008 22:33:08 GMT

If I tell VMware 1.04server to make the machine use BusLogic as the SCSI driver for the disk, it failes in the same manner as your image. ~~It does appear to be working with an LSI logic SCSI driver though.~~

Spoke too soon... it doesn't work with either SCSI device inside VMware Server 1.04 on Window.

Re: Ubuntu 7.10 Just Enough OS appliance

freemant — Fri, 18 Jan 2008 09:30:06 GMT

VMware player 1.01 on Win2K.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Fri, 18 Jan 2008 08:11:08 GMT

ok thanks. what host/vmware product are you using?

Re: Ubuntu 7.10 Just Enough OS appliance

freemant — Fri, 18 Jan 2008 06:52:25 GMT

Have to comment out the ethernet0.networkName line in order for the virtual NIC to work.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Wed, 16 Jan 2008 19:54:26 GMT

too weird. seems that vmware server 1.04 simple can't run the ubuntu virtual kernel. i run 2.0 beta now and it works fine but you may not have that option. the final won't be released until april probably...

could you do a little test for me. create a new VM, attach http://cdimage.ubuntu.com/jeos/releases/gutsy/release/ubuntu-7.10-jeos-i386.iso and boot from it. if that doesn't work (which i suspect it wont), the only option left is to use a full kernel (which is over almost 100mb instead of 30).

i could strip the full kernel down to about the size of the virtual kernel but i'm reluctant to do that since the purpose of this appliance is not to strip down packages, just have a few of them as possible. once the kernel is stripped down, i could start on many more packages and get the appliance probably close to 100mb but it will become unsupported and i dont want that.

let me know how the test goes and i'll build one with a full kernel. will be bigger but also more compatible...

Re: Ubuntu 7.10 Just Enough OS appliance

ka9dgx — Wed, 16 Jan 2008 19:23:36 GMT

I downloaded your new version 1/14/2008, and still no go.

I removed/re-added the disk... no go...

the last few lines are like this:

http:// timestamp.milliseconds sd 2:0:15:6 rejecting I/O to offline device

http:// timestamp.milliseconds sd 2:0:15:6 sddh Asking for cache data failed

http:// timestamp.milliseconds sd 2:0:15:6 sddh Assuming drive cache: write through

http:// timestamp.milliseconds sd 2:0:15:7 rejecting I/O to offline device

http:// timestamp.milliseconds sd 2:0:15:7 sddh Asking for cache data failed

http:// timestamp.milliseconds sd 2:0:15:7 sddh Assuming drive cache: write through

(initframfs)

Sorry I couldn't figure it out either.

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Mon, 14 Jan 2008 12:40:32 GMT

ok, i recreated the appliance on a vmware server. it seems to work ok in vmware server now. please redownload it from http://www.vmware.com/appliances/directory/1136 and see if it works. (and don't forget to rate it properly if it works)

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Sat, 12 Jan 2008 00:40:36 GMT

looks like it sees a device at id 255. you can try removing the disk (in edit configuration), hit OK and edit again, re-adding the disks as existing disks. other people have the same problem (although that makes two. didn't hear from any of the other 7500 downloaders).

check out this message: http://communities.vmware.com/message/838841#838841

Re: Ubuntu 7.10 Just Enough OS appliance

ka9dgx — Fri, 11 Jan 2008 21:50:07 GMT

I tried a few different variations of what you suggested, and even removing it... still no good.

The host is VMware server 1.04 on Windows XP.

~~Mike~~

Re: Ubuntu 7.10 Just Enough OS appliance

ka9dgx — Fri, 11 Jan 2008 21:44:13 GMT

Please see the attached screen grab... this is after I downloaded Ubuntu Server 7.10 ISO and told it where to find it in the VMX file...

there are a lot of lines like

sd 2:0:1:5: rejecting I/O to offline device

it was still doing this after 415 seconds.

Oh... and here's the VMware log as well

Re: Ubuntu 7.10 Just Enough OS appliance

brugh — Fri, 11 Jan 2008 21:05:41 GMT

to disable the cdrom is pretty easy. open the .vmx file in your favorite editor and change the line ide1:0.startConnected = "TRUE" to "FALSE" or disable IDE complete by setting ide1:0.present = "FALSE".

But that's IDE so that doesn't sound like the problem you're experiencing with SCSI detection. I tried several different setups from workstation 6 on windows to esx 3 and vmware server on linux. never had any problems. what host are you using? perhaps have a look at the vmware.log file (or post it so we can check it).

Re: Ubuntu 7.10 Just Enough OS appliance

ka9dgx — Fri, 11 Jan 2008 18:15:01 GMT

Brugh,

Thanks for doing the work to get this thing shrunk down to size.

There seems to be a dependency that's keeping it from working for me.I don't have the ISO image file D:\Images\ubuntu-7.10-server-i386.iso, so it's spending a lot of time trying to scan the scsi bus to find it... (which it never will).

Is there some way to start it without that file?

Apparently, it's not the missing CD-ROM, there's something deeper at fault here. I gave it a different Ubuntu ISO to try to use, and it still did the same thing... looking through EVERY SCSI device/ID/HOST trying to find something... at 10 seconds per iteration. I assume it would eventually give up after an hour or two... but that makes it unusable with a boot time that long.

I hope it's a simple fix.

Ubuntu 7.10 Just Enough OS appliance

brugh — Mon, 07 Jan 2008 23:38:03 GMT

http://www.vmware.com/appliances/directory/1136

A basic Ubuntu 7.10 server installation trimmed down to under 100MB (280MB unzipped). It has a manual installation of VMware tools. It's purpose is to have a good basic system to build an appliance on and be properly small for an appliance.