On 19 April 2016 at 12:22, Patrick O'Callaghan <pocallag...@gmail.com> wrote:
> On Mon, 2016-04-18 at 12:56 -0700, Samuel Sieb wrote: > > On 04/18/2016 05:19 AM, Patrick O'Callaghan wrote: > > > > > > On Sun, 2016-04-17 at 14:31 +0100, Patrick O'Callaghan wrote: > > > > > > > > I've been occasionally using a Windows 7 VM with the libvirt > > > > system > > > > for > > > > several months now and have had no problems up to now. However > > > > recently > > > > I've been getting error messages from Windows about the network > > > > being > > > > "unknown" and my shared host/guest volume is unavailable. On the > > > > most > > > > recent attempt I see: > > > > > > > > Virtual network 'default': NAT (Inactive) > > > > > > > > as the entry under the Network Source drop-down in Virtual > > > > Machine > > > > Manager's "Show Hardware Details" menu. > > > > > > > > This is most likely PEBKAC but I'd be grateful for a newbie's > > > > guide > > > > to > > > > how this stuff should be set up without straying too far from > > > > defaults. > > > > My goal is pretty simple: a bridged network to get shared folders > > > > with > > > > my Fedora 23 host and Internet client access from the guest. > > > I still have no idea how this happened, but I found the fix here: > > > > > > http://ask.xmodulo.com/network-default-is-not-active.html > > > > > > and it worked. > > > > > Have you tried rebooting since then? Does it still work? I don't > > think > > you should have an ifcfg file for that interface as you don't want > > NetworkManager interacting with it. If everything still works after > > rebooting, then great. Otherwise, try removing that file. > > Good call. It failed again on rebooting. I removed the file and > rebooted again and now it works. > > Is one supposed to know this by magic? I can't be the only one who's > had this problem. I read the Release Notes every time I update the > system and can't recall seeing it anywhere. > > > Note that a standard install has no ifcfg-virbr0 config ... it's handled entirely by libvirt Remove that file entirely and let libvirt handle setting up the NAT interface If something puts it back then put NM_CONTROLLED=no in the file to prevent NM from using it.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
