@olivierlambert Thanks, I see they are there

https://www.cisco.com/c/en/us/products/collateral/servers-unified-computing/ucs-x-series-modular-system/ucs-x210c-m7-compute-node-aag.html

Thanks in advance

@olivierlambert Thanks

Hi all.
I upgraded from 8.3 Beta 2 to RC1 via yum update but do not see anything to indicate that this took place.
On the XCP-ng console it just says "XCP-ng 8.3" as does the Advanced settings under XO - 8.3.0 ()
Thanks

Hi All,
I am not clear of the process required here.
I have a Windows Server VM with a 6TB attached RDM LUN
Do i need to detach it in VMware, migrate the VM, then re-attach somehow in XO?
Thanks in advance,
Murf.

@florent the thing is I am looking for a seamless migration workflow from VMware.. not a manual VM per VM migration. (unless v2v has this also?)

@Danp
In VMware->

In XOA after import ->

@Danp no need really, they are just set to DHCP instead of the static settings we had, as if I had added a new interface altogether

@Danp Yes the import process. I think it is because we are using VMXNET 3 interfaces, not E1000 (which caused us horrible problems over the years)

@Danp When I migrate Windows Server VMs the network interface does not have the settings anymore and I have to reconfigure them manually, is this expected behavior?

@Danp Sure, how do I attach a zip file to the post? it wont let me.

@Danp updated to Xen Orchestra, commit f7223 and still the same issue.

I have inspected the UI console, in case this helps

@Danp thanks I will update, and yeah, that was a tongue-in-cheek poke at the previous topic of " Problem with importing large VMDK disks"

Hi all, I just get a spinning wheel when importing a 20MB VMDK
I am using Xen Orchestra, commit eedac
I would upload the VMDK but it has sensitive host name info in the name and metadata sorry. I could change it but that would just be introducing something else to potentially cause issues, however I can describe how I created it

1. Edit a VM in vCenter and add a new 20MB drive, thin provisioned
2. In the Windows Server 2022 VM enable the new drive and initialise/format it
3. Copy the XenServer tools exe to the drive from within the VM
4. unmount the drive
5. Download the drive from the datastore through vCenter UI, this creates a zip file
6. Extract the zipfile
7. drag the VMDK/s to the XO Import UI

Thanks in advance

@julien-f Thanks, the VM had been assigned to VIF default with VLAN ID -1, I just had to move it to my Management VLAN VIF
:
xe vif-move

Further to this, I believe this should already be working, since the primary PIF has the VLAN built into it already, the VM is attached to the PIF and in the same network, however I cant ping the XOA VM

@julien-f Yes thanks, this now applied to the VM but after a reboot I cant ping XOA.

I am using a trunked interface on my XCP-NG host, and the management interface is on VLAN 2850 (set in XCP-NG console VLAN setting)

The IP address I am assigning to the XOA VM is also in the same subnet/VLAN.

I tried the following bit it made no difference:
xe vm-param-set uuid="$uuid" xenstore-data:vm-data/vlan="2850"

@Danp this worked great except I cant change the static IP of the XOA VM:

[14:39 ost-cla-ucs-b0408-xcpng tmp]# xe vif-list vm-uuid=6ad2ed7b-bb4a-6648-89d3-f27fc1bd72f0
uuid ( RO)            : 5bc599d3-be60-c556-4393-0f69ffaa906f
         vm-uuid ( RO): 6ad2ed7b-bb4a-6648-89d3-f27fc1bd72f0
          device ( RO): 0
    network-uuid ( RO): 2b5c4825-5dc5-9283-cada-a81f965872c4


[14:40 ost-cla-ucs-b0408-xcpng tmp]# xe vif-configure-ipv4 uuid=5bc599d3-be60-c556-4393-0f69ffaa906f mode=static address=172.17.132.200/24 gateway=172.17.132.1
You attempted an operation on a VM which lacks the feature.
vm: 6ad2ed7b-bb4a-6648-89d3-f27fc1bd72f0 (XOA)
[14:40 ost-cla-ucs-b0408-xcpng tmp]#

@Danp Thanks I will try a manual download

Hi all, I am using the "xe vm-import url=http://xoa.io/xva" from behind a firewall and need it to fetch the image via our proxy, but can not find any way to do this.
Any help most welcome thanks.
Murf.