There were a number of changes in the kernel last 6 months, I just
recently did a pull and the lguest port is screwed. I spent part of
today fixing things and catching up, and am now stuck in the first
taskswitch.

Symptoms are odd. It dies in the first call to gotolabel.

But here is the output from some prints:
mmuswitch done return to 0xc01508de
port/proc.c goto label c0470008 (pc c01013b3, sp c0059778)

That pc is init0; the SP is good, previously allocated in newproc().
Next line after this is from lguest program. Lguest says this:
lguest: Bad address 0xc0012c01 (gpte 01008200)

The gpte is the pte that the lguest kernel code found for that address.

Hi,
I have tried to run the lguest port on a 2.6.25 kernel, with not much luck. I guess i was successful in setting the thing up, as

it's fixed for me, the new code is on sources or so I recall. I just
ran it yesterday.

Someone else reported a problem, I don't have time to work on it until
next week.

thanks

ron

note that you really need to run latest now, e.g. 2.6.25 with the
newest lguest port.

ron

could you please clear out how this should work?
I have my own compiled kernel, with the following options:
# zcat /proc/config.gz | 9 grep -i '(lguest|virtio)'
CONFIG_LGUEST_GUEST=y
CONFIG_NET_9P_VIRTIO=m
CONFIG_VIRTIO_BLK=m
CONFIG_VIRTIO_NET=m
CONFIG_VIRTIO_CONSOLE=y
CONFIG_LGUEST=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=m

I run it in the following way:
modprobe lg syscall_vector=64
..../Documentation/lguest/lguest --tunnet 192.168.19.2 --block thx9.img 256 9lguestcpu.elf 'venti=#S/sd00/arenas;bootdisk=local!#S/sd00/fossil;bootargs=local!#S/sd00/fossil'

As I said, the kernel does boot, but fails at the network bits, i think. With kernel 9lguestcpu.elf it says:
#l0: lg: lguest: bad read address 0xc0012044 len 4