Archive for June, 2007

Converting Parallels Machines to VMWare Fusion, and KQEMU on OSX attempts

I’m following these instructions to convert a Parallels machine into a VMWare Fusion Machine. So far so good.

I’m doing a XP Home machine now, planning to try a FreeBSD machine too, but I’m not sure if that will work. No, doesn’t look like the conversion of FreeBSD will work. Too bad.

Also, you have to re-activate Windows XP Home once you convert the machine, and since Windows limits the amount of times you can re-activate a Windows XP license, I’m not going to at this time. As I keep saying, I will move to QEMU for good once KQEMU is ported to OS X.

Just for the heck of it I tried compiling KQEMU on my Macbook, but no luck:

make -C common all
gcc -Wall -O2 -Werror -g -D__KERNEL__ -I.. -o genoffsets genoffsets.c
./genoffsets > monitor_def.h
gcc -D__KERNEL__ -nostdinc -iwithprefix include -I. -I.. -D__ASSEMBLY__ -c -o i386/nexus_asm.o i386/nexus_asm.S
i386/nexus_asm.S:27:Unknown pseudo-op: .global
i386/nexus_asm.S:27:Rest of line ignored. 1st junk character valued 95 (_).
i386/nexus_asm.S:86:operands given don't match any known 386 instruction
i386/nexus_asm.S:117:bad register name ('%dr7')
i386/nexus_asm.S:146:bad register name ('%dr7')
i386/nexus_asm.S:170:operands given don't match any known 386 instruction
make[1]: *** [i386/nexus_asm.o] Error 1
make: *** [kqemu.o] Error 2

Well this is quite interesting:

Kqemu for Darwin

Its from March of 2007, three months ago, so even though very little is said about it, it appears to be the real deal. I was able to get it to load, but I’m not sure if its getting used by Q.

Kernel Module unloaded:
1:40 to boot debian to login prompt.

root# ./load_kqemu.sh
kextload: extension kqemu.kext appears to be valid
kextload: notice: extension kqemu.kext has debug properties set
kextload: loading extension kqemu.kext
kextload: kqemu.kext loaded successfully
kextload: loading personalities named:
kextload: kqemu
kextload: sending 1 personality to the kernel
kextload: matching started for kqemu.kext

And it took 1:37 to do the same thing after the kernel module was loaded. Hmmm. When I try to pass a qemu argument to use kqemu, I get an error saying -kernel-kqemu is not a valid option.

I was just checking out the OpenSUSE kqemu qemu docs and found a cool trick for qemu: you can access a vm monitor by changing consoles by typing alt-ctrl-2 all at once.

20070701_kqemu-not-compiled.jpg

I am able to compile Q with the kqemu option enabled, but then when I try to run anything, it doesn’t work at all. :-(

I’m doing this by editing the qemu/configure file to have kqemu=”yes”, when following the Downloading and compiling Q instructions given by the Q developers. The qemu folder gets copied to tmp/qemu in the build_i386.sh process.

What does this do:

20070701_kqemuclient.jpg This is all so surprising to me how little documentation or even available conversation there is on this stuff. This is really good stuff! I wonder if more has been done, but it just isn’t available or documented.

With this client, I am able to connect, get the version, and run the three test. I’m not able to init or exec. I did a little more writing about this over at OSXCentral.com.

The new Q icons look awesome:
20070701_q-icons.jpg

Very cool - I just realized I can use a Parallels drive with Q if it is in the raw format. I have to change the extension to .img, but that’s fine with me. Yes its slower on a Mac but at least it will be portable to other computers which can use kqemu. :-)

LTSP: PXE-E32 TFTP open timeout

I’m trying to setup Ubuntu ltsp. No luck, dhcp gives ip but then the tftp server never serves the goodies. Here’s the strace:


Looks like it finds the pxelinux.0 file OK, but then something funky happens. Not sure what though.

Cool! I got it to work. Turns out there was two tftpd programs running, so I stopped /etc/init.d/openbsd-inetd and commented out the tftp server anyway. I then had to manually stop the processes. I then started the tftpd-hpa daemon and it booted!

It looks terrible on my screen though. Reminds me of how the Aopen screen looked.

The cool thing is that I also booted off a t5125, and the screen looked fine. I bet I will be able to boot off of a wide variety of devices. I’d also like to figure out how to do network installs using PXE boot. I gotta check out this Debian FAI - Fully Automatic Installation.

The Thecus is back in ACTION!




Wow, I finally got the Thecus running debian again. :-)

Here’s the commands I used in redboot to load the initrd and kernel via tftp.

ip_address -l 192.168.0.56 
ip_address -h 192.168.0.2 
load -r initrd -b 0x00800000
load -r vmlinuz -b 0x00200000
exec -c "console=ttyS0,115200 root=/dev/ram0 initrd=0xa0800000,42M mem=128M@0xa0000000"





openssl enc -d -des -in n2100.bin -out upgrade.tar.gz -K 7A9816A4C275D557 -iv 0 -nosalt -nopad

I had to extract the initrd and the vmlinuz from the n2100.bin that debian provided because my system was all messed up. The new debian installer is great - skips the bad hostname part, and everything went smoothly.

This time I’m only running with one disk, and the power consumption is still at 18 watts. What’s up with that? And iperf is only able to get 120 Mbits / second, even when the link is 1000Mbits. Oh well, at least its running now.

Frankenstein City

I’ve been building a lot of frankenstein machines lately - the kinds where you patch together pieces from different computers, with varying results. Here’s two I built recently:

t5135 with internal Belkin USB nic

This one didn’t turn out so hot:

snb10679.JPG

snb10682.JPG

20070628_hp-belkin-nic.jpg

PC Chips V21G VIA C7, APEX Case, Morex Power Supply

This one turned out awesome, and didn’t require and damaging modifications.

snb10699.JPG

The power supply is mounted to the back panel, and the power adapter even fit in the top left hand, and I used a few pieces of double sided tape to keep it in place. This system has an onboard nic (VIA Rhine), two intel gigE low profile cards, a VIA C7 processor, 512MB of RAM, and a 32 disk-on-module running m0n0wall. It only uses about 24 watts of power, and we’re currently using it as our production bridge. I’m really happy with this setup, and may build more like it!