On Thu, Nov 17, 2016 at 10:32 AM, Grundmann, Christian < christian.grundm...@fabasoft.com> wrote:
> Hi, > > @ Probably because containers in Windows actually run inside VMs, > therefore using nested Virtualization. > > that’s not true anymore for Server 2016, > > they have “real“ container Support now > Good to know. I've read differently at [1], but I may have not understood it fully: " In order to run Hyper-V containers, the Hyper-V role is required. If the Windows container host is itself a Hyper-V virtual machine, nested virtualization will need to be enabled before installing the Hyper-V role. For more information on nested virtualization, see Nested Virtualization." I think my confusion is between 'Windows Containers' and 'Hyper-V Containers' (which are similar to running containers on Atomic guests, I reckon, though we do not require nested virtualization for that). The other article[2] hints at what changes are needed for networking to work. Perhaps related to this issue. Y. [1] https://msdn.microsoft.com/en-us/virtualization/windowscontainers/deployment/deployment [2] https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/user_guide/nesting > > > > > > *Von:* Yaniv Kaul [mailto:yk...@redhat.com] > *Gesendet:* Mittwoch, 16. November 2016 23:13 > *An:* Grundmann, Christian <christian.grundm...@fabasoft.com> > *Cc:* Gal Hammer <gham...@redhat.com>; Dan Kenigsberg <dan...@redhat.com>; > users@ovirt.org > > *Betreff:* Re: [ovirt-users] Windows Server Container Support > > > > On Nov 16, 2016 7:54 PM, "Grundmann, Christian" < > christian.grundm...@fabasoft.com> wrote: > > > > Hi, > > i tried a few vnic configurations, > > looks like it works with e1000 > > but with virtio i have the problem > > > > @ How did the VM die? Is there an error message in > /var/log/vdsm/vdsm.log, or /var/log/libvirt/qemu/* > > The VM dies at OS Level, it boots but most oft he services are not > starting, so no network and many other things not working > > Probably because containers in Windows actually run inside VMs, therefore > using nested Virtualization. > Y. > > > > > > > > > -----Ursprüngliche Nachricht----- > > Von: Dan Kenigsberg [mailto:dan...@redhat.com] > > Gesendet: Mittwoch, 16. November 2016 17:48 > > An: Grundmann, Christian <christian.grundm...@fabasoft.com> > > Cc: users@ovirt.org; gham...@redhat.com > > Betreff: Re: [ovirt-users] Windows Server Container Support > > > > On Wed, Nov 16, 2016 at 12:28:30PM +0000, Grundmann, Christian wrote: > > > Hi, > > > I tried installing Windows Server 2016 and enabling Container Support > > > and Docker But after enabling Docker, the VM dies. > > > All Network related services are timeouting when booting the Server. > > > If I unplug the NIC the VMs starts normally and Docker works > > > > > > I tried to enable the macspoof vdsm hook but it doesn't help > > > > > > Anything else I can try? > > > > > > Thx Christian > > > > Could you give more details? > > > > How did the VM die? Is there an error message in /var/log/vdsm/vdsm.log, > or /var/log/libvirt/qemu/* > > > > How was the VM defined? Which type was the vNIC? > > _______________________________________________ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users