All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Brychcy <bober@brychcy.net>
To: xen-devel@lists.xen.org
Subject: Re: Struggling with PCI-Passthrough
Date: Tue, 11 Mar 2014 11:26:37 +0100	[thread overview]
Message-ID: <531EE4DD.2060607@brychcy.net> (raw)
In-Reply-To: <531D9D4F.7040008@citrix.com>

Am 10.03.2014 12:09, schrieb Andrew Cooper:
> On 10/03/14 09:59, Alexander Brychcy wrote:
>> Hi,
>>
>> I'm currently trying to create a Windows 7 HVM with GPU Passthrough.
>>
>> My setup is the following:
>> CPU:	Xeon E3-1230v3
>> Board:	Asus P9D-E/4L
>> RAM:	16GB Kingston from Board QVL
>> GPU:	Sapphire R9 270X 4GB
>>
>> The passthrough itself is working (Tested with Debian Wheezy dom0 on Xen
>> 4.1, then XenServer 6.2 and now Debian Jessie dom0 on Xen 4.3)
>>
>> Under Debian Jessie i was not able to passthrough the USB Controller,
>> although it appeard at xl pci-assignable-list and i cannot assign more
>> than 2GB of memory to the HVM.
>>
>> The overall problem is, that the HVM starts up and is running fine. But
>> after a unspecific amount of time the hole system freezes. The cursor in
>> dom0 still blinking, but no input possible - not even in xen serial
>> console. I had one run, without a freeze, but the GPU performance was
>> very poor, so i tried a manual reset. After the HVM reboot the
>> performance was as expected, but soon the system froze again.
>>
>> I'm not sure, if this problem is related to Xen, because i tried to
>> create the virtual machine with KVM and had the same issue. But i
>> switched to Xen to get the best performace.
>>
>> I will add my config and log files and hope you can help me to get this
>> setup fully working.
>>
>> Kind regards,
>> Alexander
> 
> Looking at the serial log, it would appear that Xen has decided to
> schedule no vcpus whatsoever, and is completely idle.
> 
> Looking at the 'Q' output, only two vcpus (one from each domain) are not
> in a blocked state, but no obvious reason for them to be blocked; they
> are not blocked waiting for events.
> 
> Are you able to try this with a debug version of Xen?  Perhaps an
> assertion will be tripped which might give more of a clue.
> 
> It is certainly interesting that the same behaviour exists with KVM,
> suggesting it is something to do with hardware interaction, but I can
> see no obvious reason why Xen is as idle as it is.
> 
> ~Andrew
> 

I will try everything to get this machine running, but i won't be able
test again before the weekend. The nullmodem cable was only borrowed and
it takes some time for my own to arrive.

Which switches do I have to set during configure to get a debug version?

I will start a new thread on xen-users when everything is set up. Just
clicked on the wrong mailto when starting this conversation.

  reply	other threads:[~2014-03-11 10:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10  9:59 Struggling with PCI-Passthrough Alexander Brychcy
2014-03-10 11:09 ` Andrew Cooper
2014-03-11 10:26   ` Alexander Brychcy [this message]
2014-03-11 10:49     ` Andrew Cooper
2014-03-24 19:18       ` Alexander Brychcy
2014-03-25 10:46         ` Gordan Bobic
2014-03-25 20:33           ` Alexander Brychcy
2014-03-25 23:40             ` Gordan Bobic

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=531EE4DD.2060607@brychcy.net \
    --to=bober@brychcy.net \
    --cc=xen-devel@lists.xen.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.