I think that for hot plugging devices you need acpid installed and running inside the guest
On Fri, Jan 24, 2014 at 2:55 PM, Subramanian <[email protected]> wrote: > Hi Rajshree, > > The vmware_wsdl_location needs to be set only if you want to over ride the > default location it is hosted on vCenter server. Normally you would never > need to set this. > > Regarding reboot of instance. Once the volume is attached it is presented to > the VM as a new block device. You would have to "rescan for new hardware" > from within the VM. This command is very OS specific. If you are running an > Ubuntu VM then you could look at this video > http://www.youtube.com/watch?v=aZtxevA0VpU for the commands to rescan. Hope > that helps. > > Thanks, > Subbu > > > > On Fri, Jan 24, 2014 at 6:03 PM, Rajshree Thorat <[email protected]> > wrote: >> >> Hi All, >> >> >> The problem is solved by pointing vmware_wsdl_location parameter to right >> location where VMware SDK placed. >> Now I could successfully attach cinder volumes to instances. However, I >> had to reboot the instance to get it to >> pick up the attached volume. >> >> Is there a way to pick up the attached volume without rebooting guest >> virtual machine? >> >> Regards, >> Rajshree >> >> On 1/24/2014 3:57 PM, Rajshree Thorat wrote: >>> >>> Hi All, >>> >>> I'm deploying OpenStack Havana for provisioning VMs using ESXi as a >>> hypervisor. >>> I want to use ESX datastore as a cinder backend storage. However, when I >>> try to create a volume, >>> it gives me the following error. >>> >>> 2014-01-23 06:35:02.960 2862 ERROR >>> cinder.scheduler.filters.capacity_filter >>> [req-e9444c9b-4abb-411b-9476-80213e4c47a1 dc1ab39557d7405ebcf35d98885c8dcd >>> 1d2b0c8ade234ca08bcef380acdeb8b9] Free capacity not set: volume node info >>> collection broken. >>> 2014-01-23 06:35:02.961 2862 ERROR cinder.volume.flows.create_volume >>> [req-e9444c9b-4abb-411b-9476-80213e4c47a1 dc1ab39557d7405ebcf35d98885c8dcd >>> 1d2b0c8ade234ca08bcef380acdeb8b9] Failed to schedule_create_volume: No valid >>> host was found. >>> >>> Provided is the driver configuration file which I am using. >>> >>> volume_driver=cinder.volume.drivers.vmware.vmdk.VMwareEsxVmdkDriver >>> vmware_host_ip=<vmware_host_ip> >>> vmware_host_username=<vmware_host_username> >>> vmware_host_password=<vmware_host_password> >>> >>> Does anyone have any idea? Pointers in the right direction are always >>> welcome. >>> >>> Thanks in advance. >>> >>> Regards, >>> Rajshree >>> >> >> -- >> Regards, >> Rajshree >> >> >> _______________________________________________ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : [email protected] >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
