Ask Your Question
0

Unable to import guestfsfalling back to VFSLocalFS

asked 2015-04-01 12:30:20 -0500

AlonFre gravatar image

Hi all,

we having a problem to create new instances on a new compute node. the compute node is installed with nova-compute version: 1:2014.2.2-0ubuntu1~cloud0

The main errors in the log file are:

  • Unable to import guestfsfalling back to VFSLocalFS
  • Error defining a domain with XML: domain type="kvm"

Any suggestions? Thanks in advance,

Alon here is the log file of nova-compute.log:

2015-04-01 20:13:31.652 4698 AUDIT nova.compute.manager [req-d77ecf7b-8e11-4686-9aa2-da61cc9f9a48 None] [instance: 50a8caa4-dcc2-435d-a13a-0b9d7e9dfab6] Starting instance...
2015-04-01 20:13:31.760 4698 AUDIT nova.compute.claims [-] [instance: 50a8caa4-dcc2-435d-a13a-0b9d7e9dfab6] Attempting claim: memory 512 MB, disk 1 GB
2015-04-01 20:13:31.761 4698 AUDIT nova.compute.claims [-] [instance: 50a8caa4-dcc2-435d-a13a-0b9d7e9dfab6] Total memory: 3863 MB, used: 512.00 MB
2015-04-01 20:13:31.762 4698 AUDIT nova.compute.claims [-] [instance: 50a8caa4-dcc2-435d-a13a-0b9d7e9dfab6] memory limit: 5794.50 MB, free: 5282.50 MB
2015-04-01 20:13:31.762 4698 AUDIT nova.compute.claims [-] [instance: 50a8caa4-dcc2-435d-a13a-0b9d7e9dfab6] Total disk: 68 GB, used: 0.00 GB
2015-04-01 20:13:31.763 4698 AUDIT nova.compute.claims [-] [instance: 50a8caa4-dcc2-435d-a13a-0b9d7e9dfab6] disk limit not specified, defaulting to unlimited
2015-04-01 20:13:31.775 4698 AUDIT nova.compute.claims [-] [instance: 50a8caa4-dcc2-435d-a13a-0b9d7e9dfab6] Claim successful
2015-04-01 20:13:31.883 4698 INFO nova.scheduler.client.report [-] Compute_service record updated for ('ubuntuServer4', 'ubuntuServer4')
2015-04-01 20:13:32.001 4698 INFO nova.scheduler.client.report [-] Compute_service record updated for ('ubuntuServer4', 'ubuntuServer4')
2015-04-01 20:13:32.360 4698 INFO nova.virt.libvirt.driver [-] [instance: 50a8caa4-dcc2-435d-a13a-0b9d7e9dfab6] Creating image
2015-04-01 20:13:32.543 4698 INFO nova.scheduler.client.report [-] Compute_service record updated for ('ubuntuServer4', 'ubuntuServer4')
2015-04-01 20:13:32.704 4698 INFO nova.virt.disk.vfs.api [-] Unable to import guestfsfalling back to VFSLocalFS
2015-04-01 20:13:34.019 4698 ERROR nova.virt.libvirt.driver [-] Error defining a domain with XML: <domain type="kvm">
  <uuid>50a8caa4-dcc2-435d-a13a-0b9d7e9dfab6</uuid>
  <name>instance-0000002c</name>
  <memory>524288</memory>
  <vcpu cpuset="0-3">1</vcpu>
  <metadata>
    <nova:instance xmlns:nova="http://openstack.org/xmlns/libvirt/nova/1.0">
      <nova:package version="2014.2.2"/>
      <nova:name>three</nova:name>
      <nova:creationTime>2015-04-01 17:13:32</nova:creationTime>
      <nova:flavor name="m1.tiny">
        <nova:memory>512</nova:memory>
        <nova:disk>1</nova:disk>
        <nova:swap>0</nova:swap>
        <nova:ephemeral>0</nova:ephemeral>
        <nova:vcpus>1</nova:vcpus>
      </nova:flavor>
      <nova:owner>
        <nova:user uuid="268e9696ac504a34a9eb1cb75cb81e35">admin</nova:user>
        <nova:project uuid="d21835e6ea054b6799fba4dceaf9edcc">admin</nova:project>
      </nova:owner>
      <nova:root type="image" uuid="77c39020-845a-487f-ab13-6f79310b78b1"/>
    </nova:instance>
  </metadata>
  <sysinfo type="smbios">
    <system>
      <entry name="manufacturer">OpenStack Foundation</entry>
      <entry name="product">OpenStack Nova</entry>
      <entry name="version">2014.2.2</entry>
      <entry name="serial">81d86ad7-2351-cb11-8423-e9dd7be011fa</entry>
      <entry name="uuid">50a8caa4-dcc2-435d-a13a-0b9d7e9dfab6</entry>
    </system>
  </sysinfo>
  <os>
    <type>hvm</type>
    <boot dev="hd"/>
    <smbios mode="sysinfo"/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <clock offset="utc">
    <timer name="pit" tickpolicy="delay"/>
    <timer name="rtc" tickpolicy="catchup"/>
    <timer name="hpet" present="no"/>
  </clock>
  <cpu mode="host-model" match="exact">
    <topology sockets="1" cores="1" threads="1"/>
  </cpu>
  <devices>
    <disk type="file" device="disk">
      <driver name="qemu" type="qcow2" cache ...
(more)
edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
1

answered 2015-04-01 20:48:42 -0500

don gravatar image

Install python-guestfs on your nova-compute nodes. $ apt-get install python-guestfs

edit flag offensive delete link more

Comments

Hi Don, Thanks for your response, i tried it, but i still get the same error. any other ideas?

AlonFre gravatar imageAlonFre ( 2015-04-02 11:14:22 -0500 )edit
1

run python, import guestfs. see what it says:

$ python
>>> import guestfs

this works for me, if u get an error, it might help understand what is wrong.

don gravatar imagedon ( 2015-04-03 13:17:13 -0500 )edit

Hi don, Thanks for your help. we import the guestfs and now this error disappeared from the log file:

2015-04-01 20:13:32.704 4698 INFO nova.virt.disk.vfs.api [-] Unable to import guestfsfalling back to VFSLocalFS

any suggestion for this error:

Error defining a domain with XML

Thanks (:

AlonFre gravatar imageAlonFre ( 2015-04-12 03:11:55 -0500 )edit
1

answered 2015-04-01 12:46:13 -0500

Let's start with the simple things... are the kvm kernel modules loaded?

"no supported architecture for os type 'hvm'" indicates that the KVM kernel modules were not loaded. To check:

# lsmod | grep kvm

If the output does not show that the kvm module is loaded, run the following command to load it:

# modprobe -a kvm

If you cannot start VMs after installation without rebooting, the permissions might not be set correctly. This can happen if you load the KVM module before you install nova-compute. To check whether the group is set to kvm, run:

# ls -l /dev/kvm

If it is not set to kvm, run:

# udevadm trigger
edit flag offensive delete link more

Comments

Hi tedlit, thanks for your response. the kvm kernal module is seems to be loded according to the "lsmod" command. i dont have a /kvm inside /dev. but anyway i tried the command "udevadm trigger" but i still have the same problem. any suggestions? thanks.

AlonFre gravatar imageAlonFre ( 2015-04-02 11:18:32 -0500 )edit
0

answered 2015-04-12 03:48:40 -0500

AlonFre gravatar image

updated 2015-04-12 03:49:44 -0500

Hi The Kvm only apears in the following. Not in /dev..

alonfre@ubuntuServer4:~$ sudo find / -name "kvm"
/sys/kernel/debug/tracing/events/kvm
/sys/module/kvm
/usr/src/linux-headers-3.13.0-32/virt/kvm
/usr/src/linux-headers-3.13.0-32/drivers/s390/kvm
/usr/src/linux-headers-3.13.0-32/arch/powerpc/kvm
/usr/src/linux-headers-3.13.0-32/arch/arm64/kvm
/usr/src/linux-headers-3.13.0-32/arch/tile/kvm
/usr/src/linux-headers-3.13.0-32/arch/s390/kvm
/usr/src/linux-headers-3.13.0-32/arch/x86/kvm
/usr/src/linux-headers-3.13.0-32/arch/ia64/kvm
/usr/src/linux-headers-3.13.0-32/arch/arm/kvm
/usr/src/linux-headers-3.13.0-32/arch/mips/kvm
/usr/src/linux-headers-3.13.0-32/include/kvm
/usr/src/linux-headers-3.13.0-48/virt/kvm
/usr/src/linux-headers-3.13.0-48/drivers/s390/kvm
/usr/src/linux-headers-3.13.0-48/arch/powerpc/kvm
/usr/src/linux-headers-3.13.0-48/arch/arm64/kvm
/usr/src/linux-headers-3.13.0-48/arch/tile/kvm
/usr/src/linux-headers-3.13.0-48/arch/s390/kvm
/usr/src/linux-headers-3.13.0-48/arch/x86/kvm
/usr/src/linux-headers-3.13.0-48/arch/ia64/kvm
/usr/src/linux-headers-3.13.0-48/arch/arm/kvm
/usr/src/linux-headers-3.13.0-48/arch/mips/kvm
/usr/src/linux-headers-3.13.0-48/include/kvm
/usr/src/linux-headers-3.13.0-48-generic/arch/x86/kvm
/usr/src/linux-headers-3.13.0-48-generic/include/kvm
/usr/src/linux-headers-3.13.0-48-generic/include/config/kvm
/usr/src/linux-headers-3.13.0-48-generic/include/config/have/kvm
/usr/src/linux-headers-3.13.0-32-generic/arch/x86/kvm
/usr/src/linux-headers-3.13.0-32-generic/include/kvm
/usr/src/linux-headers-3.13.0-32-generic/include/config/kvm
/usr/src/linux-headers-3.13.0-32-generic/include/config/have/kvm
/lib/modules/3.13.0-32-generic/kernel/arch/x86/kvm
/lib/modules/3.13.0-48-generic/kernel/arch/x86/kvm
edit flag offensive delete link more

Comments

Hey all!

Thank you for your help we solved the problem. Apperantly we needed to enable the VT options in the BIOS, After that we managed to create instances on the new compute node.

AlonFre gravatar imageAlonFre ( 2015-04-12 04:31:39 -0500 )edit

HI alonfre~ I enabled VT option of my compute node, but the problem still exists . any idea?

wz200210 gravatar imagewz200210 ( 2015-10-20 06:24:33 -0500 )edit

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

Stats

Asked: 2015-04-01 12:30:20 -0500

Seen: 1,658 times

Last updated: Apr 12 '15