subject:"Windows 7 and Windows XP give same error when trying to capture"

Re: Windows 7 and Windows XP give same error when trying to capture

2011-04-15 Thread Andy Kurth

Ahh, I think I found the problem.  There's a typo in your VM profile 
configuration:

"ethernet0.networkName" => "HostyOnly",

Change this to "HostOnly" then make a new reservation.

-Andy

On 4/14/2011 4:35 PM, Tyler Hardesty wrote:

Well I followed the updated DHCP instructions and I'm still getting the:
2011-04-14
14:10:21|8980|64:64|reload|Module.pm:code_loop_timeout(728)|attempt 57:
waiting for vm-1 to respond to SSH
2011-04-14 14:10:21|8980|64:64|reload|OS.pm:is_ssh_responding(386)|vm-1
is NOT responding to SSH, ports 22 or 24 are both closed
2011-04-14
14:10:21|8980|64:64|reload|Module.pm:code_loop_timeout(724)|attempt 57:
code returned false, seconds elapsed/remaining: 474/426, sleeping for 8
seconds.
But, my /var/log/messages looks like yours withouth the request/ack at
the end... Watching VMware when trying to create a reservation, the
images that VCL creates still have 169.254.xxx.xxx on NA1 and 0.0.0.0 on
NA2... do you know of any other log files I can look at to try and see
what else is going on?

/var/log/messages:
Apr 14 14:23:25 vcl dhcpd: Internet Systems Consortium DHCP Server
V3.0.5-RedHat
Apr 14 14:23:25 vcl dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Apr 14 14:23:25 vcl dhcpd: All rights reserved.
Apr 14 14:23:25 vcl dhcpd: For info, please visit
http://www.isc.org/sw/dhcp/
Apr 14 14:23:25 vcl dhcpd: WARNING: Host declarations are global.  They
are not limited to the scope you declared them in.
Apr 14 14:23:25 vcl dhcpd: Wrote 0 deleted host decls to leases file.
Apr 14 14:23:25 vcl dhcpd: Wrote 0 new dynamic host decls to leases file.
Apr 14 14:23:25 vcl dhcpd: Wrote 0 leases to leases file.
Apr 14 14:23:25 vcl dhcpd: Listening on LPF/vmnet1/00:50:56:c0:00:01/vmnet1
Apr 14 14:23:25 vcl dhcpd: Sending on   LPF/vmnet1/00:50:56:c0:00:01/vmnet1
Apr 14 14:23:25 vcl dhcpd: Sending on   Socket/fallback/fallback-net
Apr 14 14:23:56 vcl /usr/lib/vmware/bin/vmware-hostd[17786]: Accepted
password for user root from 127.0.0.1
Apr 14 14:24:28 vcl last message repeated 12 times

[root@vcl ~]# ps -ef |grep dhcp
root 12616 1  0 14:23 ?00:00:00 /usr/sbin/dhcpd vmnet1
root 14881  8477  0 14:29 pts/200:00:00 grep dhcp

[root@vcl ~]# cat /etc/sysconfig/dhcpd
# Command line options here
DHCPDARGS=vmnet1

[root@vcl ~]# cat /etc/init.d/dhcpd
#!/bin/sh
#
### BEGIN INIT INFO
# Provides: dhcpd
# Default-Start:
# Default-Stop:
# Should-Start:
# Required-Start: $network
# Required-Stop:
# Short-Description: Start and stop the DHCP server
# Description: dhcpd provides the Dynamic Host Configuration Protocol (DHCP)
#  server.
### END INIT INFO
#
# The fields below are left around for legacy tools (will remove later).
#
# chkconfig: - 65 35
# description: dhcpd provides the Dynamic Host Configuration Protocol
(DHCP) \
#  server
# processname: dhcpd
# config: /etc/dhcpd.conf
# config: /var/lib/dhcpd/dhcpd.leases
# pidfile: /var/run/dhcpd.pid

. /etc/init.d/functions

RETVAL=0

prog=dhcpd
dhcpd=/usr/sbin/dhcpd
lockfile=/var/lock/subsys/dhcpd
pidfile=/var/run/dhcpd.pid
statedir=/var/lib/dhcpd

[ -f /etc/sysconfig/dhcpd ] && . /etc/sysconfig/dhcpd

# if the user specified a different config file, make sure we reference it
findConfig() {
 for arg in $DHCPDARGS ; do
 if [ "$found" = 1 ]; then
 [ -f "$arg" ] && echo "$arg"
 return
 fi
 if [ "$arg" = "-cf" ]; then
 found=1
 continue
 fi
 done
 echo "/etc/dhcpd.conf"
}

conf="$(findConfig "$DHCPDARGS")"

if [ ! -f $statedir/dhcpd.leases ] ; then
 mkdir -p $statedir
 touch $statedir/dhcpd.leases
 [ -x /sbin/restorecon ] && [ -d /selinux ] && /sbin/restorecon
$statedir/dhcpd.leases >/dev/null 2>&1
fi

configtest() {
 [ -x $dhcpd ] || return 5
 [ -f $conf ] || return 6
 $dhcpd -q -t -cf $conf
 RETVAL=$?
 if [ $RETVAL -eq 1 ]; then
 $dhcpd -t -cf $conf
 else
 echo "Syntax: OK" >&2
 fi
 return $RETVAL
}

start() {
 [ -x $dhcpd ] || return 5
 [ -f $conf ] || return 6

 pidofproc $prog >/dev/null 2>&1
 RETVAL=$?
 [ $RETVAL -eq 0 ] && return $RETVAL

 echo -n $"Starting $prog: "
 daemon $dhcpd $DHCPDARGS 2>/dev/null
 RETVAL=$?
 echo
 [ $RETVAL = 0 ] && touch $lockfile
 return $RETVAL
}

stop() {
 pidofproc $prog >/dev/null 2>&1
 if [ $? -ne 0 ]; then
 RETVAL=7
 return $RETVAL
 fi

 echo -n $"Shutting down $prog: "
 killproc $prog
 RETVAL=$?
 [ $RETVAL = 0 ] && rm -f $lockfile
 echo
 return $RETVAL
}

if [ $# -gt 1 ]; then
 RETVAL=2
 exit $RETVAL
fi

case "$1" in
 start)
 start
 RETVAL=$?
 ;;
 stop)
 stop
 RETVAL=$?
 ;;
 restart|force-reload)
 stop ; start
 RETVAL=$?
 ;;
 condrestart)
 if [ -f $lockfile ]; then
 stop ; start
 RETVAL=$?
 fi

Re: Windows 7 and Windows XP give same error when trying to capture

2011-04-13 Thread Andy Kurth


I have updated the DHCP instructions on:
https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+Management+Node+Installation

Redo the "Install & Configure the DHCP Service" instructions.  Remove 
the "vmnet1" string if you previously added it to /etc/init.d/dhcpd. 
The instructions now explain to modify /etc/sysconfig/dhcpd to achieve 
the same result.  Having "vmnet1" added to both of these files will 
cause the "No subnet declaration for vmnet1 (0.0.0.0)" message.


I tested the instructions and DHCP is working for me.  My 
/var/log/messages output looks like this:


Apr 13 12:43:44 blade1g2-6 dhcpd: Internet Systems Consortium DHCP 
Server V3.0.5-RedHat
Apr 13 12:43:44 blade1g2-6 dhcpd: Copyright 2004-2006 Internet Systems 
Consortium.

Apr 13 12:43:44 blade1g2-6 dhcpd: All rights reserved.
Apr 13 12:43:44 blade1g2-6 dhcpd: For info, please visit 
http://www.isc.org/sw/dhcp/
Apr 13 12:43:44 blade1g2-6 dhcpd: WARNING: Host declarations are global. 
 They are not limited to the scope you declared them in.

Apr 13 12:43:44 blade1g2-6 dhcpd: Wrote 0 deleted host decls to leases file.
Apr 13 12:43:44 blade1g2-6 dhcpd: Wrote 0 new dynamic host decls to 
leases file.

Apr 13 12:43:44 blade1g2-6 dhcpd: Wrote 0 leases to leases file.
Apr 13 12:43:44 blade1g2-6 dhcpd: Listening on 
LPF/vmnet1/00:50:56:c0:00:01/vmnet1
Apr 13 12:43:44 blade1g2-6 dhcpd: Sending on 
LPF/vmnet1/00:50:56:c0:00:01/vmnet1

Apr 13 12:43:44 blade1g2-6 dhcpd: Sending on   Socket/fallback/fallback-net
Apr 13 12:48:45 blade1g2-6 dhcpd: DHCPREQUEST for 192.168.1.1 from 
00:50:56:1a:01:01 via vmnet1
Apr 13 12:48:45 blade1g2-6 dhcpd: DHCPACK on 192.168.1.1 to 
00:50:56:1a:01:01 via vmnet1


-Andy


On 4/12/2011 7:24 PM, Tyler Hardesty wrote:

Here is also another update.. after killing the vmnet-dhcpd I tried just
creating a whole new base image and capturing it again, although I get
the same "not responding to ssh message", a new message popped up in
/var/log/messages... it says no subnet declaration for vmnet1, but as
you can see from my previous email I do have that set in /etc/dhcpd ...:

Apr 12 15:07:15 vcl /usr/lib/vmware/bin/vmware-hostd[4112]: Accepted
password for user root from 127.0.0.1
Apr 12 15:07:16 vcl kernel: device eth0 left promiscuous mode
Apr 12 15:07:16 vcl kernel: bridge-eth0: disabled promiscuous mode
Apr 12 15:07:16 vcl kernel: device eth0 entered promiscuous mode
Apr 12 15:07:16 vcl kernel: bridge-eth0: enabled promiscuous mode
Apr 12 15:07:17 vcl /usr/lib/vmware/bin/vmware-hostd[4112]: Accepted
password for user root from 127.0.0.1
Apr 12 17:03:24 vcl dhcpd: Internet Systems Consortium DHCP Server
V3.0.5-RedHat
Apr 12 17:03:24 vcl dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Apr 12 17:03:24 vcl dhcpd: All rights reserved.
Apr 12 17:03:24 vcl dhcpd: For info, please visit
http://www.isc.org/sw/dhcp/
Apr 12 17:03:24 vcl dhcpd: WARNING: Host declarations are global.  They
are not limited to the scope you declared them in.
Apr 12 17:03:24 vcl dhcpd: Wrote 0 deleted host decls to leases file.
Apr 12 17:03:24 vcl dhcpd: Wrote 0 new dynamic host decls to leases file.
Apr 12 17:03:24 vcl dhcpd: Wrote 0 leases to leases file.
Apr 12 17:03:24 vcl dhcpd: Listening on LPF/vmnet1/00:50:56:c0:00:01/vmnet1
Apr 12 17:03:24 vcl dhcpd: Sending on   LPF/vmnet1/00:50:56:c0:00:01/vmnet1
Apr 12 17:03:24 vcl dhcpd:
Apr 12 17:03:24 vcl dhcpd: No subnet declaration for vmnet1 (0.0.0.0).
Apr 12 17:03:24 vcl dhcpd: ** Ignoring requests on vmnet1.  If this is
not what
Apr 12 17:03:24 vcl dhcpd:you want, please write a subnet declaration
Apr 12 17:03:24 vcl dhcpd:in your dhcpd.conf file for the network
segment
Apr 12 17:03:24 vcl dhcpd:to which interface vmnet1 is attached. **
Apr 12 17:03:24 vcl dhcpd:
Apr 12 17:03:24 vcl dhcpd: Sending on   Socket/fallback/fallback-net


On Tue, Apr 12, 2011 at 1:48 PM, Tyler Hardesty mailto:tharde...@gmail.com>> wrote:

You are correct, I saw both of those listed, so I kept: 'root
23941 1  0 Apr08 ?00:00:00 /usr/sbin/dhcpd vmnet1
vmnet1' and I killed the other one. The messages log doesn't seem to
be of much use (or maybe the lack there of tells us something?) I
tried reseting the VMs and even just powered them down and tried a
new reservation and I still get the same not responding to ssh
message and this is the output in the /var/log/messages:

Apr 12 12:40:44 vcl kernel: device eth0 left promiscuous mode
Apr 12 12:40:44 vcl kernel: bridge-eth0: disabled promiscuous mode
Apr 12 12:44:29 vcl /usr/lib/vmware/bin/vmware-hostd[1533]: Accepted
password for user root from 127.0.0.1
Apr 12 12:45:00 vcl last message repeated 13 times
Apr 12 12:45:04 vcl last message repeated 2 times
Apr 12 12:45:05 vcl kernel: device eth0 entered promiscuous mode
Apr 12 12:45:05 vcl kernel: bridge-eth0: enabled promiscuous mode
Apr 12 12:45:06 vcl /usr/lib/vmware/bin/vmware-hostd[1533]: Accepted
password for user root from 127.0

Re: Windows 7 and Windows XP give same error when trying to capture

2011-04-12 Thread Tyler Hardesty

You are correct, I saw both of those listed, so I kept: 'root 23941
1  0 Apr08 ?00:00:00 /usr/sbin/dhcpd vmnet1 vmnet1' and I killed the
other one. The messages log doesn't seem to be of much use (or maybe the
lack there of tells us something?) I tried reseting the VMs and even just
powered them down and tried a new reservation and I still get the same not
responding to ssh message and this is the output in the /var/log/messages:

Apr 12 12:40:44 vcl kernel: device eth0 left promiscuous mode
Apr 12 12:40:44 vcl kernel: bridge-eth0: disabled promiscuous mode
Apr 12 12:44:29 vcl /usr/lib/vmware/bin/vmware-hostd[1533]: Accepted
password for user root from 127.0.0.1
Apr 12 12:45:00 vcl last message repeated 13 times
Apr 12 12:45:04 vcl last message repeated 2 times
Apr 12 12:45:05 vcl kernel: device eth0 entered promiscuous mode
Apr 12 12:45:05 vcl kernel: bridge-eth0: enabled promiscuous mode
Apr 12 12:45:06 vcl /usr/lib/vmware/bin/vmware-hostd[1533]: Accepted
password for user root from 127.0.0.1
Apr 12 12:45:10 vcl last message repeated 2 times
Apr 12 12:45:12 vcl kernel: device eth0 left promiscuous mode
Apr 12 12:45:12 vcl kernel: bridge-eth0: disabled promiscuous mode
Apr 12 12:45:12 vcl kernel: device eth0 entered promiscuous mode
Apr 12 12:45:12 vcl kernel: bridge-eth0: enabled promiscuous mode

-Tyler

On Tue, Apr 12, 2011 at 11:54 AM, Andy Kurth  wrote:

> It looks like you're close.  DHCP on the private host-only network isn't
> working.  The VM that VCL created was assigned the correct MAC addresses:
> |15920|53:53|reload| :   "ethernet0.address" => "00:50:56:1a:01:01",
> |15920|53:53|reload| :   "ethernet1.address" => "00:50:56:1a:01:02",
>
> I think it may be failing because VMware installed and started its own DHCP
> service when the host-only network was configured.  Run this command:
> ps -ef | grep dhcp
>
> Do you see 2 processes that look like this?:
> /usr/sbin/dhcpd vmnet1
>
> /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf
> /etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid
> vmnet1
>
> If you do see the vmnet-dhcpd process along with dhcpd, try killing the
> vmnet-dhcpd process.  Hopefully this allows the normal dhcpd process to
> respond to the VM's DHCP request.
>
> The main way to debug DHCP problems is to look at /var/log/messages. Try
> running the following command:
> tail -f /var/log/messages | grep -i dhcp
>
> Then reboot the VM that VCL created.  If the VM's DHCP request is getting
> to the dhcpd service running on the management node then you should see
> output containing the private MAC address: 00:50:56:1a:01:01.
>
> The public IP address isn't necessarily a problem.  Once the private
> interface gets an IP address and responds to SSH, vcld will SSH in and
> configure the public interface with a static address if you have configured
> the management node and IP address for the VM in the VCL database
> accordingly.
>
> -Andy
>
>
> On 4/11/2011 1:41 PM, Tyler Hardesty wrote:
>
>> Ok, sorry to be such a bug with the same problem but I've done
>> everything exactly how it is in the link that you provided and after
>> this image is created, it still fails to be reserved saying it's not
>> responding to ssh. Here are some of my configs:
>>
>> [root@vcl ~]# ifconfig
>> eth0  Link encap:Ethernet  HWaddr 00:1B:63:99:DA:B6
>>   inet addr:144.38.205.200 
>>  Bcast:144.38.205.255   Mask:255.255.255.128
>>
>>   inet6 addr: fe80::21b:63ff:fe99:dab6/64 Scope:Link
>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>   RX packets:26728797 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:14037294 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000
>>   RX bytes:3637195452 (3.3 GiB)  TX bytes:2717331485 (2.5 GiB)
>>   Interrupt:185
>>
>> loLink encap:Local Loopback
>>   inet addr:127.0.0.1  Mask:255.0.0.0
>>   inet6 addr: ::1/128 Scope:Host
>>   UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>   RX packets:714243376 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:714243376 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:0
>>   RX bytes:2461321418 (2.2 GiB)  TX bytes:2461321418 (2.2 GiB)
>>
>> vmnet1Link encap:Ethernet  HWaddr 00:50:56:C0:00:01
>>   inet addr:192.168.0.1  Bcast:192.168.255.255  Mask:255.255.0.0
>>   inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>   RX packets:4237 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:6875 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000
>>   RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>
>> [root@vcl ~]# cat /etc/dhcpd.conf
>> #
>> # DHCP Server Configuration file.
>> #   see /usr/share/doc/dhcp*/dhcpd.conf.sample
>> #
>> ddns-update-style none; shared-network vmnet1 {
>>

Re: Windows 7 and Windows XP give same error when trying to capture

2011-04-12 Thread Andy Kurth

It looks like you're close.  DHCP on the private host-only network isn't 
working.  The VM that VCL created was assigned the correct MAC addresses:

|15920|53:53|reload| :   "ethernet0.address" => "00:50:56:1a:01:01",
|15920|53:53|reload| :   "ethernet1.address" => "00:50:56:1a:01:02",

I think it may be failing because VMware installed and started its own 
DHCP service when the host-only network was configured.  Run this command:

ps -ef | grep dhcp

Do you see 2 processes that look like this?:
/usr/sbin/dhcpd vmnet1

/usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf 
/etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf 
/var/run/vmnet-dhcpd-vmnet1.pid vmnet1


If you do see the vmnet-dhcpd process along with dhcpd, try killing the 
vmnet-dhcpd process.  Hopefully this allows the normal dhcpd process to 
respond to the VM's DHCP request.


The main way to debug DHCP problems is to look at /var/log/messages. 
Try running the following command:

tail -f /var/log/messages | grep -i dhcp

Then reboot the VM that VCL created.  If the VM's DHCP request is 
getting to the dhcpd service running on the management node then you 
should see output containing the private MAC address: 00:50:56:1a:01:01.


The public IP address isn't necessarily a problem.  Once the private 
interface gets an IP address and responds to SSH, vcld will SSH in and 
configure the public interface with a static address if you have 
configured the management node and IP address for the VM in the VCL 
database accordingly.


-Andy

On 4/11/2011 1:41 PM, Tyler Hardesty wrote:

Ok, sorry to be such a bug with the same problem but I've done
everything exactly how it is in the link that you provided and after
this image is created, it still fails to be reserved saying it's not
responding to ssh. Here are some of my configs:

[root@vcl ~]# ifconfig
eth0  Link encap:Ethernet  HWaddr 00:1B:63:99:DA:B6
   inet addr:144.38.205.200 
  Bcast:144.38.205.255   Mask:255.255.255.128
   inet6 addr: fe80::21b:63ff:fe99:dab6/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:26728797 errors:0 dropped:0 overruns:0 frame:0
   TX packets:14037294 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:3637195452 (3.3 GiB)  TX bytes:2717331485 (2.5 GiB)
   Interrupt:185

loLink encap:Local Loopback
   inet addr:127.0.0.1  Mask:255.0.0.0
   inet6 addr: ::1/128 Scope:Host
   UP LOOPBACK RUNNING  MTU:16436  Metric:1
   RX packets:714243376 errors:0 dropped:0 overruns:0 frame:0
   TX packets:714243376 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:2461321418 (2.2 GiB)  TX bytes:2461321418 (2.2 GiB)

vmnet1Link encap:Ethernet  HWaddr 00:50:56:C0:00:01
   inet addr:192.168.0.1  Bcast:192.168.255.255  Mask:255.255.0.0
   inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:4237 errors:0 dropped:0 overruns:0 frame:0
   TX packets:6875 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@vcl ~]# cat /etc/dhcpd.conf
#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample
#
ddns-update-style none; shared-network vmnet1 {
  subnet 192.168.0.0 netmask 255.255.0.0 {
  ignore unknown-clients;
  option routers 192.168.0.1;
host vm-1 {
option host-name "vm-1";
hardware ethernet 00:50:56:1a:01:01;
fixed-address 192.168.1.1;
filename "/tftpboot/pxelinux.0";
option dhcp-server-identifier 127.0.0.1;
next-server 127.0.0.1;
}

host vm-2 {
option host-name "vm-2";
hardware ethernet 00:50:56:1a:01:03;
fixed-address 192.168.1.2;
filename "/tftpboot/pxelinux.0";
option dhcp-server-identifier 127.0.0.1;
next-server 127.0.0.1;
}

host vm-3 {
option host-name "vm-3";
hardware ethernet 00:50:56:1a:01:05;
fixed-address 192.168.1.3;
filename "/tftpboot/pxelinux.0";
option dhcp-server-identifier 127.0.0.1;
next-server 127.0.0.1;
}
.
.

   }
}

When I set up the VM Base machines, I followed the instructions on the
site with network adapter 1 set to HostOnly and network adapter 2 set to
Bridged... the host only network gets automatically configured with a
192.168.128.x ip so I statically set it to 192.168.1.x to match what's
in the database and I statically set network adapter 2 with
144.38.205.201  . after the image is captured
and it tries to make a reservation I notice that the network adapter 1
has an IP of 169.254.212.140 (or 169.254.xxx.xxx) and adapter 2 has an
IP of 0.0.0.0 ... Does that even matter? Here are some snippets of my
log file (my full log file can be found here -
http://tylerhardesty.info/it4600/reslog.txt and again, sorry for being
so trouble

Re: Windows 7 and Windows XP give same error when trying to capture

2011-04-11 Thread Tyler Hardesty

Ok, sorry to be such a bug with the same problem but I've done everything
exactly how it is in the link that you provided and after this image is
created, it still fails to be reserved saying it's not responding to ssh.
Here are some of my configs:

[root@vcl ~]# ifconfig
eth0  Link encap:Ethernet  HWaddr 00:1B:63:99:DA:B6
  inet addr:144.38.205.200  Bcast:144.38.205.255 Mask:255.255.255.128
  inet6 addr: fe80::21b:63ff:fe99:dab6/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:26728797 errors:0 dropped:0 overruns:0 frame:0
  TX packets:14037294 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:3637195452 (3.3 GiB)  TX bytes:2717331485 (2.5 GiB)
  Interrupt:185

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:714243376 errors:0 dropped:0 overruns:0 frame:0
  TX packets:714243376 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:2461321418 (2.2 GiB)  TX bytes:2461321418 (2.2 GiB)

vmnet1Link encap:Ethernet  HWaddr 00:50:56:C0:00:01
  inet addr:192.168.0.1  Bcast:192.168.255.255  Mask:255.255.0.0
  inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:4237 errors:0 dropped:0 overruns:0 frame:0
  TX packets:6875 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@vcl ~]# cat /etc/dhcpd.conf
#
# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp*/dhcpd.conf.sample
#
ddns-update-style none; shared-network vmnet1 {
 subnet 192.168.0.0 netmask 255.255.0.0 {
 ignore unknown-clients;
 option routers 192.168.0.1;
host vm-1 {
option host-name "vm-1";
 hardware ethernet 00:50:56:1a:01:01;
fixed-address 192.168.1.1;
filename "/tftpboot/pxelinux.0";
 option dhcp-server-identifier 127.0.0.1;
next-server 127.0.0.1;
}

host vm-2 {
option host-name "vm-2";
hardware ethernet 00:50:56:1a:01:03;
 fixed-address 192.168.1.2;
filename "/tftpboot/pxelinux.0";
 option dhcp-server-identifier 127.0.0.1;
next-server 127.0.0.1;
}

host vm-3 {
option host-name "vm-3";
hardware ethernet 00:50:56:1a:01:05;
 fixed-address 192.168.1.3;
filename "/tftpboot/pxelinux.0";
 option dhcp-server-identifier 127.0.0.1;
next-server 127.0.0.1;
}
   .
   .

  }
}

When I set up the VM Base machines, I followed the instructions on the site
with network adapter 1 set to HostOnly and network adapter 2 set to
Bridged... the host only network gets automatically configured with a
192.168.128.x ip so I statically set it to 192.168.1.x to match what's in
the database and I statically set network adapter 2 with
144.38.205.201. after the image is captured and it tries to make a
reservation I
notice that the network adapter 1 has an IP of 169.254.212.140 (or
169.254.xxx.xxx) and adapter 2 has an IP of 0.0.0.0 ... Does that even
matter? Here are some snippets of my log file (my full log file can be found
here - http://tylerhardesty.info/it4600/reslog.txt and again, sorry for
being so troublesome but thanks for all the help):

2011-04-11 01:58:11|15920|53:53|reload|VMware.pm:prepare_vmx(1699)|created
temporary vmx file: /tmp/vm-1_34-v0.vmx
2011-04-11
01:58:12|15920|53:53|reload|Linux.pm:create_directory(1502)|directory
already exists on localvmhost: '/var/lib/vmware/Virtual Machines/vm-1_34-v0'
2011-04-11 01:58:12|15920|53:53|reload|utils.pm:run_scp_command(5584)|attempting
to copy file via SCP: '/tmp/vm-1_34-v0.vmx' -->
'localvmhost:"/var/lib/vmware/Virtual\ Machines/vm-1_34-v0/vm-1_34-v0.vmx"'
2011-04-11 01:58:12|15920|53:53|reload|utils.pm:run_scp_command(5620)|copied
file via SCP: '/tmp/vm-1_34-v0.vmx' -->
'localvmhost:"/var/lib/vmware/Virtual\ Machines/vm-1_34-v0/vm-1_34-v0.vmx"'
2011-04-11 01:58:12|15920|53:53|reload|Linux.pm:copy_file_to(1837)|copied
file from management node to localvmhost: '/tmp/vm-1_34-v0.vmx' -->
localvmhost:'/var/lib/vmware/Virtual Machines/vm-1_34-v0/vm-1_34-v0.vmx'
2011-04-11 01:58:12|15920|53:53|reload|VMware.pm:prepare_vmx(1711)|created
vmx file on VM host: /var/lib/vmware/Virtual
Machines/vm-1_34-v0/vm-1_34-v0.vmx
2011-04-11 01:58:12|15920|53:53|reload|VMware.pm:prepare_vmx(1714)|deleted
temporary vmx file: /tmp/vm-1_34-v0.vmx
2011-04-11 01:58:12|15920|53:53|reload|utils.pm:insertloadlog(3875)|inserted
computer=8, vmsetupconfig, prepared vmx file
2011-04-11 01:58:12|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd
call count: 6 (vmsvc/getallvms)
2011-04-11 01:58:13|30717|vcld:main(167)|lastcheckin time updated for
management node 1: 2011-04-11 01:58:13
2011-04-11 01:58:14|15920|53:53|reload|VIM_SSH.pm:_run_vim_cmd(

Re: Windows 7 and Windows XP give same error when trying to capture

2011-04-07 Thread Andy Kurth

DHCP is a requirement for the private interface but you should still be 
able to get it to work.  I have configured similar installations before. 
 For the private network, you'll want to configure a VMware host-only 
network, not a bridged network.


I created updated instructions to configure a standalone environment 
using VMware Server 2.0:

https://cwiki.apache.org/confluence/display/VCL/Configuring+a+Standalone+VCL+Environment+using+VMware+Server+2.0

The instructions haven't been tested and there are probably a couple 
errors but this will hopefully point you in the right direction.


To use static public addresses, you just need to define them when you 
add new computers and configure the management node to use static 
addresses and specify the correct subnet mask, gateway, and DNS servers 
under Management Nodes > Edit.


-Andy


On 4/6/2011 4:03 PM, Tyler Hardesty wrote:

Thanks Andy, you have been sooo helpful!! My image seemed to capture
successfully, but it wasn't the Data Store Path I had to clear, it was
the Image repository path, then I ran setup again and it said image
capture successful... however now I can't seem to successfully reserve
the image... I still think it has something to do with the ip, do I need
to change to a static setup since I don't have a DHCP server handing out
IPs (i.e. this is a single machine running everything (vmware, Apache
VCL, management node, etc) that is located inside the network closet at
my school and is statically assigned an ip of 144.38.205.200 and I am
allowed to use IPs up til about 205.215 but they aren't handed out by a
DHCP server). Well you will probably know better, this is my log output:

2011-04-06
12:39:59|1614|42:42|new|Module.pm:code_loop_timeout(724)|attempt 107:
code returned false, seconds el\
apsed/remaining: 898/2, sleeping for 8 seconds
2011-04-06 12:40:03|30717|vcld:main(167)|lastcheckin time updated for
management node 1: 2011-04-06 12:40:03
2011-04-06
12:40:07|1614|42:42|new|Module.pm:code_loop_timeout(728)|attempt 108:
waiting for vm4 to respond to S\
SH
2011-04-06 12:40:07|1614|42:42|new|OS.pm:is_ssh_responding(386)|vm4 is
NOT responding to SSH, ports 22 or 24 are\
  both closed
2011-04-06
12:40:07|1614|42:42|new|Module.pm:code_loop_timeout(736)|waiting for vm4
to respond to SSH, code did \
not return true after waiting 900 seconds

|1614|42:42|new|  WARNING 
|1614|42:42|new| 2011-04-06
12:40:07|1614|42:42|new|OS.pm:wait_for_response(465)|failed to connect
to vm4 via SS\
H after 900 seconds
|1614|42:42|new| ( 0) OS.pm, wait_for_response (line: 465)
|1614|42:42|new| (-1) Windows.pm, post_load (line: 591)
|1614|42:42|new| (-2) VMware.pm, load (line: 415)
|1614|42:42|new| (-3) new.pm , reload_image (line: 687)
|1614|42:42|new| (-4) new.pm , process (line: 282)
|1614|42:42|new| (-5) vcld, make_new_child (line: 568)


|1614|42:42|new|  WARNING 
|1614|42:42|new| 2011-04-06
12:40:07|1614|42:42|new|Windows.pm:post_load(592)|vm4 never responded to SSH
|1614|42:42|new| ( 0) Windows.pm, post_load (line: 592)
|1614|42:42|new| (-1) VMware.pm, load (line: 415)
|1614|42:42|new| (-2) new.pm , reload_image (line: 687)
|1614|42:42|new| (-3) new.pm , process (line: 282)
|1614|42:42|new| (-4) vcld, make_new_child (line: 568)
|1614|42:42|new| (-5) vcld, main (line: 346)


|1614|42:42|new|  WARNING 
|1614|42:42|new| 2011-04-06
12:40:07|1614|42:42|new|VMware.pm:load(419)|failed to perform OS
post-load tasks on \
VM vm4 on VM host: localvmhost
|1614|42:42|new| ( 0) VMware.pm, load (line: 419)
|1614|42:42|new| (-1) new.pm , reload_image (line: 687)
|1614|42:42|new| (-2) new.pm , process (line: 282)
|1614|42:42|new| (-3) vcld, make_new_child (line: 568)
|1614|42:42|new| (-4) vcld, main (line: 346)


|1614|42:42|new|  WARNING 
|1614|42:42|new| 2011-04-06
12:40:07|1614|42:42|new|new.pm:reload_image(692)|vmwarewinxp-xp231-v0
failed to load\
  on vm4, returning
|1614|42:42|new| ( 0) new.pm , reload_image (line: 692)
|1614|42:42|new| (-1) new.pm , process (line: 282)
|1614|42:42|new| (-2) vcld, make_new_child (line: 568)
|1614|42:42|new| (-3) vcld, main (line: 346)

2011-04-06 12:40:07|1614|42:42|new|utils.pm:insertloadlog(3875)|inserted
computer=5, loadimagefailed, vmwarewinx\
p-xp231-v0 failed to load on vm4

|1614|42:42|new|  WARNING 
|1614|42:42|new| 2011-04-06
12:40:07|1614|42:42|new|new.pm:process(329)|failed to load vm4 with
vmwarewinxp-xp23\
1-v0
|1614|42:42|new| ( 0) new.pm , process (line: 329)
|1614|42:42|new| (-1) vcld, make_new_child (line: 568)
|1614|42:42|new| (-2) vcld, main (line: 346)

2011-04-06
12:40:07|1614|42:42|new|DataStructure.pm:get_computer_state_name(2299)|attempting
to retrieve current\
  state of computer vm4 from the database
2011-04-06
12:40:07|1614|42:42|new|DataStructure.pm:get_computer_state_name(2330)|retrieved
current state of com\
puter vm4 from the da

Re: Windows 7 and Windows XP give same error when trying to capture

2011-04-06 Thread Tyler Hardesty

Thanks Andy, you have been sooo helpful!! My image seemed to capture
successfully, but it wasn't the Data Store Path I had to clear, it was the
Image repository path, then I ran setup again and it said image capture
successful... however now I can't seem to successfully reserve the image...
I still think it has something to do with the ip, do I need to change to a
static setup since I don't have a DHCP server handing out IPs (i.e. this is
a single machine running everything (vmware, Apache VCL, management node,
etc) that is located inside the network closet at my school and is
statically assigned an ip of 144.38.205.200 and I am allowed to use IPs up
til about 205.215 but they aren't handed out by a DHCP server). Well you
will probably know better, this is my log output:

2011-04-06 12:39:59|1614|42:42|new|Module.pm:code_loop_timeout(724)|attempt
107: code returned false, seconds el\
apsed/remaining: 898/2, sleeping for 8 seconds
2011-04-06 12:40:03|30717|vcld:main(167)|lastcheckin time updated for
management node 1: 2011-04-06 12:40:03
2011-04-06 12:40:07|1614|42:42|new|Module.pm:code_loop_timeout(728)|attempt
108: waiting for vm4 to respond to S\
SH
2011-04-06 12:40:07|1614|42:42|new|OS.pm:is_ssh_responding(386)|vm4 is NOT
responding to SSH, ports 22 or 24 are\
 both closed
2011-04-06 12:40:07|1614|42:42|new|Module.pm:code_loop_timeout(736)|waiting
for vm4 to respond to SSH, code did \
not return true after waiting 900 seconds

|1614|42:42|new|  WARNING 
|1614|42:42|new| 2011-04-06
12:40:07|1614|42:42|new|OS.pm:wait_for_response(465)|failed to connect to
vm4 via SS\
H after 900 seconds
|1614|42:42|new| ( 0) OS.pm, wait_for_response (line: 465)
|1614|42:42|new| (-1) Windows.pm, post_load (line: 591)
|1614|42:42|new| (-2) VMware.pm, load (line: 415)
|1614|42:42|new| (-3) new.pm, reload_image (line: 687)
|1614|42:42|new| (-4) new.pm, process (line: 282)
|1614|42:42|new| (-5) vcld, make_new_child (line: 568)


|1614|42:42|new|  WARNING 
|1614|42:42|new| 2011-04-06
12:40:07|1614|42:42|new|Windows.pm:post_load(592)|vm4 never responded to SSH
|1614|42:42|new| ( 0) Windows.pm, post_load (line: 592)
|1614|42:42|new| (-1) VMware.pm, load (line: 415)
|1614|42:42|new| (-2) new.pm, reload_image (line: 687)
|1614|42:42|new| (-3) new.pm, process (line: 282)
|1614|42:42|new| (-4) vcld, make_new_child (line: 568)
|1614|42:42|new| (-5) vcld, main (line: 346)


|1614|42:42|new|  WARNING 
|1614|42:42|new| 2011-04-06
12:40:07|1614|42:42|new|VMware.pm:load(419)|failed to perform OS post-load
tasks on \
VM vm4 on VM host: localvmhost
|1614|42:42|new| ( 0) VMware.pm, load (line: 419)
|1614|42:42|new| (-1) new.pm, reload_image (line: 687)
|1614|42:42|new| (-2) new.pm, process (line: 282)
|1614|42:42|new| (-3) vcld, make_new_child (line: 568)
|1614|42:42|new| (-4) vcld, main (line: 346)


|1614|42:42|new|  WARNING 
|1614|42:42|new| 2011-04-06
12:40:07|1614|42:42|new|new.pm:reload_image(692)|vmwarewinxp-xp231-v0
failed to load\
 on vm4, returning
|1614|42:42|new| ( 0) new.pm, reload_image (line: 692)
|1614|42:42|new| (-1) new.pm, process (line: 282)
|1614|42:42|new| (-2) vcld, make_new_child (line: 568)
|1614|42:42|new| (-3) vcld, main (line: 346)

2011-04-06 12:40:07|1614|42:42|new|utils.pm:insertloadlog(3875)|inserted
computer=5, loadimagefailed, vmwarewinx\
p-xp231-v0 failed to load on vm4

|1614|42:42|new|  WARNING 
|1614|42:42|new| 2011-04-06 12:40:07|1614|42:42|new|new.pm:process(329)|failed
to load vm4 with vmwarewinxp-xp23\
1-v0
|1614|42:42|new| ( 0) new.pm, process (line: 329)
|1614|42:42|new| (-1) vcld, make_new_child (line: 568)
|1614|42:42|new| (-2) vcld, main (line: 346)

2011-04-06
12:40:07|1614|42:42|new|DataStructure.pm:get_computer_state_name(2299)|attempting
to retrieve current\
 state of computer vm4 from the database
2011-04-06
12:40:07|1614|42:42|new|DataStructure.pm:get_computer_state_name(2330)|retrieved
current state of com\
puter vm4 from the database: reloading
2011-04-06 12:40:07|1614|42:42|new|DataStructure.pm:_automethod(835)|data
structure updated: $self->request_data\
->{reservation}{42}{computer}{state}{name}
|1614|42:42|new| computer_state_name = reloading
2011-04-06
12:40:07|1614|42:42|new|DataStructure.pm:get_computer_private_ip_address(1582)|attempting
to retrieve\
 private IP address for computer: vm4
2011-04-06
12:40:07|1614|42:42|new|DataStructure.pm:get_computer_private_ip_address(1586)|retrieved
contents of \
/etc/hosts on this management node, contains 8 lines
2011-04-06
12:40:07|1614|42:42|new|DataStructure.pm:get_computer_private_ip_address(1639)|returning
IP address f\
rom /etc/hosts file: 192.168.128.3
2011-04-06 12:40:07|1614|42:42|new|utils.pm:is_inblockrequest(6147)|zero
rows were returned from database select
2011-04-06
12:40:07|1614|42:42|new|DataStructure.pm:get_image_affiliation_name(2029)|image
owner id: 1
2011-04-06 12:40:07|1614|42:42|new|utils.pm:getnewdbh(2709)|database
requested (information_schema) does not mat\
ch handle stored in

Re: Windows 7 and Windows XP give same error when trying to capture

2011-04-04 Thread Andy Kurth


Hello,
I responded earlier to your "dynamic vs static ip" message before 
noticing this message.  I think I see the problem.  You seem to be using 
the same machine as the management node and VM host but the VM profile 
datastore path and repository path are the same.  Configure the VM 
profile to not use the image repository:


-Click "Virtual Hosts"
-Select localvmhost from the list and click "Configure Host"
-Note the value next to "VM Profile"
-Click "VM Host Profiles"
-Select the profile being used by localvmhost and click "Configure Profile"
-Clear the value of "Data Store Path"
-Set "VM Disk" to networkdisk

Your captured image should probably work in its current state even 
though the capture failed.  The image capture only failed because it was 
unable to make a duplicate copy of the vmdk directory in the image 
repository.  This feature isn't necessary if you're using a single box 
or all network storage.


The only step that would have occurred if the image capture was 
successful would have been to set image.deleted and 
imagerevision.deleted to 0 in the database.  You can easily set this if 
you have phpMyAdmin installed or run 'mysql' from the command line and 
execute:


UPDATE image SET deleted = '0' WHERE name = 'vmwarewin7-vm4win720-v0';
UPDATE imagerevision SET deleted = '0' WHERE imagename = 
'vmwarewin7-vm4win720-v0';


Make sure the image has been put into an image group.  You should see 
the image in the "New Reservation" list.  Try to make a reservation.


Hope this helps,
Andy


On 3/28/2011 4:59 PM, Tyler Hardesty wrote:

So I've been trying for about 3 weeks to get an image captured... I kept
trying with a windows xp vm and finally decided to try win 7 to see if
that made a difference, it didn't. I get this same error when trying to
capture both win xp and win7 and can't figure it out. Any help would be
fantastic!!

2011-03-28 14:39:43|11006|16:16|image|Linux.pm:file_exists(1368)|file or
directory does not exist on localvmhost: '/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk'
2011-03-28
14:39:43|11006|16:16|image|VMware.pm:rename_vmdk(4995)|attempting to
rename vmdk: '/var/lib/vmware/Virtual Machines/vm4/vm4.vmdk' -->
'/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk'
2011-03-28
14:39:43|11006|16:16|image|Linux.pm:create_directory(1498)|directory
created on localvmhost: '/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0'
2011-03-28
14:39:43|11006|16:16|image|VMware.pm:rename_vmdk(5018)|'move_virtual_disk'
subroutine has not been implemented by the API:
VCL::Module::Provisioning::VMware::VIM_SSH
2011-03-28
14:39:43|11006|16:16|image|VMware.pm:rename_vmdk(5025)|attempting to
rename vmdk file using vmware-vdiskmanager: /var/lib/vmware/Virtual
Machines/vm4/vm4.vmdk --> /var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk
2011-03-28
14:39:44|11006|16:16|image|VMware.pm:rename_vmdk(5032)|renamed vmdk file
by executing 'vmware-vdiskmanager' command on VM host:
|11006|16:16|image| command: vmware-vdiskmanager -n
"/var/lib/vmware/Virtual Machines/vm4/vm4.vmdk" "/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk"
|11006|16:16|image| output: Renaming completed successfully.
2011-03-28
14:39:44|11006|16:16|image|Linux.pm:file_exists(1382)|'/var/lib/vmware/Virtual
Machines' exists on localvmhost, files: 0, directories: 1, links: 0
2011-03-28
14:39:44|11006|16:16|image|VMware.pm:is_repository_mounted_on_vmhost(5454)|image
repository is mounted on VM host localvmhost: /var/lib/vmware/Virtual
Machines
2011-03-28 14:39:44|11006|16:16|image|VMware.pm:capture(593)|vmdk will
be copied directly from VM host localvmhost to the image repository in
the 2gbsparse disk format
2011-03-28
14:39:45|11006|16:16|image|VMware.pm:get_vmhost_product_name(5374)|VMware 
product
being used on VM host localvmhost: 'VMware Server 2.0.2 build-203138'
2011-03-28
14:39:45|11006|16:16|image|Linux.pm:file_exists(1382)|'/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk' exists on
localvmhost, files: 1, directories: 0, links: 0
2011-03-28 14:39:46|30717|vcld:main(167)|lastcheckin time updated for
management node 1: 2011-03-28 14:39:46
2011-03-28
14:39:46|11006|16:16|image|Linux.pm:file_exists(1382)|'/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk' exists on
localvmhost, files: 1, directories: 0, links: 0
|11006|16:16|image|  WARNING 
|11006|16:16|image| 2011-03-28
14:39:46|11006|16:16|image|VMware.pm:copy_vmdk(4750)|destination vmdk
file path already exists on VM host localvmhost: /var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk
|11006|16:16|image| ( 0) VMware.pm, copy_vmdk (line: 4750)
|11006|16:16|image| (-1) VMware.pm, capture (line: 597)
|11006|16:16|image| (-2) image.pm , process (line: 165)
|11006|16:16|image| (-3) vcld, make_new_child

Windows 7 and Windows XP give same error when trying to capture

2011-03-28 Thread Tyler Hardesty

So I've been trying for about 3 weeks to get an image captured... I kept
trying with a windows xp vm and finally decided to try win 7 to see if that
made a difference, it didn't. I get this same error when trying to capture
both win xp and win7 and can't figure it out. Any help would be fantastic!!

2011-03-28 14:39:43|11006|16:16|image|Linux.pm:file_exists(1368)|file or
directory does not exist on localvmhost: '/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk'
2011-03-28 14:39:43|11006|16:16|image|VMware.pm:rename_vmdk(4995)|attempting
to rename vmdk: '/var/lib/vmware/Virtual Machines/vm4/vm4.vmdk' -->
'/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk'
2011-03-28
14:39:43|11006|16:16|image|Linux.pm:create_directory(1498)|directory created
on localvmhost: '/var/lib/vmware/Virtual Machines/vmwarewin7-vm4win720-v0'
2011-03-28
14:39:43|11006|16:16|image|VMware.pm:rename_vmdk(5018)|'move_virtual_disk'
subroutine has not been implemented by the API:
VCL::Module::Provisioning::VMware::VIM_SSH
2011-03-28 14:39:43|11006|16:16|image|VMware.pm:rename_vmdk(5025)|attempting
to rename vmdk file using vmware-vdiskmanager: /var/lib/vmware/Virtual
Machines/vm4/vm4.vmdk --> /var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk
2011-03-28 14:39:44|11006|16:16|image|VMware.pm:rename_vmdk(5032)|renamed
vmdk file by executing 'vmware-vdiskmanager' command on VM host:
|11006|16:16|image| command: vmware-vdiskmanager -n "/var/lib/vmware/Virtual
Machines/vm4/vm4.vmdk" "/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk"
|11006|16:16|image| output: Renaming completed successfully.
2011-03-28
14:39:44|11006|16:16|image|Linux.pm:file_exists(1382)|'/var/lib/vmware/Virtual
Machines' exists on localvmhost, files: 0, directories: 1, links: 0
2011-03-28
14:39:44|11006|16:16|image|VMware.pm:is_repository_mounted_on_vmhost(5454)|image
repository is mounted on VM host localvmhost: /var/lib/vmware/Virtual
Machines
2011-03-28 14:39:44|11006|16:16|image|VMware.pm:capture(593)|vmdk will be
copied directly from VM host localvmhost to the image repository in the
2gbsparse disk format
2011-03-28
14:39:45|11006|16:16|image|VMware.pm:get_vmhost_product_name(5374)|VMware
product being used on VM host localvmhost: 'VMware Server 2.0.2
build-203138'
2011-03-28
14:39:45|11006|16:16|image|Linux.pm:file_exists(1382)|'/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk' exists on
localvmhost, files: 1, directories: 0, links: 0
2011-03-28 14:39:46|30717|vcld:main(167)|lastcheckin time updated for
management node 1: 2011-03-28 14:39:46
2011-03-28
14:39:46|11006|16:16|image|Linux.pm:file_exists(1382)|'/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk' exists on
localvmhost, files: 1, directories: 0, links: 0
|11006|16:16|image|  WARNING 
|11006|16:16|image| 2011-03-28
14:39:46|11006|16:16|image|VMware.pm:copy_vmdk(4750)|destination vmdk file
path already exists on VM host localvmhost: /var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk
|11006|16:16|image| ( 0) VMware.pm, copy_vmdk (line: 4750)
|11006|16:16|image| (-1) VMware.pm, capture (line: 597)
|11006|16:16|image| (-2) image.pm, process (line: 165)
|11006|16:16|image| (-3) vcld, make_new_child (line: 568)
|11006|16:16|image| (-4) vcld, main (line: 346)
|11006|16:16|image|  WARNING 
|11006|16:16|image| 2011-03-28
14:39:46|11006|16:16|image|VMware.pm:capture(601)|failed to copy the vmdk
files after the VM was powered off: '/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk' -->
'/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk'
|11006|16:16|image| ( 0) VMware.pm, capture (line: 601)
|11006|16:16|image| (-1) image.pm, process (line: 165)
|11006|16:16|image| (-2) vcld, make_new_child (line: 568)
|11006|16:16|image| (-3) vcld, main (line: 346)
2011-03-28
14:39:46|11006|16:16|image|Linux.pm:file_exists(1382)|'/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk' exists on
localvmhost, files: 1, directories: 0, links: 0
2011-03-28 14:39:46|11006|16:16|image|Linux.pm:file_exists(1368)|file or
directory does not exist on localvmhost: '/var/lib/vmware/Virtual
Machines/vm4/vm4.vmdk'
2011-03-28 14:39:46|11006|16:16|image|VMware.pm:rename_vmdk(4995)|attempting
to rename vmdk: '/var/lib/vmware/Virtual
Machines/vmwarewin7-vm4win720-v0/vmwarewin7-vm4win720-v0.vmdk' -->
'/var/lib/vmware/Virtual Machines/vm4/vm4.vmdk'
2011-03-28
14:39:46|11006|16:16|image|Linux.pm:create_directory(1502)|directory already
exists on localvmhost: '/var/lib/vmware/Virtual Machines/vm4'
2011-03-28
14:39:46|11006|16:16|image|VMware.pm:rename_vmdk(5018)|'move_virtual_disk'
subroutine has not been implemented by the API:
VCL::Module::Provisioning::VMware::VIM_SSH
2011-03-28 14:39:46|11006

Re: Windows 7 and Windows XP give same error when trying to capture

Re: Windows 7 and Windows XP give same error when trying to capture

Re: Windows 7 and Windows XP give same error when trying to capture

Re: Windows 7 and Windows XP give same error when trying to capture

Re: Windows 7 and Windows XP give same error when trying to capture

Re: Windows 7 and Windows XP give same error when trying to capture

Re: Windows 7 and Windows XP give same error when trying to capture

Re: Windows 7 and Windows XP give same error when trying to capture

Windows 7 and Windows XP give same error when trying to capture

9 matches

Site Navigation

Mail list logo

Footer information