Community Forum

cyberjorge
cyberjorge
Offline
Resolved
0 votes
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
Monday, January 04 2010, 10:17 AM
Share this post:
Responses (14)
  • Accepted Answer

    Sean
    Sean
    Offline
    Sunday, September 26 2010, 06:00 PM - #Permalink
    Resolved
    0 votes
    The reply is currently minimized Show
  • Accepted Answer

    gergull
    gergull
    Offline
    Saturday, September 04 2010, 11:47 PM - #Permalink
    Resolved
    0 votes
    Hi mat,
    I'm very glad that you got it working.

    Welcome to club! :laugh:

    rgrds,
    Bráulio Gergull
    The reply is currently minimized Show
  • Accepted Answer

    mat
    mat
    Offline
    Saturday, September 04 2010, 07:53 AM - #Permalink
    Resolved
    0 votes
    gergull wrote:

    So I don't think this is the problem.

    Double check if your network setup is correct on XenCenter. Maybe try to remove and recreate your VM's virtual NIC's.

    You can also try tcpdump within the VM to see if you can see any traffic.

    By the way, the first I virtualized ClearOS on XenCenter I followed a guide quite similar to the one you followed. I did succes but it was pain in the ass.

    I try as you suggested. You are right, that was not a problem. As soon as I turn off firewall service my NICs starts working :silly:. But, before I paravirtualize VM, NICs were just Ok, so I guess paravirtualize process somehow reorder my NICs...


    After some testings and trial and errors I found out that it IS possible to install ClearOS paravirtualized on XenServer in one round.

    Following are (VERY) brief directions:

    - Create a new VM using CentOS 5.* template and start the installation. The installation system will boot a Xen PV kernel.

    - When you reach the install media screen there´ll be an error, media not found, or something like that;

    - Ok. Go back ONE screen and select install from FTP

    - You can either install directly from Clearfoundation FTP site (time consuming) or you can copy the contents of the ISO to an FTP server on your LAN and install from there.

    - Done, the installation finishes and you end up with PV ClearOS system!, no conversion needed.

    I also tried this method and it worked. :woohoo:

    Well, after spending lot of time on different forums to figure out how to paravirtualize ClearOS, your tips were like ray of light in dark tunnel :) .

    Gergull thanks for sharing, thanks a lot.
    The reply is currently minimized Show
  • Accepted Answer

    gergull
    gergull
    Offline
    Friday, September 03 2010, 01:30 AM - #Permalink
    Resolved
    0 votes
    Hi mat,

    I've just revised my logs and found that I have the same message, on two PV Clearos systems, both in production and working perfectly.

    - Machine one with three NICs:

    dmesg | grep eth
    netfront: Initialising virtual ethernet driver.
    netfront: device eth0 has copying receive path.
    netfront: device eth1 has copying receive path.
    netfront: device eth2 has copying receive path.

    Machine two with two NICs:

    dmesg | grep eth
    netfront: Initialising virtual ethernet driver.
    netfront: device eth0 has copying receive path.
    netfront: device eth1 has copying receive path.

    Also, accordin to Ian Pratt (Xen developer) this is the default behavior since a long time ago:

    http://lists.xensource.com/archives/html/xen-devel/2006-11/msg01224.html

    So I don't think this is the problem.

    Double check if your network setup is correct on XenCenter. Maybe try to remove and recreate your VM's virtual NIC's.

    You can also try tcpdump within the VM to see if you can see any traffic.

    By the way, the first I virtualized ClearOS on XenCenter I followed a guide quite similar to the one you followed. I did succes but it was pain in the ass.

    After some testings and trial and errors I found out that it IS possible to install ClearOS paravirtualized on XenServer in one round.

    Following are (VERY) brief directions:

    - Create a new VM using CentOS 5.* template and start the installation. The installation system will boot a Xen PV kernel.

    - When you reach the install media screen there´ll be an error, media not found, or something like that;

    - Ok. Go back ONE screen and select install from FTP

    - You can either install directly from Clearfoundation FTP site (time consuming) or you can copy the contents of the ISO to an FTP server on your LAN and install from there.

    - Done, the installation finishes and you end up with PV ClearOS system!, no conversion needed.

    rgrds,
    Bráulio Gergull
    The reply is currently minimized Show
  • Accepted Answer

    mat
    mat
    Offline
    Wednesday, September 01 2010, 05:15 PM - #Permalink
    Resolved
    0 votes
    gergull wrote:
    Hmmm, I see... So you converted a VMware HVM to a Citrix PV, I did it another way.

    No, I skiped 1. step and I installed ClearOS as New VM (Other install media), then installed kernel-xen, configure grub and pygrub...


    lsmod | grep xennet

    [root@system ~]# lsmod | grep xennet
    xennet 29704 0 [permanent]


    [root@system ~]# dmesg | grep eth
    netfront: Initialising virtual ethernet driver.
    netfront: device eth0 has copying receive path.
    netfront: device eth1 has copying receive path.
    netfront: device eth2 has copying receive path.
    The reply is currently minimized Show
  • Accepted Answer

    gergull
    gergull
    Offline
    Wednesday, September 01 2010, 04:30 PM - #Permalink
    Resolved
    0 votes
    Hmmm, I see... So you converted a VMware HVM to a Citrix PV, I did it another way.

    Anyway, what does the following commcand returns to you?

    lsmod | grep xennet
    The reply is currently minimized Show
  • Accepted Answer

    mat
    mat
    Offline
    Wednesday, September 01 2010, 11:23 AM - #Permalink
    Resolved
    0 votes
    gergull wrote:
    I'm running ClearOS paravirtualized under Citrix XenServer 5.5 without issues.


    How did you install ClearOS as paravirtualized VM?
    The reply is currently minimized Show
  • Accepted Answer

    gergull
    gergull
    Offline
    Wednesday, September 01 2010, 02:39 AM - #Permalink
    Resolved
    0 votes
    What kind of NIC problem?

    I'm running ClearOS paravirtualized under Citrix XenServer 5.5 without issues.
    The reply is currently minimized Show
  • Accepted Answer

    mat
    mat
    Offline
    Tuesday, August 31 2010, 11:26 PM - #Permalink
    Resolved
    0 votes
    Jorge, did you found solution for NICs problem? I run into same problem with Xenserver 5.6.0 and ClearOS 5.2.
    The reply is currently minimized Show
  • Accepted Answer

    kfox
    kfox
    Offline
    Thursday, February 18 2010, 11:09 PM - #Permalink
    Resolved
    0 votes
    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 :)
    The reply is currently minimized Show
Your Reply