systemctl restart network, VMs and suspend

[fedora]

On 2014-06-07 12:24, Mateusz Marzantowicz wrote:
> On 30.05.2014 10:06, Aleksandar Kostadinov wrote:
>> Hello,
>>
>> I already filed a bugzilla issue with this [1] but I'd like to know if
>> anybody else has troubles with VMs' network after suspend. And if others
>> are able to do a "systemctl restart network" successfully.
>>
>> I mean, am I an isolated case because of some unknown configuration I
>> have or is this common?
>>
>> What I do is:
>> launch VM
>> suspend laptop
>> wake up laptop after awhile (1 hour maybe)
>> network of VM loses default route
>> systemctl restart network # fails on both fedora 20 - guest and host
>>
>> I'll appreciate if somebody else with same experience comments in the
>> bugzilla issue directly.
>>
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1100034
>
> What kind of virtualization technology are you using? What kind of
> networking setup do you have (bridged, NAT-ed, host-only). Does your
> laptop connect with network using wireless or Ethernet card? Why aren't
> you using Network Manager for managing your network? What do you mean by
> "systemctl restart network fails" (could you post here some log messages?)
>
>
> Mateusz Marzantowicz


I do Virtualization using VirtualBox.
The VMs are from WindowsXP, Windows7, Fedora Linux, Solaris, FreeBSD, 
OpenBSD, you name it.
But I never hibernate nor suspend the Host system, while a VM is 
running, I always do a Save-the-machine-State on all VMs before I 
hibernate or suspend the Host.
And when I wake up the Host, usually the VMs come up when waked up 
whithout problems.

suomi