Re: [Qemu-devel] qemu-user[armel/mips] and debian-rootfs
On Mar 12 Jul 2011 11:23:40 riku voipio escribió: Hi Wesley [snip] For whatever reason I was unable to apply your patches directly, so I had to recreate them. I've rolled your patches to: http://git.linaro.org/gitweb?p=people/rikuvoipio/qemu.git;a=shortlog;h=refs /heads/linux-user-for-upstream I have tested this by getting the source code, creating a Debian package as if it were a NMU of the last version in Sid (although with different sources, but fair enough for testing I guess) and I can say it works :-) I have both been able to setup a rootfs for my Ubiquiti RouterStation Pro and also compiled some qt stuff in a chroot in my desktop :-) Kinds regards, Lisandro. -- The box said 'Requires Windows 95 or better'. So I installed Linux. Anonymous Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: [Qemu-devel] qemu-user[armel/mips] and debian-rootfs
2011/7/11 Riku Voipio riku.voi...@iki.fi: On Mon, Jul 11, 2011 at 11:10:50AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: Thanks Riku! This bug has already been solved by Wesley Terpstra: http://lists.nongnu.org/archive/html/qemu-devel/2011-07/msg00313.html Ok, I missed these patches. Will adjust the linux-user patchset to include these patches if no bugs found in them. Just a heads up---if you only use my original patch, mipseb still won't be able to run 'make'. My final patchset (sent as a series of 6 patches) resolves this in addition to the other problems.
Re: [Qemu-devel] qemu-user[armel/mips] and debian-rootfs
On Mar 12 Jul 2011 08:32:51 Wesley W. Terpstra escribió: [snip] Just a heads up---if you only use my original patch, mipseb still won't be able to run 'make'. My final patchset (sent as a series of 6 patches) resolves this in addition to the other problems. And there you solved my last problem :-) Thanks! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: [Qemu-devel] qemu-user[armel/mips] and debian-rootfs
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
Re: [Qemu-devel] qemu-user[armel/mips] and debian-rootfs
On Mon, Jul 11, 2011 at 11:10:50AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: Thanks Riku! This bug has already been solved by Wesley Terpstra: http://lists.nongnu.org/archive/html/qemu-devel/2011-07/msg00313.html Ok, I missed these patches. Will adjust the linux-user patchset to include these patches if no bugs found in them. Riku
Re: [Qemu-devel] qemu-user[armel/mips] and debian-rootfs
On Lun 11 Jul 2011 10:45:27 riku voipio escribió: 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 Thanks Riku! This bug has already been solved by Wesley Terpstra: http://lists.nongnu.org/archive/html/qemu-devel/2011-07/msg00313.html I have patched the debian package, rebuilt and use it perfectly :-) Kinds regards, Lisandro. -- The volume of a pizza of thickness a and radius z can be described by the following formula: pi zz a Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: [Qemu-devel] qemu-user[armel/mips] and debian-rootfs
Hi! First of all, sorry for breaking the thread [0] (although it is too old maybe). [0] http://lists.gnu.org/archive/html/qemu-devel/2010-05/msg00116.html As I have stumbled upon this bug, I would like to know if there is something I can do to try to help fixing it. I have never seen qemu's code and I am really a newbie to it, so any pointer would be higly appreciated. Kinds regrads, Lisandro. -- Wiki is not WysiWyg. It's an intelligence test of sorts to be able to edit a wiki page. It's not rocket science, but it doesn't appeal to the VideoAddicts. If it doesn't appeal, they don't participate, which leaves those of us who read and write to get on with rational discourse. http://www.c2.com/cgi/wiki?WhyWikiWorks Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: [Qemu-devel] qemu-user[armel/mips] and debian-rootfs
On Vie 01 Jul 2011 14:46:05 Lisandro Damián Nicanor Pérez Meyer escribió: Hi! First of all, sorry for breaking the thread [0] (although it is too old maybe). [0] http://lists.gnu.org/archive/html/qemu-devel/2010-05/msg00116.html As I have stumbled upon this bug, I would like to know if there is something I can do to try to help fixing it. I have never seen qemu's code and I am really a newbie to it, so any pointer would be higly appreciated. 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. Also I would like to thank josch who has been helping me a lot with this :-) Kinds regards, Lisandro. -- Quizá, para muchos, ahora que lo pienso, Wikipedia tiene ciertamente un defecto imperdonable. No adorna. Ariel Torres, Probablemente, la Wikipedia esté bien La Nación Tecnología, Sábado 25 de agosto de 2007 http://www.lanacion.com.ar/tecnologia/nota.asp?nota_id=937889 Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
[Qemu-devel] qemu-user[armel/mips] and debian-rootfs
I'm trying to setup a debian root that I can chroot into for armel and mips from an ubuntu 9.10 x86_64. While I have it working for armel on a specific qemu the mips target is more problematic. first both fail for qemu newer than 6173d56bdcb53389c54e803873e6bf8f87836a4f. doing /sbin/ldconfig. I get bad address now on to mips. during installation of debian I get the following error, /bin/tar: ./postinst: Cannot utime: Level 2 not synchronized now I guess what is really happening is that my x86_64 kernel is returning ENOSYS and that maps to the mostly unused EL2NSYNC on mips. arch/mips/include/asm/errno.h:#define EL2NSYNC38 /* Level 2 not synchronized */ include/asm-generic/errno.h:#define EL2NSYNC45 /* Level 2 not synchronized */ include/asm-generic/errno.h:#define ENOSYS 38 /* Function not implemented */ Is there anything that can be done to fix this ?? I do not know what syscall this is happening on :(
