>> Can you specify exactly when does X crash. You must be configuring your
>> network using ifconfig i suppose, so please specify the details of the time
>> and conditions under which X crashes. As such the X server is also built on
>> the server/client model so may be, just may be it is due to some network
>> conflict.
> The UI screen starts, then the crash occurs with a bunch of messages (not
> line-broken like those leading to X starting) "X must of crashed" and such.
> After a bunch of these, I can log on to the console. Next time I will try
> luther/luther and see.

X keeps a log of things,
you can see why X crashes by typing this command (as luther):

$ cat /var/log/X/Xorg.0.log |grep EE


>
>>I have successfully run dyne2.4 on VirtualBox and qemu on my NVidia
>>AMD 64 1GB RAM. I have had problems on other reasonable hardware,
>>especially those with less than 512MB of memory.
> I have 512mb of memory. As I said, with limited NAT networking, I have run
> dyne2.4 just fine in vbox. Since qemu starts wtih more network options, I get
> the X crash. An AMD64 is a different beast. Either way, one should not need
> 1gig to play with this stuff.
>
>

There could be a problem with the network setup; Each network interface
(whether virtual or physical) has an IP address, each interface should
have its own IP range. You can see the IP addresses like this:

$ ifconfig

If you want virtual box to be fully integrated in the network (to access
all the hosts and other virtual machines) you must setup a bridge.