Vagrant Cascadian wrote: > Version: 1.0+dfsg-1 > > On Mon, Sep 12, 2011 at 07:18:40PM +1000, Trent W. Buck wrote: > > Package: qemu-user-static > > Version: 0.15.0~rc2+dfsg-1 > > Severity: normal > > File: /usr/bin/qemu-arm-static > > > > I did this: > > > > mkdir -p target/usr/bin > > cp /usr/bin/qemu-arm-static target/usr/bin > > cdebootstrap -f minimal -k /etc/debmirror/trustedkeys.gpg -a armhf > > unstable target http://apt/debian-ports > > > > Where http://apt/debian-ports is a partial mirror of debian-ports.org, made > > today. > > > > When this finished, I chrooted in and installed aptitude. Running > > aptitude --help works, but aptitude -u clears the screen then prints > > > > Segmentation fault > > apparently, armhf is at least reasonably well supported now(maybe it always > was), and so i tested with aptitude 0.6.4-1.2+b1 in an armhf sid chroot. > > i was able to reproduce this behavior with qemu-user-static 0.15.1+dfsg-3, but > not with qemu-user-static 1.0+dfsg-1, so it appears to be fixed in newer > versions.
Sorry, I forgot all about this ticket. I don't remember if I said so when I reported this, but (assuming I'm remembering the right bug) it turned out to be something about qemu not zeroing memory before handing it out to the guest process or something. Someone on #kvm or #qemu gave me a short (~dozen lines) patch that I applied to debian's qemu source package, and after doing that I compiled a qemu-arm-static binary that didn't exhibit this behaviour. Sorry for dropping the ball on this one. Fortunately it looks like the chap from IRC pushed the patch into upstream, since Vagrant indicates it has trickled down to Debian in the current version :-) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
