Re: VM deleted while attempting to capture image in standalone installation (again)
(Looks like these emails got hung up some where, i just got this one over the weekend.) Right the datastore path should be your golden or safe images which in this case would be /image/vmware. The vmpath is were your running images would be located. Aaron On 4/28/10 9:58 AM, Mark Gardner wrote: Looks like I got that backwards. datastorepath should be /images/vmware and vmpath should be /home/vm/vmware. At least the master image is being copied... Mark On Wed, Apr 28, 2010 at 9:38 AM, Mark Gardnerlil.lis...@gmail.com wrote: OK. That makes sense. I had a symlink between /home/vm/vmware and /images/vmware. I have removed it. My original vm image is in /home/vm/vmware and the cloned image should be in /images/vmware. Do I set datastorepath to /home/vm/vmware and vmpath to /images/vmware? Mark On Mon, Apr 26, 2010 at 12:21 PM, Aaron Peeleraaron_pee...@ncsu.eduwrote: Hi Mark, Sorry you ran into this, unfortunately this is an unexpected event of running a vcl setup in standalone mode. https://cwiki.apache.org/VCL/configuring-a-standalone-vmware-vcl-environment.html Do you have separate locations for your image library and your running vms? It looks like you might be using the same location /images/vmware. This is the intended behavior of the vmware.pm module when using local disk. The idea behind this is to keep the disk on the vmware host server freed up and not have too many non-running vmware disk images residing on the remote machine. Also the same would happen if the disk usage would be close to full for the partition where the virtual machine path was defined. But since the vmware host server and the vcl management node are on the same box, I can see where this can happen if not careful. In this setup vcld(the management node) assumes that the remote localvmhost server is a different machine, etc and that the copy of the image on the vcld management node server is safe. Looking at your logs. The part around 10:31:53 reports the vm is on but appears could not ssh into it. Thus it returned a RELOAD flag. The the load routine calls control_VM routine to clear any possible vms running with that hostname vmguest-1 So it finds a vm running out of /home/vm/vmware and stops and removes it. /home/vm/vmware/vmwarelinux-xubuntu904-v0vmguest-1/vmwarelinux-xubuntu904-v0vmguest-1.vmx I'm not sure where this is coming from, since /home/vm/vmware is not in your vmprofile table. Could this be one you manually fired up? Is /home/vm/vmware a symlink to /images/vmware? Anyway, when using the standalone mode(not recommended for anything production) please make sure to have a separate directory or partition for your stored vms and your running vms. Aaron On 4/26/10 11:18 AM, Mark Gardner wrote: [Still looking for help with this.] I have obviously misconfigured something... I have been working on a standalone system and have been systematically fixing errors I find in the logs. On the last attempt to make a reservation, the VMware Server virtual machine was unregistered and deleted. Needless to say it was definitely a surprise! I am enclosing vcld.log. The problem occurs at time 10:31:55. I am also enclosing selects from related tables. Your help in correcting this unexpected behavior would be greatly appreciated. == BEGIN vcld.log === === OUTPUT for vcld run on 2010-04-20 10:31:22 === 2010-04-20 10:31:22|25426|vcld:main(116)|vcld environment variable set to 1 for this process 2010-04-20 10:31:22|25426|utils.pm:rename_vcld_process(7901)|renamed process to 'vcld vcld' 2010-04-20 10:31:22|25426|utils.pm: get_management_node_info(6815)|management node info retrieved from database for localhost 2010-04-20 10:31:22|25426|vcld:main(127)|retrieved management node information from database 2010-04-20 10:31:22|25426|vcld:main(140)|management_node_id environment variable set: 1 2010-04-20 10:31:22|25426|vcld:main(148)|management node checkin interval is 5 seconds 2010-04-20 10:31:22|25426|vcld:main(149)|vcld started on localhost 2010-04-20 10:31:27|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:27 2010-04-20 10:31:32|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:32 2010-04-20 10:31:37|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:37 2010-04-20 10:31:42|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:42 2010-04-20 10:31:47|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:47 2010-04-20 10:31:52|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:52 2010-04-20 10:31:52|25426|7:7|new|utils.pm: reservation_being_processed(9634)|computerloadlog 'begin' entry does NOT exist for reservation 7 2010-04-20 10:31:52|25426|7:7|new|utils.pm:
Re: VM deleted while attempting to capture image in standalone installation (again)
OK. That makes sense. I had a symlink between /home/vm/vmware and /images/vmware. I have removed it. My original vm image is in /home/vm/vmware and the cloned image should be in /images/vmware. Do I set datastorepath to /home/vm/vmware and vmpath to /images/vmware? Mark On Mon, Apr 26, 2010 at 12:21 PM, Aaron Peeler aaron_pee...@ncsu.eduwrote: Hi Mark, Sorry you ran into this, unfortunately this is an unexpected event of running a vcl setup in standalone mode. https://cwiki.apache.org/VCL/configuring-a-standalone-vmware-vcl-environment.html Do you have separate locations for your image library and your running vms? It looks like you might be using the same location /images/vmware. This is the intended behavior of the vmware.pm module when using local disk. The idea behind this is to keep the disk on the vmware host server freed up and not have too many non-running vmware disk images residing on the remote machine. Also the same would happen if the disk usage would be close to full for the partition where the virtual machine path was defined. But since the vmware host server and the vcl management node are on the same box, I can see where this can happen if not careful. In this setup vcld(the management node) assumes that the remote localvmhost server is a different machine, etc and that the copy of the image on the vcld management node server is safe. Looking at your logs. The part around 10:31:53 reports the vm is on but appears could not ssh into it. Thus it returned a RELOAD flag. The the load routine calls control_VM routine to clear any possible vms running with that hostname vmguest-1 So it finds a vm running out of /home/vm/vmware and stops and removes it. /home/vm/vmware/vmwarelinux-xubuntu904-v0vmguest-1/vmwarelinux-xubuntu904-v0vmguest-1.vmx I'm not sure where this is coming from, since /home/vm/vmware is not in your vmprofile table. Could this be one you manually fired up? Is /home/vm/vmware a symlink to /images/vmware? Anyway, when using the standalone mode(not recommended for anything production) please make sure to have a separate directory or partition for your stored vms and your running vms. Aaron On 4/26/10 11:18 AM, Mark Gardner wrote: [Still looking for help with this.] I have obviously misconfigured something... I have been working on a standalone system and have been systematically fixing errors I find in the logs. On the last attempt to make a reservation, the VMware Server virtual machine was unregistered and deleted. Needless to say it was definitely a surprise! I am enclosing vcld.log. The problem occurs at time 10:31:55. I am also enclosing selects from related tables. Your help in correcting this unexpected behavior would be greatly appreciated. == BEGIN vcld.log === === OUTPUT for vcld run on 2010-04-20 10:31:22 === 2010-04-20 10:31:22|25426|vcld:main(116)|vcld environment variable set to 1 for this process 2010-04-20 10:31:22|25426|utils.pm:rename_vcld_process(7901)|renamed process to 'vcld vcld' 2010-04-20 10:31:22|25426|utils.pm: get_management_node_info(6815)|management node info retrieved from database for localhost 2010-04-20 10:31:22|25426|vcld:main(127)|retrieved management node information from database 2010-04-20 10:31:22|25426|vcld:main(140)|management_node_id environment variable set: 1 2010-04-20 10:31:22|25426|vcld:main(148)|management node checkin interval is 5 seconds 2010-04-20 10:31:22|25426|vcld:main(149)|vcld started on localhost 2010-04-20 10:31:27|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:27 2010-04-20 10:31:32|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:32 2010-04-20 10:31:37|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:37 2010-04-20 10:31:42|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:42 2010-04-20 10:31:47|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:47 2010-04-20 10:31:52|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:52 2010-04-20 10:31:52|25426|7:7|new|utils.pm: reservation_being_processed(9634)|computerloadlog 'begin' entry does NOT exist for reservation 7 2010-04-20 10:31:52|25426|7:7|new|utils.pm: reservation_being_processed(9686)|reservation is NOT currently being processed 2010-04-20 10:31:52|25426|7:7|new|vcld:main(276)|reservation 7 is NOT already being processed 2010-04-20 10:31:52|25426|7:7|new|utils.pm: get_request_info(5354)|standalone affiliation found: Local 2010-04-20 10:31:52|25426|7:7|new|utils.pm: get_management_node_info(6815)|management node info retrieved from database for localhost 2010-04-20 10:31:52|25426|7:7|new|vcld:main(281)|retrieved request information
Re: VM deleted while attempting to capture image in standalone installation (again)
Looks like I got that backwards. datastorepath should be /images/vmware and vmpath should be /home/vm/vmware. At least the master image is being copied... Mark On Wed, Apr 28, 2010 at 9:38 AM, Mark Gardner lil.lis...@gmail.com wrote: OK. That makes sense. I had a symlink between /home/vm/vmware and /images/vmware. I have removed it. My original vm image is in /home/vm/vmware and the cloned image should be in /images/vmware. Do I set datastorepath to /home/vm/vmware and vmpath to /images/vmware? Mark On Mon, Apr 26, 2010 at 12:21 PM, Aaron Peeler aaron_pee...@ncsu.eduwrote: Hi Mark, Sorry you ran into this, unfortunately this is an unexpected event of running a vcl setup in standalone mode. https://cwiki.apache.org/VCL/configuring-a-standalone-vmware-vcl-environment.html Do you have separate locations for your image library and your running vms? It looks like you might be using the same location /images/vmware. This is the intended behavior of the vmware.pm module when using local disk. The idea behind this is to keep the disk on the vmware host server freed up and not have too many non-running vmware disk images residing on the remote machine. Also the same would happen if the disk usage would be close to full for the partition where the virtual machine path was defined. But since the vmware host server and the vcl management node are on the same box, I can see where this can happen if not careful. In this setup vcld(the management node) assumes that the remote localvmhost server is a different machine, etc and that the copy of the image on the vcld management node server is safe. Looking at your logs. The part around 10:31:53 reports the vm is on but appears could not ssh into it. Thus it returned a RELOAD flag. The the load routine calls control_VM routine to clear any possible vms running with that hostname vmguest-1 So it finds a vm running out of /home/vm/vmware and stops and removes it. /home/vm/vmware/vmwarelinux-xubuntu904-v0vmguest-1/vmwarelinux-xubuntu904-v0vmguest-1.vmx I'm not sure where this is coming from, since /home/vm/vmware is not in your vmprofile table. Could this be one you manually fired up? Is /home/vm/vmware a symlink to /images/vmware? Anyway, when using the standalone mode(not recommended for anything production) please make sure to have a separate directory or partition for your stored vms and your running vms. Aaron On 4/26/10 11:18 AM, Mark Gardner wrote: [Still looking for help with this.] I have obviously misconfigured something... I have been working on a standalone system and have been systematically fixing errors I find in the logs. On the last attempt to make a reservation, the VMware Server virtual machine was unregistered and deleted. Needless to say it was definitely a surprise! I am enclosing vcld.log. The problem occurs at time 10:31:55. I am also enclosing selects from related tables. Your help in correcting this unexpected behavior would be greatly appreciated. == BEGIN vcld.log === === OUTPUT for vcld run on 2010-04-20 10:31:22 === 2010-04-20 10:31:22|25426|vcld:main(116)|vcld environment variable set to 1 for this process 2010-04-20 10:31:22|25426|utils.pm:rename_vcld_process(7901)|renamed process to 'vcld vcld' 2010-04-20 10:31:22|25426|utils.pm: get_management_node_info(6815)|management node info retrieved from database for localhost 2010-04-20 10:31:22|25426|vcld:main(127)|retrieved management node information from database 2010-04-20 10:31:22|25426|vcld:main(140)|management_node_id environment variable set: 1 2010-04-20 10:31:22|25426|vcld:main(148)|management node checkin interval is 5 seconds 2010-04-20 10:31:22|25426|vcld:main(149)|vcld started on localhost 2010-04-20 10:31:27|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:27 2010-04-20 10:31:32|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:32 2010-04-20 10:31:37|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:37 2010-04-20 10:31:42|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:42 2010-04-20 10:31:47|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:47 2010-04-20 10:31:52|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:52 2010-04-20 10:31:52|25426|7:7|new|utils.pm: reservation_being_processed(9634)|computerloadlog 'begin' entry does NOT exist for reservation 7 2010-04-20 10:31:52|25426|7:7|new|utils.pm: reservation_being_processed(9686)|reservation is NOT currently being processed 2010-04-20 10:31:52|25426|7:7|new|vcld:main(276)|reservation 7 is NOT already being processed 2010-04-20 10:31:52|25426|7:7|new|utils.pm: get_request_info(5354)|standalone
Re: VM deleted while attempting to capture image in standalone installation (again)
Hi Mark, Sorry you ran into this, unfortunately this is an unexpected event of running a vcl setup in standalone mode. https://cwiki.apache.org/VCL/configuring-a-standalone-vmware-vcl-environment.html Do you have separate locations for your image library and your running vms? It looks like you might be using the same location /images/vmware. This is the intended behavior of the vmware.pm module when using local disk. The idea behind this is to keep the disk on the vmware host server freed up and not have too many non-running vmware disk images residing on the remote machine. Also the same would happen if the disk usage would be close to full for the partition where the virtual machine path was defined. But since the vmware host server and the vcl management node are on the same box, I can see where this can happen if not careful. In this setup vcld(the management node) assumes that the remote localvmhost server is a different machine, etc and that the copy of the image on the vcld management node server is safe. Looking at your logs. The part around 10:31:53 reports the vm is on but appears could not ssh into it. Thus it returned a RELOAD flag. The the load routine calls control_VM routine to clear any possible vms running with that hostname vmguest-1 So it finds a vm running out of /home/vm/vmware and stops and removes it. /home/vm/vmware/vmwarelinux-xubuntu904-v0vmguest-1/vmwarelinux-xubuntu904-v0vmguest-1.vmx I'm not sure where this is coming from, since /home/vm/vmware is not in your vmprofile table. Could this be one you manually fired up? Is /home/vm/vmware a symlink to /images/vmware? Anyway, when using the standalone mode(not recommended for anything production) please make sure to have a separate directory or partition for your stored vms and your running vms. Aaron On 4/26/10 11:18 AM, Mark Gardner wrote: [Still looking for help with this.] I have obviously misconfigured something... I have been working on a standalone system and have been systematically fixing errors I find in the logs. On the last attempt to make a reservation, the VMware Server virtual machine was unregistered and deleted. Needless to say it was definitely a surprise! I am enclosing vcld.log. The problem occurs at time 10:31:55. I am also enclosing selects from related tables. Your help in correcting this unexpected behavior would be greatly appreciated. == BEGIN vcld.log === === OUTPUT for vcld run on 2010-04-20 10:31:22 === 2010-04-20 10:31:22|25426|vcld:main(116)|vcld environment variable set to 1 for this process 2010-04-20 10:31:22|25426|utils.pm:rename_vcld_process(7901)|renamed process to 'vcld vcld' 2010-04-20 10:31:22|25426|utils.pm:get_management_node_info(6815)|management node info retrieved from database for localhost 2010-04-20 10:31:22|25426|vcld:main(127)|retrieved management node information from database 2010-04-20 10:31:22|25426|vcld:main(140)|management_node_id environment variable set: 1 2010-04-20 10:31:22|25426|vcld:main(148)|management node checkin interval is 5 seconds 2010-04-20 10:31:22|25426|vcld:main(149)|vcld started on localhost 2010-04-20 10:31:27|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:27 2010-04-20 10:31:32|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:32 2010-04-20 10:31:37|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:37 2010-04-20 10:31:42|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:42 2010-04-20 10:31:47|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:47 2010-04-20 10:31:52|25426|vcld:main(165)|lastcheckin time updated for management node 1: 2010-04-20 10:31:52 2010-04-20 10:31:52|25426|7:7|new|utils.pm:reservation_being_processed(9634)|computerloadlog 'begin' entry does NOT exist for reservation 7 2010-04-20 10:31:52|25426|7:7|new|utils.pm:reservation_being_processed(9686)|reservation is NOT currently being processed 2010-04-20 10:31:52|25426|7:7|new|vcld:main(276)|reservation 7 is NOT already being processed 2010-04-20 10:31:52|25426|7:7|new|utils.pm:get_request_info(5354)|standalone affiliation found: Local 2010-04-20 10:31:52|25426|7:7|new|utils.pm:get_management_node_info(6815)|management node info retrieved from database for localhost 2010-04-20 10:31:52|25426|7:7|new|vcld:main(281)|retrieved request information from database 2010-04-20 10:31:52|25426|7:7|new|utils.pm:get_management_node_info(6815)|management node info retrieved from database for localhost 2010-04-20 10:31:52|25426|7:7|new|DataStructure.pm:is_parent_reservation(854)|returning true: parent reservation ID for this request: 7 2010-04-20 10:31:52|25426|7:7|new|utils.pm:update_request_state(2186)|request 7 state updated to: pending, laststate to: new 2010-04-20
