From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sun, 6 Mar 2011 22:45:04 -0500 To: 9fans@9fans.net Message-ID: <98783fe93adc0829ac2f9c12d1d22103@brasstown.quanstro.net> In-Reply-To: References: <10045_2495_16663b8cca278b776372dbc44b36387b57580924_6@arpnetworks.tenderapp> <10045_2495_16663b8cca278b776372dbc44b36387b57580924_5@arpnetworks.tenderapp> <10045_2495_16663b8cca278b776372dbc44b36387b57580924_4@arpnetworks.tenderapp> <10045_2495_16663b8cca278b776372dbc44b36387b57580924_3@arpnetworks.tenderapp> <10045_2495_16663b8cca278b776372dbc44b36387b57580924_2@arpnetworks.tenderapp> <10045_2495_16663b8cca278b776372dbc44b36387b57580924_7@arpnetwork> <288e83061e963edf1c2aa45b26729934@EXAMPLE> <4aac3b8993d7aa7085545f30b037> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] recent plan9.iso on hosted kvm/qemu Topicbox-Message-UUID: b7835568-ead6-11e9-9d60-3106f5b1d025 On Sun Mar 6 22:33:33 EST 2011, stanley.lieber@gmail.com wrote: > > 9atom's 9load prints "%d e820 entries" on boot. is that number 0? > > found 7 e8s0 entries > > Then it freezes. it's not the e820 code, then. it's either falling over initializing the console, or it's falling over probing devices for the .ini file. after e820, 9load starts up the console and probes devices looking for a .ini file. i would think the odds are good that 9load has found an i/o port that should not be touched. devices are probed in this order floppy. ether, cd, sd. i don't really have a kvm setup, but if it's possible, you might try removing devices (espeically ethernet devices) from a copy of 9load until you find something that boots, then add 'em back in till it doesn't. sounds tedious, no? :-) - erik