On Nov 16, 2016 7:54 PM, "Grundmann, Christian" <Christian.Grundmann@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:danken@redhat.com]
> Gesendet: Mittwoch, 16. November 2016 17:48
> An: Grundmann, Christian <Christian.Grundmann@fabasoft.com>
> Cc: users@ovirt.org; ghammer@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