Open marcusbooyah opened 3 years ago
After adding a new network manually, I could import the xva:
[15:15 xcp3 ~]# xe network-create name-label="Pool-wide network associated with eth1"
86b68a9f-d40f-dced-411e-17a3060af205
[15:15 xcp3 ~]# xe vm-import url=http://s3-us-west-2.amazonaws.com/neonkube/vm-images/xenserver/neon-ubuntu-20.04.latest.xva
[15:15 xcp3 ~]# xe network-list
uuid ( RO) : bc351807-8076-f9b7-8d94-1369f20a6ecd
name-label ( RW): Pool-wide network associated with usb0
name-description ( RW):
bridge ( RO): brusb0
uuid ( RO) : 86e8dcb3-35f8-6832-9130-59b88791aeed
name-label ( RW): Host internal management network
name-description ( RW): Network on which guests will be assigned a private link-local IP address which can be used to talk XenAPI
bridge ( RO): xenapi
uuid ( RO) : 18729ffe-cae4-37f8-c58d-82961345724e
name-label ( RW): Pool-wide network associated with eth0
name-description ( RW):
bridge ( RO): xenbr0
uuid ( RO) : 86b68a9f-d40f-dced-411e-17a3060af205
name-label ( RW): Pool-wide network associated with eth1
name-description ( RW):
bridge ( RO): xapi1
[15:15 xcp3 ~]# xe vm-import url=http://s3-us-west-2.amazonaws.com/neonkube/vm-images/xenserver/neon-ubuntu-20.04.latest.xva
3309bc27-1879-c040-a4d5-2cecea0ebe19
It looks like when we import a VM, it tries to import the networks associated with it. In this case where I only had 1 NIC, the second network couldn't be created.