-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libvirt: Could not find any guests for architecure type hvm/x86_64 #570
Comments
I expect this is an old or broken libvirt/QEMU/kernel setup. We'll see if your Fedora upgrade helps.
More OS X discussion in #201. |
@wking I upgrade my Fedora to 27 from 25, but still got the below errors. What do you suggest? Thanks! [jzhang@dhcp-140-18 installer]$ ./bin/openshift-install create cluster
? Image [? for help] (http://aos-ostree.rhev-ci-vms.eng.rdu2.redhat.com/rhcos/images/cloud/late? Image http://aos-ostree.rhev-ci-vms.eng.rdu2.redhat.com/rhcos/images/cloud/latest/rhcos-qemu.qcow2.gz
INFO Fetching OS image...
INFO Using Terraform to create cluster...
ERROR Error: Error applying plan:
2 error(s) occurred:
* libvirt_domain.master: 1 error(s) occurred:
* libvirt_domain.master: Error defining libvirt domain: virError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for domaintype=kvm ')
* module.bootstrap.libvirt_domain.bootstrap: 1 error(s) occurred:
* libvirt_domain.bootstrap: Error defining libvirt domain: virError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for domaintype=kvm ')
Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
FATAL Error executing openshift-install: exit status 1 System info: [jzhang@dhcp-140-18 installer]$ cat /etc/redhat-release
Fedora release 27 (Twenty Seven)
[jzhang@dhcp-140-18 installer]$ uname -a
Linux dhcp-140-18.nay.redhat.com 4.13.9-300.fc27.x86_64 #1 SMP Mon Oct 23 13:41:58 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
Can you provide: $ openshift-install version
$ ~/.terraform.d/plugins/terraform-libvirt-provider -version
$ cat /proc/cpuinfo
$ lsmod | grep kvm ? The last two are suggested here. |
Sure, as below:
|
Can you also provide the |
@wking Related with BIOS intel virtualization switchs? |
Could be. The comment I linked earlier suggests the error message comes from broken/missing KVM, but I'm not familiar enough with KVM to know how it's likely to break. |
@wking thanks, and make sense |
I hit a similar issue when create cluster on libvirt.
|
What CPU are you on? That looks like dmacvicar/terraform-provider-libvirt#262. |
@jianzhangbjz @jiajliu about the bios switches, take thinkpad as example |
@wjiangjay cool! Thanks a lot! |
@wking Thank you. I also encountered the above errors @jiajliu said. INFO Using Terraform to create cluster...
ERROR Error: Error applying plan:
2 error(s) occurred:
* module.bootstrap.libvirt_domain.bootstrap: 1 error(s) occurred:
* libvirt_domain.bootstrap: [DEBUG] Could not find any guests for architecure type hvm/x86_64
* libvirt_domain.master: 1 error(s) occurred:
* libvirt_domain.master: [DEBUG] Could not find any guests for architecure type hvm/x86_64
Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
FATAL Error executing openshift-install: exit status 1 System info: [root@preserved-cluster-up-ui-long-term-use installer]$ uname -a
Linux preserve-olm.localdomain 3.10.0-514.26.1.el7.x86_64 #1 SMP Tue Jun 20 01:16:02 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
[root@preserved-cluster-up-ui-long-term-use installer]$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.3 (Maipo) CPU info(8 vcpu, 16G): [root@preserved-cluster-up-ui-long-term-use installer]$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 85
model name : Intel(R) Xeon(R) Gold 6152 CPU @ 2.10GHz
stepping : 4
microcode : 0x1
cpu MHz : 2095.078
cache size : 16384 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology eagerfpu pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch arat tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1
bogomips : 4190.15
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
...
...
... You can also access the OpenStack Instances with your libra key, search |
I guess the original problem |
The host with libvirt and installer on it is a vm on openstack. [root@preserve-installer-4 ~]# cat /proc/cpuinfo |
The reason you hit You need to explicitly yum install qemu-kvm (or preferably qemu-kvm-[rh]ev if you are on RHEL/CentOS). See also: |
Closing due to inactivity. |
@crawford: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
For what it's worth, I was hitting a similar issue to this on Arch Linux, and installing qemu got me past that hurdle. Thanks, @xsgordon! |
Version
Sorry, I cannot provide the version now. I clone and build it today, may be the latest version. I will provide the exact version later.
$ openshift-install version
Platform (aws|libvirt|openshift):
libevirt
What happened?
What you expected to happen?
create the cluster successfully.
How to reproduce it (as minimally and precisely as possible)?
Not sure. I just followed the https://github.com/openshift/installer/blob/master/docs/dev/libvirt-howto.md step by step.
$ no console
Anything else we need to know?
I used Fedora 25 for this building, I'm upgrading it to 28, and then have a try.
References
By the way, how can I build the 4.0 cluster in the MacOS?
The text was updated successfully, but these errors were encountered: