Re: [XEN] xs_single device/vbd xs_talkv read_reply panic: bad stray interrupt

I've just committed a change so that hda corresponds to xbd0. Also
I've tested xen 3.3 from hg and have booted a kernel off an md. I
think the key thing is just to give it the right root.

-Kip


On Sat, Aug 23, 2008 at 3:31 AM, Brad Pitney <pitney.brad_at_googlemail.com> wrote:
> On Sat, Aug 23, 2008 at 2:13 AM, Kip Macy <kmacy_at_freebsd.org> wrote:
>> There is no way for a device to show up as xbd0 at this time. Next
>> time you see the mount root prompt type ?.
>>
>> From my config:
>> <...>
>> disk = [ 'file:/home/kmacy/xen/mdroot-7.0,hda,w' ]
>> <...>
>> extra += ",vfs.root.mountfrom=ufs:/dev/xbd768a"
>> <...>
>
> sorry, I sent the mail before finishing:
>
> once I type ? at the mount root prompt type, I get:
>
> mountroot> ?
>
> List of GEOM managed disk devices:
>  xbd1cs1d xbd1cs1c xbd1cs1a xbd1cs1 xbd1s1d xbd1s1c xbd1s1a xbd1c
> xbd1a xbd1s1 xbd3 xbd2 xbd1
>
> Manual root filesystem specification:
>  <fstype>:<device>  Mount <device> using filesystem <fstype>
>                       eg. ufs:da0s1a
>  ?                  List valid disk boot devices
>  <empty line>       Abort manual input
>
> mountroot> bad stray interrupt
>
> sometimes that 'bad stray interrupt' pops up.
>
> once I type ufs:xbd1s1a I then get:
>
> mountroot> ufs:xbd1bad stray interrupts1a
> Trying to mount root from ufs:xbd1s1a
> panic: vm_fault: fault on nofault entry, addr: c0877000
> cpuid = 0
> KDB: enter: panic
> [thread pid 12 tid 100024 ]
> Stopped at      kdb_enter+0x3a: movl    $0,kdb_why
> db> bt
> Tracing pid 12 tid 100024 td 0xc16a8cc0
> kdb_enter(c0340eed,c0340eed,c0360502,cbe448ec,0,...) at kdb_enter+0x3a
> panic(c0360502,c0877000,1,cbe44a0c,cbe449fc,...) at panic+0x12c
> vm_fault(c0871000,c0877000,1,0,c0877fd0,...) at vm_fault+0x178
> dblfault_handler() at dblfault_handler+0x551
> --- trap 0x17, eip = 0, esp = 0, ebp = 0 ---
> db>
>
> I tried both ufs:xbd1s1a and ufs:xbd1cs1a, I have managed to get
> further than this.
>
> I actually need to redo the file image as it is completely
> un-configured in the sense of no fstab, etc.
>
> to create the image I did:
>
> # cd /tmp && truncate -s +1G xbd0
> # mdconfig -a -f xbd0
> # fdisk -i /dev/md0
> # disklabel -wB /dev/md0s1 && disklabel -e /dev/md0s1
> # mount /dev/md0s1a /dist
> # cd /usr/src && make world distribution DESTDIR=/dist
> # umount /dist && mdconfig -d -u 0
>
> then transferred to my Xen dom0.
>
> my config:
> ##
> name = "bldr-fbsd32"
> kernel = "/var/xen/" + name + "/kernel"
> disk = [ 'file://var/xen/' + name + '/xbd0,0x01,w',
>         'file://var/xen/' + name + '/xbd1,0x02,w',
>         'file://var/xen/' + name + '/xbd2,0x03,w' ]
> vif = [ 'mac=00:bd:c4:12:00:ef,bridge=bridge0' ]
> memory = 256
> on_crash = 'preserve'
> #extra = "boot_verbose"
> extra = "boot_single"
> extra += "vfs.root.mountfrom=ufs:/dev/xbd1s1a"
> extra += ",kern.hz=100"
>
> thanks
>
> --
> Best regards,
>  Brad
>