Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Why my vm is not responding to ARP request

Hi guys,

Here is a quick descritpion of my setup.

A CentOS7 VM and liberty distro, I used packstack and my config is "all-in-one". I've created a router, an external network and an internal network.

I've created a cirros image, and a test vm.

I've added the security rules for ping and ssh.

When I ping my vm with it's internal adress ( provided dynamically at creation ), I've got no answer either from my default namespace or from the router namespace.

With tcpdump, I monitored the tap interface and I see arp request, but the vm doesn't answer.

> nova list tells me the instance is ACTIVE and running.

And if I use virsh screenshot I have:

SeaBIOS (versio xxxxxxx)
Machine UUID xxxxxxxxxx
iPXE (http://ipxe.org) 00.03.0 C980 PCI2.10 PnP PMM

console.log is empty and my vm seems to be stuck in the boot step, but nova list and logs tell me that everything is fine.

I found a post on the net describing the same problem and the guy said that its image wasn't created correcly.

But I followed basic steps:

> wget http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
> glance image-create --name "cirros-0.3.4-x86_64" --file cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format bare --visibility public --progress
> nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64 --key-name tapaas-key --nic net-id=cc615845-dc51-41e7-b470-10e00c4b5518 vm-cirros-0.3.4-x86_64

I tried we other version of cirros and other images. But it's the same. At first I've created a floating ip and if I ping this address, it is correctly translated in the internal address, because I see the ARP request.

I'm running out of ideas.

So If someone could help me, I'd be thankful.

Charles.

Why my vm is not responding to ARP request

Hi guys,

Here is a quick descritpion of my setup.

A CentOS7 VM and liberty distro, I used packstack and my config is "all-in-one". I've created a router, an external network and an internal network.

I've created a cirros image, and a test vm.

I've added the security rules for ping and ssh.

When I ping my vm with it's internal adress ( provided dynamically at creation ), I've got no answer either from my default namespace or from the router namespace.

With tcpdump, I monitored the tap interface and I see arp request, but the vm doesn't answer.

> nova list tells me the instance is ACTIVE and running.

And if I use virsh screenshot I have:

SeaBIOS (versio xxxxxxx)
Machine UUID xxxxxxxxxx
iPXE (http://ipxe.org) 00.03.0 C980 PCI2.10 PnP PMM

console.log is empty and my vm seems to be stuck in the boot step, but nova list and logs tell me that everything is fine.

I found a post on the net describing the same problem and the guy said that its image wasn't created correcly.

But I followed basic steps:

> wget http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
> glance image-create --name "cirros-0.3.4-x86_64" --file cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format bare --visibility public --progress
> nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64 --key-name tapaas-key --nic net-id=cc615845-dc51-41e7-b470-10e00c4b5518 vm-cirros-0.3.4-x86_64

I tried we other version of cirros and other images. But it's the same. At first I've created a floating ip and if I ping this address, it is correctly translated in the internal address, because I see the ARP request.

I'm running out of ideas.

So If someone could help me, I'd be thankful.

Charles.


!!!!! EDITING !!!!!

Hi,

I am editing my post because I cannot add comments or an answer for this thread, I send an email two days ago to AskOpestack team but so far no answer.

First thank you for your help and here my answer to your comments.

Yes I agree with you this is more a boot instance problem than a network problem. I tried to load the image with VirtualBox, but it failed at boot it was not recognize as a valid image I used this command:

VBoxManage convertfromraw --format VDI vdisk_raw.img vdisk.vdi

I tried glance image-download and diff ... same image. I tried other versions of cirros images, but with the same result. I have access to VNC console and I've got the same message as in the screenshoot ( stuck with the iPxe message ).

Charles.

Why my vm is not responding to ARP request

Hi guys,

Here is a quick descritpion of my setup.

A CentOS7 VM and liberty distro, I used packstack and my config is "all-in-one". I've created a router, an external network and an internal network.

I've created a cirros image, and a test vm.

I've added the security rules for ping and ssh.

When I ping my vm with it's internal adress ( provided dynamically at creation ), I've got no answer either from my default namespace or from the router namespace.

With tcpdump, I monitored the tap interface and I see arp request, but the vm doesn't answer.

> nova list tells me the instance is ACTIVE and running.

And if I use virsh screenshot I have:

SeaBIOS (versio xxxxxxx)
Machine UUID xxxxxxxxxx
iPXE (http://ipxe.org) 00.03.0 C980 PCI2.10 PnP PMM

console.log is empty and my vm seems to be stuck in the boot step, but nova list and logs tell me that everything is fine.

I found a post on the net describing the same problem and the guy said that its image wasn't created correcly.

But I followed basic steps:

> wget http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
> glance image-create --name "cirros-0.3.4-x86_64" --file cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format bare --visibility public --progress
> nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64 --key-name tapaas-key --nic net-id=cc615845-dc51-41e7-b470-10e00c4b5518 vm-cirros-0.3.4-x86_64

I tried we other version of cirros and other images. But it's the same. At first I've created a floating ip and if I ping this address, it is correctly translated in the internal address, because I see the ARP request.

I'm running out of ideas.

So If someone could help me, I'd be thankful.

Charles.


!!!!! EDITING !!!!!Edit1:

Hi,

I am editing my post because I cannot add comments or an answer for this thread, I send an email two days ago to AskOpestack team but so far no answer.

First thank you for your help and here my answer to your comments.

Yes I agree with you this is more a boot instance problem than a network problem. I tried to load the image with VirtualBox, but it failed at boot it was not recognize as a valid image I used this command:

VBoxManage convertfromraw --format VDI vdisk_raw.img vdisk.vdi

I tried glance image-download and diff ... same image. I tried other versions of cirros images, but with the same result. I have access to VNC console and I've got the same message as in the screenshoot ( stuck with the iPxe message ).

Charles.


Edit2:

I've tested all the images I've downloaded, all checksums are ok.

As for the file format, I downloaded qcow2 because of the following comment on this page get image

"If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent 64-bit qcow2 image as of this writing is cirros-0.3.4-x86_64-disk.img."

I have a reference plateform ( someone else installed it but I cannot contact him ) and the cirros is a qcow2.

Here is the infos about the image I use:

# qemu-img info cirros-0.3.0-x86_64-disk.img
image: cirros-0.3.0-x86_64-disk.img
file format: qcow2
virtual size: 39M (41126400 bytes)
disk size: 9.3M
cluster_size: 65536
Format specific information:
    compat: 0.10

Why my vm is not responding to ARP request

Hi guys,

Here is a quick descritpion of my setup.

A CentOS7 VM and liberty distro, I used packstack and my config is "all-in-one". I've created a router, an external network and an internal network.

I've created a cirros image, and a test vm.

I've added the security rules for ping and ssh.

When I ping my vm with it's internal adress ( provided dynamically at creation ), I've got no answer either from my default namespace or from the router namespace.

With tcpdump, I monitored the tap interface and I see arp request, but the vm doesn't answer.

> nova list tells me the instance is ACTIVE and running.

And if I use virsh screenshot I have:

SeaBIOS (versio xxxxxxx)
Machine UUID xxxxxxxxxx
iPXE (http://ipxe.org) 00.03.0 C980 PCI2.10 PnP PMM

console.log is empty and my vm seems to be stuck in the boot step, but nova list and logs tell me that everything is fine.

I found a post on the net describing the same problem and the guy said that its image wasn't created correcly.

But I followed basic steps:

> wget http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
> glance image-create --name "cirros-0.3.4-x86_64" --file cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format bare --visibility public --progress
> nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64 --key-name tapaas-key --nic net-id=cc615845-dc51-41e7-b470-10e00c4b5518 vm-cirros-0.3.4-x86_64

I tried we other version of cirros and other images. But it's the same. At first I've created a floating ip and if I ping this address, it is correctly translated in the internal address, because I see the ARP request.

I'm running out of ideas.

So If someone could help me, I'd be thankful.

Charles.


Edit1:

Hi,

I am editing my post because I cannot add comments or an answer for this thread, I send an email two days ago to AskOpestack team but so far no answer.

First thank you for your help and here my answer to your comments.

Yes I agree with you this is more a boot instance problem than a network problem. I tried to load the image with VirtualBox, but it failed at boot it was not recognize as a valid image I used this command:

VBoxManage convertfromraw --format VDI vdisk_raw.img vdisk.vdi

I tried glance image-download and diff ... same image. I tried other versions of cirros images, but with the same result. I have access to VNC console and I've got the same message as in the screenshoot ( stuck with the iPxe message ).


Edit2:

I've tested all the images I've downloaded, all checksums are ok.

As for the file format, I downloaded qcow2 because of the following comment on this page get image

"If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent 64-bit qcow2 image as of this writing is cirros-0.3.4-x86_64-disk.img."

I have a reference plateform ( someone else installed it but I cannot contact him ) and the cirros is a qcow2.

Here is the infos about the image I use:

# qemu-img info cirros-0.3.0-x86_64-disk.img
image: cirros-0.3.0-x86_64-disk.img
file format: qcow2
virtual size: 39M (41126400 bytes)
disk size: 9.3M
cluster_size: 65536
Format specific information:
    compat: 0.10

Edit3:

@ doka: my problem is that I cannot access to a vnc console, at the time I wrote the title of my post I wasn't sure about the problem, now it looks like my vm is not booting properly, hence no responde to arp request.

I checked libvirt logs too and used virsh to test if my vm is running, and everything looks fine, exept that I cannot connect to the vm, and I have the message "seaBIOS" that make me thing that the vm is stuck at boot waiting something.