On 02/29/2012 12:23 PM, Michael S. Tsirkin wrote: > On Wed, Feb 29, 2012 at 12:09:14PM +0200, Avi Kivity wrote: > > On 02/29/2012 12:58 AM, Michael S. Tsirkin wrote: > > > > > > What I did, to allow bisect, is rebase Avi's patches on top > > > of my bridge implementation, then run qemu with a bridge. > > > bridge without Avi's patches at least starts booting, with > > > Avi's patches crashes before guest start. > > > > > > If you want to play with that, take it from branch bisectme > > > on my qemu tree on github. > > > > > > > How do you reproduce it? > > > > I tried > > > > qemu-system-x86_64 -device pci-bridge,chassis_nr=23 > > > > but that boots. > > It could be that you need more devices. This is my command line: > qemu-system-x86_64 -m 1G -drive file=/home/mst/rhel6.qcow2 -netdev > user,id=bar -net nic,netdev=bar,model=e1000,macaddr=52:54:00:12:34:57 > -redir tcp:8022::22 -device pci-bridge,id=bog,chassis_nr=1 -netdev > tap,id=foo,ifname=msttap0,script=/home/mst/ifup,downscript=no,vhost=on > -nographic >
Boots too, even after supplying a peer to foo. I did get an abort with -enable-kvm, but that looks like the old issue, no? Looking into it. Suggest a valgrind run. -- error compiling committee.c: too many arguments to function
