@olivierlambert Hi, It does work, in that the machine will boot and run without the tools but the network drivers dont install so I'm stuck on 100Mbit which seems to struggle to get above 30Mbit in actual usage. Is there no one out there or at Vates who can look at this problem as to why the XCP-NG tools fail to install at the final part ? I'll happily pay for someone to look at it and fix it, even if its just get the networking up to 1gb.
regards,
Paul
Hi,
We have a couple of client VMs on Windows 2008 R2 (don't ask, these machines are apparently "critical" ) and I'm looking for windows 2008 tools.
I've tried a few old files that I've found to get the tools but they either only work for 2012 onwards on just "fail to install".
Does anyone have any versions of the tools somewhere is a dusty filestore that may work ?
regards,
Paul
@olivierlambert No problem. Since writing the original post, I've realised I got it the wrong way round and found an easier workaround (from a user perspective) and noted it above. My code change turned out to be wrong and irrelevant. Of course there may be a way for allowing both in the code, I'll leave that to you guys.
We run ESX7 but we have machines that have been with us for many years since we ran ESX 5. When importing some of these old VMs we would get the following error. We're running the "latest" branch on our XOA.
404 Not Found https://vca152.dcmanaged.net/folder/fcclaims-liv-claims03/emptyBackingString?dcPath=Enfield&dsName=FC-ENF-CLAIMS-ESX-SC1
The "emptyBackingString" part comes from CDROM entries in the VMX file and machines that give the 404 error have cdrom-raw type
ide0:0.startConnected = "FALSE"
ide0:0.deviceType = "cdrom-raw"
ide0:0.clientDevice = "TRUE"
ide0:0.fileName = "emptyBackingString"
ide0:0.present = "TRUE"
VMs that do import have a different CDROM device type, they also have ide1 rather than ide0
ide1:0.startConnected = "FALSE"
ide1:0.deviceType = "atapi-cdrom"
ide1:0.clientDevice = "TRUE"
ide1:0.fileName = "emptyBackingString"
ide1:0.present = "TRUE"
I found the lines in XOA:/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/vmware-explorer/esxi.mjs that referred to the atapi-cdrom so I suspect the code needs to be adjusted to include the cdrom-raw type.
The workaround in the meantime is to change the CDROM settings in VMware to be "Emulate" rather than "Passthrough", this changes the type to Atapi anyway and the VM will then import.
regards,
Paul
Hi,
I recently had to import 60 VLANs (each a /24 networks) into our two XCP pools in order to be able to import client VMs in to them. I'm putting my quick and dirty perl code here in case it helps anyone else, perl is installed on the XCP hosts by default, best run on the master of the pool.
You will need your data formatted like this one vlan/network per line into a file I called "in.txt" . The "IP Range" is only used to be tagged to the end of the description . As you can tell this was a straight export out of our CMDB as an HTML table.
<tr><td>Network Name</td><td>VLAN ID</td><td>IP Range</td><td>Description</td></tr>
<tr><td>PI External 223.0</td><td>1032</td><td>8.8.8.0/25</td><td>PI Space</td></tr>
# UUIDS of host PIFs that you want this vlan presented on, can be bonded or not.
# UUID of PIF of master host in pool MUST be the first one
my @pif_uuids = ('MASTERUUID','NEXTUUID','NEXTUUID');
open (IN,"in.txt");
while (<IN>) {
chomp $_;
my @array = split(/<\/td><td>/,$_);
$array[0] =~ s/<tr><td>//;
$array[3] =~ s/<\/td><\/tr>//;
# First create the base network and get the network UUID back
my $uuid = `xe network-create name-label='$array[0]' name-description='$array[3] - $array[2]'`;
chomp($uuid);
my $string = "VLANS created ";
# Now iterate over the PIFs of the hosts attaching the VLAN to the network.
foreach my $pifuuid (@pif_uuids) {
my $command = "xe vlan-create network-uuid=$uuid pif-uuid=$pifuuid vlan=$array[1]";
my $vlanuuid= `$command`;
chomp $vlanuuid;
$string .= $vlanuuid .' ';
}
print $string . " for VLAN " . $array[1] ."\n";
sleep 2;
}
Hope this helps someone
Regards
Paul
It depends on what you use vmware for. If it's all the deep level stuff like VSAN etc then yes vmware has the upper hand (although it is coming to xcp-ng from what I have seen). However if you have VMs that you want to run with High Availability on shared storage with an integrated backup solution the XCP-NG wins and its much cheaper than vmware especially post broadcom.
Paul