[vfio-users] [FEEDBACK NEEDED] Rewriting the Arch wiki article

thibaut noah thibaut.noah at gmail.com
Tue Apr 19 01:51:23 UTC 2016


Correct me if i'm wrong but i think the only thing you need to do in order
to have a bridge on the virtual machine is to create a bridge in your xml
with the <source bridge='your bridge name'/> in it. (if you have a bridge
set on the host with said name of course)
If i'm right even the mac adress on it is rubbish and can be anything as
long as it can be a valid mac adress?

If that's the case what we need on a wiki is a simple how to do a bridge on
the host with something not cumbersome and easy to setup like netctl and an
example of a bridge as it should be in the xml, thus people could just copy
paste the code, modify the bridge name to their needs and have something
that works out of the box without bothering themselves.


2016-04-19 1:03 GMT+02:00 Nicolas Roy-Renaud <
nicolas.roy-renaud.1 at ens.etsmtl.ca>:

> I'd put the networking stuff, synergy and all that into some sort of
> "Potential improvements" section and link to related pages instead, to
> avoid filling the vfio page with unrelated content for the sake of having
> an entire guide in one place.
>
> About the bridge, double-check the output of `ip a` or `networkctl` if
> you're using systemd-networkd, to make sure that your bridge is properly
> setup as the primary network interface and that nothing else is trying to
> use eth0/enp0s0.
>
> Nicolas
>
>
> On 2016-04-18 18:56, Garland Key wrote:
>
> I just tried this and as soon as I start the VM, my bridge on the host
> fails and defaults to the wired connection.
>
> I think that if the pci-passthrough wiki is going to talk about synergy as
> an input solution, then it should also discuss creating a bridge, since
> it's necessary in order to accomplish said goal.
>
> On Mon, Apr 18, 2016 at 6:22 PM, Jonas Camillus Jeppesen <
> <jonascj at sdu.dk>jonascj at sdu.dk> wrote:
>
>> On a fresh Arch install (no desktop environment, no network manager) I
>> added a bridge like this with systemd's networkd service:
>> https://wiki.archlinux.org/index.php/Systemd-networkd#DHCP_with_two_distinct_IP
>> . Then in virt-manager under network adapter I just choose "Specify shared
>> device name" as "Network source" and type in "br0" which is the name I gave
>> my bridge.
>>
>> This page is unnecessarily complicated it seems to me:
>> <https://wiki.archlinux.org/index.php/QEMU#Networking>
>> https://wiki.archlinux.org/index.php/QEMU#Networking
>>
>> The Arch wiki page on vfio isn't really about networking in qemu/kvm, but
>> a note could be added to visit the KVM and QEMU pages, and those could then
>> be updated to mention this systemd-networkd example.
>>
>> On 04/18/2016 11:57 PM, Bronek Kozicki wrote:
>>
>> For me setting up networking with an existing bridge "just works", I
>> wrote few days ago on this lis how I've set it up on my machine. Hint: I do
>> not use virsh "networks" capabilities at all - none defined (undefined the
>> default one) and none started. Just my, manually crafted bridge, explicitly
>> used in VM definitions.
>>
>>
>> B.
>>
>> *From: *Garland Key
>> *Sent: *Monday, 18 April 2016 22:21
>> *To: *Nicolas Roy-Renaud; vfio-users
>> *Subject: *Re: [vfio-users] [FEEDBACK NEEDED] Rewriting the Arch wiki
>> article
>>
>> I'm an intermediate Linux user, so this this stuff can be complicated to
>> me sometimes.  Right now I'm having trouble setting up a network bridge
>> that virt-manager will recognize.  I've arrived at the conclusion that this
>> simply isn't possible on Arch.  That said, I can't find any documentation
>> on how to convince qemu to use an existing network bridge.  If you're
>> willing, please add this information as well.  If you already know how, any
>> pointers would be greatly appreciated.
>>
>> Best,
>> Garland
>>
>> On Mon, Apr 18, 2016 at 5:14 PM, Garland Key <
>> <david.garland.key at gmail.com>david.garland.key at gmail.com> wrote:
>>
>>> Please add what to do if you have two identical GPUs.  Here is exactly
>>> what is needed to make it work.
>>>
>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>>> - - - -
>>>
>>> * /etc/modprobe.d/vfio.conf*
>>>
>>>     install vfio-pci /sbin/vfio-pci-override-vga.sh
>>>     options vfio-pci disable_vga=1 allow_unsafe_interrupts=1
>>>
>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>>> - - - -
>>>
>>> */sbin/vfio-pci-override-vga.sh*
>>>
>>>     #!/bin/sh
>>>
>>>     for i in $(find /sys/devices/pci* -name boot_vga); do
>>>             if [ $(cat $i) -eq 0 ]; then
>>>                     GPU=$(dirname $i)
>>>                     AUDIO=$(echo $GPU | sed -e "s/0$/1/")
>>>                    echo "vfio-pci" > $GPU/driver_override
>>>                     if [ -d $AUDIO ]; then
>>>                             echo "vfio-pci" > $AUDIO/driver_override
>>>                     fi
>>>             fi
>>>     done
>>>
>>>     modprobe -i vfio-pci
>>>
>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>>> - - - -
>>>
>>> Add the following to */etc/mkinitcpio.conf* and then run *mkinitcpio -p
>>> linux*
>>>
>>>     BINARIES="/usr/bin/find /usr/bin/dirname"
>>>     FILES="/sbin/vfio-pci-override-vga.sh"
>>>
>>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>>> - - - -
>>>
>>> *Tested Hardware:*
>>>
>>> Motherboard: Asus Sabertooth X99
>>> <https://www.asus.com/us/Motherboards/SABERTOOTH_X99/>
>>> CPU: Intel Core i7-5930K
>>> <http://ark.intel.com/products/82931/Intel-Core-i7-5930K-Processor-15M-Cache-up-to-3_70-GHz>
>>> GPU 1: GIGABYTE GeForce GTX 970 4GB G1 Gaming OC Edition
>>> <http://www.newegg.com/Product/Product.aspx?Item=N82E16814125684>
>>> GPU 2: GIGABYTE GeForce GTX 970 4GB G1 Gaming OC Edition
>>> <http://www.newegg.com/Product/Product.aspx?Item=N82E16814125684>
>>> RAM: 32GB Corsair Dominator Platinum DDR4 (CMD16GX4M2A2666C15)
>>> <http://www.newegg.com/Product/Product.aspx?Item=N82E16820233709>
>>>
>>>
>>> On Tue, Apr 12, 2016 at 3:36 PM, Nicolas Roy-Renaud <
>>> nicolas.roy-renaud.1 at ens.etsmtl.ca> wrote:
>>>
>>>> I'm currently planning a full rewrite of the article on Arch wiki
>>>> about PCI passthroughs
>>>> <https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF> and,
>>>> as per Arch wiki guidelines, I'm supposed get the approval of other users
>>>> before undergoing such comlex edits. If anyone on this mailing list is an
>>>> Arch wiki collaborator or frequent user, I would appreciate if you could give
>>>> me some feedback on the planned structure
>>>> <https://wiki.archlinux.org/index.php/Talk:PCI_passthrough_via_OVMF#Page_rewrite>
>>>> and propose additional sections or potential user mistakes to highlight. My
>>>> primary objective here is to make most of what's on Alex Williamson's blog
>>>> more straightforward and concise.
>>>>
>>>> I've already rewritten the first two sections ("Prerequisites" and
>>>> "Setting up IOMMU"), and the rest of the article should essentially follow
>>>> the same basic structure and style. Replies here or on the wiki's
>>>> discussion page would be much appreciated.
>>>>
>>>> -Nicolas
>>>>
>>>> _______________________________________________
>>>> vfio-users mailing list
>>>> vfio-users at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/vfio-users
>>>>
>>>>
>>>
>>
>>
>>
>> _______________________________________________
>> vfio-users mailing listvfio-users at redhat.comhttps://www.redhat.com/mailman/listinfo/vfio-users
>>
>>
>>
>> _______________________________________________
>> vfio-users mailing list
>> vfio-users at redhat.com
>> https://www.redhat.com/mailman/listinfo/vfio-users
>>
>>
>
>
> _______________________________________________
> vfio-users mailing listvfio-users at redhat.comhttps://www.redhat.com/mailman/listinfo/vfio-users
>
>
>
> _______________________________________________
> vfio-users mailing list
> vfio-users at redhat.com
> https://www.redhat.com/mailman/listinfo/vfio-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20160419/57ff679b/attachment.htm>


More information about the vfio-users mailing list