RE: [uml-user] NFS hanging badly

[Mooneer S. <mo...@ea...>]

It could be possible that you have not allocated enough RAM
to the UML process. By default, 16MB is allocated. I generally
allocate 64MB at the very least for each UML, and leave 128MB of
RAM for the host system.

Even with that, on my system ICMP pings sometimes freeze up for
a few seconds and then resume, and ping would show 0% loss. It
might be helpful to change the wait period between pings.

-----Original Message-----
From: use...@li...
[mailto:use...@li...]On Behalf Of
Rodrigo Barbosa (aka morcego)
Sent: Sunday, December 03, 2000 9:18 AM
To: Use...@li...
Subject: Re: [uml-user] NFS hanging badly


Well, I managed to make uml's eth0 interface work. I also managed
(using proxyarp) to make it looks just like any other machine on our
network.

The problem that still persist (with umn and eth0 both), is the high
package loosing.

Take a look at it (10.0.23.129 is my uml box. Morcego is the host):

morcego [/root] # ping 10.0.23.129
PING 10.0.23.129 (10.0.23.129): 56 octets data
64 octets from 10.0.23.129: icmp_seq=0 ttl=255 time=6.8 ms
64 octets from 10.0.23.129: icmp_seq=1 ttl=255 time=6.2 ms
64 octets from 10.0.23.129: icmp_seq=2 ttl=255 time=5.9 ms
64 octets from 10.0.23.129: icmp_seq=3 ttl=255 time=6.1 ms
64 octets from 10.0.23.129: icmp_seq=4 ttl=255 time=6.0 ms
64 octets from 10.0.23.129: icmp_seq=5 ttl=255 time=6.6 ms
64 octets from 10.0.23.129: icmp_seq=10 ttl=255 time=6.0 ms
64 octets from 10.0.23.129: icmp_seq=20 ttl=255 time=6.1 ms
64 octets from 10.0.23.129: icmp_seq=30 ttl=255 time=1.8 ms

uml is running as root (# ./linux), and the um_eth_net_util is running with
'nice -n -1', having high priority over anything else (almost. Lets not
forget init :-)).

I simply can't figure what is going wrong.

Any clues ?