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

Re: [BUG] Passed through PCI devices lost after Windows HVM DomU reboot


  • To: Paul Leiber <paul@xxxxxxxxxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Tue, 8 Jun 2021 08:24:16 +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-SenderADCheck; bh=6d7B/Jaq2T7t7N2Xwb5Ch47g331S3widrRMqH6FSvhs=; b=Q99iMyKHA6OSEDc1dEyl9aZSFo7R/1hn0rdpaZoPn7YpHAub7YGHh8dUaMj0uZQWSh1D3Z9W77FWx17RD2mKbdEbfAziE1Cm1ubaa/pWshQaG0MKKVnQwjmhKGTiLcY+H6okfigu17zt0nCxMcQiFkdG3fiSRxmODmUNzACa2QLbWKdAmGJ50dRSXne0jTmupCSb0edYzLnN9jYcpjRWK60YORgrYFX/EpALldvuUr6K/9GfJOjL/Amoy/Mjp4aL4uCKDDrWwelWQCwnTeBkQVk8t7LjTUHZZoPh71gTowJc1AiMDYUYV6abVyA1Mrx3I70VbIAut0Ar1tfqtJZO+Q==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=e64V1QIu2mdDzS1PfmK9d6t15JfSlSruJGRZOHNE71jvkE2G73IXj9YuV++P6FSbfPeZ4kTg4MOzvyQxnjmrQNquxva1BF/dfRy4cZVNq35J1rfTMRajegGTGBja/H++uyBIZyc1Bxzhi1n92Kg+WaZYgrXuQOurw1BfC8V4QSAokxhhCxX6RgIaKvoFBIr8pxaZ51+N9NikAQfR0ulaemrZtVpPK4R7QZcqx9DS6qZpHpRjMp6ZWotcrD8jlhl08cFBSSiPIdacB8qQPRJFMoFrjHrJaslSooU5+gRdlo2iIkUKJNHuz0zIxSc5Mw4aulK2VTTXASO0P4wKD7AETQ==
  • Authentication-results: lists.xenproject.org; dkim=none (message not signed) header.d=none;lists.xenproject.org; dmarc=none action=none header.from=suse.com;
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 08 Jun 2021 06:24:28 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 08.06.2021 01:44, Paul Leiber wrote:
> After more testing, I have come to the following conclusion: It seems that 
> every time I do a _reboot_ from within a Windows DomU, the PCI device does 
> not get attached to the DomU. After DomU reboot, it is immediately available 
> for attachment in the Dom0 when I check for it with "xl pci-assignable-list", 
> and I can reattach it to the DomU with "xl pci-attach" without any major 
> problems beside some annoying side effects (e. g. need to reapply settings).

A well-known problem on ...

> xl info:
> 
> host                   : xxx
> release                : 4.19.0-14-amd64
> version                : #1 SMP Debian 4.19.171-2 (2021-01-30)
> machine                : x86_64
> nr_cpus                : 4
> max_cpu_id             : 3
> nr_nodes               : 1
> cores_per_socket       : 4
> threads_per_core       : 1
> cpu_mhz                : 1992.100
> hw_caps                : 
> bfebfbff:77faf3ff:2c100800:00000121:0000000f:009c6fbf:00000000:00000100
> virt_caps              : hvm hvm_directio
> total_memory           : 32542
> free_memory            : 20836
> sharing_freed_memory   : 0
> sharing_used_memory    : 0
> outstanding_claims     : 0
> free_cpus              : 0
> xen_major              : 4
> xen_minor              : 11
> xen_extra              : .4
> xen_version            : 4.11.4

... this old Xen version, I believe. I don't recall when exactly it was
fixed (and I don't know at all whether the fix was backported), but
trying a recent version of Xen should get you past this. If a fully
maintained version is still affected, a backport could be requested.

Jan




 


Rackspace

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