No valid Host found just in WINDOWS 2012 images

[eariasn]

Hello folks,

Trying to get this VIO running Windows 2012, issue is that the VM gets provisioned, I even can see it being copied in Vsphere, it gets to the inventory in VIO with a status of build but never finishes, after a while it goes into an ERROR state and throws the exception "NO VALID HOST FOUND", which is generic and misleading, cause right after that I go and provision a 2008 image same flavor and it does it.

Anyone with experience with 2012 that could help ?

thanks!

[admin]

would you mind scheduling an office hour and I can get resources to help debug live. just fill this short form with date/time and info on issue (you can link this post there)

tinyurl.com/vio-office

[mvoelker]

Hello eariasn,

The "no valid hosts" error often indicates that the nova scheduler was unable to find a suitable host on which to launch the instance.  If one image is working (e.g. 2008) and another isn't (2012), you may be running into problems such as:

1.)  The 2012 image has a larger disk size which exceeds the available capacity (or in some cases, the image cache has insufficient space to transfer the image).

2.)  The 2012 image is being launched with a different flavor type and the scheduler can't find a host with enough available CPU or memory.

3.) In some much rarer cases, this problem might occur if some of the nova-compute hosts are not communicating with the scheduler properly (e.g. they've been disconnected from the message bus, etc) which causes nova to not recognize the resources available in the corresponding cluster.  If this is the case, usually restarting nova-compute will clear up the problem.

You may find more information in the nova-compute logs.  Please also feel free to schedule some time during office hours with ArvindSoni if you need more help pinpointing the problem!

[eariasn]

Hello all,

In compute log I found this:

2016-01-13 01:36:11.573 1569 ERROR nova.compute.manager [req-19fd3faf-49df-49c2-bba4-34d50a397ba7 c1471e4d13794a1381e70b68c192d8e0 b10d4b7b64a04c30bde8695369ef5f8e - - -] [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0] Instance failed to spawn

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0] Traceback (most recent call last):

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2487, in _build_resources

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0]     yield resources

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2359, in _build_and_run_instance

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0]     block_device_info=block_device_info)

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/driver.py", line 501, in spawn

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0]     admin_password, network_info, block_device_info)

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmops.py", line 864, in spawn

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0]     raise exception.NovaException(_("Unexpected guest tools state "

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0] NovaException: Unexpected guest tools state change. toolsRunningStatus is not guestToolsRunning

2016-01-13 01:36:11.573 1569 TRACE nova.compute.manager [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0]

2016-01-13 01:36:11.576 1569 INFO nova.compute.manager [req-19fd3faf-49df-49c2-bba4-34d50a397ba7 c1471e4d13794a1381e70b68c192d8e0 b10d4b7b64a04c30bde8695369ef5f8e - - -] [instance: 34089c9b-cf3a-4845-bc34-4cb7f27b50d0] Terminating instance

I saw a thread with a similar solution:

Windows image with or without cloud-init?

I am thinking to apply here, what I am concerned is if the command:

• viocli deployment --limit compute configure

Will affect my current installation of VIO? or is it more like a stop /start of services with new config files.

Any thoughts ?

[admin]

What version of VIO are you using?

If 2.0 and later than you can use Eric's instruction from that thread to disable guest customization. It shouldn't cause any problems with your deployment.