Re: [one-users] opennebula 4.4 esxi 5.1 windows vms lose nic dirver

2013-12-13 Thread Tino Vazquez
Hi,

In the ESX, after the VM fails to boot, it should appear a vmware.log file in

/vmfs/volumes///disk.0

could you send it through?

Regards,

-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple

--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
www.c12g.com | @C12G | es.linkedin.com/in/tinova

--
Confidentiality Warning: The information contained in this e-mail and
any accompanying documents, unless otherwise expressly indicated, is
confidential and privileged, and is intended solely for the person
and/or entity to whom it is addressed (i.e. those identified in the
"To" and "cc" box). They are the property of C12G Labs S.L..
Unauthorized distribution, review, use, disclosure, or copying of this
communication, or any part thereof, is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify us
immediately by e-mail at ab...@c12g.com and delete the e-mail and
attachments and any copy from your system. C12G thanks you for your
cooperation.


On Tue, Dec 10, 2013 at 3:24 AM, hansz  wrote:
> Hi Tino,
> thinks for your replay,
> without the e1000 model (but has select virtual Networks) ,the VM boot, but
> does not has NIC driver. the vm i have ready install vmware tools
> the following are the steps i create a vm
> 1)i  first create vms throuht the vmware's esxi (while create the vm ,i
> select the network  ,and the model,after the vm boot ,i
> install the vmware tools,at that moment the vm has NIC driver,and i can ping
> to other vms),
> 2)and then tar the window-flat.vmdk and the disk.vmdk a xxx.tar.bz2
> 3) upload the xxx.tar.bz2 through the sunstone to the image ,
> 4)create template
> 5)create  vms
>
> but ,if i set model=e1000 at the template when the vm startup the vm will
> stay on the starting screen,
> else if i set model=E1000 at the template the vm will faild
> the log (for model=E1000)
> Tue Dec 10 04:58:00 2013 [DiM][I]: New VM state is ACTIVE.
> Tue Dec 10 04:58:00 2013 [LCM][I]: New VM state is PROLOG.
> Tue Dec 10 04:59:40 2013 [LCM][I]: New VM state is BOOT
> Tue Dec 10 04:59:40 2013 [VMM][I]: Generating deployment file:
> /var/lib/one/vms/30/deployment.0
> Tue Dec 10 04:59:41 2013 [VMM][I]: Successfully execute network driver
> operation: pre.
> Tue Dec 10 04:59:48 2013 [VMM][I]: Command execution fail:
> /var/lib/one/remotes/vmm/vmware/deploy '/var/lib/one/vms/30/deployment.0'
> 'esxi01' 30 esxi01
> Tue Dec 10 04:59:48 2013 [VMM][I]:
> /var/lib/one/remotes/vmm/vmware/vi_driver.rb:138:in `initialize': Cannot
> find VM one-30 (RuntimeError)
> Tue Dec 10 04:59:48 2013 [VMM][I]: from
> /var/lib/one/remotes/vmm/vmware/vmware_driver.rb:418:in `new'
> Tue Dec 10 04:59:48 2013 [VMM][I]: from
> /var/lib/one/remotes/vmm/vmware/vmware_driver.rb:418:in `handle_metadata'
> Tue Dec 10 04:59:48 2013 [VMM][I]: from
> /var/lib/one/remotes/vmm/vmware/vmware_driver.rb:398:in `define_domain'
> Tue Dec 10 04:59:48 2013 [VMM][I]: from
> /var/lib/one/remotes/vmm/vmware/vmware_driver.rb:88:in `deploy'
> Tue Dec 10 04:59:48 2013 [VMM][I]: from
> /var/lib/one/remotes/vmm/vmware/deploy:38
> Tue Dec 10 04:59:48 2013 [VMM][I]: ExitCode: 1
> Tue Dec 10 04:59:48 2013 [VMM][I]: Failed to execute virtualization driver
> operation: deploy.
> Tue Dec 10 04:59:48 2013 [VMM][E]: Error deploying virtual machine
> Tue Dec 10 04:59:48 2013 [DiM][I]: New VM state is FAILED
> anyother may be wrong ? wait for your replay ,thinks
>
>
>
>
>
>
>
> At 2013-12-09 22:44:36,"Tino Vazquez"  wrote:
>>Hi,
>>
>>Without the E1000 model, does the VM boot? If so, does it recognise
>>the NIC if you install the vmware tools?
>>
>>This may be of help:
>>http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805
>>
>>I suggest approaching the problem by creating a Windows VM in VMware
>>that recognises the NIC, and afterwards creating the same VM through
>>OpenNebula.
>>
>>Regards,
>>
>>-Tino
>>--
>>OpenNebula - Flexible Enterprise Cloud Made Simple
>>
>>--
>>Constantino Vázquez Blanco, PhD, MSc
>>Senior Infrastructure Architect at C12G Labs
>>www.c12g.com | @C12G | es.linkedin.com/in/tinova
>>
>>--
>>Confidentiality Warning: The information contained in this e-mail and
>>any accompanying documents, unless otherwise expressly indicated, is
>>confidential and privileged, and is intended solely for the person
>>and/or entity to whom it is addressed (i.e. those identified in the
>>"To" and "cc" box). They are the property of C12G Labs S.L..
>>Unauthorized distribution, review, use, disclosure, or copying of this
>>communication, or any part thereof, is strictly prohibited and may be
>>unlawful. If you have received this e-mail in error, please notify us
>>immediately by e-mail at ab...@c12g.com and delete the e-mail and
>>attachments and any copy from your system. C12G thanks you for your
>>cooperation.
>>
>>
>>On Fri, Dec 6, 2013 at 8:47 AM, hansz  wrote:
>>> hi man,
>>> yesterday i install opennebula4.4 on centos,but the wind

Re: [one-users] opennebula 4.4 esxi 5.1 windows vms lose nic dirver

2013-12-09 Thread hansz
Hi Tino,
thinks for your replay,
without the e1000 model (but has select virtual Networks) ,the VM boot, but 
does not has NIC driver. the vm i have ready install vmware tools
the following are the steps i create a vm
1)i  first create vms throuht the vmware's esxi (while create the vm ,i select 
the network  ,and the model,after the vm boot ,i install the 
vmware tools,at that moment the vm has NIC driver,and i can ping to other vms),
2)and then tar the window-flat.vmdk and the disk.vmdk a xxx.tar.bz2
3) upload the xxx.tar.bz2 through the sunstone to the image ,
4)create template 
5)create  vms


but ,if i set model=e1000 at the template when the vm startup the vm will stay 
on the starting screen,
else if i set model=E1000 at the template the vm will faild 
the log (for model=E1000)
Tue Dec 10 04:58:00 2013 [DiM][I]: New VM state is ACTIVE.
Tue Dec 10 04:58:00 2013 [LCM][I]: New VM state is PROLOG.
Tue Dec 10 04:59:40 2013 [LCM][I]: New VM state is BOOT
Tue Dec 10 04:59:40 2013 [VMM][I]: Generating deployment file: 
/var/lib/one/vms/30/deployment.0
Tue Dec 10 04:59:41 2013 [VMM][I]: Successfully execute network driver 
operation: pre.
Tue Dec 10 04:59:48 2013 [VMM][I]: Command execution fail: 
/var/lib/one/remotes/vmm/vmware/deploy '/var/lib/one/vms/30/deployment.0' 
'esxi01' 30 esxi01
Tue Dec 10 04:59:48 2013 [VMM][I]: 
/var/lib/one/remotes/vmm/vmware/vi_driver.rb:138:in `initialize': Cannot find 
VM one-30 (RuntimeError)
Tue Dec 10 04:59:48 2013 [VMM][I]: from 
/var/lib/one/remotes/vmm/vmware/vmware_driver.rb:418:in `new'
Tue Dec 10 04:59:48 2013 [VMM][I]: from 
/var/lib/one/remotes/vmm/vmware/vmware_driver.rb:418:in `handle_metadata'
Tue Dec 10 04:59:48 2013 [VMM][I]: from 
/var/lib/one/remotes/vmm/vmware/vmware_driver.rb:398:in `define_domain'
Tue Dec 10 04:59:48 2013 [VMM][I]: from 
/var/lib/one/remotes/vmm/vmware/vmware_driver.rb:88:in `deploy'
Tue Dec 10 04:59:48 2013 [VMM][I]: from 
/var/lib/one/remotes/vmm/vmware/deploy:38
Tue Dec 10 04:59:48 2013 [VMM][I]: ExitCode: 1
Tue Dec 10 04:59:48 2013 [VMM][I]: Failed to execute virtualization driver 
operation: deploy.
Tue Dec 10 04:59:48 2013 [VMM][E]: Error deploying virtual machine
Tue Dec 10 04:59:48 2013 [DiM][I]: New VM state is FAILED 
anyother may be wrong ? wait for your replay ,thinks










At 2013-12-09 22:44:36,"Tino Vazquez"  wrote:
>Hi,
>
>Without the E1000 model, does the VM boot? If so, does it recognise
>the NIC if you install the vmware tools?
>
>This may be of help:
>http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805
>
>I suggest approaching the problem by creating a Windows VM in VMware
>that recognises the NIC, and afterwards creating the same VM through
>OpenNebula.
>
>Regards,
>
>-Tino
>--
>OpenNebula - Flexible Enterprise Cloud Made Simple
>
>--
>Constantino Vázquez Blanco, PhD, MSc
>Senior Infrastructure Architect at C12G Labs
>www.c12g.com | @C12G | es.linkedin.com/in/tinova
>
>--
>Confidentiality Warning: The information contained in this e-mail and
>any accompanying documents, unless otherwise expressly indicated, is
>confidential and privileged, and is intended solely for the person
>and/or entity to whom it is addressed (i.e. those identified in the
>"To" and "cc" box). They are the property of C12G Labs S.L..
>Unauthorized distribution, review, use, disclosure, or copying of this
>communication, or any part thereof, is strictly prohibited and may be
>unlawful. If you have received this e-mail in error, please notify us
>immediately by e-mail at ab...@c12g.com and delete the e-mail and
>attachments and any copy from your system. C12G thanks you for your
>cooperation.
>
>
>On Fri, Dec 6, 2013 at 8:47 AM, hansz  wrote:
>> hi man,
>> yesterday i install opennebula4.4 on centos,but the windows2008r2 vms also
>> has  NIC driver problem
>> if i add  model =e1000 ,the vms will black screen ,when the vms startup, the
>> follow are the network and the template
>> the network
>> [oneadmin@nebula ~]$ onevnet show 0 -x
>> 
>>   0
>>   0
>>   0
>>   oneadmin
>>   oneadmin
>>   EsxiNetwork
>>   
>> 1
>> 1
>> 0
>> 0
>> 0
>> 0
>> 0
>> 0
>> 0
>>   
>>   -1
>>   
>>   0
>>   VM Network
>>   0
>>   
>>   
>>   
>>   
>>   
>> 10.24.101.95
>> 10.24.101.103
>>   
>>   2
>>   
>> 
>> 
>> 
>>   
>>   
>> 
>>   02:00:0a:18:65:5f
>>   10.24.101.95
>>   fe80::400:aff:fe18:655f
>>   1
>>   2
>> 
>> 
>>   02:00:0a:18:65:60
>>   10.24.101.96
>>   fe80::400:aff:fe18:6560
>>   1
>>   3
>> 
>>   
>> 
>> [oneadmin@nebula ~]$
>>
>> the template
>> [oneadmin@nebula ~]$ onetemplate show 2 -x
>> 
>>   2
>>   0
>>   0
>>   oneadmin
>>   oneadmin
>>   windows2
>>   
>> 1
>> 1
>> 0
>> 0
>> 0
>> 0
>> 0
>> 0
>> 0
>>   
>>   1386342845
>>   
>> 
>>   
>>   
>> 
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>> 
>> 
>>   
>>

Re: [one-users] opennebula 4.4 esxi 5.1 windows vms lose nic dirver

2013-12-09 Thread Tino Vazquez
Hi,

Without the E1000 model, does the VM boot? If so, does it recognise
the NIC if you install the vmware tools?

This may be of help:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805

I suggest approaching the problem by creating a Windows VM in VMware
that recognises the NIC, and afterwards creating the same VM through
OpenNebula.

Regards,

-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple

--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
www.c12g.com | @C12G | es.linkedin.com/in/tinova

--
Confidentiality Warning: The information contained in this e-mail and
any accompanying documents, unless otherwise expressly indicated, is
confidential and privileged, and is intended solely for the person
and/or entity to whom it is addressed (i.e. those identified in the
"To" and "cc" box). They are the property of C12G Labs S.L..
Unauthorized distribution, review, use, disclosure, or copying of this
communication, or any part thereof, is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify us
immediately by e-mail at ab...@c12g.com and delete the e-mail and
attachments and any copy from your system. C12G thanks you for your
cooperation.


On Fri, Dec 6, 2013 at 8:47 AM, hansz  wrote:
> hi man,
> yesterday i install opennebula4.4 on centos,but the windows2008r2 vms also
> has  NIC driver problem
> if i add  model =e1000 ,the vms will black screen ,when the vms startup, the
> follow are the network and the template
> the network
> [oneadmin@nebula ~]$ onevnet show 0 -x
> 
>   0
>   0
>   0
>   oneadmin
>   oneadmin
>   EsxiNetwork
>   
> 1
> 1
> 0
> 0
> 0
> 0
> 0
> 0
> 0
>   
>   -1
>   
>   0
>   VM Network
>   0
>   
>   
>   
>   
>   
> 10.24.101.95
> 10.24.101.103
>   
>   2
>   
> 
> 
> 
>   
>   
> 
>   02:00:0a:18:65:5f
>   10.24.101.95
>   fe80::400:aff:fe18:655f
>   1
>   2
> 
> 
>   02:00:0a:18:65:60
>   10.24.101.96
>   fe80::400:aff:fe18:6560
>   1
>   3
> 
>   
> 
> [oneadmin@nebula ~]$
>
> the template
> [oneadmin@nebula ~]$ onetemplate show 2 -x
> 
>   2
>   0
>   0
>   oneadmin
>   oneadmin
>   windows2
>   
> 1
> 1
> 0
> 0
> 0
> 0
> 0
> 0
> 0
>   
>   1386342845
>   
> 
>   
>   
> 
> 
> 
>   
>   
> 
> 
>   
> 
> 
>   
>   
> 
> 
>   
>   
> 
> 
>   
>   
> 
> 
>   
>   
> 
> 
> 
>   
>   
>   
> 
> 
>   
> 
> 
>   
> 
> [oneadmin@nebula ~]$
>
>
>
>
>
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org


[one-users] opennebula 4.4 esxi 5.1 windows vms lose nic dirver

2013-12-05 Thread hansz
hi man,
yesterday i install opennebula4.4 on centos,but the windows2008r2 vms also has  
NIC driver problem
if i add  model =e1000 ,the vms will black screen ,when the vms startup, the 
follow are the network and the template
the network
[oneadmin@nebula ~]$ onevnet show 0 -x

  0
  0
  0
  oneadmin
  oneadmin
  EsxiNetwork
  
1
1
0
0
0
0
0
0
0
  
  -1
  
  0
  VM Network
  0
  
  
  
  
  
10.24.101.95
10.24.101.103
  
  2
  



  
  

  02:00:0a:18:65:5f
  10.24.101.95
  fe80::400:aff:fe18:655f
  1
  2


  02:00:0a:18:65:60
  10.24.101.96
  fe80::400:aff:fe18:6560
  1
  3

  

[oneadmin@nebula ~]$ 


the template
[oneadmin@nebula ~]$ onetemplate show 2 -x

  2
  0
  0
  oneadmin
  oneadmin
  windows2
  
1
1
0
0
0
0
0
0
0
  
  1386342845
  

  
  



  
  


  


  
  


  
  


  
  


  
  



  
  
  


  


  

[oneadmin@nebula ~]$ 



___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org