> > When I specify the entire path to /bin/disk/fdisk, the "'./disk' file does > > not exist" part doesn't happen. > > /bin/disk/fdisk: diskread 68 at 0.446: > > Yes, this shows that %r in print(2) can be misleading if errstr > hasn't been cleared from a previous error. The "file does not exist" > message is not relevant to your disk problem. > > You've included lots of useful information but three more things > might help: > > - what release of xen? from "xm info" output: version : NetBSD 5.1 (XEN3PAE_DOM0) #0: Sun Apr 10 06:52:16 UTC 2011 a...@mercury.acfsys.net:/usr/src/sys/arch/i386/compile/XEN3PAE_DOM0 xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p > - what's in the xen config file? kernel = "/ort/xenimages/plan9/9xeninst-pae.gz" memory = 96 name = "plan9" vif = [ 'mac=aa:00:00:50:02:f5, bridge=0' ] disk = [ 'file:/ort/xenimages/plan9/plan9.img,sda,w','file:/ort/xenimages/plan9.iso,sdb,r' ] # This is the equivalent of plan9.ini: extra=""" nobootprompt=local!/boot/bzroot bootfile=sd01!cdboot!bootdisk.img """ > - what does 'ls -l' say about the virtual disk file on the host OS? mercury# ls -l plan9.img -rw-r--r-- 1 root wheel 1073741824 Sep 26 08:08 plan9.img > >
Thanks, Alan C. Fisher
