linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-devel] Something wrong with booting the UML in new kernel
Date: Tue, 23 Jan 2007 09:00:09 +0100	[thread overview]
Message-ID: <200701230900.10008.blaisorblade@yahoo.it> (raw)
In-Reply-To: <420863.17264.qm@web15301.mail.cnb.yahoo.com>

On Sunday 21 January 2007 03:34, An Ching wrote:
> Hi,
>
> I had recompiled my host kernel with setting the EXT2_FS_SECURITY and
> EXT3_FS_SECURITY in filesystem configuration. My UML is OK before doing
> this, but now I can not boot the UML in the new-recompiled kernel. It just
> went to the step...
>
> [root@RH9 linux-2.6.17]# ./linux root=/dev/sda1 rootflags=/
> rootfstype=hostfs ro con0=fd:0,fd;1 init/bin/sh -l Checking that ptrace can
> change system call numbers...OK
> Checking syscall emulation patch for ptrace...OK
> Checking advanced syscall emulation patch for ptrace...OK
> Checking for tmpfs mount on /dev/shm...OK
> Checking PROT_EXEC mmap in /dev/shm/...OK
> Checking for the skas3 patch in the host:
>   - /proc/mm...not found
>   - PTRACE_FAULTINFO...not found
>   - PTRACE_LDT...not found
> UML running in SKAS0 mode
> Checking that ptrace can change system call numbers...OK
> Checking syscall emulation patch for ptrace...OK
> Checking advanced syscall emulation patch for ptrace...OK
>
> Just down to this step, and not any response next...
>
> I guessed maybe the kernel of UML didn't support the XATTR  of filesystem
> and then I reconfigured the UML and set EXT2_XATTR, EXT2_FS_SECURITY,
> EXT3_XATTR, EXT3_FS_SECURITY to "Y".
This wouldn't matter, since UML is using hostfs (which does not support XATTR 
at all, to my knowledge) and not ext2/ext3.
> But after I recompiled the kernel of 
> UML and run it,  I  was given the same  message mentioned above.
>
> What should do  next?   Could anybody  give me some advices?

There are few reasons usually for using hostfs, normally using a dedicated 
root_fs is a better solution. And using hostfs on your / can cause trouble to 
both your host and your guest (well, if you boot with init=/bin/sh then there 
are less problems).
-- 
Inform me of my mistakes, so I can add them to my list!
Paolo Giarrusso, aka Blaisorblade
http://www.user-mode-linux.org/~blaisorblade
Chiacchiera con i tuoi amici in tempo reale! 
 http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2007-01-23  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21  2:34 [uml-devel] Something wrong with booting the UML in new kernel An Ching
2007-01-23  8:00 ` Blaisorblade [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200701230900.10008.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox