Can not Create VM under Citrix Xenserver Free 6.2

Hi, I have the following problem. The setup: - 5 Centos based KVM vHosts - 2 Citrix Xenserver 4 nics each eth0=management eth1=trunk eth2=storage(nfs) eth3=storage(iscsi) for now I am only using NFS 2 volumes for the KVM and 1 volume for the XEN The centos versions with KVM are working for years without any problem. Now I added 2 Citrix Xenservers, downloaded the Citrix images via 'new system images'. If I want to deploy those I get the message below:

> Copying 525.92 MB image file to system 10.24.68.184 .............................................. .. done Creating virtual system with Citrix Xen .. .. creation failed : Failed to create root disk : Failed to create partition : Unable to open /dev/xvdf <<<<<< The virtual machine is created on the xenserver, but no disk to find on the volume. The created VM is not visible in cloudmin, so i had to remove the vm via xencenter.

If I Create a empty system from a template, Teh virtual machine is created, also the Disk is available, But cannot be started, see error file below

> Creating virtual system with Citrix Xen .. .. creation started.

Waiting for creation to complete .. .. creation has completed successfully.

Adding virtual network interfaces .. .. created 1 interfaces

Mounting new instance's filesystem .. .. not possible for a VM created from an installation template

Adding DNS entry node-129.localhost.localdomain. for IP address 10.24.63.129 .. .. done

Starting up new Citrix Xen instance .. .. failed to start : The bootloader returned an error vm: d93148cc-1df0-7427-b291-2c857b0b4679 (node-129.localhost.localdomain) msg: INVALID_SOURCE Unable to access a required file in the specified repository: ftp://ftp.surfnet.nl/pub/os/Linux/distr/CentOS/6.5/isos/x86_64/CentOS-6.....

Fetching current status .. .. status successfully retrieved (Down)

Enabling system at host boot time .. .. done

> The repository is available, on teh same Citrix xenserver I downloaded the file in /home/ISO with wget.

Maybe you are able to give me some tips and tricks

Status: 
Closed (fixed)

Comments

So in the first failure, it looks like the VM's disk didn't get attached to the host system - which is needed for Cloudmin to manage partitions and apply the VM image.

After this happened, could you see in XenCenter if the VM had any disks at all?

Situation 1:
I watched it more closely in xencenter, during creation you see that cloudmin wants to create a disk and disappears again and the error in the cloudmin interface occurs. VM is not visible in Cloudmin, but is created on Xenserver. Removal VM only possible in xencenter

Situation 2:
De disk is really created but does not start, I think due to clean install. VM is visible in cloudmin, and can be deleted within the cloudmin interface

FYI: If I log in to the console of the xenserver I can write into this NFS mountpoint. So I am quite sure that read/write rights are correct.

Someone else reported a similar issue, and I was able to debug this on his system. To see if you are seeing the same problem, could you run the following commands for me on your XenServer machine :

xe vm-list
hostname

and post the output here.

Hi,

The requested output:
[root@vHost-184 ~]# xe vm-list
uuid ( RO) : 6284eff1-8d89-ff31-b2cd-413ba89d6f6a
name-label ( RW): node-129.localhost.localdomain
power-state ( RO): halted

uuid ( RO) : f61548fc-15f1-4e56-96ec-b3bcef0a2748
name-label ( RW): Control domain on host: vHost-184
power-state ( RO): running

uuid ( RO) : d93148cc-1df0-7427-b291-2c857b0b4679
name-label ( RW): node-129.localhost.localdomain
power-state ( RO): halted

[root@vHost-184 ~]# hostname
vHost-184

The odd thing is that I was quite sure that I removed the node-129 VM. Suddenly they appear again...strange. Attached also the snapshot that they were visible in XenCenter. (I know sometimes you must close and open xencenter again to see the changes)

Seems to be an VM of situation 1 (without a disk) and situation 2 (with a template created disk).
Shall I try to remove them again?
Shall I check it with xe-list and then try to create a new VM with only option 1?
Send you the results?

Screenshot Xencenter named in #4

Extra information Situation 2 Cloudmin info about node-129: Citrix Xen VM name node-129.localhost.localdomain Citrix Xen UUID d93148cc-1df0-7427-b291-2c857b0b4679 Citrix Xen virtualization type PV (Paravirtualization) Manage Disks node-129.localhost.localdomain No virtual disks were found on this system! The odd thing about this is: Cloudmin tells me that this VM with UUID ****679 has no disks, but xencenter says that there is a disk of 8GB.

Thanks - it looks like you are seeing the same problem as the other user I am investigating. I will update this ticket when I have more details.

A fix for this has finally been implemented, and will be included in the next Cloudmin release.

Hi,

When is the release of this new version approximately?

A couple of weeks, but I can send you a beta if you like.

I was maybe a little optimistic when I said this was fixed - it turns out there a few other XenServer 6.2 issues to deal with :-(

Automatically closed -- issue fixed for 2 weeks with no activity.

Hi Are few other issues fixed already, or do you have a timeframe for it (releasing cloudmin new version)

thanks

Hi Are few other issues fixed already, or do you have a timeframe for it (releasing cloudmin new version)

thanks

Yes, Cloudmin 7.6 should fix all the XenServer issues mentioned here.

Hi Jamie,

You did great work and creation is almost smoothly, still a few remarks;
(after the upgrade)
- If VLAN (XAPI's) are used on a Bridge, this XAPI's are not visible on XenServer host level.
The Xen VM will be created on the default bridge (4 x nic, so xenbr0-3), because the XAPI's are not known.
Afterwards in cloudmin you cant see the XAPI which i needed for the vm. I changed the connection for this vm to the right xapi (i.e. xapi0 vlan 963) in XenCenter. And now it becomes visible in the vm network connection (see picture).
In short: You still need Xencenter if you want to use vlans in a bridge. Can that be solved?
-In FIrefox 27.01. If I create a xen vm it shows all info needed (see picture), but at the end I get a refresh on the right pane and it gives me nothing (ssl error, which is strange because the self signed cert is imported). When I open the other browser I see the VM is successfully created and can be started.
-In Chrome If I create a xen vm it shows all info needed (see picture), but at the end I get NO refresh. When I open the other browser I see the VM is successfully created and can be started.

May be you can take a look and find the solution for this. If this is fixed I can upgrade to 500 vm's :0)

Good luck

The problem with the bridges may be due to Cloudmin not looking for the correct interface names.

What do the commands brctl show and ifconfig -a output when run on your XenServer system?

Hi, hereby my output

[root@vHost-186 ~]# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 0000.0015c5fcb69c no eth0
xenbr1 0000.0015c5fcb69e no eth1
xapi2
xenbr2 0000.001422ff57b8 no eth2
xenbr3 0000.001422ff57b9 no eth3

[root@vHost-186 ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:15:C5:FC:B6:9C
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:1826593 errors:0 dropped:0 overruns:0 frame:0
TX packets:596866 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:583742995 (556.7 MiB) TX bytes:91328442 (87.0 MiB)

eth1 Link encap:Ethernet HWaddr 00:15:C5:FC:B6:9E
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:166848 errors:0 dropped:0 overruns:0 frame:0
TX packets:16945 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12633402 (12.0 MiB) TX bytes:2961389 (2.8 MiB)

eth2 Link encap:Ethernet HWaddr 00:14:22:FF:57:B8
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:1782746 errors:0 dropped:0 overruns:0 frame:0
TX packets:1604327 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:233927862 (223.0 MiB) TX bytes:2291038811 (2.1 GiB)

eth3 Link encap:Ethernet HWaddr 00:14:22:FF:57:B9
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:41275 errors:0 dropped:0 overruns:0 frame:0
TX packets:41275 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:39459380 (37.6 MiB) TX bytes:39459380 (37.6 MiB)

xapi2 Link encap:Ethernet HWaddr 00:15:C5:FC:B6:9E
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:47510 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3078593 (2.9 MiB) TX bytes:0 (0.0 b)

xenbr0 Link encap:Ethernet HWaddr 00:15:C5:FC:B6:9C
inet addr:10.24.68.186 Bcast:10.24.68.255 Mask:255.255.255.0
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:1826595 errors:0 dropped:0 overruns:0 frame:0
TX packets:583521 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:576436839 (549.7 MiB) TX bytes:87841752 (83.7 MiB)

xenbr1 Link encap:Ethernet HWaddr 00:15:C5:FC:B6:9E
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:111133 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7615758 (7.2 MiB) TX bytes:0 (0.0 b)

xenbr2 Link encap:Ethernet HWaddr 00:14:22:FF:57:B8
inet addr:10.24.17.186 Bcast:10.24.17.255 Mask:255.255.255.0
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:1742318 errors:0 dropped:0 overruns:0 frame:0
TX packets:318981 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:231502150 (220.7 MiB) TX bytes:2206205975 (2.0 GiB)

xenbr3 Link encap:Ethernet HWaddr 00:14:22:FF:57:B9
inet addr:10.24.18.186 Bcast:10.24.18.255 Mask:255.255.255.0
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Note: in my vHost-184 its Xapi1 instead of Xapi2

Can you also post the output of the command xe network-list

HI Jamie,

See attachment (format is better than copy paste in this field)

Mario

Thanks - it looks like the xapiN bridges are listed there. I will have Cloudmin consult this as well when detecting available bridges in the next release.

Automatically closed -- issue fixed for 2 weeks with no activity.