Ask Your Question

Quickstart demo launching instance fails

asked 2015-01-08 18:11:27 -0600

ggont gravatar image

updated 2015-01-09 05:23:52 -0600

dbaxps gravatar image


I am completely new to openstack and cloud concepts. I thought it would be a good idea to get a "look and feel" by installing allinone in a laptop running centos os7 minimal. After a few tries i managed to install openstack using packstack and access the horizon dashboard. After that I logged in as "demo" and followed the instructions to run and instance of fedora19:

When I try to launch instance it fails. Checked nova-compute logs and see this error:

2015-01-08 15:32:01.235 24175 ERROR nova.virt.libvirt.driver [-] Error defining a domain with XML: <domain type="kvm">

You can see more info as it has the XML in the attached logs.

Could you please help me out?

Looks like I have issues uploading so here is the XML:

2015-01-08 15:32:01.235 24175 ERROR nova.virt.libvirt.driver [-] Error defining a domain with XML: <domain type="kvm">
  <vcpu cpuset="0-3">1</vcpu>
    <nova:instance xmlns:nova="">
      <nova:package version="2014.2.1-1.el7.centos"/>
      <nova:creationTime>2015-01-08 20:31:59</nova:creationTime>
      <nova:flavor name="m1.small">
        <nova:user uuid="953ab77a3d1f48a09a6a73ce04075ab0">demo</nova:user>
        <nova:project uuid="40777baf659245f1b9468bf1f161a10c">demo</nova:project>
      <nova:root type="image" uuid="04448312-db23-47be-86b6-757967de14ac"/>
  <sysinfo type="smbios">
      <entry name="manufacturer">Fedora Project</entry>
      <entry name="product">OpenStack Nova</entry>
      <entry name="version">2014.2.1-1.el7.centos</entry>
      <entry name="serial">0e598d67-dc28-46f0-961a-068479576e5d</entry>
      <entry name="uuid">f85e8f27-4df1-4fea-8cf9-3a3ad54b1a8d</entry>
    <boot dev="hd"/>
    <smbios mode="sysinfo"/>
  <clock offset="utc">
    <timer name="pit" tickpolicy="delay"/>
    <timer name="rtc" tickpolicy="catchup"/>
    <timer name="hpet" present="no"/>
  <cpu mode="host-model" match="exact">
    <topology sockets="1" cores="1" threads="1"/>
    <disk type="file" device="disk">
      <driver name="qemu" type="qcow2" cache="none"/>
      <source file="/var/lib/nova/instances/f85e8f27-4df1-4fea-8cf9-3a3ad54b1a8d/disk"/>
      <target bus="virtio" dev="vda"/>
    <interface type="bridge">
      <mac address="fa:16:3e:ee:10:fc"/>
      <model type="virtio"/>
      <source bridge="qbr2aac5f0a-57"/>
      <target dev="tap2aac5f0a-57"/>
    <serial type="file">
      <source path="/var/lib/nova/instances/f85e8f27-4df1-4fea-8cf9-3a3ad54b1a8d/console.log"/>
    <serial type="pty"/>
    <input type="tablet" bus="usb"/>
    <graphics type="vnc" autoport="yes" keymap="en-us" listen=""/>
      <model type="cirrus"/>
    <memballoon model="virtio">
      <stats period="10"/>

2015-01-08 15:32:01.236 24175 ERROR nova.compute.manager [-] [instance: f85e8f27-4df1-4fea-8cf9-3a3ad54b1a8d] Instance failed to spawn
edit retag flag offensive close merge delete


Is there anything special in your libvirtd.log ?

fifieldt gravatar imagefifieldt ( 2015-01-09 02:56:10 -0600 )edit

Could you please,post ( as update to answer)

1. ifconfig
2. ovs-vcstl show
3. brctl show
dbaxps gravatar imagedbaxps ( 2015-01-09 05:26:54 -0600 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2015-01-09 14:34:57 -0600

ggont gravatar image

Thank you very much for the responses. I found the answer to my problem. KVM was disabled by my company in the laptop. I found this by following the commands in this document: (

If anyone is interested how I found this out keep reading.

The error suggested that there was an issue with "kvm". In the beginning because I grepped the log file for "ERR" didn't see the whole XML file. Then I saw the line in XML <type>hvm<> and a message in logs libvirtError: internal error: no supported architecture for os type 'hvm'

With this information I did a new google search and found some simiar cases. When I tried to follow the kvm config document I saw an error message saying that virtualization is disabled in BIOS.

Since I had to wait till the next day to enable it, I tried changing the nova.conf virt_type to qemu (not sure what I was doing...). However there was the same issue. In XML it was hvm.

I would appreciate if someone could explain what is this hvm and why qemu didn't work.


edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2015-01-08 18:11:27 -0600

Seen: 3,364 times

Last updated: Jan 09 '15