From: Simon Martin <furryfuttock@gmail.com>
To: xen-devel@lists.xen.org
Subject: Problems accessing passthrough PCI device
Date: Thu, 13 Nov 2014 10:29:21 -0300 [thread overview]
Message-ID: <198478230.20141113102921@gmail.com> (raw)
Hi all,
I am back on my virtual machine once again and have run into a bit of
a problem (once again). So I am coming to you cap in hand...
I am having 2 major problems at the moment.
1.- Access to the PCI device from the PV will fail the second time I
create it UNLESS I call xl pci-assignable-remove/pci-assignable-add
between each creation. If I don't do this then all PCI accesses return
-1. I get the same if I disable memory access in the PCI configuration
register.
1.1.- Is this expected behaviour?
1.2.- If not, how do I work around it? I have looked at
HYPERVISOR_physdev_op but I'm not sure how/whether to use it.
1.3.- xl dmesg and dmesg in Dom0 do not show anything. I have set
loglvl=all in the Xen command line.
2.- Whenever I perform a software reset on the PCI device (it is an
Intel 82546 Ethernet NIC) the hypervisor crashes. There is no oops,
kernel panic or the like, just a crash. My development device has no
serial port so I can't do much debugging.
Any suggestions.
--
Best regards,
Simon mailto:furryfuttock@gmail.com
next reply other threads:[~2014-11-13 13:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 13:29 Simon Martin [this message]
2014-11-13 14:08 ` Problems accessing passthrough PCI device Jan Beulich
2014-11-13 15:07 ` Simon Martin
2014-11-13 15:52 ` Jan Beulich
2014-11-13 17:49 ` Simon Martin
2014-11-13 19:03 ` Konrad Rzeszutek Wilk
2014-11-13 19:21 ` Simon Martin
2014-11-13 19:29 ` Konrad Rzeszutek Wilk
2014-11-18 16:25 ` Simon Martin
2014-11-14 8:27 ` Jan Beulich
2014-11-18 16:24 ` Simon Martin
2014-11-18 16:49 ` Jan Beulich
2014-11-19 15:12 ` Simon Martin
2014-11-19 20:53 ` Konrad Rzeszutek Wilk
2014-11-21 16:53 ` Simon Martin
2014-11-21 17:26 ` Konrad Rzeszutek Wilk
2014-11-20 8:51 ` Jan Beulich
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=198478230.20141113102921@gmail.com \
--to=furryfuttock@gmail.com \
--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.