>>> On 16.05.16 at 05:41, wrote:
> I also met this problem when passthrough 82599 to domU by SRIOV, and the
> call stack as follows:
> (XEN) Xen call trace:
> (XEN)[] panic+0xc3/0x1a0
> (XEN)[] symbols_lookup+0x22/0x2a0
> (XEN)[] syscall_enter+0x88/0x8d
> (XEN)[] syscall_enter+0x8
May 16, 2016 5:56 PM
To: liuenliang; xen-devel@lists.xen.org
Cc: Fanhenglong; Hanweidong (Randy)
Subject: Re: [Xen-devel] xen: 82599 passthrough problem
On 16/05/16 04:41, liuenliang wrote:
> Hi,all:
>
> I also met this problem when passthrough 82599 to domU by SRIOV, and the call
> stack as
On 16/05/16 04:41, liuenliang wrote:
> Hi,all:
>
> I also met this problem when passthrough 82599 to domU by SRIOV, and the call
> stack as follows:
> (XEN) Xen call trace:
> (XEN)[] panic+0xc3/0x1a0
> (XEN)[] symbols_lookup+0x22/0x2a0
> (XEN)[] syscall_enter+0x88/0x8d
> (XEN)[] sy
Hi,all:
I also met this problem when passthrough 82599 to domU by SRIOV, and the call
stack as follows:
(XEN) Xen call trace:
(XEN)[] panic+0xc3/0x1a0
(XEN)[] symbols_lookup+0x22/0x2a0
(XEN)[] syscall_enter+0x88/0x8d
(XEN)[] syscall_enter+0x88/0x8d
(XEN)[] __print_symbol+0x8a/
Hi,
I met a problem when passthrough 82599 to domU(for some reasons, I use pci
passthrough not SRIOV).
It works well after passthrough, but the host hung after destroy domU.
Btw, no log prints even from serial port, but I found it hung afer unbind irq.
anyone knows what's wrong with it? thanks.
