RE: failed: failed to list data store contents /var/lib/vmware/Virtual Machines on vm host
Hello Andy, Will resend. Regards, Reco Knowles -Original Message- From: Andy Kurth [mailto:andy_ku...@ncsu.edu] Sent: Wednesday, February 09, 2011 2:34 PM To: vcl-dev@incubator.apache.org Subject: Re: failed: failed to list data store contents /var/lib/vmware/Virtual Machines on vm host I don't think the attachment came through. Please try to copy/paste it into your email reply. -Andy On 2/8/2011 3:25 PM, Reco Knowles wrote: > Hello Andy, > I have attached a copy of the requested file. > > Regards, > Reco > > > Date: Sun, 6 Feb 2011 11:04:31 -0500 > > From: andy_ku...@ncsu.edu > > To: vcl-dev@incubator.apache.org > > Subject: Re: failed: failed to list data store contents > /var/lib/vmware/Virtual Machines on vm host > > > > Hello, > > Please send the vcld.log file contents for a failed reservation. > > > > Regards, > > Andy > > > > Reco Knowles wrote: > > > Hello, > > > > > > I am having some issues making reservations. Whenever I create a new > > > reservation I get the following error: "failed: failed to list data > store > > > contents /var/lib/vmware/Virtual Machines on vm host". I am running > Vmware > > > server 1.10 and trying to reserve a CentOS image. Any insight as to > why I am > > > getting this error? > > > > > > > > > > > > > > > > > > Regards, > > > > > > Reco Knowles > > > > > >
Re: windows 7 failed to start
Thanks Andy. I'm almost complete with the new Windows 7 image, but Cygwin is not cooperating. I keep getting permission denied errors. The folders have no restrictions and I am the root account with administrator access. I've tried a few work arounds to now avail. Have you seen this behavior before? -Patrick On Feb 9, 2011, at 4:09 PM, Andy Kurth wrote: > I took a closer look at the files you sent. The base image vmx is using > scsi0.virtualDev = "lsisas1068". The vmguest vmx is using scsi0.virtualDev = > "LsiLogic". Setting the vmguest vmx file to lsisas1068 should allow the > guest to boot. > > The VMware SDK and vim-cmd utility return "LsiLogic" even though a virtual > hard drive was created using the "lsisas1068" controller type. If you look > inside the first vmdk file, it probably also contains ddb.adapterType = > "LsiLogic". As a result, it's impossible for VCL to know if an image was > created using LsiLogic or lsisas1068. LsiLogic is used because that's what > VMware reported the disk to be using. > > I'd like to eventually improve the hardware compatibility by saving the data > from the original vmx file when an image is captured and using it to generate > new vmx files when reservations are made. > > For now, avoid lsisas1068. I don't know if the virtual disk can be > converted. I think it will be easiest to recreate the base image. Be sure > to expand the "Product Compatibility" option under "Guest Operating System" > and choose Virtual Hardware version 4. I believe this should cause it to use > LsiLogic. Check the virtualDev value in the vmx file before installing the > OS. ESXi allows you to specify which adapter to use but I don't think Server > 2.0 has this option. > > -Andy > > > > On 2/9/2011 12:18 PM, James Patrick Sigmon wrote: >> It still has the same problem with "winvista-64" in the vmx file. To >> clarify, the original image boots up fine, but the copy VCL makes for a >> reservation doesn't. >> >> Thanks, >> >> Patrick >> >> On Feb 9, 2011, at 10:53 AM, Andy Kurth wrote: >> >>> It looks like VMware Server 2.0 doesn't recognize the Windows 7 guestOS >>> values. Try changing it to "winvista-64" and see if this allows the VM to >>> boot. If this works, I can add an exception in the code to use the >>> winvista guestOS values for Windows 7 under VMware Server 2.0. >>> >>> -Andy >>> >>> On 2/9/2011 3:08 AM, James Patrick Sigmon wrote: Hey Andy, Sorry I for not responding earlier; I had to put this issue on the back burner for a bit for other things. Attached is the output for the vcld.log. Also, the error is currently captured in the attached screenshot. The vmguests for this image still fail to start. Here is the basic output from VMware: [root@server15 Virtual Machines]# vmware-vim-cmd vmsvc/getallvms Vmid Name FileGuest OS Version Annotation 208vmwarewin7-base-v1[local] vmwarewin7-base-v1/vmwarewin7-base-v1.vmx otherGuest vmx-07 384vmguest-3:vmwarewin7-base-v1 [local] vmguest-3_8-v0/vmguest-3_8-v0.vmx otherGuest vmx-07 The guestOS value is "windows7-64." I've also, attached copies of the vmx files for the base image and the vmguest. Thanks, Patrick On Jan 28, 2011, at 2:23 PM, Andy Kurth wrote: > What is the guestOS value in the .vmx file? Also, it would be helpful to > include the vcld.log output. > > -Andy > > On 1/26/2011 3:14 PM, James Patrick Sigmon wrote: >> Hey guys, >> >> With the Internet issue resolved, I was able to return to my Windows 7 >> image and complete the Cygwin install. I proceeded to complete all the >> necessary steps thereafter. >> >> When I make a reservation for the image, it gets to where it boots the >> image then windows fails to load - "Windows failed to start. A recent >> hardware or software change might be the cause" (see attached >> screenshot). >> >> I checked the vmware server manager and the only difference I can see is >> that the vmguest is being assigned the Guest OS: Other (32-bit). As my >> image is a 64-bit, I believe this to be a hint at the problem. I double >> checked the database and the architecture is set to x86_64. So I'm at a >> lose as to what's going on here. >> >> Any ideas? >> >> Thanks, >> >> Patrick Sigmon >> >>
Re: auto image capturing for imaging reservations
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 With 2.2, anyone with access to make imaging reservations will see at least up to 12 hours as the duration for imaging reservations. If they are in a user group with access to longer durations, they'll see the maximum duration of all of their user groups. Josh On Thursday February 10, 2011, Aaron Peeler wrote: > Hi Alex, > > Right, an edit feature would be good on any active imaging reservations. > > In case you haven't had the chance to look at the to 2.2 version, the > release allows the initial duration to be selected for greater than 8 hours > as long as the user is in a usergroup with a longer duration defined. > > Aaron > > On Thu, Feb 10, 2011 at 12:31 PM, Alexander Patterson < > > alexander.patter...@csueastbay.edu> wrote: > > Hello Aaron Peeler, > > > > I think this is a great idea, I have had this happen to me before and > > It's no fun. I would also love to see a easy way to extend the time > > frame that you can create images for. Currently it is set to 8 hours. > > If there was a menu options with a time frame drop down, or even an > > edit mode that would extend the time to create/modify images that > > would be helpful as well as your suggested auto image patch. > > > > -Alex > > > > On Wed, Feb 9, 2011 at 1:01 PM, Mark Gardner wrote: > > > Seems like a desirable feature to me. > > > > > > Mark > > > > > > On Wed, Feb 9, 2011 at 3:48 PM, Aaron Peeler > > > > wrote: > > >> I'd like to add in a feature to automatically capture an image and at > > > > the > > > > >> end of or at the timeout of image creation reservations. > > >> > > >> There have been some cases, where end-users have been in image > > >> creation mode, made many changes, then lost everything due to their > > >> reservation > > > > being > > > > >> timed out. This feature, would at the end of their imaging reservation > > >> automatically start the image capture process instead of timing it > > >> out. > > >> > > >> The changes would be minor and would affect the front end and the > > > > backend > > > > >> inuse module. > > >> > > >> frontend changes: > > >> * add create image routines to available xmlrpc functions > > >> * additionally the frontend would > > >> 1 insert new image if it was a kickstart type image > > >> 2 insert new image if end-user is not the image owner > > >> 3 update the image if end-user is the image owner > > >> > > >> inuse.pm changes > > >> - when end time is reached - 10 minute warning > > >> - and if request has forimaging flag set > > >> - send different message to end-user about automatically starting the > > >> capture process > > >> - call xmrpc_create_image with reservation/request id > > >> - exit quietly from the insue.pm module (imaging process will take > > > > over) > > > > >> Note this would affect anyone here who is using image creation > > > > reservations > > > > >> for long-term reservations to get around the check-user flag. As part > > >> of service loads scheduled for the 2.3 release I think we had planned > > >> to > > > > extend > > > > >> user and user group attributes to disable user checks on per > > >> reservation using a user attribute in addition to the current image > > >> profile > > > > attribute. > > > > >> Unless anyone chimes in over the next days, I'll assume it's ok to > > >> move forward on this change. > > >> > > >> Aaron > > >> > > >> -- > > >> Aaron Peeler > > >> Program Manager > > >> Virtual Computing Lab > > >> NC State University > > > > > > -- > > > Mark Gardner > > > -- > > > > -- > > Thanks, > > Alex Patterson > > User Support Services > > Operating System Analyst > > California State University, East Bay - -- - --- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk1ULMMACgkQV/LQcNdtPQNfqwCfTfrukG9ichrRvKFGR1RNTHGE UHIAn3TkT5kQot4ABUbtYaqDRpyYlWON =YHz4 -END PGP SIGNATURE-
Re: auto image capturing for imaging reservations
Hi Alex, Right, an edit feature would be good on any active imaging reservations. In case you haven't had the chance to look at the to 2.2 version, the release allows the initial duration to be selected for greater than 8 hours as long as the user is in a usergroup with a longer duration defined. Aaron On Thu, Feb 10, 2011 at 12:31 PM, Alexander Patterson < alexander.patter...@csueastbay.edu> wrote: > Hello Aaron Peeler, > > I think this is a great idea, I have had this happen to me before and > It's no fun. I would also love to see a easy way to extend the time > frame that you can create images for. Currently it is set to 8 hours. > If there was a menu options with a time frame drop down, or even an > edit mode that would extend the time to create/modify images that > would be helpful as well as your suggested auto image patch. > > -Alex > > On Wed, Feb 9, 2011 at 1:01 PM, Mark Gardner wrote: > > Seems like a desirable feature to me. > > > > Mark > > > > On Wed, Feb 9, 2011 at 3:48 PM, Aaron Peeler > wrote: > > > >> I'd like to add in a feature to automatically capture an image and at > the > >> end of or at the timeout of image creation reservations. > >> > >> There have been some cases, where end-users have been in image creation > >> mode, made many changes, then lost everything due to their reservation > being > >> timed out. This feature, would at the end of their imaging reservation > >> automatically start the image capture process instead of timing it out. > >> > >> The changes would be minor and would affect the front end and the > backend > >> inuse module. > >> > >> frontend changes: > >> * add create image routines to available xmlrpc functions > >> * additionally the frontend would > >> 1 insert new image if it was a kickstart type image > >> 2 insert new image if end-user is not the image owner > >> 3 update the image if end-user is the image owner > >> > >> inuse.pm changes > >> - when end time is reached - 10 minute warning > >> - and if request has forimaging flag set > >> - send different message to end-user about automatically starting the > >> capture process > >> - call xmrpc_create_image with reservation/request id > >> - exit quietly from the insue.pm module (imaging process will take > over) > >> > >> Note this would affect anyone here who is using image creation > reservations > >> for long-term reservations to get around the check-user flag. As part of > >> service loads scheduled for the 2.3 release I think we had planned to > extend > >> user and user group attributes to disable user checks on per reservation > >> using a user attribute in addition to the current image profile > attribute. > >> > >> Unless anyone chimes in over the next days, I'll assume it's ok to move > >> forward on this change. > >> > >> Aaron > >> > >> -- > >> Aaron Peeler > >> Program Manager > >> Virtual Computing Lab > >> NC State University > >> > > > > > > > > -- > > Mark Gardner > > -- > > > > > > -- > Thanks, > Alex Patterson > User Support Services > Operating System Analyst > California State University, East Bay > -- Aaron Peeler Program Manager Virtual Computing Lab NC State University
Re: auto image capturing for imaging reservations
Hello Aaron Peeler, I think this is a great idea, I have had this happen to me before and It's no fun. I would also love to see a easy way to extend the time frame that you can create images for. Currently it is set to 8 hours. If there was a menu options with a time frame drop down, or even an edit mode that would extend the time to create/modify images that would be helpful as well as your suggested auto image patch. -Alex On Wed, Feb 9, 2011 at 1:01 PM, Mark Gardner wrote: > Seems like a desirable feature to me. > > Mark > > On Wed, Feb 9, 2011 at 3:48 PM, Aaron Peeler wrote: > >> I'd like to add in a feature to automatically capture an image and at the >> end of or at the timeout of image creation reservations. >> >> There have been some cases, where end-users have been in image creation >> mode, made many changes, then lost everything due to their reservation being >> timed out. This feature, would at the end of their imaging reservation >> automatically start the image capture process instead of timing it out. >> >> The changes would be minor and would affect the front end and the backend >> inuse module. >> >> frontend changes: >> * add create image routines to available xmlrpc functions >> * additionally the frontend would >> 1 insert new image if it was a kickstart type image >> 2 insert new image if end-user is not the image owner >> 3 update the image if end-user is the image owner >> >> inuse.pm changes >> - when end time is reached - 10 minute warning >> - and if request has forimaging flag set >> - send different message to end-user about automatically starting the >> capture process >> - call xmrpc_create_image with reservation/request id >> - exit quietly from the insue.pm module (imaging process will take over) >> >> Note this would affect anyone here who is using image creation reservations >> for long-term reservations to get around the check-user flag. As part of >> service loads scheduled for the 2.3 release I think we had planned to extend >> user and user group attributes to disable user checks on per reservation >> using a user attribute in addition to the current image profile attribute. >> >> Unless anyone chimes in over the next days, I'll assume it's ok to move >> forward on this change. >> >> Aaron >> >> -- >> Aaron Peeler >> Program Manager >> Virtual Computing Lab >> NC State University >> > > > > -- > Mark Gardner > -- > -- Thanks, Alex Patterson User Support Services Operating System Analyst California State University, East Bay
could not collect dynamic IP address for node
Hello, I'm having an issue with a new build Image Here is the error Log State Est/Act TimeTotal Time confirming image exists(22) 0:04/0:14 0:14 starting load process(40) 0:06/0:02 0:16 creating configuration file(28) 0:02/5:32 5:48 starting virtual machine(48)0:03/0:04 5:52 machine booting(46) 1:08/9:45 15:37 [b]failed: could not collect dynamic IP address for node[/b] 2011-02-10 09:10:54|18390|36903:36639|new|vmware.pm:load(883)|vmguest-70 ROUND 1 checks loop 52 of 40 2011-02-10 09:10:54|18390|36903:36639|new|utils.pm:run_ssh_command(6180)|executing SSH command on vclesx08: |18390|36903:36639|new| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x vclesx08 'vmware-cmd /virtualmachines/36639vmguest-70/36639vmguest-70.vmx getstate' 2>&1 2011-02-10 09:10:54|18390|36903:36639|new|utils.pm:run_ssh_command(6262)|run_ssh_command output: |18390|36903:36639|new| Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/VMware/VmPerl.pm line 114. |18390|36903:36639|new| getstate() = on 2011-02-10 09:10:54|18390|36903:36639|new|utils.pm:run_ssh_command(6276)|SSH command executed on vclesx08, returning (0, "Use of uninitialized value in ...") 2011-02-10 09:10:54|18390|36903:36639|new|vmware.pm:load(887)|rechecking state of vm vmguest-70 /virtualmachines/36639vmguest-70/36639vmguest-70.vmx 2011-02-10 09:10:54|18390|36903:36639|new|vmware.pm:load(892)|vm vmguest-70 reports on 2011-02-10 09:10:54|18390|36903:36639|new|vmware.pm:load(903)|sshd is NOT active on vmguest-70 yet 2011-02-10 09:10:56|12372|vcld:main(165)|lastcheckin time updated for management node 1: 2011-02-10 09:10:56 2011-02-10 09:10:56|18814|36902:36638|inuse|utils.pm:check_connection(1765)|checking for connection by yw5765 on vmguest-59, attempt 23 2011-02-10 09:10:56|18814|36902:36638|inuse|utils.pm:run_ssh_command(6180)|executing SSH command on vmguest-59: |18814|36902:36638|inuse| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x vmguest-59 'netstat -an' 2>&1 2011-02-10 09:11:01|12372|vcld:main(165)|lastcheckin time updated for management node 1: 2011-02-10 09:11:01 2011-02-10 09:11:05|18390|36903:36639|new|vmware.pm:load(883)|vmguest-70 ROUND 1 checks loop 53 of 40 2011-02-10 09:11:05|18390|36903:36639|new|utils.pm:run_ssh_command(6180)|executing SSH command on vclesx08: |18390|36903:36639|new| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x vclesx08 'vmware-cmd /virtualmachines/36639vmguest-70/36639vmguest-70.vmx getstate' 2>&1 2011-02-10 09:11:05|18390|36903:36639|new|utils.pm:run_ssh_command(6262)|run_ssh_command output: |18390|36903:36639|new| Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/VMware/VmPerl.pm line 114. |18390|36903:36639|new| getstate() = on 2011-02-10 09:11:05|18390|36903:36639|new|utils.pm:run_ssh_command(6276)|SSH command executed on vclesx08, returning (0, "Use of uninitialized value in ...") 2011-02-10 09:11:05|18390|36903:36639|new|vmware.pm:load(887)|rechecking state of vm vmguest-70 /virtualmachines/36639vmguest-70/36639vmguest-70.vmx 2011-02-10 09:11:05|18390|36903:36639|new|vmware.pm:load(892)|vm vmguest-70 reports on Use of uninitialized value in pattern match (m//) at /usr/local/vcl/bin/../lib/VCL/utils.pm line 2745 (#1) |18390|36903:36639|new| WARNING |18390|36903:36639|new| 2011-02-10 09:11:05|18390|36903:36639|new|vcld:warning_handler(636)|Use of uninitialized value in pattern match (m//) at /usr/local/vcl/bin/../lib/VCL/utils.pm line 2745. |18390|36903:36639|new| ( 0) utils.pm, notify (line: 737) |18390|36903:36639|new| (-1) vcld, warning_handler (line: 636) |18390|36903:36639|new| (-2) utils.pm, _sshd_status (line: 2745) |18390|36903:36639|new| (-3) vmware.pm, load (line: 894) |18390|36903:36639|new| (-4) new.pm, reload_image (line: 665) |18390|36903:36639|new| (-5) new.pm, process (line: 266) |18390|36903:36639|new| (-6) vcld, make_new_child (line: 594) |18390|36903:36639|new| WARNING |18390|36903:36639|new| 2011-02-10 09:11:05|18390|36903:36639|new|vcld:warning_handler(636)|Use of uninitialized value in pattern match (m//) at /usr/local/vcl/bin/../lib/VCL/utils.pm line 2745. |18390|36903:36639|new| ( 0) utils.pm, notify (line: 737) |18390|36903:36639|new| (-1) vcld, warning_handler (line: 636) |18390|36903:36639|new| (-2) utils.pm, _sshd_status (line: 2745) |18390|36903:36639|new| (-3) vmware.pm, load (line: 894) |18390|36903:36639|new| (-4) new.pm, reload_image (line: 665) |18390|36903:36639|new| (-5) new.pm, process (line: 266) |18390|36903:36639|new| (-6) vcld, make_new_child (line: 594) 2011-02-10 09:11:05|18390|36903:36639|new|utils.pm:run_ssh_command(6180)|executing SSH command on vmguest-70: |18390|36903:36639|new| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x vmguest-70 'uname -s' 2>&1 2011-02-10 09:11:06|12372|vcld:main(165)|lastcheckin time updated for management node 1: 2011-02-10 09:11:06 2011-02-10
