Hello,
I installed VS2005R2 on a HW with 2 NICs (host OS is WS2003R2 SP2).

As advised by VS Administration guide, I reserved one NIC for the
host, unbinding the VS service, and the other one to the VMs, binding
only the VS service.
Then I created a Virtual Network for VMs, which uses this NIC

Sometimes, when I start a VM, I get this error: "VMname could not
initialize emulated Ethernet controller", and in fact, when the VM is
up, it has no NIC and so no network....

From the VS console, in the "failing" VM configuration I correctly see
the "Virtual Network Adapter 1", bound to the correct Virtual Network.

The only way I can fix this is to turn off the VM, and remove and
readd its Virtual Network Adapter.

Any idea?

Thanks

k

On 18 Mar, 11:05, karamatic <karama...@libero.it> wrote:
> Hello,
> I installed VS2005R2 on a HW with 2 NICs (host OS is WS2003R2 SP2).
>
> As advised by VS Administration guide, I reserved one NIC for the
> host, unbinding the VS service, and the other one to the VMs, binding
> only the VS service.
> Then I created a Virtual Network for VMs, which uses this NIC
>
> Sometimes, when I start a VM, I get this error: "VMname could not
> initialize emulated Ethernet controller", and in fact, when the VM is
> up, it has no NIC and so no network....
>
> From the VS console, in the "failing" VM configuration I correctly see
> the "Virtual Network Adapter 1", bound to the correct Virtual Network.
>
> The only way I can fix this is to turn off the VM, and remove and
> readd its Virtual Network Adapter.
>
> Any idea?
>
> Thanks
>
> k

If this can : the error occurs when booting VMs after the VS
service is restarted... If I restart VMs withour restarting the VS
service, I don't get the error.
Thanks
k

On 18 Mar, 13:55, karamatic <karama...@libero.it> wrote:
> On 18 Mar, 11:05, karamatic <karama...@libero.it> wrote:
>
>
>
>
>
> > Hello,
> > I installed VS2005R2 on a HW with 2 NICs (host OS is WS2003R2 SP2).
>
> > As advised by VS Administration guide, I reserved one NIC for the
> > host, unbinding the VS service, and the other one to the VMs, binding
> > only the VS service.
> > Then I created a Virtual Network for VMs, which uses this NIC
>
> > Sometimes, when I start a VM, I get this error: "VMname could not
> > initialize emulated Ethernet controller", and in fact, when the VM is
> > up, it has no NIC and so no network....
>
> > From the VS console, in the "failing" VM configuration I correctly see
> > the "Virtual Network Adapter 1", bound to the correct Virtual Network.
>
> > The only way I can fix this is to turn off the VM, and remove and
> > readd its Virtual Network Adapter.
>
> > Any idea?
>
> > Thanks
>
> > k
>
> If this can : the error occurs when booting VMs after the VS
> service is restarted... If I restart VMs withour restarting the VS
> service, I don't get the error.
> Thanks

Hello,
I read some similar cases in the NG, so I understood the NIC drivers
had to be changed.
I installed up-tp-date drivers (we're talking about an HP DL360 G5
with Broadcom Multifunction NIC drivers) and I also unistalled the HP
Network Config Utility, to have the simpler situation possibile. I
disabled one NIC and activated the VS service, and the usual other
network services, all on the remaining NIC - again, to have the
"plainest" situation possibile for my test.
Well, nothing changed.
Again, each time the server starts (or the Virtual Server service is
restarted), when VMs boot they "cannot initialize emulated ethernet
controller" and, again, to fix this I have just to enter the VS admin
site, go to Virtual Network\Configure\<VNname> (the one used byt the
VMs, bound to the only NIC enabled) \Network Settings and just click
"OK"....

At this point I really don't know what else I could try!

thanks for any ...

k

On 10 Apr, 10:43, karamatic <karama...@libero.it> wrote:
> On 18 Mar, 13:55, karamatic <karama...@libero.it> wrote:
>
> > On 18 Mar, 11:05, karamatic <karama...@libero.it> wrote:
>
> > > Hello,
> > > I installed VS2005R2 on a HW with 2 NICs (host OS is WS2003R2 SP2).
>
> > > As advised by VS Administration guide, I reserved one NIC for the
> > > host, unbinding the VS service, and the other one to the VMs, binding
> > > only the VS service.
> > > Then I created a Virtual Network for VMs, which uses this NIC
>
> > > Sometimes, when I start a VM, I get this error: "VMname could not
> > > initialize emulated Ethernet controller", and in fact, when the VM is
> > > up, it has no NIC and so no network....
>
> > > From the VS console, in the "failing" VM configuration I correctly see
> > > the "Virtual Network Adapter 1", bound to the correct Virtual Network.
>
> > > The only way I can fix this is to turn off the VM, and remove and
> > > readd its Virtual Network Adapter.
>
> > > Any idea?
>
> > > Thanks
>
> > > k
>
> > If this can : the error occurs when booting VMs after the VS
> > service is restarted... If I restart VMs withour restarting the VS
> > service, I don't get the error.
> > Thanks
>
> Hello,
> I read some similar cases in the NG, so I understood the NIC drivers
> had to be changed.
> I installed up-tp-date drivers (we're talking about an HP DL360 G5
> with Broadcom Multifunction NIC drivers) and I also unistalled the HP
> Network Config Utility, to have the simpler situation possibile. I
> disabled one NIC and activated the VS service, and the usual other
> network services, all on the remaining NIC - again, to have the
> "plainest" situation possibile for my test.
> Well, nothing changed.
> Again, each time the server starts (or the Virtual Server service is
> restarted), when VMs boot they "cannot initialize emulated ethernet
> controller" and, again, to fix this I have just to enter the VS admin
> site, go to Virtual Network\Configure\<VNname> (the one used byt the
> VMs, bound to the only NIC enabled) \Network Settings and just click
> "OK"....
>
> At this point I really don't know what else I could try!
>
> thanks for any ...
>
> k

Tried also to disable offload settings on the NIC (thanks for the
hint, Bill...), but still no result.
I cheked HP site and my drivers are now the most up-to-date....
Any other idea?

thanks!
k

On 10 Apr, 14:11, karamatic <karama...@libero.it> wrote:
> On 10 Apr, 10:43,karamatic<karama...@libero.it> wrote:
>
>
>
>
>
> > On 18 Mar, 13:55,karamatic<karama...@libero.it> wrote:
>
> > > On 18 Mar, 11:05,karamatic<karama...@libero.it> wrote:
>
> > > > Hello,
> > > > I installed VS2005R2 on a HW with 2 NICs (host OS is WS2003R2 SP2).
>
> > > > As advised by VS Administration guide, I reserved one NIC for the
> > > > host, unbinding the VS service, and the other one to the VMs, binding
> > > > only the VS service.
> > > > Then I created a Virtual Network for VMs, which uses this NIC
>
> > > > Sometimes, when I start a VM, I get this error: "VMname could not
> > > > initialize emulated Ethernet controller", and in fact, when the VM is
> > > > up, it has no NIC and so no network....
>
> > > > From the VS console, in the "failing" VM configuration I correctly see
> > > > the "Virtual Network Adapter 1", bound to the correct Virtual Network.
>
> > > > The only way I can fix this is to turn off the VM, and remove and
> > > > readd its Virtual Network Adapter.
>
> > > > Any idea?
>
> > > > Thanks
>
> > > > k
>
> > > If this can : the error occurs when booting VMs after the VS
> > > service is restarted... If I restart VMs withour restarting the VS
> > > service, I don't get the error.
> > > Thanks
>
> > Hello,
> > I read some similar cases in the NG, so I understood the NIC drivers
> > had to be changed.
> > I installed up-tp-date drivers (we're talking about an HP DL360 G5
> > with Broadcom Multifunction NIC drivers) and I also unistalled the HP
> > Network Config Utility, to have the simpler situation possibile. I
> > disabled one NIC and activated the VS service, and the usual other
> > network services, all on the remaining NIC - again, to have the
> > "plainest" situation possibile for my test.
> > Well, nothing changed.
> > Again, each time the server starts (or the Virtual Server service is
> > restarted), when VMs boot they "cannot initialize emulated ethernet
> > controller" and, again, to fix this I have just to enter the VS admin
> > site, go to Virtual Network\Configure\<VNname> (the one used byt the
> > VMs, bound to the only NIC enabled) \Network Settings and just click
> > "OK"....
>
> > At this point I really don't know what else I could try!
>
> > thanks for any ...
>
> > k
>
> Tried also to disable offload settings on the NIC (thanks for the
> hint, Bill...), but still no result.
> I cheked HP site and my drivers are now the most up-to-date....
> Any other idea?
>
> thanks!

Just tried also to remove and reinstall the virtual network services
from the host's network connection properties (tip found on Ben
Armstrong's blog).
Same as before!!!
! :-)

k

On Thu, 17 Apr 2008 01:44:06 -0700 (PDT), karamatic wrote:

> Just tried also to remove and reinstall the virtual network services
> from the host's network connection properties (tip found on Ben
> Armstrong's blog).
> Same as before!!!

At some point you are likely going to have to open a support case with
Microsoft Support.

--
Paul Adare
http://www.identit.ca
This fortune soaks up 47 times its own weight in excess memory.

Option 3 on this page was the only thing that worked for me. Hope it s!

http://support.microsoft.com/kb/555629/en-us

Cheers

Glen

"Paul Adare" wrote:

> On Thu, 17 Apr 2008 01:44:06 -0700 (PDT), karamatic wrote:
>
> > Just tried also to remove and reinstall the virtual network services
> > from the host's network connection properties (tip found on Ben
> > Armstrong's blog).
> > Same as before!!!
>
> At some point you are likely going to have to open a support case with
> Microsoft Support.
>
> --
> Paul Adare
> http://www.identit.ca
> This fortune soaks up 47 times its own weight in excess memory.
>

Same problem here, tried Windows 2003 R2 X64 host, Windows 2008 host and now
Windows 2003 R2 X86 host all with Virt Server 2005 SP1..... no nics on
virtual server clients (Win 2003 R2 X86). Added NIC's, changed NIC's nothing
works, also tried internal networking...
Tried all options in the kb article.

Any more ideas??
Thanks!






"Paul Adare" wrote:

> On Thu, 17 Apr 2008 01:44:06 -0700 (PDT), karamatic wrote:
>
> > Just tried also to remove and reinstall the virtual network services
> > from the host's network connection properties (tip found on Ben
> > Armstrong's blog).
> > Same as before!!!
>
> At some point you are likely going to have to open a support case with
> Microsoft Support.
>
> --
> Paul Adare
> http://www.identit.ca
> This fortune soaks up 47 times its own weight in excess memory.
>