I tried compiling a 2.6.20 plain vanilla kernel for my host machine, and
running the command suggested by R. L. Nevot
iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -d 0.0.0.0/0 \
-j MASQUERADE
This let me get out of my host machine. Who knows, maybe I forgot to
remove the iptables --policy
On Thu, Apr 19, 2007 at 09:13:46PM -0500, Gregory Smith wrote:
> The primary problem I face with your patch is that the timer ticks are
> not interrupting at even intervals. While things /do/ work the way we
> discussed, the clock was slipping all over the place. Sleeps inside
> the VM were in sync
Hi Jeff,
Thanks again for the patch. I ended up doing something slightly
different, but reading through the code and looking at your changes
helped me arrive at a solution.
The primary problem I face with your patch is that the timer ticks are
not interrupting at even intervals. While things /do/
Yes, that seems to do the trick. Thanks very much!
Greg
On Thu, Apr 19, 2007 at 01:43:19PM -0400, Jeff Dike wrote:
> Try the patch below. I had to totally disassociate the UML's
> gettimeofday from the host's.
>
> Jeff
>
> --
> Work email - jdike at linux dot int
Try the patch below. I had to totally disassociate the UML's
gettimeofday from the host's.
Jeff
--
Work email - jdike at linux dot intel dot com
Index: linux-2.6.21-mm/arch/um/kernel/time.c
===
---
On Wed, Apr 18, 2007 at 11:59:52PM -0500, Gregory Smith wrote:
> Thus, from a UML-internal perspective, the process only slept for
> about a second, but it thinks it has slept at least 10.
It looks like jiffies doesn't really control anything any more. The
timers are driven from xtime, which UML
On Wed, Apr 18, 2007 at 11:59:52PM -0500, Gregory Smith wrote:
> Thus, from a UML-internal perspective, the process only slept for
> about a second, but it thinks it has slept at least 10.
You're right. I can start a sleep, pause UML, and if I unpause it
before the sleep is supposed to expire, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Danett song wrote:
> Hi,
>
> I tryed UML for the first time, and got impressed that
> the image in the official site doesn't work well, but
> your Debian root filesystem work perfectly.
This one is for Jeff (CCed via list).
Maybe the website should
