[Beta Release] XCP-ng Windows Client tools 8.2.1-beta1

[borzel]

@dbeato glad that it works now... I actually don't know an automated way to find all the little things that can cause the drivers to fail. It's mostly detective work

[dbeato]

@borzel said in [Beta Release] XCP-ng Windows Client tools 8.2.1-beta1:

@dbeato glad that it works now... I actually don't know an automated way to find all the little things that can cause the drivers to fail. It's mostly detective work

Yeah, that is why I am reporting here One thing I would say though, it doesn't seem to do the paste from the host as XenServer used to. Not sure if it is supposed to be that way.

[borzel]

@dbeato hmm.. never saw this feature ... I'll try with some test VMs

[borzel]

@dbeato it just works!

[dbeato]

@borzel said in [Beta Release] XCP-ng Windows Client tools 8.2.1-beta1:

@dbeato it just works!

Good, that's what I need to review again as this morning did not want to work.

[conradical]

I've installed this on Win server 2019, PV Drivers install, but XCP-ng center reports the management agent is not installed AND under the performance it says to install XCP-ng tools to view memory data.

[borzel]

@conradical Did you reboot? Do you see the XCP-ng devices in Device Manager?

[conradical]

@borzel
Yes, I did reboot. I don't see XCP-ng, but see
XenServer PV Netowrk Device
XenSRC PV scsi disk device
and XenServer PV Bus's

How that I look closer i see Xenserver Agent and XenServer PV Driver monitor. -- I'm wondering if these grabbed from windows update automatically post XCP-ng tools install.

[conradical]

Screenshots..

[conradical]

so I did a fresh 2019 install, using the server 2016 template since 2019 template isn't available yet, post install i was prompted with this screenshot:

This is also the recently re-released Win Server 2019 disk.

[conradical]

Apparently be default the template has "Windows Update tools" enabled. Should this not pull the drivers for XCP-ng?

[borzel]

@conradical we don't have xcp-ng drivers on Windows Update. Maybe later....

[conradical]

@borzel
I thought I read where you were working on that process and got it done and were registering the device IDs. I guess i read wrong

[borzel]

@conradical device id's are "registered" in the xen project and in "the pci database" ... but they are for future use

[conradical]

@borzel
Got it! Good work by the way!

[borzel]

@conradical

[borzel]

Status update: I'm currently working on avoiding these WMI errors. Here is my current progress:

https://github.com/xcp-ng/win-xenguestagent/commit/280847a38a0687a3c06608b51f9cc0cb9b4d9f9b

0 borzel committed to xcp-ng/win-xenguestagent

current progress to avoid WMI errors
- tidy up most of the unnecessary untry()-catch() blocks
- switched to .Net 4.7.1
- fix IntPtr.Int32 errors (use IntPtr.Int64!)

[RKO1337]

Thanks for the XCP-ng tools.

I tried to install the XCP-ng Tools on a new Windows Server 2019 vm (german locale), XCP-ng 7.5.
I used the Windows Server 2016 default Template.

Installed Net Framework 3.5 beforehand, launched the setup.exe as administrator.
The installation finishes with the management agenet could not be started message.

I restarted the vm, no new Xen Devices are shown in device management.
Only both of these services were installed.

I ran

C:\Program Files\XCP-ng\XenTools\InstallAgent.exe DEFAULT

this installed the XCP-ng Interface Package.

I got no popup that asked to reboot the vm, but restarted anyways.

Services after reboot:

Device manager shows two new unknown XENBUS devices. Under system devices XCP-ng Interface and XCP-ng PV Bus (0002) are now listed.
Network adapter, drives etc. are same as before the driver installation.

Xen Orchestra displays that Xen Tools are not detected, but i can see Memory Usage etc.
XCP-ng Center:

[borzel]

@RKO1337 you have to install the drivers then manually ... point the driver install dialog from windows to c:\programe files\xcp-ng\drivers (don't forget to tell him to search also in subfolders)

[RKO1337]

@borzel thanks now all devices correctly recognized