Bug 19748 – Zuweisung von PCI Geräten an eine virtuelle Instanz

Bug 19748 - Zuweisung von PCI Geräten an eine virtuelle Instanz


Summary:	Zuweisung von PCI Geräten an eine virtuelle Instanz

Status:	CLOSED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Virtualization - UVMM
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Duplicates:	49996 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-08-30 07:49 CEST by Tobias Scherer
Modified:	2023-06-28 10:46 CEST (History)
CC List:	5 users (show)

See Also:	30440
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016022921000954
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tobias Scherer

2010-08-30 07:49:37 CEST

siehe auch: http://forum.univention.de/viewtopic.php?f=33&t=1104

XEN unterstützt das Zuweisen eines PCI Gerätes des Hosts an einen dedizierten Gast. Eine Möglichkeit dies in UVMM abzubilden könnte geprüft werden.

Comment 1 Philipp Hahn

2011-02-24 13:34:25 CET

Das libvirt-Beispiel <http://libvirt.org/formatdomain.html#elementsUSB> führt zu folgendem minimalen XML-Beispiel, daß wohl auch von libvirt so weiterverarbeitet werden kann:

virsh domxml-to-native xen-sxpr <<__XML__
virsh domxml-to-native xen-xm   <<__XML__
<domain type='xen'>
  <name>N</name>
  <memory>524288</memory>
  <vcpu>1</vcpu>
  <bootloader>/usr/bin/pygrub</bootloader>
  <os>
    <type arch='x86_64' machine='xenpv'>linux</type>
  </os>
  <devices>
    <hostdev mode='subsystem' type='pci'>
      <source>
        <address bus='0x06' slot='0x00' function='0x0'/>
      </source>
    </hostdev>
  </devices>
</domain>
__XML__

Das ganze ist allerdings derzeit ungetestet.

De Relax-NG Validierung in libvirt (0.8.8) ist derzeit noch fehlerhaft, was aber die Verwendung prinzipiell nicht verhindern sollte. Fehlerbeschreibung+Patch: <http://www.mail-archive.com/libvir-list@redhat.com/msg34029.html>

Comment 2 Tim Petersen

2013-04-04 08:16:55 CEST

Erneut an http://forum.univention.de/viewtopic.php?f=11&t=2511&p=8590 angefragt.

Comment 3 Jens Thorp-Hansen

2015-05-27 10:44:52 CEST

requested again: http://forum.univention.de/viewtopic.php?f=43&t=4016&p=14672

Comment 4 Jens Thorp-Hansen

2016-03-01 14:31:07 CET

Ticket#2016022921000954 - requested again

Comment 5 Philipp Hahn

2019-08-13 17:26:39 CEST

*** Bug 49996 has been marked as a duplicate of this bug. ***

Comment 6 Ingo Steuwer

2019-08-15 10:18:14 CEST

I assume that PCI passthrough won't work in live migrations, so in case we implement this we would need to block live migration for these instances. I'm unsure if the requester of this feature are aware of that?

Comment 7 Philipp Hahn

2019-08-15 10:22:48 CEST

(In reply to Ingo Steuwer from comment #6)
> I assume that PCI passthrough won't work in live migrations,

yes

> so in case we
> implement this we would need to block live migration for these instances.

libvirt already does that.
The duplicate Bug #49996 specifically requested network interface passthrough, which is special, as modern network interface adapters have native virtualization support: Passing them through to the VM does *not* block migration (as long as the source and target system support SR-IOV)

> I'm unsure if the requester of this feature are aware of that?

Comment 8 Ingo Steuwer

2020-07-03 20:51:38 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.