This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Possible bug, gplpv / pv-netdev

>>> I'm running xen3.4.0 , and while using windows 2003 x64 and GPLPV (up >>> to >>> - I keep running into the following kernel error message >>> in
>>> dom0:
>> Did you try another Xen version. Xen 3.4.1 should work better.
> Installing xen 3.4-testing as we speak.
> This bug has been haunting me since 3.0, so I have little hope it'll be
> fixed..

This will be a dom0 kernel issue, not a hypervisor issue, so upgrading only
Xen will not fix it.
I am running this off of the 2.6.18 kernel provided with xen.
Any loopholes I need to be aware of?

Well... strictly speaking I think there is probably also a bug in GPLPV
that causes a situation that also triggers a bug in the Dom0 kernel.
It can be considered to be a bug since it locks up domU, I suppose..

During various stages of GPLPV development I have also been able to
completely crash Dom0 (as in hang and/or reboot) from the DomU.
Isn't that supposed to be impossible?
These kind of bugs scare me, one compromised or malfunctioning domU taking down a whole system..

I'm in the middle of investigating pvUSB support under GPLPV but once it
at least doesn't crash I'll have a look at this network bug and see if I
can find out what is causing it in DomU. Hopefully the fix in Dom0
should then be obvious (unless of course GPLPV is actually doing the
right thing and Dom0 just doesn't like more than one disable->enable


Can anyone actually reproduce this bug?



Xen-devel mailing list