[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [BUG] Consistent LBR/TSX vmentry failure (0x80000022) calling domain_crash() in vmx.c:3324

  • To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • From: Elliot Killick <elliotkillick@xxxxxxxxxxx>
  • Date: Wed, 20 May 2020 11:20:44 +0000
  • Arc-authentication-results: i=1; mx.zohomail.eu; dkim=pass header.i=zohomail.eu; spf=pass smtp.mailfrom=elliotkillick@xxxxxxxxxxx; dmarc=pass header.from=<elliotkillick@xxxxxxxxxxx> header.from=<elliotkillick@xxxxxxxxxxx>
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu; s=zohoarc; t=1589973650; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=aR7gBnILmO1RKcA2jKLkKUAJB/f8NlfON0JDkwcQY3Y=; b=cAljNXntotx474riSRV1ig4S+u1y22eLAIB/VXrST4OYS5TywPh9RJbt+4T2NK1m7IHs9/FwPITzQq+wrrL3YVsIec9Up/gD5SIn7WBBVftDHbwC46LP34mrjbBetkcnqFk9Bw4i6SHJiP/2xyqDbTmFxTJaR4HTVK0aoz82UEA=
  • Arc-seal: i=1; a=rsa-sha256; t=1589973650; cv=none; d=zohomail.eu; s=zohoarc; b=Te8D8MxAZn8lO8f1D6jw2Vod41cgY0fLXmT63HCkreH322mL0tWy8z98PrIel+odBF2bwwjDLhgGmqJsIqsynyTIgfa4Hz1UhM4g6ZkzoORrOtuAXcyYXlaobKZCjZQfBRC0LYWSvCjui3U3TuWAOUH9OdA1I0bmklwBvm7SvOc=
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 20 May 2020 11:20:56 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 2020-05-20 11:10, Andrew Cooper wrote:
> On 20/05/2020 11:33, Elliot Killick wrote:
>> Hello,
>> Xen is crashing Windows 10 (64-bit) VMs consistently whenever IDA
>> Debugger
>> (https://www.hex-rays.com/products/ida/support/download_freeware/)
>> launches the Local Windows Debugger. The crash occurs when trying to
>> launch the debugger against any executable (e.g. calc.exe) right at the
>> time IDA says it is "Moving segment from <X address> to <Y address>".
>> Tested on Windows 7, 8 and Linux as well but the bug is only triggered
>> on Windows 10. Happens whether or not IDA is running with administrator
>> privileges. No drivers/VM tools installed. Windows has a bug check code
>> of zero, leaves no memory dump, nothing in the logs from QEMU in Dom0,
>> the domain just powers off immediately leaving a record of the incident
>> in the hypervisor.log. So, it does appear to be a Xen issue. Modern
>> Intel CPU.
>> Does anyone have some ideas on what may be causing this?
> What exact CPU do you have?  This looks exactly like the
> Haswell/Broadwell TSX errata.
> ~Andrew




Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.