On Dec 4, 2014 4:29 AM, "Ian Campbell" wrote:
>
> On Wed, 2014-12-03 at 21:31 -0400, Konrad Rzeszutek Wilk wrote:
> > so something is busted as you surmised
>
> I haven't been following closely, so this may be completely unrelated to
> the issue under discussion, but doesn't in-HVM-guest hotplug r
On Wed, 2014-12-03 at 21:31 -0400, Konrad Rzeszutek Wilk wrote:
> so something is busted as you surmised
I haven't been following closely, so this may be completely unrelated to
the issue under discussion, but doesn't in-HVM-guest hotplug require a
guest side driver to be loaded? I recall in the d
On Wed, Dec 03, 2014 at 09:31:03PM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Dec 01, 2014 at 12:01:51PM -0500, Konrad Rzeszutek Wilk wrote:
> > On Mon, Dec 01, 2014 at 02:32:44PM +0100, Olaf Hering wrote:
> > > On Mon, Dec 01, Olaf Hering wrote:
> > >
> > > > # xl pci-assignable-add 01:10.0
>
On Mon, Dec 01, 2014 at 12:01:51PM -0500, Konrad Rzeszutek Wilk wrote:
> On Mon, Dec 01, 2014 at 02:32:44PM +0100, Olaf Hering wrote:
> > On Mon, Dec 01, Olaf Hering wrote:
> >
> > > # xl pci-assignable-add 01:10.0
> > > # xl pci-assignable-list
> > > :01:10.0
> > > # xl create -f domU.cfg
> >
On Wed, Dec 03, Olaf Hering wrote:
> On Tue, Dec 02, Konrad Rzeszutek Wilk wrote:
> > On Tue, Dec 02, 2014 at 04:46:52PM +0100, Olaf Hering wrote:
> > > On Mon, Dec 01, Konrad Rzeszutek Wilk wrote:
> > ACPI hotplug. And it does work after PCI discovery.
> In a pvops kernel, is the emulated but unp
On Tue, Dec 02, Konrad Rzeszutek Wilk wrote:
> On Tue, Dec 02, 2014 at 04:46:52PM +0100, Olaf Hering wrote:
> > On Mon, Dec 01, Konrad Rzeszutek Wilk wrote:
> >
> > > That is odd - I see any device 'hot-plugged' being added at 00:05 and
> > > further.
> >
> > Does this by any chance depend on t
On Tue, Dec 02, 2014 at 04:46:52PM +0100, Olaf Hering wrote:
> On Mon, Dec 01, Konrad Rzeszutek Wilk wrote:
>
> > That is odd - I see any device 'hot-plugged' being added at 00:05 and
> > further.
>
> Does this by any chance depend on the guest?! I mean, how is the guest
I doubt it.
> notified
On Mon, Dec 01, Konrad Rzeszutek Wilk wrote:
> That is odd - I see any device 'hot-plugged' being added at 00:05 and further.
Does this by any chance depend on the guest?! I mean, how is the guest
notified that a PCI device is gone (by unplug)? Maybe the pvops case
just happens to work because th
On Mon, Dec 01, Sander Eikelenboom wrote:
> Monday, December 1, 2014, 3:34:09 PM, you wrote:
> > actually be a workaround for the double pci-attach bug.
> Don't know about that bug.
You just replied to it. ;-)
Olaf
___
Xen-devel mailing list
Xen-devel
On Mon, Dec 01, 2014 at 02:32:44PM +0100, Olaf Hering wrote:
> On Mon, Dec 01, Olaf Hering wrote:
>
> > # xl pci-assignable-add 01:10.0
> > # xl pci-assignable-list
> > :01:10.0
> > # xl create -f domU.cfg
> > # xl console domU
> > ## lspci gives just emulated PCI devices
>
> ttyS0:Rescue:~ #
Monday, December 1, 2014, 3:34:09 PM, you wrote:
> On Mon, Dec 01, Sander Eikelenboom wrote:
>> Hmm the wiki also still mentions it:
>> http://wiki.xen.org/wiki/Xen_PCI_Passthrough
>>
>> It was the ability with xend + qemu-trad to be able to specify the slot to
>> use in the guest for the pci
On Mon, Dec 01, Ian Campbell wrote:
> On Mon, 2014-12-01 at 15:34 +0100, Olaf Hering wrote:
> > On Mon, Dec 01, Sander Eikelenboom wrote:
> > > Hmm the wiki also still mentions it:
> > > http://wiki.xen.org/wiki/Xen_PCI_Passthrough
> > >
> > > It was the ability with xend + qemu-trad to be able
On Mon, 2014-12-01 at 15:34 +0100, Olaf Hering wrote:
> On Mon, Dec 01, Sander Eikelenboom wrote:
>
> > Hmm the wiki also still mentions it:
> > http://wiki.xen.org/wiki/Xen_PCI_Passthrough
> >
> > It was the ability with xend + qemu-trad to be able to specify the slot to
> > use in the guest f
On Mon, Dec 01, Sander Eikelenboom wrote:
> Hmm the wiki also still mentions it:
> http://wiki.xen.org/wiki/Xen_PCI_Passthrough
>
> It was the ability with xend + qemu-trad to be able to specify the slot to
> use in the guest for the pci device.
>
> See docs/misc/vtd.txt .. that seems it has n
Monday, December 1, 2014, 2:42:11 PM, you wrote:
> On Mon, Dec 01, Olaf Hering wrote:
>> > # xl pci-attach domU :01:10.0
> "xl pci-attach -h" mentions [Virtual Slot], but the code does not seem
> to handle an additional parameter, pciattach() ignores *vs.
> What is the "Virtual Slot", why
On Mon, Dec 01, Olaf Hering wrote:
> > # xl pci-attach domU :01:10.0
"xl pci-attach -h" mentions [Virtual Slot], but the code does not seem
to handle an additional parameter, pciattach() ignores *vs.
What is the "Virtual Slot", why is it ignored?
Olaf
_
On Mon, Dec 01, Olaf Hering wrote:
> # xl pci-assignable-add 01:10.0
> # xl pci-assignable-list
> :01:10.0
> # xl create -f domU.cfg
> # xl console domU
> ## lspci gives just emulated PCI devices
ttyS0:Rescue:~ # lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev
I tried to attach a PCI device (IGB Virtual Function) to a HVM guest.
To actually get it assigned its required to run
pci-attach/pci-detach/pci-attach because it does not show up right away.
Did anyone noticed this bug already, is there a fix? There is no error
reported in dom0 dmesg, xl dmesg or
18 matches
Mail list logo
