>>> On 28.06.16 at 13:23, wrote:
> A clue on doing this would be useful, I can't debug what is now release
> code all day.
Well, debugging (released code or not) is what's needed, I'm afraid.
A first step would be to find out how far the corruption extends:
Considering the non-zero code bytes tha
A clue on doing this would be useful, I can't debug what is now release
code all day.
4.5 is absolutely fine. 4.6.3 (tried last night) does not fail either but
refuses to start my domU that has two nics assigned to it in a vif line.
I'm presuming other people are successfully running multiple NICs
>>> On 28.06.16 at 00:28, wrote:
> (XEN) [2016-06-27 22:11:41.712] [ Xen-4.7.0 x86_64 debug=n Not tainted
> ]
> (XEN) [2016-06-27 22:11:41.712] CPU:0
> (XEN) [2016-06-27 22:11:41.712] RIP:e008:[]
> domain_relinquish_resources+0x10/0x2f0
> (XEN) [2016-06-27 22:11:41.712] RFLAGS
Xen 4.5 was fine, but Xen 4.7 is reliably crashing hard. 4.7 rc 5 was
crashing most of the time.
This is with a HVM FreeBSD domU, with GPU passthrough.
Unusual configurations : I am running on a system that does not have
SLAT (Core 2 system), and it's on Salix (Slackware). This was fine and
stabl
