[openstack-dev] nova-compute vfsguestfs
abhishek jain
ashujain9727 at gmail.com
Mon Jun 23 10:33:38 UTC 2014
Hi Rich
I'm trying to run VM from controller node onto compute node and it is
stucking at spawning state.I'm able to get the libvirt.xml in
/opt/stack/data/nova/instances/729482302900..... on the compute node and
below is the libvirt.xml file..
domain type="kvm">
<uuid>7210aa10-6c98-418a-b97e-94ef2dcbb7f3</uuid>Hi
I'm trying to run VM from controller node onto compute node and it is
stucking at spawning state.I'm able to get the libvirt.xml in
/opt/stack/data/nova/instances/729482302900..... on the compute node and
below is the libvirt.xml file..
domain type="kvm">
<uuid>7210aa10-6c98-418a-b97e-94ef2dcbb7f3</uuid>
<name>instance-00000003</name>
<memory>524288</memory>
<vcpu>1</vcpu>
<os>
<type machine="ppce500">hvm</type>
<kernel>/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/kernel</kernel>
<initrd>/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/ramdisk</initrd>
<cmdline>root=/dev/vda console=tty0 console=ttyS0</cmdline>
</os>
<features>
<acpi/>
<apic/>
</features>
<clock offset="utc">
<timer name="pit" tickpolicy="delay"/>
<timer name="rtc" tickpolicy="catchup"/>
</clock>
<devices>
<disk type="file" device="disk">
<driver name="qemu" type="qcow2" cache="none"/>
<source
file="/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/disk"/>
<target bus="virtio" dev="vda"/>
</disk>
<interface>
<model type="virtio"/>
<source bridge="qbr5d2ebebf-03"/>
<target dev="tap5d2ebebf-03"/>
<filterref filter="nova-instance-instance-00000003-fa163ebb2b75"/>
</interface>
<serial type="file">
<source
path="/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/console.log"/>
</serial>
<serial type="pty"/>
</devices>
</domain>
I'm able to manually run VM through virsh and it is appearing running in
virsh list but I'm not able to understand that why it is not able to run
automatically from the cloud itself.
Below are the steps for running VM manually through virsh..
virsh undefine instance-00000003
virsh define libvirt.xml
virsh start instance-00000003
Please help regarding this.
Thanks
<name>instance-00000003</name>
<memory>524288</memory>
<vcpu>1</vcpu>
<os>
<type machine="ppce500">hvm</type>
<kernel>/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/kernel</kernel>
<initrd>/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/ramdisk</initrd>
<cmdline>root=/dev/vda console=tty0 console=ttyS0</cmdline>
</os>
<features>
<acpi/>
<apic/>
</features>
<clock offset="utc">
<timer name="pit" tickpolicy="delay"/>
<timer name="rtc" tickpolicy="catchup"/>
</clock>
<devices>
<disk type="file" device="disk">
<driver name="qemu" type="qcow2" cache="none"/>
<source
file="/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/disk"/>
<target bus="virtio" dev="vda"/>
</disk>
<interface>
<model type="virtio"/>
<source bridge="qbr5d2ebebf-03"/>
<target dev="tap5d2ebebf-03"/>
<filterref filter="nova-instance-instance-00000003-fa163ebb2b75"/>
</interface>
<serial type="file">
<source
path="/opt/stack/data/nova/instances/7210aa10-6c98-418a-b97e-94ef2dcbb7f3/console.log"/>
</serial>
<serial type="pty"/>
</devices>
</domain>
I'm able to manually run VM through virsh and it is appearing running
in virsh list but I'm not able to understand that why it is not able to run
automatically from the cloud itself.
Below are the steps for running VM manually through virsh..
virsh undefine instance-00000003
virsh define libvirt.xml
virsh start instance-00000003
Please help regarding this.
Thanks
On Wed, Jun 18, 2014 at 3:55 PM, abhishek jain <ashujain9727 at gmail.com>
wrote:
> Hi RIch
>
> Thanks for the reply.The libguestfs is working fine here and there are no
> issues regarding that on the ubuntu compute node.From the nova-compute logs
> on the compute node,it appears that the tap interface is not coming up on
> the compute node.
>
> Also in the file driver.py at the path /opt/stack/nova/nova/virt/libvirt
> in the below section,
>
>
>
>
>
>
>
>
>
>
>
> *uuid = dom.UUIDString() if event ==
> libvirt.VIR_DOMAIN_EVENT_STOPPED: transition =
> virtevent.EVENT_LIFECYCLE_STOPPED elif event ==
> libvirt.VIR_DOMAIN_EVENT_STARTED: transition =
> virtevent.EVENT_LIFECYCLE_STARTED elif event ==
> libvirt.VIR_DOMAIN_EVENT_SUSPENDED: transition =
> virtevent.EVENT_LIFECYCLE_PAUSED elif event ==
> libvirt.VIR_DOMAIN_EVENT_RESUMED: transition =
> virtevent.EVENT_LIFECYCLE_RESUMED*
> the compute node should go in the second part i.e in
>
> *libvirt.VIR_DOMAIN_EVENT_STARTED ,which it it missing. *
> The output of brctl show is follows on the ubuntu compute node--
>
> brctl show
> bridge name bridge id STP enabled interfaces
> qbr06865952-4f 8000.6654b7d239b7 no qvb06865952-4f
> qbr9cbe0875-42 8000.da3180e79619 no qvb9cbe0875-42
> qbrb61ecf20-cf 8000.e24a1b9d71c0 no qvbb61ecf20-cf
> qbrda8485b3-73 8000.f602a0f09835 no qvbda8485b3-73
>
> The main problem is that the tap interface is not able to come up.Below
> are the nova-compute logs..
>
> ova.virt.libvirt.config [req-6ce8d1f9-5d85-4d4c-a06e-bd8c4d3071ec admin
> admin] Generated XML <domain type="kvm">^M
> <uuid>3a0e6076-1136-47d2-b883-326d7a87e5d4</uuid>^M
> <name>instance-00000009</name>^M
> <memory>524288</memory>^M
> <vcpu>1</vcpu>^M
> <os>^M
> <type>hvm</type>^M
>
> <kernel>/opt/stack/data/nova/instances/3a0e6076-1136-47d2-b883-326d7a87e5d4/kernel</kernel>^M
>
> <initrd>/opt/stack/data/nova/instances/3a0e6076-1136-47d2-b883-326d7a87e5d4/ramdisk</initrd>^M
> <cmdline>root=/dev/vda console=tty0 console=ttyS0</cmdline>^M
> </os>^M
> <features>^M
> <acpi/>^M
> <apic/>^M
> </features>^M
> <clock offset="utc">^M
> <timer name="pit" tickpolicy="delay"/>^M
> <timer name="rtc" tickpolicy="catchup"/>^M
> </clock>^M
> <devices>^M
> <disk type="file" device="disk">^M
> <driver name="qemu" type="qcow2" cache="none"/>^M
> <source
> file="/opt/stack/data/nova/instances/3a0e6076-1136-47d2-b883-326d7a87e5d4/disk"/>^M
> <target bus="virtio" dev="vda"/>^M
> </disk>^M
> <interface type="bridge">^M
> <mac address="fa:16:3e:17:c5:cc"/>^M
> <model type="virtio"/>^M
> <source bridge="qbrb61ecf20-cf"/>^M
> <target dev="tapb61ecf20-cf"/>^M
> <filterref filter="nova-instance-instance-00000009-fa163e17c5cc"/>^M
> </interface>^M
> <serial type="file">^M
> <source
> path="/opt/stack/data/nova/instances/3a0e6076-1136-47d2-b883-326d7a87e5d4/console.log"/>^M
>
> 365,103 6%
>
> Please help regarding this.
>
> Thanks
>
>
>
>
> On Tue, Jun 17, 2014 at 8:05 PM, Richard W.M. Jones <rjones at redhat.com>
> wrote:
>
>> On Fri, Jun 13, 2014 at 03:06:25PM +0530, abhishek jain wrote:
>> > Hi Rich
>> >
>> > Can you help me regarding the possible cause for VM stucking at
>> spawning
>> > state on ubuntu powerpc compute node in openstack using devstack.
>>
>> Did you solve this one? It's impossible to debug unless you collect
>> the full debugging information. See also:
>>
>>
>> http://libguestfs.org/guestfs-faq.1.html#how-do-i-debug-when-using-the-api
>> https://bugs.launchpad.net/nova/+bug/1279857
>>
>> Rich.
>>
>> --
>> Richard Jones, Virtualization Group, Red Hat
>> http://people.redhat.com/~rjones
>> Read my programming and virtualization blog: http://rwmj.wordpress.com
>> Fedora Windows cross-compiler. Compile Windows programs, test, and
>> build Windows installers. Over 100 libraries supported.
>> http://fedoraproject.org/wiki/MinGW
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140623/ce267264/attachment.html>
More information about the OpenStack-dev
mailing list