Date: Sun, 14 Dec 2014 06:51:25 +0000 From: Miguel Clara <miguelmclara@gmail.com> To: "David P. Discher" <dpd@dpdtech.com> Cc: freebsd-xen@freebsd.org Subject: Re: Attempting to Get Xen FreeBSD Dom0 working Message-ID: <CADGo8CUsGSSTXE%2Bd9wh2e4QYUnj2a467FFzT7owdB%2BeZEQeFJw@mail.gmail.com> In-Reply-To: <55E2C419-E537-4324-B7AB-A21E94863E17@dpdtech.com> References: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com> <547DFCC0.6030003@citrix.com> <DCB954B5-0E45-4DE6-AAC4-C5ACF7FD90A7@dpdtech.com> <547F1476.8080305@citrix.com> <29437DB9-7DC8-47A8-8FC4-2BFDE736B5BC@dpdtech.com> <547F59B4.1010105@citrix.com> <2DDCAA68-3B11-4E3C-AE61-EAD8CEEF1E2D@dpdtech.com> <547F6AC1.9060709@citrix.com> <BBBFE7EC-BB42-4514-9A68-437ECAB8E640@dpdtech.com> <7C356027-01D8-4800-B211-282566BC9871@dpdtech.com> <54801F77.5050700@citrix.com> <C56B19DD-B001-4AB6-A296-EC221C58297C@dpdtech.com> <D2157B5C-391D-478B-A9F0-4D34DC21534A@dpdtech.com> <54819D6A.4050603@citrix.com> <7F90454D-16D5-4871-A155-5ADD01014976@dpdtech.com> <5486B287.7070302@citrix.com> <55E2C419-E537-4324-B7AB-A21E94863E17@dpdtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I was just trying too boot Freebsd Xen dom0 on a laptop but I just get a
black screen after the boot process....
any idea what it could be?
the system boots fine wihtout loading "boot/xen", I'm not sure how to get
more info with the black scren!
thanks
Melhores Cumprimentos // Best Regards
-----------------------------------------------
*Miguel Clara*
*IT - Sys Admin & Developer*
*E-mail: *miguelmclara@gmail.com
www.linkedin.com/in/miguelmclara/
On Tue, Dec 9, 2014 at 7:17 PM, David P. Discher <dpd@dpdtech.com> wrote:
>
> ah, sorry missed that. Will try that today.
>
> AHCI lasted over night with MSI off. Something I noticed, is that when
> the AHCI bus was timing out, it looked like the Xen Kernel was re-scannin=
g
> the PCI bus. (Sorry, didn=E2=80=99t save these logs). I=E2=80=99ve love =
to dig into this
> further.
>
> Please let me know what/where to add some debugging code.
>
> -
> David P. Discher
> http://davidpdischer.com/
> AIM: DavidDPD | Y!M: daviddpdz
> Mobile: 408.368.3725
>
>
>
> On Dec 9, 2014, at 12:27 AM, Roger Pau Monn=C3=A9 <roger.pau@citrix.com> =
wrote:
>
> > Hello,
> >
> > El 08/12/14 a les 23.45, David P. Discher ha escrit:
> > <SNIP>
> >>
> >> Sent SIGTERM to all processes
> =E2=94=82
> >> Sent SIGKILL to all
> processes=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=
=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=
=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=
=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=
=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=
=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=98
> >> Requesting system reboot
> >> [ 1157.299205] Restarting system.
> >> root@borg:/zdata/debian #
> >> root@borg:/zdata/debian #
> >> root@borg:/zdata/debian # xl create -c debian.cfg
> >> root@borg:/zdata/debian # xl destroy debian
> >> xc: error: Could not bounce buffer for version hypercall (35 =3D
> Resource temporarily unavailabl): Internal error
> >> xc: error: Could not bounce buffer for version hypercall (35 =3D
> Resource temporarily unavailabl): Internal error
> >> xc: error: Could not bounce buffer for version hypercall (35 =3D
> Resource temporarily unavailabl): Internal error
> >> xc: error: Could not bounce buffer for version hypercall (35 =3D
> Resource temporarily unavailabl): Internal error
> >> xc: error: Could not bounce buffer for version hypercall (35 =3D
> Resource temporarily unavailabl): Internal error
> >> xc: error: Could not bounce buffer for version hypercall (35 =3D
> Resource temporarily unavailabl): Internal error
> >> libxl: error: libxl.c:658:libxl_list_domain: getting domain info
> list: Resource temporarily unavailable
> >> debian is an invalid domain identifier (rc=3D-5)
> >> root@borg:/zdata/debian #
> >>
> >> I=E2=80=99m running AHCI with MSI off in the FreeBSD kernel, and so fa=
r, so
> good on that front. The great thing is now I got the Xen console working=
,
> so can get the debug output. However the bounce buffer/hypercall issue =
i
> would think is far more important than MSI interrupts at the monument.
> >
> > Glad to know you got it working at the end! I've already pointed this
> > out in my last email, but did you try to increase vm.max_wired even
> further?
> >
> > This usually happens when mlock in
> > freebsd_privcmd_alloc_hypercall_buffer (xc_freebsd_osdep.c) fails to
> > wire down the memory that would be used by the hypercalls.
> >
> > Roger.
> >
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADGo8CUsGSSTXE%2Bd9wh2e4QYUnj2a467FFzT7owdB%2BeZEQeFJw>