You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@vcl.apache.org by Tine Lesjak <ti...@fri.uni-lj.si> on 2011/05/13 17:04:13 UTC

RE: Cygwin "linked dll data write copy failed" on Windows 7 virtualized

Hello guys,

I just want to tell as promised, in case somebody will experience the same
issue, that I found out that this error is caused by VMware Tools. But not
all versions of it. The rebaseall does the trick on some versions, but on
some other (newer) versions, it doesn't have any effect - meaning Cygwin is
failing constantly. After I uninstalled VMware Tools, the problem has gone
away. VMware Tools is problematic only on Windows 7 (with or without SP1).
On Windows Server 2008 R2 everything seems OK.

So, probably, Cygwin guys should add VMware Tools to their "BLODA"
(http://cygwin.com/faq/faq.using.html#faq.using.bloda) list. :)

Tine Lesjak

Faculty of Computer and Information Science
University of Ljubljana
Slovenia
Europe

-----Original Message-----
From: Tine Lesjak [mailto:tine.lesjak@fri.uni-lj.si] 
Sent: Saturday, January 29, 2011 10:46 PM
To: vcl-dev@incubator.apache.org
Cc: Andy Kurth
Subject: Re: Cygwin "linked dll data write copy failed" on Windows 7
virtualized

Thank you, Andy. To run rebaseall for each image load is a great idea. 
Now, I'm trying with this and so far so good. But I don't have much time 
to spend on testing and this problem occurs very randomly. I'll tell 
you, when I find out for sure if this is the case.

Windows 7 is freshly installed with Windows Defender disabled. I'm aware 
of "BLODA" (http://cygwin.com/faq/faq.using.html#faq.using.bloda).

Thank you again.

Tine Lesjak

Faculty of Computer and Information Science
University of Ljubljana
Slovenia
Europe


On 25.1.2011 19:43, Andy Kurth wrote:
> If you haven't already done so, try using the current 
> update_cygwin.cmd script:
>
http://svn.apache.org/repos/asf/incubator/vcl/trunk/managementnode/tools/Win
dows/Scripts/update_cygwin.cmd 
>
>
> Changes have been made to this file since VCL 2.1 including the 
> addition of calling rebaseall.  I know you said you tried rebaseall, 
> but you'll definitely want to have the updated script saved in your 
> Win7/2008 images because unpredictable behavior occurs if rebaseall 
> isn't run for each image load.
>
> Do you have any other software installed in the image such as an 
> antivirus client?  If so, I'd try uninstalling it.  You could also try 
> disabling any non-essential services to see if any of them are the 
> culprit.
>
> -Andy
>
> On 1/23/2011 5:32 PM, Tine Lesjak wrote:
>> Hi all,
>>
>>
>>
>> We are experiencing big troubles with Cygwin 1.5 (legacy) on Windows 
>> 7. We
>> tried various "versions" of Windows 7 (32/64 bit, different locales,
>> different settings for Cygwin SSHD (delayed startup, rebaseall, 
>> special DEP
>> settings, Windows Firewall as dependency service), Windows Defender 
>> is off).
>> The problem is always when VCL tries to set Windows Firewall. For 
>> example:
>>
>>
>>
>> Example 1:
>>
>> Command:
>>
>> reg.exe ADD 
>> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>> Server" /t REG_DWORD /v fDenyTSConnections /d 0 /f ;
>>
>> reg.exe ADD 
>> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>> Server\WinStations\RDP-Tcp" /t REG_DWORD /v UserAuthentication /d 0 /f ;
>>
>> netsh.exe advfirewall firewall delete rule name=all dir=in protocol=TCP
>> localport=3389 ;
>>
>> netsh.exe advfirewall firewall add rule name="VCL: allow RDP port 
>> 3389 to:
>> 10.7.97.227" description="Allows incoming RDP (TCP port 3389) traffic 
>> to:
>> 10.7.97.227" protocol=TCP localport=3389 action=allow enable=yes dir=in
>> localip=10.7.97.227
>>
>>
>>
>> Response:
>>
>> 344 [main] bash 1292 child_copy: linked dll data write copy failed,
>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>
>> 1147825 [main] bash 1292 child_copy: linked dll data write copy failed,
>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>
>> 3181277 [main] bash 1292 child_copy: linked dll data write copy failed,
>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>
>> 7208875 [main] bash 1292 child_copy: linked dll data write copy failed,
>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>
>> 15241434 [main] bash 1292 child_copy: linked dll data write copy failed,
>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87 bash: fork:
>> Resource temporarily unavailable
>>
>>
>>
>> Example 2:
>>
>> Command:
>>
>> /bin/cygstart.exe netsh.exe advfirewall firewall add rule
>> name="VCL:TempAllowAllToPrivate" description="Allows all traffic to
>> 10.3.71.209" action=allow enable=yes dir=in localip=10.3.71.209 ;
>>
>> netsh.exe advfirewall firewall delete rule name=all dir=in protocol=TCP
>> localport=22 ;
>>
>> netsh.exe advfirewall firewall add rule name="VCL: allow SSH port 22 to:
>> 10.3.71.209" description="Allows incoming SSH (TCP port 22) traffic to:
>> 10.3.71.209" protocol=TCP localport=22 action=allow enable=yes dir=in
>> localip=10.3.71.209
>>
>>
>>
>> Response:
>>
>> Deleted 1 rule(s).
>>
>> Ok.
>>
>> Ok.
>>
>> 8244 [main] bash 2200 child_copy: linked dll data write copy failed,
>> 0x2DC000..0x2E038C, done 0, windows pid 2224, Win32 error 487
>>
>> 1163369 [main] bash 2200 child_copy: linked dll data write copy failed,
>> 0x2DC000..0x2E038C, done 0, windows pid 2224, Win32 error 487
>>
>>
>>
>> It is strange, since Windows Server 2008 seems to work (but we haven't
>> tested it so heavily). We are using quite modified VCL 2.1, hosts are 
>> VMware
>> ESXi 4. I'm pretty sure, that the problem is not with VCL (because we
>> modified it), but solely with Cygwin/Windows 7.
>>
>>
>>
>> I'm just asking if someone has already bumped to this problem.
>>
>> Thank you!
>>
>>
>>
>> Tine Lesjak
>>
>>
>>
>> Faculty of Computer and Information Science
>>
>> University of Ljubljana
>>
>> Slovenia
>>
>> Europe
>>
>>

RE: Cygwin "linked dll data write copy failed" on Windows 7 virtualized

Posted by Tine Lesjak <ti...@fri.uni-lj.si>.

Hi!

My thoughts are exactly the same: VMware Tools does provide smooth work
while connected via the vSphere Client, but who needs that if we have VCL?
:) Another thing is simply the maintenance of VMware Tools. It should be up
to date, but if you have different versions of ESXs, there can be a problem.
I have remembered another thing: if you update a Linux kernel, you should
reinstall VMware Tools.
A big mystery for me is if there is really any performance improvement with
VMware Tools installed. I mean, a CPU, memory or disk performance? If there
is, how big? Is it worth it? Or maybe a stability improvement (drivers)? We
had some occasional problems when booting a Linux kernel - some ACPI issues.
Would VMware Tools fix it?
I'm just thinking aloud. :)

Thanks,
Tine Lesjak

Faculty of Computer and Information Science
University of Ljubljana
Slovenia
Europe

-----Original Message-----
From: Andy Kurth [mailto:andy_kurth@ncsu.edu] 
Sent: Friday, May 13, 2011 6:03 PM
To: vcl-dev@incubator.apache.org
Subject: Re: Cygwin "linked dll data write copy failed" on Windows 7
virtualized

Thanks very much for figuring this out.

I was thinking of removing VMware Tools from our base images.  I think 
the only benefit in our environment is better performance when you have 
to log in via the vSphere Client console.  I have seen intermittent 
problems where a VM boots and the CPU is pegged at 100% for a few 
minutes.  It seemed as though the vSphere Client reported the VMware 
Tools status as "out of date", though I'm not certain this is the culprit.

Another problem occurs if the VM host's time is incorrect and VMware 
Tools is configured to sync time with the host.  As part of the 
post-load steps, VCL runs commands to sync time on the guest OS with 
Internet NTP servers.  VMware Tools may change the time back to an 
incorrect value after this occurs.

There are some things we can do in the VCL code to work around these 
problems.  The VMware services can be disabled before the image is 
captured and then started after the computer responds to SSH.  The Tools 
settings or possibly the vmx file can also be configured to not sync 
time with the host.  Thoughts?

-Andy

On 5/13/2011 11:04 AM, Tine Lesjak wrote:
> Hello guys,
>
> I just want to tell as promised, in case somebody will experience the same
> issue, that I found out that this error is caused by VMware Tools. But not
> all versions of it. The rebaseall does the trick on some versions, but on
> some other (newer) versions, it doesn't have any effect - meaning Cygwin
is
> failing constantly. After I uninstalled VMware Tools, the problem has gone
> away. VMware Tools is problematic only on Windows 7 (with or without SP1).
> On Windows Server 2008 R2 everything seems OK.
>
> So, probably, Cygwin guys should add VMware Tools to their "BLODA"
> (http://cygwin.com/faq/faq.using.html#faq.using.bloda) list. :)
>
> Tine Lesjak
>
> Faculty of Computer and Information Science
> University of Ljubljana
> Slovenia
> Europe
>
> -----Original Message-----
> From: Tine Lesjak [mailto:tine.lesjak@fri.uni-lj.si]
> Sent: Saturday, January 29, 2011 10:46 PM
> To: vcl-dev@incubator.apache.org
> Cc: Andy Kurth
> Subject: Re: Cygwin "linked dll data write copy failed" on Windows 7
> virtualized
>
> Thank you, Andy. To run rebaseall for each image load is a great idea.
> Now, I'm trying with this and so far so good. But I don't have much time
> to spend on testing and this problem occurs very randomly. I'll tell
> you, when I find out for sure if this is the case.
>
> Windows 7 is freshly installed with Windows Defender disabled. I'm aware
> of "BLODA" (http://cygwin.com/faq/faq.using.html#faq.using.bloda).
>
> Thank you again.
>
> Tine Lesjak
>
> Faculty of Computer and Information Science
> University of Ljubljana
> Slovenia
> Europe
>
>
> On 25.1.2011 19:43, Andy Kurth wrote:
>> If you haven't already done so, try using the current
>> update_cygwin.cmd script:
>>
>
http://svn.apache.org/repos/asf/incubator/vcl/trunk/managementnode/tools/Win
> dows/Scripts/update_cygwin.cmd
>>
>>
>> Changes have been made to this file since VCL 2.1 including the
>> addition of calling rebaseall.  I know you said you tried rebaseall,
>> but you'll definitely want to have the updated script saved in your
>> Win7/2008 images because unpredictable behavior occurs if rebaseall
>> isn't run for each image load.
>>
>> Do you have any other software installed in the image such as an
>> antivirus client?  If so, I'd try uninstalling it.  You could also try
>> disabling any non-essential services to see if any of them are the
>> culprit.
>>
>> -Andy
>>
>> On 1/23/2011 5:32 PM, Tine Lesjak wrote:
>>> Hi all,
>>>
>>>
>>>
>>> We are experiencing big troubles with Cygwin 1.5 (legacy) on Windows
>>> 7. We
>>> tried various "versions" of Windows 7 (32/64 bit, different locales,
>>> different settings for Cygwin SSHD (delayed startup, rebaseall,
>>> special DEP
>>> settings, Windows Firewall as dependency service), Windows Defender
>>> is off).
>>> The problem is always when VCL tries to set Windows Firewall. For
>>> example:
>>>
>>>
>>>
>>> Example 1:
>>>
>>> Command:
>>>
>>> reg.exe ADD
>>> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>>> Server" /t REG_DWORD /v fDenyTSConnections /d 0 /f ;
>>>
>>> reg.exe ADD
>>> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>>> Server\WinStations\RDP-Tcp" /t REG_DWORD /v UserAuthentication /d 0 /f ;
>>>
>>> netsh.exe advfirewall firewall delete rule name=all dir=in protocol=TCP
>>> localport=3389 ;
>>>
>>> netsh.exe advfirewall firewall add rule name="VCL: allow RDP port
>>> 3389 to:
>>> 10.7.97.227" description="Allows incoming RDP (TCP port 3389) traffic
>>> to:
>>> 10.7.97.227" protocol=TCP localport=3389 action=allow enable=yes dir=in
>>> localip=10.7.97.227
>>>
>>>
>>>
>>> Response:
>>>
>>> 344 [main] bash 1292 child_copy: linked dll data write copy failed,
>>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>>
>>> 1147825 [main] bash 1292 child_copy: linked dll data write copy failed,
>>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>>
>>> 3181277 [main] bash 1292 child_copy: linked dll data write copy failed,
>>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>>
>>> 7208875 [main] bash 1292 child_copy: linked dll data write copy failed,
>>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>>
>>> 15241434 [main] bash 1292 child_copy: linked dll data write copy failed,
>>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87 bash: fork:
>>> Resource temporarily unavailable
>>>
>>>
>>>
>>> Example 2:
>>>
>>> Command:
>>>
>>> /bin/cygstart.exe netsh.exe advfirewall firewall add rule
>>> name="VCL:TempAllowAllToPrivate" description="Allows all traffic to
>>> 10.3.71.209" action=allow enable=yes dir=in localip=10.3.71.209 ;
>>>
>>> netsh.exe advfirewall firewall delete rule name=all dir=in protocol=TCP
>>> localport=22 ;
>>>
>>> netsh.exe advfirewall firewall add rule name="VCL: allow SSH port 22 to:
>>> 10.3.71.209" description="Allows incoming SSH (TCP port 22) traffic to:
>>> 10.3.71.209" protocol=TCP localport=22 action=allow enable=yes dir=in
>>> localip=10.3.71.209
>>>
>>>
>>>
>>> Response:
>>>
>>> Deleted 1 rule(s).
>>>
>>> Ok.
>>>
>>> Ok.
>>>
>>> 8244 [main] bash 2200 child_copy: linked dll data write copy failed,
>>> 0x2DC000..0x2E038C, done 0, windows pid 2224, Win32 error 487
>>>
>>> 1163369 [main] bash 2200 child_copy: linked dll data write copy failed,
>>> 0x2DC000..0x2E038C, done 0, windows pid 2224, Win32 error 487
>>>
>>>
>>>
>>> It is strange, since Windows Server 2008 seems to work (but we haven't
>>> tested it so heavily). We are using quite modified VCL 2.1, hosts are
>>> VMware
>>> ESXi 4. I'm pretty sure, that the problem is not with VCL (because we
>>> modified it), but solely with Cygwin/Windows 7.
>>>
>>>
>>>
>>> I'm just asking if someone has already bumped to this problem.
>>>
>>> Thank you!
>>>
>>>
>>>
>>> Tine Lesjak
>>>
>>>
>>>
>>> Faculty of Computer and Information Science
>>>
>>> University of Ljubljana
>>>
>>> Slovenia
>>>
>>> Europe
>>>
>>>
>

Re: Cygwin "linked dll data write copy failed" on Windows 7 virtualized

Posted by Andy Kurth <an...@ncsu.edu>.

Thanks very much for figuring this out.

I was thinking of removing VMware Tools from our base images.  I think 
the only benefit in our environment is better performance when you have 
to log in via the vSphere Client console.  I have seen intermittent 
problems where a VM boots and the CPU is pegged at 100% for a few 
minutes.  It seemed as though the vSphere Client reported the VMware 
Tools status as "out of date", though I'm not certain this is the culprit.

Another problem occurs if the VM host's time is incorrect and VMware 
Tools is configured to sync time with the host.  As part of the 
post-load steps, VCL runs commands to sync time on the guest OS with 
Internet NTP servers.  VMware Tools may change the time back to an 
incorrect value after this occurs.

There are some things we can do in the VCL code to work around these 
problems.  The VMware services can be disabled before the image is 
captured and then started after the computer responds to SSH.  The Tools 
settings or possibly the vmx file can also be configured to not sync 
time with the host.  Thoughts?

-Andy

On 5/13/2011 11:04 AM, Tine Lesjak wrote:
> Hello guys,
>
> I just want to tell as promised, in case somebody will experience the same
> issue, that I found out that this error is caused by VMware Tools. But not
> all versions of it. The rebaseall does the trick on some versions, but on
> some other (newer) versions, it doesn't have any effect - meaning Cygwin is
> failing constantly. After I uninstalled VMware Tools, the problem has gone
> away. VMware Tools is problematic only on Windows 7 (with or without SP1).
> On Windows Server 2008 R2 everything seems OK.
>
> So, probably, Cygwin guys should add VMware Tools to their "BLODA"
> (http://cygwin.com/faq/faq.using.html#faq.using.bloda) list. :)
>
> Tine Lesjak
>
> Faculty of Computer and Information Science
> University of Ljubljana
> Slovenia
> Europe
>
> -----Original Message-----
> From: Tine Lesjak [mailto:tine.lesjak@fri.uni-lj.si]
> Sent: Saturday, January 29, 2011 10:46 PM
> To: vcl-dev@incubator.apache.org
> Cc: Andy Kurth
> Subject: Re: Cygwin "linked dll data write copy failed" on Windows 7
> virtualized
>
> Thank you, Andy. To run rebaseall for each image load is a great idea.
> Now, I'm trying with this and so far so good. But I don't have much time
> to spend on testing and this problem occurs very randomly. I'll tell
> you, when I find out for sure if this is the case.
>
> Windows 7 is freshly installed with Windows Defender disabled. I'm aware
> of "BLODA" (http://cygwin.com/faq/faq.using.html#faq.using.bloda).
>
> Thank you again.
>
> Tine Lesjak
>
> Faculty of Computer and Information Science
> University of Ljubljana
> Slovenia
> Europe
>
>
> On 25.1.2011 19:43, Andy Kurth wrote:
>> If you haven't already done so, try using the current
>> update_cygwin.cmd script:
>>
> http://svn.apache.org/repos/asf/incubator/vcl/trunk/managementnode/tools/Win
> dows/Scripts/update_cygwin.cmd
>>
>>
>> Changes have been made to this file since VCL 2.1 including the
>> addition of calling rebaseall.  I know you said you tried rebaseall,
>> but you'll definitely want to have the updated script saved in your
>> Win7/2008 images because unpredictable behavior occurs if rebaseall
>> isn't run for each image load.
>>
>> Do you have any other software installed in the image such as an
>> antivirus client?  If so, I'd try uninstalling it.  You could also try
>> disabling any non-essential services to see if any of them are the
>> culprit.
>>
>> -Andy
>>
>> On 1/23/2011 5:32 PM, Tine Lesjak wrote:
>>> Hi all,
>>>
>>>
>>>
>>> We are experiencing big troubles with Cygwin 1.5 (legacy) on Windows
>>> 7. We
>>> tried various "versions" of Windows 7 (32/64 bit, different locales,
>>> different settings for Cygwin SSHD (delayed startup, rebaseall,
>>> special DEP
>>> settings, Windows Firewall as dependency service), Windows Defender
>>> is off).
>>> The problem is always when VCL tries to set Windows Firewall. For
>>> example:
>>>
>>>
>>>
>>> Example 1:
>>>
>>> Command:
>>>
>>> reg.exe ADD
>>> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>>> Server" /t REG_DWORD /v fDenyTSConnections /d 0 /f ;
>>>
>>> reg.exe ADD
>>> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>>> Server\WinStations\RDP-Tcp" /t REG_DWORD /v UserAuthentication /d 0 /f ;
>>>
>>> netsh.exe advfirewall firewall delete rule name=all dir=in protocol=TCP
>>> localport=3389 ;
>>>
>>> netsh.exe advfirewall firewall add rule name="VCL: allow RDP port
>>> 3389 to:
>>> 10.7.97.227" description="Allows incoming RDP (TCP port 3389) traffic
>>> to:
>>> 10.7.97.227" protocol=TCP localport=3389 action=allow enable=yes dir=in
>>> localip=10.7.97.227
>>>
>>>
>>>
>>> Response:
>>>
>>> 344 [main] bash 1292 child_copy: linked dll data write copy failed,
>>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>>
>>> 1147825 [main] bash 1292 child_copy: linked dll data write copy failed,
>>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>>
>>> 3181277 [main] bash 1292 child_copy: linked dll data write copy failed,
>>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>>
>>> 7208875 [main] bash 1292 child_copy: linked dll data write copy failed,
>>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87
>>>
>>> 15241434 [main] bash 1292 child_copy: linked dll data write copy failed,
>>> 0x4A1000..0x4A13E4, done 0, windows pid 1480, Win32 error 87 bash: fork:
>>> Resource temporarily unavailable
>>>
>>>
>>>
>>> Example 2:
>>>
>>> Command:
>>>
>>> /bin/cygstart.exe netsh.exe advfirewall firewall add rule
>>> name="VCL:TempAllowAllToPrivate" description="Allows all traffic to
>>> 10.3.71.209" action=allow enable=yes dir=in localip=10.3.71.209 ;
>>>
>>> netsh.exe advfirewall firewall delete rule name=all dir=in protocol=TCP
>>> localport=22 ;
>>>
>>> netsh.exe advfirewall firewall add rule name="VCL: allow SSH port 22 to:
>>> 10.3.71.209" description="Allows incoming SSH (TCP port 22) traffic to:
>>> 10.3.71.209" protocol=TCP localport=22 action=allow enable=yes dir=in
>>> localip=10.3.71.209
>>>
>>>
>>>
>>> Response:
>>>
>>> Deleted 1 rule(s).
>>>
>>> Ok.
>>>
>>> Ok.
>>>
>>> 8244 [main] bash 2200 child_copy: linked dll data write copy failed,
>>> 0x2DC000..0x2E038C, done 0, windows pid 2224, Win32 error 487
>>>
>>> 1163369 [main] bash 2200 child_copy: linked dll data write copy failed,
>>> 0x2DC000..0x2E038C, done 0, windows pid 2224, Win32 error 487
>>>
>>>
>>>
>>> It is strange, since Windows Server 2008 seems to work (but we haven't
>>> tested it so heavily). We are using quite modified VCL 2.1, hosts are
>>> VMware
>>> ESXi 4. I'm pretty sure, that the problem is not with VCL (because we
>>> modified it), but solely with Cygwin/Windows 7.
>>>
>>>
>>>
>>> I'm just asking if someone has already bumped to this problem.
>>>
>>> Thank you!
>>>
>>>
>>>
>>> Tine Lesjak
>>>
>>>
>>>
>>> Faculty of Computer and Information Science
>>>
>>> University of Ljubljana
>>>
>>> Slovenia
>>>
>>> Europe
>>>
>>>
>