Ask Your Question
0

xenapi create_vdi error

asked 2011-04-25 07:32:23 -0600

laurent-borensky gravatar image

Hi,

I do not understand why I have this error message. Is this a configuration or use error, or also a bug? I don't know.

The error is (original code) :

2011-04-24 16:19:31,967 DEBUG nova.rpc [-] Initing the Adapter Consumer for compute from (pid=3107) __init__ /home/openstack/nova/nova/rpc.py:148 2011-04-24 16:20:32,316 INFO nova.virt.xenapi.vm_utils [-] (VM_UTILS) xenserver vm state -> |Running| 2011-04-24 16:20:32,316 INFO nova.virt.xenapi.vm_utils [-] (VM_UTILS) xenapi power_state -> |1| 2011-04-24 16:21:10,578 DEBUG nova.rpc [-] received {u'_context_request_id': u'TMAD3ND8FJBE7W44485V', u'_context_read_deleted': False, u'args': {u'instance_id': 14, u'injected_files': [], u'availability_zone': None}, u'_context_is_admin': True, u'_context_timestamp': u'2011-04-24T14:21:10Z', u'_context_user': u'client1', u'method': u'run_instance', u'_context_project': u'appli1', u'_context_remote_address': None} from (pid=3107) _receive /home/openstack/nova/nova/rpc.py:167 2011-04-24 16:21:10,578 DEBUG nova.rpc [-] unpacked context: {'timestamp': u'2011-04-24T14:21:10Z', 'remote_address': None, 'project': u'appli1', 'is_admin': True, 'user': u'client1', 'request_id': u'TMAD3ND8FJBE7W44485V', 'read_deleted': False} from (pid=3107) _unpack_context /home/openstack/nova/nova/rpc.py:331 2011-04-24 16:21:13,649 AUDIT nova.compute.manager [TMAD3ND8FJBE7W44485V client1 appli1] instance 14: starting... 2011-04-24 16:21:13,773 DEBUG nova.rpc [-] Making asynchronous call on network.6Cloud01 ... from (pid=3107) call /home/openstack/nova/nova/rpc.py:350 2011-04-24 16:21:13,773 DEBUG nova.rpc [-] MSG_ID is 97b27c0938d443998093108cdcee354a from (pid=3107) call /home/openstack/nova/nova/rpc.py:353 2011-04-24 16:21:14,245 DEBUG nova.virt.xenapi.vm_utils [-] Detected KERNEL_RAMDISK format for image 5, instance 14 from (pid=3107) log_disk_format /home/openstack/nova/nova/virt/xenapi/vm_utils.py:494 2011-04-24 16:21:14,488 DEBUG nova.virt.xenapi.vm_utils [-] Size for image 5:4099360 from (pid=3107) _fetch_image_glance_disk /home/openstack/nova/nova/virt/xenapi/vm_utils.py:442 2011-04-24 16:21:15,595 DEBUG nova.virt.xenapi.vm_utils [-] Created VDI OpaqueRef:6d15d8cb-b89d-01b9-efed-56b7bd355807 (Glance image 5, 4099360, False) on OpaqueRef:506f6691-e685-d001-c84d-d9e900c78e36. from (pid=3107) create_vdi /home/openstack/nova/nova/virt/xenapi/vm_utils.py:277 2011-04-24 16:21:15,596 ERROR nova.compute.manager [TMAD3ND8FJBE7W44485V client1 appli1] Instance '14' failed to spawn. Is virtualization enabled in the BIOS? (nova.compute.manager): TRACE: Traceback (most recent call last): (nova.compute.manager): TRACE: File "/home/openstack/nova/nova/compute/manager.py", line 234, in run_instance (nova.compute.manager): TRACE: self.driver.spawn(instance_ref) (nova.compute.manager): TRACE: File "/home/openstack/nova/nova/virt/xenapi_conn.py", line 188, in spawn (nova.compute.manager): TRACE: self._vmops.spawn(instance) (nova.compute.manager): TRACE: File "/home/openstack/nova/nova/virt/xenapi/vmops.py", line 117, in spawn (nova.compute.manager): TRACE: vdi_uuid = self._create_disk(instance) (nova.compute.manager): TRACE: File "/home/openstack/nova/nova/virt/xenapi/vmops.py", line 113, in _create_disk (nova.compute.manager): TRACE: instance.image_id, user, project, disk_image_type) (nova.compute.manager): TRACE: File "/home/openstack/nova/nova/virt/xenapi/vm_utils.py", line 382, in fetch_image (nova.compute.manager): TRACE: access, image_type) (nova.compute.manager ... (more)

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2011-07-25 15:14:01 -0600

I'll assume it does solve your issue -- If not please reopen the bug by setting its status back to New.

edit flag offensive delete link more
0

answered 2011-07-26 09:42:02 -0600

From DanPrince:

I think this may be a configuration issue. The current nova xenapi code requires that nova-compute be run inside a VM on the actual XenServer host machine it is controlling. If you do this then you should automatically have the /sys/hypervisor/uuid file available for nova-compute to read.

The nova xenapi plugins (which get installed on the XenServer itself) use this to create and mount a VDI device in the nova-compute VM where the raw image data can be written.

Hope this helps.

Dan

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

Stats

Asked: 2011-04-25 07:32:23 -0600

Seen: 20 times

Last updated: Jul 26 '11