openstack team mailing list archive

[Nikhil Mittal <mittalnikhil@xxxxxxxxx>]

Output of command "ls -l
/var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96"

-rw-r--r-- 1 nova kvm 6285240320 May 15 06:21
/var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96

Seems normal to me...

I added the image in glance using command:
glance add name="CCM_9001" is_public=true container_format=bare
disk_format=iso < *image_file*

The same commands have been working fine in Essex release.

On Wed, May 15, 2013 at 12:51 PM, lzy.dev@xxxxxxxxx <lzy.dev@xxxxxxxxx>wrote:

> Can you check the backing file:
> /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96
> is in normal?
>
> On Wed, May 15, 2013 at 3:16 PM, Nikhil Mittal <mittalnikhil@xxxxxxxxx>
> wrote:
> > Any suggestions on debugging this issue ? As I mentioned below, the
> command
> > qemu-img shows information where the file format is qcow2 whereas the
> image
> > used in this instance is ISO. Is this a bug or am I missing something ?
> > Thanks,
> > -Nikhil
> >
> >
> > On Tue, May 14, 2013 at 3:30 PM, Nikhil Mittal <mittalnikhil@xxxxxxxxx>
> > wrote:
> >>
> >> Here it is:
> >> ===============
> >> image: /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk
> >> file format: qcow2
> >> virtual size: 160G (171798691840 bytes)
> >> disk size: 200K
> >> cluster_size: 65536
> >> backing file:
> >> /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96
> >> ===============
> >> BTW, I launched the instance with ISO image format NOT qcow2. Don't know
> >> why it is showing the format as qcow2.
> >>
> >>
> >> On Tue, May 14, 2013 at 3:23 PM, lzy.dev@xxxxxxxxx <lzy.dev@xxxxxxxxx>
> >> wrote:
> >>>
> >>> Nikhil
> >>>
> >>> What  the 'qemu-img info
> >>> /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'
> >>> command say?
> >>>
> >>> Zhi Yan
> >>>
> >>> On Tue, May 14, 2013 at 5:43 PM, Nikhil Mittal <mittalnikhil@xxxxxxxxx
> >
> >>> wrote:
> >>> > Wang,
> >>> > I guess you are referring to to the instance specific XML file under
> >>> > /etc/libvirt/qemu. It has the following section having 'vda':
> >>> >
> >>> > ===========================
> >>> > <devices>
> >>> >     <emulator>/usr/bin/kvm</emulator>
> >>> >     <disk type='file' device='disk'>
> >>> >       <driver name='qemu' type='qcow2' cache='none'/>
> >>> >       <source
> >>> >
> >>> >
> file='/var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'/>
> >>> >       <target dev='vda' bus='virtio'/>
> >>> >       <address type='pci' domain='0x0000' bus='0x00' slot='0x04'
> >>> > function='0x0'/>
> >>> >     </disk>
> >>> > ....
> >>> > ===========================
> >>> > Can you specify what exactly I need to change ?
> >>> > Thanks,
> >>> > Nikhil
> >>> >
> >>> >
> >>> >
> >>> > On Tue, May 14, 2013 at 1:45 PM, Wangpan <hzwangpan@xxxxxxxxxxxxxxxx
> >
> >>> > wrote:
> >>> >>
> >>> >> seems like the roog disk is not a bootable device, you may need to
> >>> >> check
> >>> >> the vda/xvda device in libvirt XML config file is bootable or not.
> >>> >>
> >>> >> 2013-05-14
> >>> >> ________________________________
> >>> >> Wangpan
> >>> >> ________________________________
> >>> >> 发件人：Nikhil Mittal
> >>> >> 发送时间：2013-05-14 15:59
> >>> >> 主题：[Openstack] [OPENSTACK] VMs don't start on host machine reboot
> >>> >> (Grizzly
> >>> >> over Ubuntu 13.04)
> >>> >> 收件人："openstack"<openstack@xxxxxxxxxxxxxxxxxxx>
> >>> >> 抄送：
> >>> >>
> >>> >> Hello,
> >>> >> I recently installed Grizzly (single-node) on Ubuntu 13.04 on x86 64
> >>> >> bit
> >>> >> having two physical NICs. I posted about the networking issues that
> I
> >>> >> was
> >>> >> facing after the installation in an earlier post.
> >>> >> Well, while I was debugging the networking issue, I came across a
> more
> >>> >> serious issue -- my host machine got rebooted (power-cycle) and on
> >>> >> reboot I
> >>> >> see that my two VMs are shown in "shut-off" Status and "shut-down"
> >>> >> Power
> >>> >> state in the Dashboard GUI. The options available to me are only
> "soft
> >>> >> reboot", "hard reboot", "terminate instance", "Disassociate Floating
> >>> >> IP" and
> >>> >> "Edit Instance". I did first "soft reboot" and the console shows "No
> >>> >> bootable device". Then i tried "Hard reboot" and again the same
> >>> >> message "No
> >>> >> bootable device".
> >>> >> I checked that all services are running fine and there are no error
> >>> >> messages in the logs for nova, quantum, etc.
> >>> >>
> >>> >> I followed installation instructions based on the following link:
> >>> >>
> >>> >>
> >>> >>
> https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_SingleNode/OpenStack_Grizzly_Install_Guide.rst
> >>> >>
> >>> >> Thanks,
> >>> >> Nikhil
> >>> >>
> >>> >
> >>> >
> >>> > _______________________________________________
> >>> > Mailing list: https://launchpad.net/~openstack
> >>> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> >>> > Unsubscribe : https://launchpad.net/~openstack
> >>> > More help   : https://help.launchpad.net/ListHelp
> >>> >
> >>
> >>
> >
>