Thanks for the quick reply Russ. I did try running textonly AFTER manually running mbr and fdisk. It gave me the same result.
HOWEVER! out of pure frustration and lack of anything else to do ;) I decided to take it from the top. I rewiped my virtual machine drive file and filled it with 0s (dd if=/dev/zero of=plan9.img bs=1024 count=1024k). After doing this, I booted the VM back up and was able to successfully install with no quirks or hacks! Well, at least it looks like its going to be successful. I am at the copydist stage now (knock on wood). And yes, you have to use the 9xeninst kernel to boot the installer. I just grabbed it from http://cm.bell-labs.com/sources/xen/9xeninst.gz. Anyway, this is still a bug in my opinion. For the record, the drive geometry/size was WAY off in fdisk when I started. it said i had some like 4x 200GB partitions with free space in between. i wish ;) WHen i deleted them all, however, it accurately showed the free space size of 1gb flat. Might be related, might not be. Either way, the partitioner and mbr installer should not need a zeroed drive to work correctly. Thanks again and let me know if you need reproducing this later! Jason On 2/23/06, Russ Cox <[EMAIL PROTECTED]> wrote: > > So I have 2 questions: > > 1) the obvious: Whats going wrong and how can i fix it? > > 2) What are all the steps required to manually install from the shell? > > I've gotten the mbr install, the fdisk partitioning, now i'm stuck at > > the options for parm and format. > > Now that it has an mbr and fdisk is happy, > I would try running inst/textonly again. > > I just looked at the install scripts and I don't > see why disk/mbr would fail without printing an error. > Perhaps disk/mbr decided the sector size > was 0 instead of 512? cat /dev/sd01/ctl. > > I'm surprised you've gotten this far. I didn't > think the standard PC kernels booted under Xen. > > Russ > > -- Jason Lash jason.lash (at) gmail.com
