Atom 330 Fanless server

Wondering what’s all about the title?

Nearly 4 weeks ago I noticed my server was getting slow even having minimal load so I tried to check if my disk was already full which turns out its not. Though my desktop PC and my server is only less than 2 meters apart (besides I can see the server based on my sitting position when I’m in front of my desktop PC) I don’t really go to my server to check it physically besides having there running continously for more than 3 years already. So I installed a cpu temp diagnostic software and I saw the cpu was running between 50-60 and sometimes peaking to 65 degrees Celcius. But I didn’t get my attention because I knew summer season was started already and based on past experiences if its not running in an airconditioned room its a normal temp. Then early this morning something “seriously” happened….

I was about to prepare installing SQL Server 2008 R2 Express Edition (that’s right folks, I’m using the CLEAN and FREE MS SQL Server !! so nothing to worry about Piracy right?), running SQL Server before really bothers me especially eating almost 50% of my entire RAM so I decided to check my server if its all normal both “digitally and physically”. When I was going to put my finger to the CPU heatsink I noticed the temperature inside the server casing was not normal, then at the point I already touched the heatsink I was shocked and suprised- It’s fu@#$%ng HOT!!!, as in super HOT!!!. So I grab a flashlight to see whats going on until I stumbled to saw that the CPU Fan was not working at all!.

I instantly grab the power plug and pulled it off (sorry, I can’t imagine to go to my desktop PC and do some RDP to shutdown the server there). I took my time thinking and wondering how the hell the server survived that long without active (and passive) cooling given the point the room temp average was 30-39 Celcius. I made a conclusion to when the fan started failing and why. This is my 3rd generation and was also the longest running server-without-failure I had, fans have a life too so maybe it was his time to retire. Problem was he didn’t gave me notice (kidding) and really it was all my fault.

So.. what’s this blog all about- The extreme powerness of my Intel Atom 330! @ Php 3,500 pesos when I purchased it 3 years ago (including the Intel board and built-in graphics) it wont let you down.

Besides being the most eco-friendly server I had and the cpu was consuming only 8 watts plus 20 watts on the chipset, it was the most versatile low-power reliable processor I known. Intel should also give a credit to me for being one of the first person to implement a “micro-server” architecture long before they started to marketed it.

For now, I replace the defective CPU fan with “extrenal” active cooling solution. take a look below

My Atom 330 fanless server

My Atom 330 fanless server

If you noticed the small fan at the foreground-rightmost part of the picture that was the original CPU fan installed on the heatsink. Anyway, that will work for now :D

Creating Debian Squeeze Xen image for Cloudmin

4 days since this article was written, Debian Squeeze was officially released (as current STABLE). And one of the things I was excited about was the full support of Xen 4. Upgrading from Lenny to Squeeze was easy as 1,2,3 but after I configured my newly “fresh installed” Squeeze Xen server I was bit surprised that there were no (based on several hours of googling?) “free” downloadable Xen images for Squeeze though I found this site that exactly offers the same images but its not free (thought it was always an OpenSource eih?). So I decided to make my own.

Cloudmin GPL is really awesome! (and of course my all-time favorite Webmin), it saves me a lot of time creating and managing Xen guest servers because I’m not really a hardcore Unix guy you know (btw I ‘m a Windows Sysadmin and .NET developer right?) that is why I stick to GUI as much as possible. Anyway here is the trick to make an instant Squeeze Xen image.

1. You must find a way to get a fresh and clean Squeeze environment to be use as your base image. There were lot of ways to do this, in my case I used my VMware Workstation 7 to setup and make Debian Squeeze (using the debian-6.0.0-xxx-netinst iso file downloaded from debian website).

2. After successfully setup a fresh OS turn it off (be sure to Power Off, do not suspend).

3. Get the VMware Virtual Disk drive file of the Squeeze you created in VMware (just find it in your computer -> or check it in your VMware settings).

4. Copy the file to your Xen/Cloudmin server (in my case the file is Debian Squeeze.vmdk).

5. You must convert the file first to xen compatible format. To do this You will need the qemu-img disk image manipulation tool. You can install using-> apt-get install qemu

6. After successfully installing the tool, run -> qemu-img convert -f vmdk vmware_image.vmdk -O raw xen_image.img

7.  Then rest of it will be in the cloudmin.

8. Login to your Cloudmin using the root account (unless you made a user that has enough privileged to create new images its fine).

9. Go to Cloudmin Settings -> New System Images.

10. Click the Create Image for Xen link at the lower right part just above the Download Selected Images

11.  In the details form, select whole disk as Image file format then Debian Linux in Operating System. Specify the location of the converted image file you made before in the Image Source textbox. You have the option also to put the processed image to the Cloudmin storage location after, but in my case I didn’t selected it cause it gets me trouble looking the file after. Please put the unique ID of the image you wanna create and also DO NOT USE SPACE! You can only do that on the description box below. I highly recommend to compress the file to save disk space.

12.  After reviewing the settings, Click Create button below. It will start processing so be patient.

13. When it successfully finished You can now start creating your new Xen “Squeeze” guest systems. Congrats!

Microsoft RemoteFX VMware and Virtualbox issue

Yesterday I was really excited when I got the RC release of Service Pack 1 of Windows 7 and Windows Server 2008 R2 to test the new feature they added which will be a promising technology called RemoteFX. This new technology will impact those users who always or frequently uses Remote  Desktop to access their system. One of my(and others for sure) current problem with Remote Desktop is the way it communicates with the system being remotely accessed. I won’t explain technically how it works but the thing is with todays technology applications tends to be more and more complex in a way on how it presents its user interface (UI). Example of this is applications built with Windows Presentation Foundation or WPF. Since most of the UI layers built are Double Buffered, when you view the application inside Remote Desktop it shows significant performance degradation because the way it renders comparing the same application when you run it physically on the system it was installed. RemoteFX will eliminate that issue and improved UI responsiveness. In fact, you can play those high graphics games now via Remote Desktop.

The Bad news is… You can’t do RemoteFX on VMware and VirtualBox- FOR SURE!. Answer: RemoteFX needs Windows Virtualization technology called Hyper-V as as its pre-requisite in order for you to install and use it. Since you’re Windows 7/Windows 2008 R2 was running already as “Virtualized”  on top of your existing Host Operating System. Hypervisor could not be passed from to the Host OS to the Guest OS. Put simply, you can’t virtualized another system if you are on top of already virtualized OS.

Well, I know some of people think it was stupid to use RemoteFX in already had “remote desktop” virtual software. But all I can say is how Virtualbox sucks on graphics which is poorer than VMware(I know Virtualbox is faster in terms of CPU,Memory Access and IO Operations but can it run Aero desktop support?I don’t think so). VMware can support Aero graphics but really not as good as it is. Yeah I know VMware uses same protocol as RDP and Virtualbox uses VNC protocol for theirs but don’t you think its time for them to step forward and do something “seriously” about Graphics Virtualization. Not until Intel and AMD release their CPU support for it. By the way, RemoteFX utilizes GPU  power for rendering and not CPU as opposed to the current Remote Desktop. I forgot how great VMware and Virtualbox graphics adapter!

My point is, people who has capable of running multiple virtualized desktop OS for different purposes like for “Testing” could not use this upcoming technology. I can blame both Microsoft and those Virtualization companies for my failure. Why Microsoft depends Hypre-V for the RemoteFX (I know there was technical reasons for it) and why virtualization companies couldn’t improve graphics. We were almost a year or so before using 22 nanometer silicon technology why software was still in a hundreds until now?

Virtualbox RemoteFX

Virtualbox RemoteFX Failed

VMware RemoteFX

VMware RemoteFX Failed