[uml-devel] Re: [uml-user] Re: Workaround for bug #851759 - SuSE YAST in textmode does not work

["roland" <for_spam@gmx.de>]

hi!

> Known workarounds:
>   * boot with "hwprobe=-sys" (that will make the hardware detect
>     skip the critical test), or
ah - thanks, that seems to work fine. is this just a param, that tells 
yast to skip the detection test? can you tell me,  why i need to pass 
that as a kernel param, not as a Yast param or an environment variable? 
if this doesn`t break or influence other things, i think this is _THE_
workaround for the problem and should be mentioned in the suse-howto or 
in the faq. btw: does YaST2 in gui mode behave the same? don`t have X11-
Yast installed inside my uml root-image - so i cannot test at the moment.

i deliver a text snippet here - perhaps someone could make some correction 
or addition because my english is not so perfect:

------------------

Yast problems within UML
------------------------
Yast is the setup and configuration tool of SuSE-Linux. If you are going 
to use it, you may encounter problems(Yast seems to freeze). It`s not for 
sure, but it is possibly an UML bug (to be fixed). Some modules within YaST 
do automatic hardware detection and there is a routine inside which detects, 
if your linux runs "inside" vmware. This seems to cause the problem. A known 
workaround for this is to add "hwprobe=-sys" to the uml commandline. This 
will make the hardware detection inside Yast skip the critical test. Further 
information can be found here:
http://sourceforge.net/mailarchive/message.php?msg_id=6224097


-----------------


regards
roland




----- Original Message ----- 
From: "Gerd Knorr" <kraxel@bytesex.org>
To: "roland" <for_spam@gmx.de>
Cc: <user-mode-linux-devel@lists.sourceforge.net>; "uml-user" <user-mode-linux-user@lists.sourceforge.net>
Sent: Monday, December 08, 2003 10:59 AM
Subject: [uml-user] Re: Workaround for bug #851759 - SuSE YAST in textmode does not work


> > "list systemProbe = SCR:Read(.probe.system);"
> 
> Oh, that one.  Didn't know yast triggeres this too.  That is actually
> a bug in the uml kernel (there should be a mail in the -devel archive
> ...).  One if the things the hardware probes does is to check whenever
> it runs within vmware or not, and that test hangs (source code below).
> 
> Known workarounds:
>   * boot with "hwprobe=-sys" (that will make the hardware detect
>     skip the critical test), or
>   * don't use skas mode (it hangs in skas mode only for some
>     musterious reason), or
>   * just do something else in another terminal, that will unblock
>     it too (scheduler bug in the uml kernel?).
> 
> > btw: what would be a better solution: asking the suse people to make
> > yast "uml-aware" or fixing those things inside uml?
> 
> IMHO this one is a UML kernel bug.
> 
>   Gerd
> 
> ==============================[ cut here ]==============================
> #define _GNU_SOURCE /* we want memmem() */
> #include <stdio.h>
> #include <stdlib.h>
> #include <string.h>
> #include <unistd.h>
> #include <signal.h>
> 
> #include <sys/types.h>
> #include <sys/wait.h>
> 
> void sigsegv_handler(int signum) { exit(77); }
> 
> int chk_vmware(void)
> {
>   static int is_vmware = -1;
>   int child, status;
> 
>   /* do the check only once */
>   if(is_vmware < 0) {
> 
>     child = fork();
> 
>     if(child == 0) {
>       signal(SIGSEGV, sigsegv_handler);
> 
>       asm(
>         "push %ebx\n"
>         "\tpush %edx\n"
>         "\tpush %eax\n"
>         "\tpush %ecx\n"
>         "\tmov $0x564d5868,%eax\n"
>         "\tmov $0xa,%ecx\n"
>         "\tmov $0x5658,%edx\n"
>         "\tin (%dx),%eax\n"
>         "\tpop %ecx\n"
>         "\tpop %eax\n"
>         "\tpop %edx\n"
>         "\tpop %ebx\n"
>       );
> 
>       _exit(66);
>     }
>     else {
>       if(waitpid(child, &status, 0) == child) {
>         status = WEXITSTATUS(status);
>         if(status == 66) is_vmware = 1;
>         if(status == 77) is_vmware = 0;
>       }
>     }
>   }
>   return is_vmware;
> }
> 
> int main(int argc, char *argv[])
> {
> int rc;
> 
> fprintf(stderr, "check for vmware... ");
> rc = chk_vmware();
> fprintf(stderr, "%s\n", rc ? "yes" : "no");
> return rc;
> }
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> User-mode-linux-user mailing list
> User-mode-linux-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
> 


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel