From: riku voipio <riku.voipio@iki.fi>
To: "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-user[armel/mips] and debian-rootfs
Date: Mon, 11 Jul 2011 16:45:27 +0300 [thread overview]
Message-ID: <4E1AFE77.8090804@iki.fi> (raw)
In-Reply-To: <201107012052.30363.perezmeyer@gmail.com>
On 07/02/2011 02:52 AM, Lisandro Damián Nicanor Pérez Meyer wrote:
> I have clearly not been verbose enough, so I'll better try to solve that :-)
>
> The problem is the following: once I create a chroot, I copy /usr/bin/qemu-
> mips-static to $CHROOT/usr/bin and then chroot $CHROOT.
>
> Now if I do run touch on any file, I get:
>
> root@debian:/# touch tito
> /usr/bin/touch: setting times of `tito': Level 2 not synchronized
>
> Once again, any pointer to try to debug it would be highly appreciated.
You can run /usr/bin/qemu-mips-static -strace /bin/touch tito to see
what syscall are being run, and what gives the level2 error.
Some basic details should also be provided for good bugreport:
1. version of qemu being used (a release or latest git?)
2. host linux version (2.6.?) and architecture (i386, x86_64, ?)
3. version of debian used to create chroot (lenny. squeeze, sid, ??)
Riku
next prev parent reply other threads:[~2011-07-11 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 17:46 [Qemu-devel] qemu-user[armel/mips] and debian-rootfs Lisandro Damián Nicanor Pérez Meyer
2011-07-01 23:52 ` Lisandro Damián Nicanor Pérez Meyer
2011-07-11 13:45 ` riku voipio [this message]
2011-07-11 14:10 ` Lisandro Damián Nicanor Pérez Meyer
2011-07-11 14:18 ` Riku Voipio
2011-07-12 11:32 ` Wesley W. Terpstra
2011-07-12 13:17 ` Lisandro Damián Nicanor Pérez Meyer
[not found] ` <4E1C58EC.8000002@iki.fi>
2011-07-22 20:59 ` Lisandro Damián Nicanor Pérez Meyer
-- strict thread matches above, loose matches on Subject: below --
2010-05-03 19:30 Kenneth Johansson
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=4E1AFE77.8090804@iki.fi \
--to=riku.voipio@iki.fi \
--cc=perezmeyer@gmail.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).