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

Oops please send me your config it looks like the device number starts
at 767 and not 768.

-Kip

On Sat, Aug 23, 2008 at 5:31 PM, Brad Pitney <pitney.brad_at_googlemail.com> wrote:
> On Sun, Aug 24, 2008 at 12:16 AM, Kip Macy <kmacy_at_freebsd.org> wrote:
>> 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.
>>
>
> thanks.
>
> something is not quite right, so I am going to restart from scratch
> only this time configure my file image so it works under a jail,
> because at the moment after your recent change I get:
> 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> ?
>
> List of GEOM managed disk devices:
>  xbd-767cs1d xbd-767cs1c xbd-767cs1a xbd-767cs1 xbd-767s1d xbd-767s1c
> xbd-767s1a xbd-767c xbd-767a xbd-767s1 xbd-765 xbd-766 xbd-767
>
> 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> ufs:xbd-767s1a
> Trying to mount root from ufs:xbd-767s1a
> 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>
>
> this time I wont use fdisk. I'll report back either way as I don't
> want you to be trying to solve a none existent problem that may well
> just be my fault :)
>
> --
> Best regards,
>  Brad
>