xen-devel
Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze wi
Hi Konrad/Jeremy,
Previously i had a working setup, with the same VM i'm using now, but quite a
few things have changed:
- Another motherboard
- Another processor
- Another USB controller (now usb3 pci-e instead of usb2 pci)
The freezes seem to be related to the USB3, but i'm not quite sure, since this
also can give another workload.
What i have tried:
- latest xen-4.0-testing compiled with debug=y
- for dom0: latest 2.6.32 pvops stable kernel from Jeremy
- for dom0: latest 2.6.32 xen-next kernel from Jeremy
- added some kernel debug options(apart from some noise about hardirq's this
doesn't seem to deliver a lot)
- for domU: 2.6.35-rc6 tree (devel/2.6.25-rc6-t2) from Konrad's tree.
- I also tried running without msi
It allways freezes at some point, but the time when seems to vary, although
most of the time within a day.
- Done another memtest to be sure it isn't faulty memory, cooling is on max and
temperatures are good, so that seems to be ruled out as well.
- I tried using the IOMMU, this should rule out DMA one should say, but it also
froze with the IOMMU enabled and working, and again nothing in serial log :-(
The things i'm about to try after i have finished some backups are:
- xen-unstable
- running the VM as a HVM
What i'm wondering about is:
- Could the 4GB memory barrier still be a problem ? The machine has 8GB, and
the domain normally would be started as one of the last, which totals up to
around the 4GB of domains running.
This night i let it run with only the troublesome pv domain, and it seems to
work so far.
- Is there a way to force a domain to live underneath the 4GB or any other
thing i could try out (besides ripping the ram out of the machine)
- Are there any other things that could prevent a full freeze by making things
more strict cq provide addiontal debug info ?
--
Sander
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, (continued)
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Jeremy Fitzhardinge
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Sander Eikelenboom
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Sander Eikelenboom
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Sander Eikelenboom
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Konrad Rzeszutek Wilk
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Sander Eikelenboom
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Jeremy Fitzhardinge
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Sander Eikelenboom
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Konrad Rzeszutek Wilk
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Jeremy Fitzhardinge
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log,
Sander Eikelenboom <=
- Re: [Xen-devel] [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log, Sander Eikelenboom
|
|
|