On Sun, 24 Aug 2008 23:58:21 -0500
"Alex Lee" <[EMAIL PROTECTED]> wrote:
> On Sun, Aug 24, 2008 at 11:32 PM, ron minnich <[EMAIL PROTECTED]> wrote:
> [snip]
> >> lguestnetwork is
> >
> > see this line? It's a variable read in /rc/bin/cpurc. You can check
> > that script and see how it can be set so that networking is a little
Hello,
I have gotten the lguest port working on the 2.6.25.0 kernel, it works mighty
fine here.
The load issue for me is only on plan9, on the host I can see with 'top' that
the lguest guest isn't consuming all the cpu, so this might ust be a plan9
problem. I have also seen quite a few messages in /sys/log/cron i get a lot of
lines saying:
$sysname Aug 25 08:31:14 time went backward
I found routed networking to be the simplest, nat gives me the creeps.
So here is my way to start the lguest guest, I hope it will be helpful:
====snip
#!/bin/bash
set -x
/root/bin/lguest --tunnet=$1 --block=/dev/mirror/plan9cpu \
512 /home/johnny/9lguestcpu.2.6.25.elf
'bootargs=local!#S/sd00/fossil;sysname=9soul;bootdisk=local!#S/sd00/fossil'
sleep 10
ip route add $3 via $1 dev $2
ip route del 192.168.0.0/24 dev $2
echo 1 > /proc/sys/net/ipv4/conf/$2/proxy_arp
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
====snip
$1 is the host ip, $2 is the tap interface the guest will use, and $3 is the ip
the guest will have. This method only works for static networking, also you
will need to install the iproute2 utilities. These command also assume the your
net is 192.168.0.0 netmask 255.255.255.0, change that to whatever suits you.
Cheers,
John
> > better. More I do not recall and the machine is not nearby ...
> >
> [snip]
> >> 2. I can ping from the host machine to the lguest interface
> >> (192.168.19.2), but when I try to connect with drawterm the connection
> >> is refused.
> >
> > Try restarting the listen? that's an odd one. If you telnet to the
> > port from the host to the guest what do you see?
>
> Ah, I see now. I added "lguestnetwork=NAT" to parameters in RUNLGUEST,
> and now both networking and drawterm are working great!
>
> >> 3. lguest always runs at full CPU. How can I figure out why this is
> >> happening? (I don't feel comfortable running lguest for more than a
> >> few minutes at a time -- the laptop gets pretty hot.)
> >
> > hmm. I have not seen this one. Again, not sure why this is happening.
> > But the halt
> > may not be working. Possibly the API has changed -- not sure.
> >
> > ron
>
> Let me know if there's any information that I can provide to help with
> this. Many thanks for all the hard work that you've put into doing
> this port.
>
> Best,
> Alex
>
>
