ClearFoundation

Hi!

Congratulations on the release of ClearOS 5.1 Final. Hope to see more improvements on the coming releases.

My installation is working great with no problems, but it installed as fully virtualized in Citrix Xenserver (Install Other Media) instead of the more recommended paravirtualized installation. And I notice extreme slowdown even under minor I/O.

I tried installing ClearOS as paravirtualized using CentOS 5.3 template and even setup a local NFS install server just to make sure I tried or modes of installation. But nothing worked, when installing in CentOS 5.3 template with proper path to the install server I get an INVALID_SOURCE error, Unable to access required file in the specified repository: file///tmp/nfs-repox0_a_b/images/xen/vmlinuz.

My question is, isn't ClearOS based in CentOS 5.4? And is the file specified above or any related files are heavily modified that cause it to fail?

Anyone has tried Clear OS as VM Citrix Xenserver? And if no one yet, can someone test it? What OS template or installation procedure do you recommend that will work well as paravirtualized?

I've been searching for a long time for this solution and will appreciate all your help so I can put ClearOS in production already.

Thank you very much in advance!
Jorge

Anyone seen this post?

I was able to paravirtualize ClearOS in Xen already following this guide:
itproctology.blogspot.com/2009/06/pv-ena...vm-on-xenserver.html

Based on the guide, I need to install the kernel-xen but I immediately get error saying "download3.clearfoundation.com/clearos/en...ise/5.1/kernels/.... is unavailable" it tried another mirror and was able to install successfully and continue with the process.

All went fine and was able to install the guest utilities successfully but the main problem is I can't connect on all NICs. Also the Graphical Console is no longer available. I guess xen is assuming the installation as normal CentOS 5.4. Can there be some conflicts? How will I fix these?

Result of ifconfig -a: http://pastebin.com/m74a5f9e8
Content of XenServer config: http://pastebin.com/m2bfd2d39

Thanks in advance!
Jorge

I think I just bumped to a bug here... https://bugzilla.redhat.com/show_bug.cgi?id=469616

Any suggestions from our developers?

Thanks!
Jorge

No response yet after 4 days?

I found this in the clarkconnect website, ccforums.clearfoundation.com/showflat.ph...mp;page=2#Post104755

But it's a bit outdated and I no longer apply for ClearOS 5.1, is there an updated guide or help on this?

I'm trying to signup in the clarkconnect forum so I can contact the poster "zylantha" but can't get in. Can somebody, show this post for any help?

I badly need some help to get my ClearOS woking already. Please help.....

TIA!
Jorge

Got the networking bit working

Brief Summary:
1. Started installation directly as PVM by booting with the xen kernel image and ramdisk image present in the installer CD. Created a sparse image.
2. Had to do an FTP install from the on-line mirrors as the CD drives would not be recognised, nor does the CD-ROM contain the structure required for a local FTP install.
3. Post install mounted the sparse image and created soft-links vmlinuz-xen and initrd-xen and modified menu.1st accordingly.
4. Booted in and recreated initrd as per old.nabble.com/Booting-DomU-gives-XENBUS-errors-td17714307.html
5. Recreated ifcfg-ethx scripts for the interfaces and restarted network. The interfaces come alive.
6. wget and rpm -ivh -f kernel-xen rpm again. This takes care of proper initrd with all the requisite modules inclusive of xennet and xenblk
7. Modified the vm conf script to use pygrub as the bootloader. Reboot and all's well.

This would not have been possible w/o the links posted by you. Thanks to you and their authors.

TIP: Used convirt to assist in the installation. Can do w/o it also.

Will try to chronicle the entire process in detail w.r.t. opensuse dom0 very soon once the test runs are over.

The display needs to be fixed as yet but is not a major bother as remote access works.

WOW! Shrenik, Bravo!

Congratulations on your milestone and thank you for taking the time to dig in to this and posting back. Hopefully someone from the ClearOS Dev Team might be able to give some more input.

Will be waiting for your detailed instructions on this. You might want to have a version for XenServer too.

Nothing's stopping you from using a completely different kernel to boot ClearOS - I've been running PV'd CC images with a domU kernel built for my gentoo platforms for almost two years (several production routers and standalones). This has given me some problems where tools have been modified to work with redhat and/or clear kernel patches but nothing that can't be quickly replaced. My problem with any of CC/Clear's attempts at xen support is the binary kernels they ship either mismatch my PAE support or any number of unclearable obstacles. I also can't stand dealing with initrds which is just the redhattian way of making things easy on people. If you build your own kernels it's entirely superfluity and you can do without the whole mess. There is no shame in a monolithic domU kernel either, you don't have a million possible drivers to run through and it saves you the trouble of copying the modules from the "foreign" kernel into your Clear image or caring what version your domU modutils supports.

If someone could point me to the actual sources Clear is using to build their new xen kernel they'd be my angel for a day

Jorge, did you found solution for NICs problem? I run into same problem with Xenserver 5.6.0 and ClearOS 5.2.

What kind of NIC problem?

I'm running ClearOS paravirtualized under Citrix XenServer 5.5 without issues.

Well, I follow this guide itproctology.blogspot.com/2009/06/pv-ena...vm-on-xenserver.html to make ClearOS paravirtualized, but when I run ClearOS paravirtualized I can't use NICs. The NICs are present and detected by the VM but can't get an IP which is working well before doing the PV guide.

dmesg shows this