> I already use "Citrix Tools for Virtual Machines" for my W2K3R2 VM which is XS61 Legacy Tools. But still hang when I try to copy very big files (>5GB). > I could not manage to apply XS61E010 patch. So I use "xenlegacy.exe" signed by Citrix Systems Inc. at 24 November 2012. I took that file from XCP 1.6 iso, folder client_install. > Is it the same file? > No, they dos not.
Problem with various Windows VMs exactly in *"xenlegacy.exe" signed by Citrix Systems Inc. at 24 November 2012* Just to check issue reduce number of vCPU to 1 in mentioned VM and try copy process again. Everything should work fine... and slow... So, you have to get xen-tools from XS61E010 hotfix. It is different version - just renamed XS 60Exx hotfix. 2013/3/19 Agi Subagio <[email protected]> > Quote from CTX135009: > How Can I Check Whether My VM is Running Legacy or Standard Tools? > > To check what Tools a Windows VM is running, click the *Start* button, > then *Control Panel*, then (depending on the version of Windows)*Add/Remove > Programs*, or *Programs and Features*, or *Uninstall a Program*. If > "Citrix Tools for Virtual machines" is listed the Legacy Tools are > installed. If "Windows Driver Package Citrix Systems Inc. (xenbus) System" > is listed then the Standard Tools are installed. > > I already use "Citrix Tools for Virtual Machines" for my W2K3R2 VM which > is XS61 Legacy Tools. But still hang when I try to copy very big files > (>5GB). > I could not manage to apply XS61E010 patch. So I use "xenlegacy.exe" > signed by Citrix Systems Inc. at 24 November 2012. I took that file from > XCP 1.6 iso, folder client_install. > Is it the same file? > > I think I'm going back to XCP 1.1 until XCP 2.0 is out. It's much easier > to prepare i350 driver compilation then patching XCP 1.6 VM. > > On 19/03/2013 2:16 PM, hook wrote: > > AFAIK, You can't install XS61E009 Update on to XCP 1.6. I've already > asked here about the way to implement binary update from Citrix to XCP, but > no luck. > > So you just would install lecacy xen-tools (or XS61E010) to your Windows > system to avoid known bugs in some configuration. > > > 2013/3/19 Agi Subagio <[email protected]> > >> Hi, >> >> I tried to digest the posts in the thread and looked into this Citrix's >> KB: >> http://support.citrix.com/article/CTX135099 >> http://support.citrix.com/article/CTX136252 >> http://support.citrix.com/article/CTX136253 >> >> Let me clarify, I must doing these steps: >> - install XCP 1.6 from the beginning >> - install hotfix XS61E009 and hotfix XS61E010, then I have two version of >> xs-tools iso in my host (standard and legacy) >> - import W2K3R2 VM >> - make sure there is no XCP 1.1 Standard Tools or XCP 1.6 Standard Tools >> in it >> - install XS61E010 Legacy Tools into W2K3R2 VM >> - and I have to do this on each W2K3R2 VM >> >> I would try first. >> >> regards, >> Agi >> >> >> On 18/03/2013 8:53 PM, Denis Cardon wrote: >> >>> Hi Agi, >>> >>> Thanks for reply... I will read it first. >>>> Do you mean p2v drivers is in xs-tools.iso? >>>> fyi, all of my W2K3 VMs use 2-4 VCPUs. >>>> >>> >>> Yes that's it, you should re-install the pv driver with a recent enough >>> build of xs-tools.iso. >>> >>> I have a dozen win2k3 running fine on XCP 1.6, so "it should work"(tm) >>> for you too! In the citrix thread I sent you, you can find the exact build >>> that address this issue. >>> >>> The recompilation of a driver is not very hard either once you got used >>> to it, but it would be a pity not to get on with XCP1.6, the Citrix team >>> did a tremendous work on this release. >>> >>> Cheers, >>> >>> Denis >>> >>> >>>> On 18/03/2013 5:04 PM, Denis Cardon wrote: >>>> >>>>> Hi Agi, >>>>> >>>>> > I have a new server with onboard Intel i350 Gigabit Ethernet, but XCP >>>>> >>>>>> 1.1 did not detect that card. Previously I install XCP 1.6 on it, but >>>>>> my >>>>>> VM (Windows) always hang randomly and hard to reboot/shutdown via >>>>>> XenCenter, so I want to use XCP 1.1 to that server. How to compile >>>>>> igb-4.1.2.tar.gz source code for XCP 1.1? >>>>>> >>>>> >>>>> I had a issue recently with a win2k WM crashing after upgrade to >>>>> XCP1.6. There has been an issue with win2k win2k3 vms that is >>>>> explained in the post below (long post). >>>>> >>>>> http://forums.citrix.com/thread.jspa?threadID=314477&start=105&tstart=0 >>>>> >>>>> Summary : >>>>> * For win2k3 and above vms, upgrade p2v drivers. >>>>> * For win2k vms, short workaround is to have only one vcpus in the VM. >>>>> (indeed, the new driver does not want to install on win2k per >>>>> citrix/windows EOL policy). If you definitly need more than one vcpus >>>>> in your win2k vm, you'll have to tweak a little more I guess. >>>>> >>>>> If you still want to recompile, you have to install kernel headers >>>>> from source iso, enable centos repo, install build tools and compile >>>>> your driver. But I'd recommend to give one more try to XCP 1.6. >>>>> >>>>> Cheers, >>>>> >>>>> Denis >>>>> >>>>> >>>> >>>> >>> >>> >> >> -- >> This message has been scanned for viruses and dangerous content >> by MBS MailScanner, and is believed to be clean and safe. >> >> >> _______________________________________________ >> Xen-api mailing list >> [email protected] >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api >> > > > > -- > WBR > > Sergey Kruchatov > > -- > This message has been scanned for viruses and dangerous content > by MBS MailScanner, and is believed to be clean and safe. > > > > -- > This message has been scanned for viruses and dangerous content > by MBS MailScanner, and is believed to be clean and safe. > > _______________________________________________ > Xen-api mailing list > [email protected] > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > -- WBR Sergey Kruchatov
_______________________________________________ Xen-api mailing list [email protected] http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
