All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Paul Leiber <paul@onlineschubla.de>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [BUG] Passed through PCI devices lost after Windows HVM DomU reboot
Date: Tue, 8 Jun 2021 08:24:16 +0200	[thread overview]
Message-ID: <5f532ea4-4ff4-e163-9492-096d16a316e7@suse.com> (raw)
In-Reply-To: <FRYP281MB05828EB0C49C963C7954578CB0389@FRYP281MB0582.DEUP281.PROD.OUTLOOK.COM>

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



  reply	other threads:[~2021-06-08  6:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 23:44 [BUG] Passed through PCI devices lost after Windows HVM DomU reboot Paul Leiber
2021-06-08  6:24 ` Jan Beulich [this message]
2021-06-08 15:13   ` AW: " Paul Leiber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5f532ea4-4ff4-e163-9492-096d16a316e7@suse.com \
    --to=jbeulich@suse.com \
    --cc=paul@onlineschubla.de \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.