Hi,
I have Ceph RBD.
But when I create a new VM, i had an error
Sat Apr 9 00:44:25 2016 : No system datastore meets capacity and SCHED_DS_REQUIREMENTS: CLUSTER_ID = 100 & !(PUBLIC_CLOUD = YES)
Whats wrong?
Hi,
I have Ceph RBD.
But when I create a new VM, i had an error
Sat Apr 9 00:44:25 2016 : No system datastore meets capacity and SCHED_DS_REQUIREMENTS: CLUSTER_ID = 100 & !(PUBLIC_CLOUD = YES)
Whats wrong?
hi, the datastore Cephds is not assigned to a cluster yet.
(see top right button: “Select Cluster”) So the scheduler cannot use the datastore.
I add System DS to cluster, but now another problem.
Mon Apr 11 14:59:23 2016 [Z0][VMM][D]: Message received: LOG I 9 ExitCode: 0
Mon Apr 11 14:59:23 2016 [Z0][VMM][D]: Message received: LOG I 9 Successfully execute network driver operation: pre.
Mon Apr 11 14:59:23 2016 [Z0][VMM][D]: Message received: LOG I 9 Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy '/var/lib/one//datastores/0/9/deployment.2' 'KVM-1' 9 KVM-1
Mon Apr 11 14:59:23 2016 [Z0][VMM][D]: Message received: LOG I 9 error: Failed to create domain from /var/lib/one//datastores/0/9/deployment.2
Mon Apr 11 14:59:23 2016 [Z0][VMM][D]: Message received: LOG I 9 error: недопустимый аргумент: could not find capabilities for arch=x86_64 domaintype=kvm
Mon Apr 11 14:59:23 2016 [Z0][VMM][D]: Message received: LOG E 9 Could not create domain from /var/lib/one//datastores/0/9/deployment.2
Mon Apr 11 14:59:23 2016 [Z0][VMM][D]: Message received: LOG I 9 ExitCode: 255
Mon Apr 11 14:59:23 2016 [Z0][VMM][D]: Message received: LOG I 9 Failed to execute virtualization driver operation: deploy.
Mon Apr 11 14:59:23 2016 [Z0][VMM][D]: Message received: DEPLOY FAILURE 9 Could not create domain from /var/lib/one//datastores/0/9/deployment.2
got this from another forum, not sure if it will help…
The error could not find capabilities for domaintype=kvm is
indicative of the lack of kvm support on the host. It may mean that the
kvm/kvm_intel/kvm_amd modules aren’t loaded, the CPU doesn’t support
hardware virtualisation, or the required options are disabled in the
BIOS.
(source: Can't get fedora 23 working with libvirt · Issue #539 · vagrant-libvirt/vagrant-libvirt · GitHub)
Unfortunately, but it does`t solve problem.
There are 4 servers:
I mounted /var/lib/one/
from KVM-1 to other hosts.
Create cluster with all KVM hosts and all Storages including CephRBD.
ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM STA
0 system 401.1G 95% KVM-TEST 0 sys - shared on
1 default 401.1G 95% - 1 img fs shared on
2 files 401.1G 95% KVM-TEST 0 fil fs ssh on
101 cephds 1.3T 100% KVM-TEST 1 img ceph ceph on
bash-4.2$ onecluster show 100
CLUSTER 100 INFORMATION
ID : 100
NAME : KVM-TEST
CLUSTER TEMPLATE
RESERVED_CPU=""
RESERVED_MEM=""
HOSTS
0
1
2
VNETS
0
DATASTORES
0
2
101
But when I want to create new VM i get errors:
Tue May 31 12:44:46 2016 [Z0][VM][I]: New state is ACTIVE
Tue May 31 12:44:46 2016 [Z0][VM][I]: New LCM state is PROLOG
Tue May 31 12:44:47 2016 [Z0][VM][I]: New LCM state is BOOT
Tue May 31 12:44:47 2016 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/6/deployment.0
Tue May 31 12:44:47 2016 [Z0][VMM][I]: ExitCode: 0
Tue May 31 12:44:47 2016 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Tue May 31 12:44:47 2016 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy '/var/lib/one//datastores/0/6/deployment.0' 'KVM-2' 6 KVM-2
Tue May 31 12:44:47 2016 [Z0][VMM][I]: error: Failed to create domain from /var/lib/one//datastores/0/6/deployment.0
Tue May 31 12:44:47 2016 [Z0][VMM][I]: error: недопустимый аргумент: could not find capabilities for arch=x86_64 domaintype=kvm
Tue May 31 12:44:47 2016 [Z0][VMM][E]: Could not create domain from /var/lib/one//datastores/0/6/deployment.0
Tue May 31 12:44:47 2016 [Z0][VMM][I]: ExitCode: 255
Tue May 31 12:44:47 2016 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Tue May 31 12:44:47 2016 [Z0][VMM][E]: Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/0/6/deployment.0
Tue May 31 12:44:47 2016 [Z0][VM][I]: New LCM state is BOOT_FAILURE
I try to restart livbritd. Check all privileges. All mounts works. Hosts available for each other.
I cant understand what the problem.
UPD:
[ceph@H1-KVM-3 ~]$ sudo service libvirtd status
Redirecting to /bin/systemctl status libvirtd.service
● libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
Active: active (running) since Вт 2016-05-31 12:56:28 MSK; 10min ago
Docs: man:libvirtd(8)
http://libvirt.org
Main PID: 794365 (libvirtd)
CGroup: /system.slice/libvirtd.service
├─ 2839 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
├─ 2840 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
└─794365 /usr/sbin/libvirtd
май 31 12:56:28 KVM-3 systemd[1]: Starting Virtualization daemon...
май 31 12:56:28 KVM-3 systemd[1]: Started Virtualization daemon.
май 31 12:56:28 KVM-3 dnsmasq[2839]: read /etc/hosts - 6 addresses
май 31 12:56:28 KVM-3 dnsmasq[2839]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
май 31 12:56:28 KVM-3 dnsmasq-dhcp[2839]: read /var/lib/libvirt/dnsmasq/default.hostsfile
май 31 13:07:17 KVM-3 libvirtd[794365]: libvirt version: 1.2.17, package: 13.el7_2.4 (CentOS BuildSystem <http://bugs.centos.org>, 2016-...tos.org)
май 31 13:07:17 KVM-3 libvirtd[794365]: недопустимый аргумент: could not find capabilities for arch=x86_64 domaintype=kvm
Hint: Some lines were ellipsized, use -l to show in full.
UPD2: If i try to change domaintype for i686 - kvm && x64_68 qemu, get error XML error: No bus PCI libvirt
This is the error from libvirt
Tue May 31 12:44:47 2016 [Z0][VMM][I]: error: недопустимый аргумент: could
not find capabilities for arch=x86_64 domaintype=kvm
It seems that your nodes are not x86_64 capable. Execute virsh capabilities
in the nodes to see the available architectures…
Problem solved.
After BIOS firmware upgrade, option Intel-VT was reset.
Now that`s OK.
p.s. Sometimes it is necessary to pay attention to details)