[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ryzen 6000 (Mobile)
- To: Dylanger Daly <dylangerdaly@xxxxxxxxxxxxxx>
- From: Jan Beulich <jbeulich@xxxxxxxx>
- Date: Tue, 16 Aug 2022 10:59:38 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=/EygQqwm9cbi5rFtal9Y7ekSUN6Z8KDQF2oCnJZQYRY=; b=esJjjKslFo/9IYpxyx2W6oEUhsZZPCs1K6hcNQTextkRIwu1bWDsQyVf5q7UWQtG80BBOUQ3vjsBcSlJq4hv09npg9f/TE8jx030oLGTbAPKSaDOaxGWgI8bkk4/Y1Z3RkG2MK8WQEq32hb7RwNiF/urBCHupjbGyAlopqEGhxpyP/4VVCm0CYM4xaPUXgC+PbBYhbnh61fnMdGbxEfsMJeuFxeTZtInh+ocDdnRcvygznFUwT/WM1xhU/9/iRVIpsi/C4L2NF24o0yGHZNfKv+3LUpReTpjiGBdOq8x+iz4h270hphWT4GBvQPEGphTpwPDpmpk2rsjBBzuvJ7IzQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=BZHZP8hKg/yWGD0x84CbdJlY9iKPusVTzYCa5xZoV/rKIcMPELhilbA5xExCbT45id50fAOS/1R8Navc20ap8BmhA9tXJXukb3EypHqjLymXFPYL+mJBXFPcsfbFus8++DJGwPX4TJgTOsuDt0X8TwNzBdn2W55a+a9d8mDGO0JCL+VL5E3jwjbjmssq3md9cT8IaP5cPMICAJeZXIVqYfEx3NOOmiy4cO/1sJMAaVig9D62v109ocivQONNyden19UUQgOE+tnhHJ8vu/fxjXRq+PkglA4Bvpv5FOKnSE9y4Rpfze8WXxm1DJcFa5nOyllMyPUuZMY+LUBN7vFaVw==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx, Andrew.Cooper3@xxxxxxxxxx
- Delivery-date: Tue, 16 Aug 2022 08:59:50 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 16.08.2022 10:34, Dylanger Daly wrote:
> Indeed no devices are being passed into the domU, I'm simply trying to start
> a vanilla VM with no PCIe devices attached.
Hmm, looking more closely it's the sound device which is being opened by
some ALSA process. I have no clue at all why this would happen while
starting a VM. If the firmware setup allows you to, you may want to try
turning off that device and see if then the VM starts successfully.
> Could it be a misconfiguration with ACPI tables? I originally thought it
> could be AMD's SEV but I think it might just be that Xen is attempting to use
> a memory region that it shouldn't
No, it's clearly ACPI which tries to evaluate / modify something. That's not
initiated by Xen at all. It's merely likely that under Xen something works
differently than under native. As said, since now you're able to see log
output on the screen, quite likely you would also see an earlier message
about some mapping operation having failed. Whether that would be a Xen or
kernel message (or both) is uncertain, as it would depend on the specific
operation that is being attempted.
Jan
|
