Re: [Xen-users] Network and SATA Instability on Xen 4.6/4.8

[Sarah Newman <srn@xxxxxxxxx>]

On 12/08/2017 03:28 PM, Kevin Stange wrote:
> On 12/08/2017 04:50 PM, Sarah Newman wrote:
>> On 12/08/2017 01:17 PM, Kevin Stange wrote:
>>>
>>> I don't know if this is a bug in Xen or something else at play, but I
>>> could really use some help figuring out what's going on, why msi=off
>>> seems to fix it, and if there are any better ways to resolve this.
>>>
>>> Thanks.
>>>
>>
>> Do you mind sharing your exact lspci output and xen and linux command lines?
> 
> Not at all.
> 
> # xl info | grep command
> xen_commandline        : placeholder dom0_mem=1535M cpuinfo
> com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all
> dom0_max_vcpus=2 msi=off

1535M is kind of an unusual amount of ram, don't you think? It shouldn't matter 
but have you tried something a bit more round, maybe at least on a
4MiB boundary?

You might want to check if there were any changes to the typical memory map in 
between 4.4 and 4.6 and review at your BIOS settings. I vaguely recall
BIOS settings related to limiting memory ranges and PCI. Maybe the old version 
of Xen was accidentally enforcing that.

> 
> # cat /proc/cmdline
> placeholder root=UUID=58788945-d0e9-4a76-87ce-4308e86b8fd6 ro nomodeset
> crashkernel=auto rd.md.uuid=88fbb495:49586ca8:0d13f6b4:86500d08
> rd.md.uuid=c00da35e:8bf4e8f6:b90591c9:dc98206d
> rd.md.uuid=c996bde2:6b217770:e8822aa5:42722e67 rhgb quiet pcie_aspm=off
> console=hvc0 earlyprintk=xen nomodeset

We run with edd=off but no modifiers to pci.

--Sarah

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-users