Bug 1903134
| Summary: | Instance remains in powering-on state forever after compute reboots | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Eduardo Olivares <eolivare> |
| Component: | python-networking-ovn | Assignee: | RHOS Maint <rhos-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | Eran Kuris <ekuris> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16.1 (Train) | CC: | apevec, jlibosva, lhh, lmartins, majopela, scohen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-12-01 14:15:00 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Eduardo Olivares
2020-12-01 12:18:32 UTC
Hi, I quickly skimmed the logs from Neutron and Nova compute but I don't see anything specific that I think would cause it to fail. But, I believe the error was in QEMU restarting the VM. Here's the creation of that the VM from the nova logs [0] 2020-11-29 10:38:39.943 7 DEBUG nova.virt.libvirt.driver [req-1ac3db66-07c2-4882-b177-a56a14b384c6 e678d845e06f46a7b588ccd7cc732eb9 48ce485e440c4ca0b10a4b4b1c4f24fb - default default] [instance: 0cf82ec3-efd1-4f6e-baf4-8f04efe90925] End _get_guest_xml xml=<domain type="kvm"> <uuid>0cf82ec3-efd1-4f6e-baf4-8f04efe90925</uuid> <name>instance-0000019a</name> ... So the instance is the "instance-0000019a". When I look at the libvirt logs for that particular instance I see that the VM failed to start [1] with: 2020-11-29T12:04:09.254297Z qemu-kvm: -device cirrus-vga,id=video0,bus=pci.0,addr=0x2: warning: 'cirrus-vga' is deprecated, please use a different VGA card instead KVM: entry failed, hardware error 0x80000021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=00000000 EBX=00000000 ECX=00000000 EDX=000006d3 ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000 EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0000 00000000 00000000 00008000 CS =0000 00000000 00000000 00009b00 SS =0000 00000000 00000000 00009300 DS =0000 00000000 00000000 00008000 FS =0000 00000000 00000000 00008000 GS =0000 00000000 00000000 00008000 LDT=0000 00000000 00000000 00008000 TR =0000 00000000 00000000 00008000 GDT= 00000000 00000000 IDT= 00000000 00000000 CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000000 Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 So maybe the problem is that the VM itself never started due to the error above and therefore never moved to ACTIVE. I don't know exactly what the error above means, maybe someone more familiar with libvirt/QEMU can give us some clues. [0] http://rhos-ci-logs.lab.eng.tlv2.redhat.com/logs/rcj/DFG-network-networking-ovn-16.1_director-rhel-virthost-3cont_2comp-ipv4-geneve-tobiko-neutron/43/compute-0/var/log/containers/nova/nova-compute.log.1.gz [1] http://rhos-ci-logs.lab.eng.tlv2.redhat.com/logs/rcj/DFG-network-networking-ovn-16.1_director-rhel-virthost-3cont_2comp-ipv4-geneve-tobiko-neutron/43/compute-0/var/log/libvirt/qemu/instance-0000019a.log.gz *** This bug has been marked as a duplicate of bug 1890895 *** |