On 15/10/2019 22:35, Håkon Alstadheim wrote: > Got this just now, as my windows domU died: > > (XEN) [2019-10-15 21:23:44] d7v0 vmentry failure (reason 0x80000021): > Invalid guest state (0) > (XEN) [2019-10-15 21:23:44] ************* VMCS Area ************** > (XEN) [2019-10-15 21:23:44] *** Guest State *** > (XEN) [2019-10-15 21:23:44] CR0: actual=0x0000000080050031, > shadow=0x0000000080050031, gh_mask=ffffffffffffffff > (XEN) [2019-10-15 21:23:44] CR4: actual=0x0000000000172678, > shadow=0x0000000000170678, gh_mask=ffffffffffe8f860 > (XEN) [2019-10-15 21:23:44] CR3 = 0x00000000001aa002 > (XEN) [2019-10-15 21:23:44] RSP = 0xffff908e440fae68 > (0xffff908e440fae68) RIP = 0xffff9581e15d560b (0xffff9581e15d560b) > (XEN) [2019-10-15 21:23:44] RFLAGS=0x00000197 (0x00000197) DR7 = > 0x0000000000000400 > (XEN) [2019-10-15 21:23:44] Sysenter RSP=0000000000000000 > CS:RIP=0000:0000000000000000 > (XEN) [2019-10-15 21:23:44] sel attr limit base > (XEN) [2019-10-15 21:23:56] printk: 52 messages suppressed. > (XEN) [2019-10-15 21:23:56] [VT-D]d7:PCIe: unmap 0000:81:00.0 > (XEN) [2019-10-15 21:23:56] [VT-D]d0:PCIe: map 0000:81:00.0 > (XEN) [2019-10-15 21:23:59] printk: 2 messages suppressed. > (XEN) [2019-10-15 21:23:59] [VT-D]d7:PCIe: unmap 0000:02:00.0
Sadly there is a large quantity of information missing here. > > xen_commandline : xen.cfg xen-marker-215 > console_timestamps=date iommu=1,intpost,verbose,debug > iommu_inclusive_mapping=1 com1=57600,8n1 com2=57600,8n1 > console=vga,com2 dom0_max_vcpus=8 dom0_mem=8G,max:8G > cpufreq=xen:performance,verbose smt=0 maxcpus=12 > core_parking=performance nmi=dom0 gnttab_max_frames=256 > gnttab_max_maptrack_frames=1024 vcpu_migration_delay=2000 > tickle_one_idle_cpu=1 spec-ctrl=no-xen sched=credit2 max_cstate=2 > clocksource=tsc tsc=stable:socket timer_slop=5000 loglvl=none/warning > guest_loglvl=none/warning ... and this would be why. Can you drop the "verbose,debug" from iommu=, and the loglvl=/guest_loglvl= on the end, and reproduce the problem again? That way, we should get the full VMCS Area dump, and I might be able to identify what state was being complained about. What hardware is this, and are what is the general configuration/workload of the Win10 guest? Thanks, ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
