Am 18.01.2014 um 18:08 schrieb Andreas Färber <afaerber@suse.de>:
Am 18.01.2014 06:57, schrieb Andreas Färber:
Guys,
JeOS builds in QEMU are completely broken ATM:
https://build.opensuse.org/package/live_build_log/devel:ARM:Factory:Contrib:...
The unsupported ioctl 0x1269 appears to be BLKPG, so I implemented it to the best of my understanding in Virtualization qemu. But it seems, the build is still using some 1.5.92 version rather than my shiny 1.7.0!
I tracked down that :Factory:ARM's qemu-linux-user-arm is packaging whatever QEMU the build host happens to have installed for some reason. But there is no dependency on QEMU so that it doesn't get updated. I therefore pieced together a trivial qemu-linux-user-arm package with my new binaries and overlaid that:
https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryP...
However, the package did not get published yet, which I guess - since kiwi uses zypper to download packages - is the reason the build still fails... "Build jobs have been processed, new repository is not yet created" although the repository on the download server does exist and contains kernel binaries.
Same problem as with 13.1 updates?
Quick update: My first building qemu-linux-user-arm package -5.1 got published after a few hours(!), by now -6.1 is published, too. So no, 13.1 updates is still not publishing, it only took reeeally long.
The output changed now from "Unsupported syscall: cmd=0x1269 (0)" to "Invalid type 0x9", which I did not find in linux-user. It occurs equally often, so something with my implementation may be wrong. Alex?
Yeah, maybe the guest is printing it. Try to write a small test program for your ioctl emulation - or try QEMU_STRACE=1 first to be sure it's really that one. Alex
Andreas
-- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org