On Sun, 2016-04-17 at 12:07 -0700, Samuel Sieb wrote:
> On 04/17/2016 06:31 AM, 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 means that the network will not be working.
Thanks, I kinda guessed that ...
> >
> > 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.
> >
> It's not clear to me from your description what you are trying to
> do.
> If you aren't trying to access Windows from anywhere else, then the
> default network is what you want. In the Virtual Machine Manager,
> select the Edit->Connection Details menu item. Go to the Virtual
> Networks tab and check why the default network isn't started.
I get:
Error starting network 'default': internal error: Network is already
in use by interface virbr0.
The "State" in the same window is shown as Inactive. The NetworkManager
status for virbr0 is Connected, which may explain the problem but I've
no idea what it's connected to. I have no other VMs running.
poc
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
http://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
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
