* [Qemu-devel] root userid remapping? ... no UID / GID variables set in NFS root?
@ 2007-05-31 22:06 Christopher Friedt
2007-05-31 22:16 ` Mark Glines
2007-06-01 5:48 ` Rob Landley
0 siblings, 2 replies; 3+ messages in thread
From: Christopher Friedt @ 2007-05-31 22:06 UTC (permalink / raw)
To: qemu-devel
Hi everyone,
I've just gotten qemu emulating an arm system on my laptop, which I'm
hoping to use for cross-compilation. I don't have a disk image to use
(is there any way to create a disk image from a directory tree??), so
I'm using NFS instead.
The strange thing is, is that although I specify no_root_squash in my
/etc/exports (and I've been using NFS for quite a long time successfully
with other machines), only when I'm using Qemu does the user id of the
'init' process [0] get remapped to some completely absurd value of
4294967295.
Has anyone heard of this happening before?
Thanks in advance for any and all responses.
~/Chris
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] root userid remapping? ... no UID / GID variables set in NFS root?
2007-05-31 22:06 [Qemu-devel] root userid remapping? ... no UID / GID variables set in NFS root? Christopher Friedt
@ 2007-05-31 22:16 ` Mark Glines
2007-06-01 5:48 ` Rob Landley
1 sibling, 0 replies; 3+ messages in thread
From: Mark Glines @ 2007-05-31 22:16 UTC (permalink / raw)
To: cfriedt; +Cc: qemu-devel
On Fri, 01 Jun 2007 00:06:43 +0200
Christopher Friedt <cfriedt@visible-assets.com> wrote:
> (is there any way to create a disk image from a directory tree??)
http://www.hohnstaedt.de/e2fsimage/
If you use this, you will get a raw e2fs filesystem image. It will not
have a partition table, which means you will want to mount it directly
as /dev/hda (or /dev/sda), not /dev/hda1 (or /dev/sda1).
> The strange thing is, is that although I specify no_root_squash in my
> /etc/exports (and I've been using NFS for quite a long time
> successfully with other machines), only when I'm using Qemu does the
> user id of the 'init' process [0] get remapped to some completely
> absurd value of 4294967295.
4294967295 is decimal for 0xffffffff, also known as -1. Maybe some
kind of bug?
Mark
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] root userid remapping? ... no UID / GID variables set in NFS root?
2007-05-31 22:06 [Qemu-devel] root userid remapping? ... no UID / GID variables set in NFS root? Christopher Friedt
2007-05-31 22:16 ` Mark Glines
@ 2007-06-01 5:48 ` Rob Landley
1 sibling, 0 replies; 3+ messages in thread
From: Rob Landley @ 2007-06-01 5:48 UTC (permalink / raw)
To: qemu-devel; +Cc: Christopher Friedt
On Thursday 31 May 2007 6:06 pm, Christopher Friedt wrote:
> Hi everyone,
>
> I've just gotten qemu emulating an arm system on my laptop, which I'm
> hoping to use for cross-compilation. I don't have a disk image to use
> (is there any way to create a disk image from a directory tree??), so
> I'm using NFS instead.
>
> The strange thing is, is that although I specify no_root_squash in my
> /etc/exports (and I've been using NFS for quite a long time successfully
> with other machines), only when I'm using Qemu does the user id of the
> 'init' process [0] get remapped to some completely absurd value of
> 4294967295.
You disabled CONFIG_UID16 in the EMBEDDED menu, so you don't have the legacy
system calls to query 16 bit user ids, but your program is using the old ones
rather than the new ones. So the attempt to make said syscall is
returning -EPERM, I.E. -1.
Nothing to do with qemu, this is your kernel .config. I'm guessing you built
a different kernel for qemu than for your host system?
Rob
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-06-01 5:48 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-31 22:06 [Qemu-devel] root userid remapping? ... no UID / GID variables set in NFS root? Christopher Friedt
2007-05-31 22:16 ` Mark Glines
2007-06-01 5:48 ` Rob Landley
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).