[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] dom0 as pvh boot problem
Hi There is a problem with booting dom0 as pvh (xen-4.5rc3, kernel 3.18.0+). After digging a bit into this it seems that the booting gets stuck upon enabling second IOMMU by writing to DMAR_GCMD_REG (See the attaches debug log). The boot process passes this stage if second iommu was not enabled. I tried multiple iommu options on boot, but it did not help. There is no problem booting baremetal linux with IOMMU enabled. The difference I have noticed its the version of microcode that is shown in baremetal and Xen. Baremetal linux shows microcode version as 0x710, Xen as 0x70d, not sure if its relevant. Any advise on how to address this is appreciated. baremetal cpuinfo: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz stepping : 7 microcode : 0x710 cpu MHz : 1200.000 cache size : 10240 KB physical id : 1 siblings : 4 core id : 3 cpu cores : 4 apicid : 38 initial apicid : 38 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 4789.44 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management -- Elena Attachment:
dom0pvh_xeon_e5 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |