Hi guys!
I have a problem running latest colinux snapshot (coLinux-20041024.exe) on my XPSP2 machine.
Here's my config:
<?xml version="1.0" encoding="UTF-8"?>
    <block_device alias="hda6" index="0" path="\Device\Harddisk0\Partition5" enabled="true" />
    <block_device alias="hda5" index="1" path="\Device\Harddisk0\Partition4" enabled="true" />
    <block_device alias="hdb6" index="2" path="\Device\Harddisk1\Partition3" enabled="true" />
    <block_device alias="hdb5" index="3" path="\Device\Harddisk1\Partition2" enabled="true" />
    <bootparams>root=/dev/hda6 nousb ro</bootparams>
    <initrd path="initrd.gz" />
    <image path="vmlinux" />
    <memory size="128" />
    <network index="0" type="bridged" name="LAN" mac="00:43:4F:4E:45:30" />
When I first run "colinux-daemon -c fedora.xml" I get this error:
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hdb6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Cannot open root device "hda6" or unknown-block(3,6)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(3,6)
colinux: kernel panic suggests that either you forget to supply a
root= kernel boot paramter or the file / device mapped to the root
file system is not found or inaccessible. Please Check your.
coLinux configuration.
When I re-run this command without any change - it works! I've seen it happening on two machines, both are Athlon XP-based.
This is 99% repeatable on my machine. I managed to successfully run colinux at the first attempt once. It was when I connected through Terminal Services, but I believe this was just a luck. I couldn't repeat this behaviour any more.
Same thing applies to running as a service. I have to start the service, wait for it to die then start it again.
I believe this may be some initrd problem. Any ideas?
BTW. Can you please add file logging to colinux so that the entire console trace can be reviewed later? Or just make the console keep its last content when disconnected.