Ask Your Question
0

Virtual Machine not connecting but logs seem to provide no errors

asked 2015-01-05 10:18:30 -0500

Poonam Agarwal gravatar image

updated 2015-01-05 14:13:45 -0500

mpetason gravatar image

I have built a new compute node on existing Openstack Setup and started the nova-compute & nova-network services. I am using a flat DHCP Network ( br100 ) When i create an instance , logs seem to suggest that the instance spawned successfully but i cant seem to see the instance console nor connect to it.

b08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Starting instance...
2015-01-05 15:14:35.949 8721 AUDIT nova.compute.claims [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4c7db
08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Attempting claim: memory 2048 MB, disk 20 GB, VCPUs 1
2015-01-05 15:14:35.950 8721 AUDIT nova.compute.claims [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4c7db
08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Total Memory: 64365 MB, used: 512.00 MB
2015-01-05 15:14:35.950 8721 AUDIT nova.compute.claims [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4c7db
08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Memory limit: 96547.50 MB, free: 96035.50 MB
2015-01-05 15:14:35.951 8721 AUDIT nova.compute.claims [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4c7db
08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Total Disk: 793 GB, used: 0.00 GB
2015-01-05 15:14:35.952 8721 AUDIT nova.compute.claims [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4c7db
08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Disk limit not specified, defaulting to unlimited
2015-01-05 15:14:35.952 8721 AUDIT nova.compute.claims [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4c7db
08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Total CPU: 24 VCPUs, used: 0.00 VCPUs
2015-01-05 15:14:35.953 8721 AUDIT nova.compute.claims [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4c7db
08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] CPU limit not specified, defaulting to unlimited
2015-01-05 15:14:35.953 8721 AUDIT nova.compute.claims [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4c7db
08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Claim successful
2015-01-05 15:14:36.416 8721 INFO nova.openstack.common.rpc.common [-] Connected to AMQP server on fmc-enf-nctl-1.enf.fmts.int:5672
2015-01-05 15:14:36.879 8721 INFO nova.virt.libvirt.driver [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4
c7db08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Creating image
2015-01-05 15:14:38.096 8721 INFO nova.virt.libvirt.driver [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4
c7db08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Injecting key into image d829a34c-4016-4535-9d03-192a
d3a6dca6
2015-01-05 15:14:38.286 8721 WARNING nova.virt.disk.api [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530 4c7d
b08bd3644fb58fca3d52501c75c6] Ignoring error injecting data into image (Error mounting /var/lib/nova/instances/6429a079-96ae-47a5-8af8-
c0584476bd5a/disk with libguestfs (unexpected end of file when reading from daemon.
This usually means the libguestfs appliance failed to start up.  Please
enable debugging (LIBGUESTFS_DEBUG=1) and rerun the command, then look at
the debug messages output prior to this error.
Or you can run 'libguestfs-test-tool' and post the complete output into
a bug report or message to the libguestfs mailing list.))
2015-01-05 15:14:38.490 8721 INFO nova.virt.libvirt.firewall [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530
 4c7db08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Called setup_basic_filtering in nwfilter
2015-01-05 15:14:38.490 8721 INFO nova.virt.libvirt.firewall [req-ed5b5b0e-f4e4-48d7-8487-2ef25e2a80cb 4de8ce3bd877407783f4c903bb9d1530
 4c7db08bd3644fb58fca3d52501c75c6] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Ensuring static filters
2015-01-05 15:14:40.807 8721 INFO nova.compute.manager [-] Lifecycle event 0 on VM 6429a079-96ae-47a5-8af8-c0584476bd5a
2015-01-05 15:14:40.877 8721 INFO nova.virt.libvirt.driver [-] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] Instance spawned successfully.
2015-01-05 15:14:41.267 8721 INFO nova.compute.manager [req-e1ad6ae8-502c-4f77-aa98-f7778946e8b2 None None] [instance: 6429a079-96ae-47a5-8af8-c0584476bd5a] During sync_power_state the instance has a pending task. Skip.
edit retag flag offensive close merge delete

Comments

What image are you using? I would recommend using a Cirros image, that way you can use the console to login to the host because Cirros has a predefined user/pass. This can be helpful in determining if your instance got an IP address, can ping out etc. There seems to be injection errors above.

schmaustech gravatar imageschmaustech ( 2015-01-05 17:43:18 -0500 )edit

I am using base ubuntu 12.04 Image. Instance is assigned an IP Address and state shows as running. However cannot ping or connect to the Instance at all. Also when i try to look at the console, it shows a black screen only. The logs dont seem to indicate the exact problem.

Poonam Agarwal gravatar imagePoonam Agarwal ( 2015-01-06 03:04:35 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-01-14 06:56:33 -0500

Poonam Agarwal gravatar image

After investigations , the problem was more fundamental and lower down than the Openstack. The physical network interface thats added to the bridge was pointing to a wrong VLAN and hence the DHCP falte network was not working as expected

Most of the other communication happened via the management interface and hence instances could be created but we couldnt connect to them.

Changing the VLAN ID on the physical network interface has solved the problem

edit flag offensive delete link more

Comments

If your answer solved your problem, than you can accept your answer.

Khayam gravatar imageKhayam ( 2015-02-17 22:41:15 -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-01-05 10:18:30 -0500

Seen: 107 times

Last updated: Jan 14 '15