Date: Thu, 4 Dec 2014 12:26:37 -0800 From: "David P. Discher" <dpd@dpdtech.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com> Cc: freebsd-xen@freebsd.org Subject: Re: Attempting to Get Xen FreeBSD Dom0 working Message-ID: <C56B19DD-B001-4AB6-A296-EC221C58297C@dpdtech.com> In-Reply-To: <54801F77.5050700@citrix.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>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Dec 4, 2014, at 12:46 AM, Roger Pau Monné <roger.pau@citrix.com> wrote: > Hello, > > El 04/12/14 a les 3.27, David P. Discher ha escrit: >> So, the “working” part … the hypervisor up, and Dom0 running, is correct. >> >> However, after ~5 minutes, the AHCI buses timeout. This seems to be constantly >> reproducible via Dom0. FreeBSD on the this bare metal does’t have this issue. > > If you boot Xen with iommu=debug, do you see any messages on the Xen > console? > > My test boxes also use AHCI, but the chipset is not exactly the same > (mine is ICH8, yours is ICH10). Do you do anything specific to trigger > the timeout, or just leaving Dom0 in an idle state also triggers this? > > Could you switch to the Xen console and post the output of the "i" debug > key when this happens? > > Also, you can try to play with the AHCI driver sysctls, to see if some > of them have any effect. I would recommend trying to disable MSI > interrupts (hint.ahci.X.msi=0) and power control (hint.ahcich.X.pm_level=0). Yes, ICH10. I’m not sure if an idle Dom0 does this, however limited access to the disks, even just editing things like /boot/loader.conf and /etc/rc.conf will eventually hang. But I’m also trying to launch a DomU, and for the convince of a documented process, I’m following your debian steps … and the debian installer is running. I’m running a zpool mirror across 4k aligned GPT partitions for the root drive. I’ll also attempt to break break the mirror, as I don’t remember this being a problem with a single drive. As first step last night, I actually moved the msi interrupts to = 2, instead of fully disabled. And this helped a little. It seemed to allow the AHCI driver to recovered after the first several timeouts. I will try disabling MSI as well and well as iommu debug. However, I’m still without a Xen console. Durning the ACPI/pci probing … my console over SOL com3 cuts out. I haven’t try to recover it yet. I will see what I can do. However, from what it looks like, Xen kernel is latching on the com port, and freebsd sees it as “busy”. I’ll see what I can figure out. I believe the pm_level is default to 0, but will double check that. - David P. Discher http://davidpdischer.com/ AIM: DavidDPD | Y!M: daviddpdz [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUgMN+AAoJEEmwU6XuhYWO87EH/3r3tyXFiZXB7mnc3JLU1T+O UN9M0MCE91sjfJDEoTH+Phh1uY40sRFvChZ3raOl1SWRSZzKQz15pqiOIoSKgBsx kS8GP/7EERxWzYKpipKbh4f78KRvDfq07xdmKomg5gj0jS1rzn9NDhRDdIDgkxi6 NKhkR+An+OnAWM/+Fn8BjxrkP95jD5thBx2/9sCpnrfhr6u5piAgF8pIGkVeKxVb HxKEmbFazl7s2rMWnyhsT3l6NGFBjuVVcF5S6M33fMCkI1b8FSX76EJz0eFZ+muU diEB1m+BmOfrxmNJDH8hsMUBuvDkNG1qkw0obbAPJfoU4BE5h4h5FQz9Qm7lPl8= =S2pq -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C56B19DD-B001-4AB6-A296-EC221C58297C>