>>> On 22.01.15 at 22:49, wrote:
> On Thu, Jan 22, 2015 at 07:08:22AM +, Tian, Kevin wrote:
>> > From: Elena Ufimtseva [mailto:elena.ufimts...@oracle.com]
>> > Sent: Thursday, January 22, 2015 4:53 AM
>> >
>> > need_iommu has to be set earler for dom0 pvh specific init
>> > functions. If not
On Thu, Jan 22, 2015 at 07:08:22AM +, Tian, Kevin wrote:
> > From: Elena Ufimtseva [mailto:elena.ufimts...@oracle.com]
> > Sent: Thursday, January 22, 2015 4:53 AM
> >
> > need_iommu has to be set earler for dom0 pvh specific init
> > functions. If not enabled, mmio regions are not mapped with
>>> On 21.01.15 at 21:53, wrote:
Apart from the issues with this submission that Kevin already
mentioned, please ...
> --- a/xen/arch/x86/domain_build.c
> +++ b/xen/arch/x86/domain_build.c
> @@ -1500,7 +1500,9 @@ int __init construct_dom0(
>
> if ( is_pvh_domain(d) )
> {
> -/
> From: Elena Ufimtseva [mailto:elena.ufimts...@oracle.com]
> Sent: Thursday, January 22, 2015 4:53 AM
>
> need_iommu has to be set earler for dom0 pvh specific init
> functions. If not enabled, mmio regions are not mapped with iommu
> during domain construction.
>
> This was discovered when work
need_iommu has to be set earler for dom0 pvh specific init
functions. If not enabled, mmio regions are not mapped with iommu
during domain construction.
This was discovered when working on booting problems of pvh dom0
on two different machines (ThinkCentre M and Dell 5600T).
On ThinkCentre during
