lguest launch hangs on "Marking TSC..."

_______________________________________________
Lguest mailing list
Lguest@...
https://lists.ozlabs.org/listinfo/lguest

Lguest on i5

_______________________________________________
Lguest mailing list
Lguest@...
https://lists.ozlabs.org/listinfo/lguest

problem on 3.0.13: unhandled trap 13 at 0x1371e36 (0x0)

OK, it's been a while ... I"ve built lguest on my chromebook. It's an
i686 kernel of course.

The location is at 1371e36 which I realize means nothing but ... it's
in default_entry. It also looks to me like it's long before virtual
addressing is turned on. Things have changed in the kernel in this
particular area so I am not as familiar with it as I was (and soon
will be, again ...)

Could this be some simple screwup on configuration or something I have
to tell lguest somehow?

The command is simple:

lguest 64m vmlinux

I realize I need a root but I want to see it get far enough to
explode. I like fireworks.

thanks for any good hints ...

And, yes, config is set as in the doc, with CONFIG_PARAVIRT=y,
CONFIG_LGUEST_GUEST=y, ..EXPERIMENTAL=y, HIGHMEM64G=n, and so on.

I think I'm doing something dumb, just not sure what ... memory fails me.

thanks

ron

Re: lguest for ARM

_______________________________________________
Lguest mailing list
Lguest@...
https://lists.ozlabs.org/listinfo/lguest

Re: lguest for ARM

On Mon, 5 Dec 2011 10:38:58 -0500, William Cunningham
<wcunning@...> wrote:
> It would appear that the /rusty/linux-2.6.git repository was never restored
> after the kernel.org failure, and I was unable to find that particular
> repo, or any other kernel repo containing that branch in Rusty's public
> github/gitorious/whatever repos. Does someone still have a copy that could
> get reposted somewhere?

Well, here's the patch which LiMing sent me, which was what I applied to
make the git tree.  It was never properly cleaned up, though if you're
interested that would be a superb thing to do!

Cheers,
Rusty.
PS. Sorry for the attachme,t; it's rather big.

_______________________________________________
Lguest mailing list
Lguest@...
https://lists.ozlabs.org/listinfo/lguest

lguest for ARM

_______________________________________________
Lguest mailing list
Lguest@...
https://lists.ozlabs.org/listinfo/lguest

Documentation/lguest in kernel 3.0

Hi All,

Is there a reason why the Documentation directrory does not contain the 
"lguest" directory (with the launcher program)?

Will the launcher from previouse releases would work?

Regards,

Eviatar

Re: Lguest on x86_64

On Sat, 2011-10-08 at 23:45 +0300, Daniel Baluta wrote:
> +Steven
> 
> On Thu, Oct 6, 2011 at 6:05 PM, Daniel Baluta
<daniel.baluta@...> wrote:
> > Hello,
> >
> > What is the status of lguest on x86_64 ?
> >
> > I know that 3 years ago, there was an effort to port
> > lguest on this architecture, but isn't very clear what
> > happened since then.
> >
> >

The developers (myself and Glauber) were moved out of the virt
departments and it became a side project that neither of us had time to
work on. I still have the source repositories, and with KVM here, we
never really got much push to pursue it.

As a hobby I thought about getting it to work again (it was functional),
but I just don't have the time.

Are people actually interested in it? I'm willing to help others get it
going again (to a limited extent).

-- Steve

Lguest on x86_64

Hello,

What is the status of lguest on x86_64 ?

I know that 3 years ago, there was an effort to port
lguest on this architecture, but isn't very clear what
happened since then.

thanks,
Daniel.

Re: question about lguest inside kvm

On Tue, 26 Jul 2011 14:36:57 +0300, Stefanos Geraggelos
<sgerag@...> wrote:
> >> the output was pv_info: kvm. Finally, I tried to comment out the
> >> return -EPERM, the module loaded but when I ran ./lguest it printed a
> >> trap 13 (or something). So, I think it indeed does Tricky Stuff :) and
> >> I though that is wise to drop you an email before I try to dig inside
> >> for the trap thing. Can you point me a solution to that?
> >>
> >> Thanks and sorry for any inconvenience!
> > 
> > Hi Stefanos!
> > 
> >     Fascinating... I think it *should* be OK to run inside KVM, as the
> > parts that kvm paravirt cover do not effect lguest.
> > 
> > Can you send your .config file?
> > 
> > Thanks,
> > Rusty.
> 
> yeap, here it is (attached).

OK.  Two problems; one is related to KVM, another is related to
CONFIG_RELOCATABLE=y.

These three patches fix it for me on your config; do they work for you?

Cheers,
Rusty.

From: Rusty Russell <rusty@...>
Subject: lguest: Allow running under paravirt-enabled KVM.

We actually can run under KVM, as it doesn't paravirtualize anything we
need to use; reduce the check to checking we are the normal ringlevel.

Reported-by: Stefanos Geraggelos <sgerag@...>
Signed-off-by: Rusty Russell <rusty@...># HG changeset patch
---
 drivers/lguest/core.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/lguest/core.c b/drivers/lguest/core.c
--- a/drivers/lguest/core.c
+++ b/drivers/lguest/core.c
@@ -313,7 +313,7 @@ static int __init init(void)
 	int err;

 	/* Lguest can't run under Xen, VMI or itself.  It does Tricky Stuff. */
-	if (paravirt_enabled()) {
+	if (get_kernel_rpl() != 0) {
 		printk("lguest is afraid of being a guest\n");
 		return -EPERM;
 	}

From: Rusty Russell <rusty@...>
Subject: lguest: don't allow KVM-detection cpuid.

Host might be running under KVM, but we shouldn't allow Guest to think it
can use KVM hypercalls (it can't, and it will embarrass itself if it tries).

Signed-off-by: Rusty Russell <rusty@...>
---
 arch/x86/lguest/boot.c |   10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/arch/x86/lguest/boot.c b/arch/x86/lguest/boot.c
--- a/arch/x86/lguest/boot.c
+++ b/arch/x86/lguest/boot.c
@@ -70,6 +70,7 @@
 #include <asm/i387.h>
 #include <asm/stackprotector.h>
 #include <asm/reboot.h>		/* for struct machine_ops */
+#include <asm/kvm_para.h>

 /*G:010
  * Welcome to the Guest!
@@ -455,6 +456,15 @@ static void lguest_cpuid(unsigned int *a
 		*ax &= 0xFFFFF0FF;
 		*ax |= 0x00000500;
 		break;
+
+	/*
+	 * This is used to detect if we're running under KVM.  We might be,
+	 * but that's a Host matter, not us.  So say we're not.
+	 */
+	case KVM_CPUID_SIGNATURE:
+		*bx = *cx = *dx = 0;
+		break;
+
 	/*
 	 * 0x80000000 returns the highest Extended Function, so we futureproof
 	 * like we do above by limiting it to known fields.

From: Rusty Russell <rusty@...>
Subject: lguest: allow booting guest with CONFIG_RELOCATABLE=y

The CONFIG_RELOCATABLE code tries to align the unpack destination to
the value of 'kernel_alignment' in the setup_hdr.  If that's 0, it
tries to unpack to address 0, which in fact causes the gunzip code
to call 'error("Out of memory while allocating output buffer")'.

The bootloader (ie. the lguest Launcher in this case) should be doing
setting this field; the normal bzImage is 16M, we can use the same.

Reported-by: Stefanos Geraggelos <sgerag@...>
Signed-off-by: Rusty Russell <rusty@...>
---
 Documentation/virtual/lguest/lguest.c |    3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/virtual/lguest/lguest.c b/Documentation/virtual/lguest/lguest.c
--- a/Documentation/virtual/lguest/lguest.c
+++ b/Documentation/virtual/lguest/lguest.c
@@ -1996,6 +1996,9 @@ int main(int argc, char *argv[])
 	/* We use a simple helper to copy the arguments separated by spaces. */
 	concat((char *)(boot + 1), argv+optind+2);

+	/* Set kernel alignment to 16M (CONFIG_PHYSICAL_ALIGN) */
+	boot->hdr.kernel_alignment = 0x1000000;
+
 	/* Boot protocol version: 2.07 supports the fields for lguest. */
 	boot->hdr.version = 0x207;

Current state of the lguest arm patch

_______________________________________________
Lguest mailing list
Lguest@...
https://lists.ozlabs.org/listinfo/lguest