Re: Tip: qemu-kvm and network-scripts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2020-04-27 16:34, Samuel Sieb wrote:
> On 4/26/20 10:22 PM, Ed Greshko wrote:
>> On 2020-04-27 12:59, ToddAndMargo via users wrote:
>>> On 2020-04-26 20:53, Ed Greshko wrote:
>>>> On 2020-04-27 11:49, ToddAndMargo via users wrote:
>>>>> both physical network cards are on the host machine.  the
>>>>> vm's connect through qemu-kvm "Network bridge: br0" to
>>>>> the host machines and then get routed to the internet
>>>>> through en12, via iptables
>>>>
>>>> Yes, I know what you've done.  I just don't know why.
>>>>
>>>> I have full connectivity using the virtual devices.  So, same question.  Why use physical HW?
>>>
>>> Because it simulates actual servers I have installed.
>>> eno2 is hooked to the internet and eno1 is hoooked
>>> up to a [switching] hub that fans out to multiple client
>>> workstations.  The server is also the firewall
>>
>> What would not work if you used Virtual HW instead of actual HW?
>>
>> All of my VM's can access all of the other servers on 3 different LAN segments.
>
> My understanding of his explanation is that the second ethernet is a private network connecting his VMs to other physical computers.
>

Right.  I suppose there may be situations one would want that.  I've just not had the need.

I noted that the ifcfg-br0 script contained NM_CONTROLLED=no.  I never had, and I don't know
if it is possible, to have a mixture of connections with some controlled by NM and others not. 

The first issue that I would see is that /usr/sbin/ifdown points to a /etc/alternatives entry.  So, you'd either
be calling the NM version which is a script that uses nmcli or the network-scripts version which doesn't
So, I believe you'd have compatibility issues.


-- 
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux