can't complete reservation
hello all, i've successfully created a base image and have its privileges configured for base users. i'm trying to create a reservation, but vcl always says the requested time is not available even though there are no other reservations configured and the time grid is entirely green. could this be an issue with the image itself? log doesn't seem to indicate where the problem may lie. TIA. -- will
Re: can't complete reservation
the image is loaded on a vm (though it is not currently powered on) and it is associated with a virtual host. i have checked the specs of the computers and of the images. i did notice, however, that the advanced options of the image seem to revert back to default after pressing confirm changes. this is what led me to think that it may be a problem with the image. will On 07/11/2012 01:43 PM, Michael Jinks wrote: Mistake we often make: Is the image loaded on at least one virtual computer, and is that computer associated with a virtual host in the list on the Virtual Hosts page? On Wed, Jul 11, 2012 at 01:29:28PM -0400, William Robinson wrote: hello all, i've successfully created a base image and have its privileges configured for base users. i'm trying to create a reservation, but vcl always says the requested time is not available even though there are no other reservations configured and the time grid is entirely green. could this be an issue with the image itself? log doesn't seem to indicate where the problem may lie. TIA. -- will
Re: can't complete reservation
thanks all, i think i am on to something. it turns out i underestimated the number of check-ins the management node does, and i did not go back nearly far enough to catch the issue (i had a 2 hour gap before i could troubleshoot). the logs show the vm not responding to pings and they also show the public ip not getting set correctly. apparently, i have a typo in the mysql database that i need to track down. will On 07/11/2012 02:22 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Will, Here is a list of things to check from a previous thread (some already covered): - -image is in an image group - -image group is mapped to a computer group - -computer group contains computers in the available state - -you have an active management node (it is updating lastcheckin in the management node table) - -management node is in a management node group - -management node group maps to a computer group containing specified computer from above - -schedule for computer is available during the selected time - -platform for image matches platform of computer - -privileges set up in Privileges section of site to allow you to access image and computer - -specs of image (min RAM, min CPU speed, etc) are at or less than specs of computer - -no other entries in the reservation table for the computer that overlap with the selected time period If you are familiar with php, you can trace through the isAvailable function in utils.php to see where it is returning. Josh
creating a base image
hi all, i'm having a problem creating a base windows 7 image and i'm wondering if it is because i'm using vcl 2.2.1 and esxi 5. the lines i think are relevant are below. any pointers would be appreciated. thanks. 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmhost_product_name(5405)|VMware product being used on VM host vclnode01: 'VMware ESXi 5.0.0 build-623860' 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(307)|product: VMware ESXi 5.0.0 build-623860, OS object: VCL::Module::OS::Linux::UnixLab 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 1 (hostsvc/datastore/listsummary) 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclnode01: vim-cmd hostsvc/datastore/listsummary 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_datastore_info(5531)|retrieved datastore info from VM host: |11089|10:10|image| datastore1 |11089|10:10|image| datastore2 |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_name(5848)|unable to determine datastore name from path: '/vmfs/volumes/local-datastore', path does not begin with any of the datastore paths: |11089|10:10|image| '[datastore2]' |11089|10:10|image| '/vmfs/volumes/datastore2' |11089|10:10|image| '/vmfs/volumes/4fd8b523-f4b9c22c-4f9b-001ec9aa4ba2' |11089|10:10|image| '[datastore1]' |11089|10:10|image| '/vmfs/volumes/datastore1' |11089|10:10|image| '/vmfs/volumes/4fcfadc7-c5fa2f69-3ffc-001ec9aa4ba2' |11089|10:10|image| ( 0) VMware.pm, _get_datastore_name (line: 5848) |11089|10:10|image| (-1) VMware.pm, _get_datastore_root_normal_path (line: 5685) |11089|10:10|image| (-2) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-3) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-4) VMware.pm, initialize (line: 313) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_root_normal_path(5687)|failed to determine datastore root normal path, unable to determine datastore name: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line: 5687) |11089|10:10|image| (-1) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-2) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-3) VMware.pm, initialize (line: 313) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_normal_path(5777)|unable to determine normal path, failed to determine datastore root normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_normal_path (line: 5777) |11089|10:10|image| (-1) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-2) VMware.pm, initialize (line: 313) |11089|10:10|image| (-3) Module.pm, new (line: 207) |11089|10:10|image| (-4) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-5) State.pm, initialize (line: 117) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmx_base_directory_path(2749)|unable to determine the vmx base directory path, failed to convert path configured in the VM profile to a normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, get_vmx_base_directory_path (line: 2749) |11089|10:10|image| (-1) VMware.pm, initialize (line: 313) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-4) State.pm, initialize (line: 117) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(315)|unable to determine vmx base directory path on VM host vclnode01 |11089|10:10|image| ( 0) VMware.pm, initialize (line: 315) |11089|10:10|image| (-1) Module.pm, new (line: 207) |11089|10:10|image| (-2) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-3) State.pm, initialize (line: 117) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) vcld, make_new_child (line: 564) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|Module.pm:create_provisioning_object(431)|provisioning object could not be created, returning 0 |11089|10:10|image| ( 0) Module.pm, create_provisioning_object (line: 431) |11089|10:10|image| (-1) State.pm, initialize (line: 117) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) vcld, make_new_child (line: 564) |11089|10:10|image| (-4) vcld, main (line: 346) |11089|10:10|image| WARNING
Re: creating a base image
you are correct. right now those are set to the system defaults: VMware ESX - local network storage VM type:vmware ESXiImage:No Image Repository Path:null Datastore Path:/vmfs/volumes/nfs-datastore1 VM Path:/vmfs/volumes/local-datastore Virtual Switch 0:Private Virtual Switch 1:Public VM Disk:localdisk i'm updating the profile and will give it another shot. thanks! will On 06/29/2012 01:40 PM, Dmitri Chebotarov wrote: Will ESXi 5.0 and VCL 2.2.1 work well together. Could please send VM host profile which is assigned to vclnode01 host? What do you have for 'Data Store Path' and 'VM path'? On vclnode01 host, where do you map datastore1 and datastore2? I think 'Data Store Path' and 'VM path' in the profile need to match paths for datastore1 and datastore2 on the VM host. Thanks. On Jun 29, 2012, at 12:31 , William Robinson wrote: hi all, i'm having a problem creating a base windows 7 image and i'm wondering if it is because i'm using vcl 2.2.1 and esxi 5. the lines i think are relevant are below. any pointers would be appreciated. thanks. 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmhost_product_name(5405)|VMware product being used on VM host vclnode01: 'VMware ESXi 5.0.0 build-623860' 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(307)|product: VMware ESXi 5.0.0 build-623860, OS object: VCL::Module::OS::Linux::UnixLab 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 1 (hostsvc/datastore/listsummary) 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclnode01: vim-cmd hostsvc/datastore/listsummary 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_datastore_info(5531)|retrieved datastore info from VM host: |11089|10:10|image| datastore1 |11089|10:10|image| datastore2 |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_name(5848)|unable to determine datastore name from path: '/vmfs/volumes/local-datastore', path does not begin with any of the datastore paths: |11089|10:10|image| '[datastore2]' |11089|10:10|image| '/vmfs/volumes/datastore2' |11089|10:10|image| '/vmfs/volumes/4fd8b523-f4b9c22c-4f9b-001ec9aa4ba2' |11089|10:10|image| '[datastore1]' |11089|10:10|image| '/vmfs/volumes/datastore1' |11089|10:10|image| '/vmfs/volumes/4fcfadc7-c5fa2f69-3ffc-001ec9aa4ba2' |11089|10:10|image| ( 0) VMware.pm, _get_datastore_name (line: 5848) |11089|10:10|image| (-1) VMware.pm, _get_datastore_root_normal_path (line: 5685) |11089|10:10|image| (-2) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-3) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-4) VMware.pm, initialize (line: 313) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_root_normal_path(5687)|failed to determine datastore root normal path, unable to determine datastore name: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line: 5687) |11089|10:10|image| (-1) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-2) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-3) VMware.pm, initialize (line: 313) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_normal_path(5777)|unable to determine normal path, failed to determine datastore root normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_normal_path (line: 5777) |11089|10:10|image| (-1) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-2) VMware.pm, initialize (line: 313) |11089|10:10|image| (-3) Module.pm, new (line: 207) |11089|10:10|image| (-4) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-5) State.pm, initialize (line: 117) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmx_base_directory_path(2749)|unable to determine the vmx base directory path, failed to convert path configured in the VM profile to a normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, get_vmx_base_directory_path (line: 2749) |11089|10:10|image| (-1) VMware.pm, initialize (line: 313) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-4) State.pm, initialize (line: 117) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(315)|unable to determine vmx base directory path on VM host vclnode01 |11089|10:10|image| ( 0
Re: VCL image capture dies, failed to prepare vmx file
hi all, new to this list. i have started setting up vcl here and clemson university and this thread has touched on one of the questions i had in trying to do so. do i assign mac addresses based on what esxi generates? if not, how do i map those correctly? thanks. will On 06/20/2012 10:16 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael, Unfortunately, yes, in 2.2.1, you can only set MAC addresses via the add multiple computers page. You'll need to set them in the database. This is fixed in 2.3. Josh On Wednesday, June 20, 2012 9:12:52 AM Michael Jinks wrote: Thanks Aaron. Ah, yes. It didn't occur to me that we'd have to have MAC addresses defined for a machine we're capturing *from*. I figured, well, it's running and has IP addresses... At any rate, I'm looking around the UI and I can't find any page that will let me enter a MAC address for an existing computer record. Is this something I have to do by hand in the database? On Wed, Jun 20, 2012 at 08:46:40AM -0400, Aaron Peeler wrote: Hello Michael, One thing that stands out in the log is that your MAC addresses are not defined. computer eth0 MAC address: undefined computer eth1 MAC address: undefined This will be needed to correctly create the vmx file and thus get an address from the private dhcp server that is should be running on your management node. Secondly also make sure you have the dhcp server setup on your management node for the private network. Aaron On Tue, Jun 19, 2012 at 5:53 PM, Michael Jinks mji...@uchicago.edu wrote: Hi, all. Trying to resurrect a thread I started on Friday, subject 'Image capture succeeds, then fails'. ?Mike Haudenschild helped me narrow down the problem but so far I haven't been able to find a cause or a fix. I'm trying to capture my first Linux VM. ?Things go along okay through the capture stage, but (thanks Mike) we fail when VCL tries to reserve and deploy the new image. The critical message from the log appears to be: ?|17491|19:19|reload| WARNING ?|17491|19:19|reload| 2012-06-19 ?14:10:22|17491|19:19|reload|VMware.pm:load(395)|failed to prepare vmx file for vcl-linux-template-2-bak on VM host: vcl0001 ?|17491|19:19|reload| ( 0) VMware.pm, load (line: 395) ?|17491|19:19|reload| (-1) new.pm, reload_image (line: 618) ?|17491|19:19|reload| (-2) new.pm, process (line: 248) ?|17491|19:19|reload| (-3) vcld, make_new_child (line: 568) ?|17491|19:19|reload| (-4) vcld, main (line: 346) Further down, I'll paste in a complete copy of the log mail I got from this attempt. Our VM storage settings for this VM host are: ?Repository Path: ? ? ? /vmfs/volumes/nfs-vcl-templates ?Data Store Path: ? ? ? /vmfs/volumes/T2_6045_dev_VCL_ds01 ?VM Path: ? ? ? /vmfs/volumes/T2_6045_dev_VCL_ds01 (Note Data Store and VM are explicitly the same; we've also had VM Path set to (empty) with no apparent difference in behavior.) Both of those paths are writable on the hypervisor. ?During capture, a VM directory appears in both locations. ?In the directory under the Repository path, we have many vmdk files, sizes ranging from 842M to 1.5k, with names like: ?vmwarelinux-linuxtemplate2v1226-v0-s001.vmdk ?vmwarelinux-linuxtemplate2v1226-v0-s002.vmdk ?vmwarelinux-linuxtemplate2v1226-v0-s003.vmdk ?[...] ?vmwarelinux-linuxtemplate2v1226-v0-s016.vmdk ?vmwarelinux-linuxtemplate2v1226-v0.vmdk My first guess is that we have one vmdk file for each attempted capture, and this is a series of xdiffs on the original? In the Data Store/VM directory, we have: ?# pwd ?/vmfs/volumes/T2_6045_dev_VCL_ds01/vmwarelinux-linuxtemplate2v1226-v0 ?# ls -lh ?-rw--- ? ?1 root ?root ? 30.0G Jun 19 20:12 vmwarelinux-linuxtemplate2v1226-v0-flat.vmdk ?-rw--- ? ?1 root ?root ? ? 527 Jun 19 20:12 vmwarelinux-linuxtemplate2v1226-v0.vmdk So, it seems that those locations are accessible and writable, and being written. ?What else might cause the vmx file prep to fail? ?I went to VMware.pm line 395, but that's a call to a subroutine, prepare_vmx(), which is a fairly lengthy chunk of code and doesn't appear to be dropping any breadcrumbs as it runs, only the failure message when it exits. ?So stepping through that without guidance is going to be a challenge. Meanwhile we've also started trying to capture a Windows image. ?That's dying too, but with a different set of error messages. ?I'll post that under separate cover. Thanks for any insight. ?Complete log message follows. -m reservation failed on vcl-linux-template-2-bak: process failed after trying to load or make available --- - time: 2012-06-19 14:10:22 caller: State.pm:reservation_failed(213) ( 0) State.pm, reservation_failed (line: 213) (-1) new.pm, process (line: 298) (-2) vcld, make_new_child (line: 568) (-3) vcld, main (line: 346) management node: pilot-lab.uchicago.edu reservation PID:
Re: VM MAC addressing, was Re: VCL image capture dies, failed to prepare vmx file
thanks michael. will On 06/25/2012 09:58 AM, Michael Jinks wrote: Hi Will. I believe that VCL requires manually assigning MAC addresses when you generate the VM records -- you must use the multi-add page under Add Computers, and have it assign a range of MAC addresses. Note that VMware uses two ranges of MAC addresses: one range for those it auto-generates, and one for those assigned by the user. I believe that VCL sets the MAC address of the VM at each deployment time, which would mean that you can't just let VMware generate the MACs and then list them in the database afterward; you must use something from the manual range. We chose two ranges under 00:50:56:xx:xx:xx, one for each of our private and public-facing net segments. I've read at least one doc that refers to this being the easiest way to set up your VM network, but after lots of experimenting I think it's actually the only way. Good luck, -m
Re: VM MAC addressing, was Re: VCL image capture dies, failed to prepare vmx file
thanks. i'm not sure i want to blow what i have configured away. i have a colleague working on this with me who is pretty knowledgeable with mysql. i'm sure i can get him to help me fix these up. this has also convinced me to install phpmyadmin to simplify things in situations like this. will On 06/25/2012 10:31 AM, Mike Haudenschild wrote: Hi Will -- The MAC address range Mike identified below is the best to use. ESXi expects any manually-assigned MAC addresses to fall within the range 00:50:56:00:yy:zzand 00:50:56:3F:yy:zz [1]. (Note these are manually-assigned from ESXi's perspective, not VCL's perspective. VCL generates a VMX file with the MAC addresses, and ESXi just accepts those addresses.) In 2.2.1 you must use the "multiple computers" option for adding VMs, as that screen provides a space to enter the starting MAC address. Note that VCL iterates the private and public MAC addresses starting with the address you specify. If you enter 00:50:56:00:00:01 as the starting address, VCL will create computers as follows: VM1 private interface (eth0): 00:50:56:00:00:01 VM1 public interface (eth1): 00:50:56:00:00:02 VM2 eth0: 00:50:56:00:00:03 VM2 eth1: 00:50:56:00:00:04 etc. If you've already added VMs via the single-add-computer screen in VCL, you'll need to either abandon them or use an SQL client to edit the "computer" table and assign them MAC addresses. [2] This should no longer be an issue in 2.3. [3] [1]http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKCexternalId=507 [2]http://markmail.org/message/bp5ax4czlqxzyto3 [3]http://markmail.org/message/v2vqktuefbaur2c4 Regards, Mike -- Mike Haudenschild Education Systems Manager Longsight Group (740) 599-5005 x809 m...@longsight.com www.longsight.com On Mon, Jun 25, 2012 at 9:58 AM, Michael Jinks mji...@uchicago.edu wrote: Hi Will. I believe that VCL requires manually assigning MAC addresses when you generate the VM records -- you must use the multi-add page under "Add Computers", and have it assign a range of MAC addresses. Note that VMware uses two ranges of MAC addresses: one range for those it auto-generates, and one for those assigned by the user. I believe that VCL sets the MAC address of the VM at each deployment time, which would mean that you can't just let VMware generate the MACs and then list them in the database afterward; you must use something from the manual range. We chose two ranges under 00:50:56:xx:xx:xx, one for each of our private and public-facing net segments. I've read at least one doc that refers to this being the "easiest" way to set up your VM network, but after lots of experimenting I think it's actually the only way. Good luck, -m On Mon, Jun 25, 2012 at 09:13:29AM -0400, William Robinson wrote: hi all, new to this list. i have started setting up vcl here and clemson university and this thread has touched on one of the questions i had in trying to do so. do i assign mac addresses based on what esxi generates? if not, how do i map those correctly? thanks. will On 06/20/2012 10:16 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael, Unfortunately, yes, in 2.2.1, you can only set MAC addresses via the add multiple computers page. You'll need to set them in the database. This is fixed in 2.3. Josh On Wednesday, June 20, 2012 9:12:52 AM Michael Jinks wrote: Thanks Aaron. Ah, yes. It didn't occur to me that we'd
