ClearOS 5.2 Enterprise foxpa.ws Xen Edition
- October 20th, 2010
- Posted in ClearOS . Virtualization
- By كارما
- Write comment
The following is the README file I have included with the package:
ClearOS 5.2 foxpaws edition Oct 2010 http://foxpa.ws This is a basic installation of ClearOS Enterprise 5.2 with modifications covered by articles at http://foxpa.ws. It resides on an ext3 filesystem on a partition within a sparse, raw disk image. It can be managed with losetup, lomount and kpartx. GRUB is configured to load a domU kernel by default and options exist for regular kernel (hvm) and the CentOS distribution of xen as a dom0 (this image should be directly writable to a hard drive). ClearSDN updates have been installed up until Oct 20 2010 and the registration has been wiped. Don't forget to add this VM to your ClearSDN account to receive updates. Caveats and considerations: - comes with iftop - custom firewall rules in webconfig block pings to external interface by default - custom snort rules with SIDs beginning with 4000000 - http://foxpa.ws/2010/06/04/bad-snort-rules/ applied - user username is user, password is user (must SU on physical console) - root password is root - automatic updates are disabled by default - graphical console disabled - serial console is forced onto /dev/ttyS0 - ports 81 and 22 open on external interface by default - eth0 ext 192.168.222.55/24 gw 192.168.222.1 - eth1 lan 192.168.111.11/24 - admin https://[192.168.222.55|192.168.111.11]:81 - grant users shell access enabled Don't forget to update the vif configuration entries to reflect the networking setup of your dom0 and ensure the MACs do not conflict with existing VMs. The installation was more or less based on this (slightly oudated) checklist: http://foxpa.ws/2010/04/16/clearos-installation-checklist/ The included domU kernel will only work on PAE-compatible or 64 bit hypervisor implementations and requires pygrub by default, however it can be run without pygrub if the domU kernel and initrd (initrd-noscsi.img) located in /boot/ are externalized.
Download at http://foxpa.ws/dist/clear-foxpaws.tar.lzma (261M)
UPDATE Check out ClearOS TROllup Edition! http://foxpa.ws/2011/01/22/clearos-trollup-edition/
Hi,
That image of yours is just awsome man, I tried it into a server I have setup for virtualization adn it’s very smooth, but it’s got a “gotcha”, whenever I make changes to smething like user passwords, or the domain the LDAP deamon won’t start anymore it sgfaults and the system becomes unusable.
Such a shame becase you’ve put a very nice project there and none of the available on the web are usable.
If you want me to help you reproduce the scenario please feel free to email me.
Thanks and congrats.
I don’t do e-mail but if you want to give me the details here I will be happy to help.
It seems that the LDAP system is very sensitive to booting up with a correct and working network configuration. Also make sure you have enough RAM assigned to the VM.
Do your system logs tell you anything useful?
Hello, thanks for a good image.
But when I try to register this system in ClearSDN I get “This system has already been registered with a different name or registered under a different account”. Do you know any solution?
Thank you.
Go to this URL /admin/register.php?Reset=yes in the webconfig. I did this before packaging the image but found I had to do it again after I redeployed it. Worked for me the second time.
Hope that helps, happy someone has found use for it :)
Yes, it is working now! Thanks :)
No problem :)
Hello again!
2Gb image is too small, so I’m out of space and need to expand it.
I was trying different howtos, but got only corruption of filesystem.
Can you point me a howto which should work for this installation?
Thank you.
The safest way (I am not a fan of disk image surgery) is to create a new blank file with dd, write a partition table to it with fdisk then use kpartx or losetup to give the partition within a loop device of its own. Create an ext3 filesystem on it then mount it as well as the source image’s partition to different directories. Copy the complete contents of the source filesystem using cp -ax then dismount them. Be sure to give the filesystem the label “/” or update fstab to point to a specific device node. Chroot to the new filesystem’s mountpoint, you may wish to boot it with a livecd to do this because you must now install GRUB to the image’s MBR (and not your host machine’s!). If you are going to try to do it straight from chroot to the full-disk-image loop device (not the one for the partition you are working on) mount -o bind /dev from the host to the new filesystem before chrooting. You may need to do some tinkering with /etc/mtab
Thank you for pointing another ways!
As I’m not an expert in partitioning, working with MBR, I’ve made a new fully-virtualized installation of ClearOS to larger image with the same partioning, used kpartx, mounted two images and copied one to another. And I have fully working GRUB in that way. Just renamed a new image to the old name – and it’s working!
Is there any (step-by-step would be great) guide to make ClearOS installation as in your image?
Thanks again :)
@Serge
Not quite but there is an outdated guide for doing a generic ClearOS install at http://foxpa.ws/2010/04/16/clearos-installation-checklist/
I’ve read that checklist, but totally lost, where is making this installation paravirtualized. Install from ISO is full-virtualized, as I understand.
I’ve installed paravirtualized CentOS from ftp before, everything is ok. But running ClearOS installation from extracted ISO by http on my network ends up with message of missing storage drivers.
It would be great to know how to install it paravirtualized, new release is coming soon :) Sorry, I’m feeling so newby…
Thank you.
If I recall correctly there is a domU kernel on the install cd images under xen/. I had to roll my own initrd though because the scsi modules interfere with the block device backend driver.
Hello , I install it and works fine.I have a question about ClearOS registration. When I try add to my account I received the message:”This system has already been registered with a different name or registered under a different account.”.
Can I find a way to register it ?Thanks in advance
Go to https://lan-ip:81/admin/register.php?Reset=yes twice and start the registration process over.
What meen “twice” When I go to the link , I receive the same message:This system has already been registered with a different name or registered under a different account.
OOOO Thank you I did it again and is`s ok