CEPH filesystem development
 help / color / mirror / Atom feed
From: Shinobu Kinjo <skinjo@redhat.com>
To: "B, Naga Venkata" <naga.b@hpe.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Errors attaching RBD image to a running VM
Date: Thu, 27 Aug 2015 09:17:03 -0400 (EDT)	[thread overview]
Message-ID: <1402664490.9438072.1440681423773.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <85E6A9CA58484A42B4C2F91092BC19870849AF3C@G4W3228.americas.hpqcorp.net>

O.k, I got you -;

> NO, debian 3.14.44-1-amd64, QEMU emulator version 2.3.0, openstack kilo, libvirt 1.2.9, ceph version 0.80.7

How about this?

> And please attach logs related to Ceph, qemu and livbirt.

Shinobu

----- Original Message -----
From: "B, Naga Venkata" <naga.b@hpe.com>
To: "Shinobu Kinjo" <skinjo@redhat.com>
Cc: "Ceph Development" <ceph-devel@vger.kernel.org>
Sent: Thursday, August 27, 2015 9:47:16 PM
Subject: RE: Errors attaching RBD image to a running VM

NO, debian 3.14.44-1-amd64, QEMU emulator version 2.3.0, openstack kilo, libvirt 1.2.9, ceph version 0.80.7

I am to attach volume to nova instance if instance is in shutoff state. For that following steps I did.

I restarted libvirtd and libvirt-guests, after libvirt-guests restart vm went to shutoff state but nova is not updated instance state still it is in running state, now I did volume attach it went fine.
If I restart nova-compute instance state is updated with shutoff state, if I try to start instance the below error I am facing.
 
libvirtError: internal error: process exited while connecting to monitor: 2015-08-27T11:16:02.726265Z qemu-system-x86_64: -drive file=rbd:volumes/volume-ee7f6e3d-8269-4ffc-8d62-a881a0d7116f:id=cinder:key=AQCfEdxVUP13MBAAv4Oj7twFIxaF1BXyY1PkRQ==:auth_supported=cephx\;none:mon_host=192.168.245.2\:6789\;192.168.245.3\:6789\;192.168.245.4\:6789,if=none,id=drive-virtio-disk1,format=raw,serial=ee7f6e3d-8269-4ffc-8d62-a881a0d7116f,cache=none: Unknown protocol 'rbd'

Still this error "Errors attaching RBD image to a running VM" is there.

Thanks & Regards,
Venkat
-----Original Message-----
From: Shinobu Kinjo [mailto:skinjo@redhat.com] 
Sent: Thursday, August 27, 2015 6:00 PM
To: B, Naga Venkata
Cc: Ceph Development
Subject: Re: Errors attaching RBD image to a running VM

Hello,

My question from first look at is that, is it your environment?

> Currently running SL 6.3, OpenStack Folsom packages from EPEL, Libvirt 
> 0.9.10, QEMU 1.2.1 built from an epel-testing SRPM for RBD support, 
> and Ceph 0.54

If it's true, you have to upgrade SL and Ceph as much as you can.
Because, as you might notice, there have been a bunch of bug fixes.

And please attach logs related to Ceph, qemu and livbirt.

Shinobu

----- Original Message -----
From: "B, Naga Venkata" <naga.b@hpe.com>
To: "Shinobu Kinjo" <skinjo@redhat.com>
Cc: "Ceph Development" <ceph-devel@vger.kernel.org>
Sent: Thursday, August 27, 2015 7:12:36 PM
Subject: RE: Errors attaching RBD image to a running VM

Hi Shinobu,

Can I have quick reply on this, is this issue with libvirt version or ceph.

Thanks & Regards,
Venkat

-----Original Message-----
From: Shinobu Kinjo [mailto:skinjo@redhat.com]
Sent: Wednesday, August 26, 2015 5:54 PM
To: B, Naga Venkata
Cc: Ceph Development
Subject: Re: Errors attaching RBD image to a running VM

Hello Venkat,

Thank you!!

 Shinobu

----- Original Message -----
From: "B, Naga Venkata" <naga.b@hpe.com>
To: skinjo@redhat.com
Cc: "Ceph Development" <ceph-devel@vger.kernel.org>
Sent: Wednesday, August 26, 2015 7:24:17 PM
Subject: RE: Errors attaching RBD image to a running VM

Hi Shinobu,

This is from http://comments.gmane.org/gmane.comp.file-systems.ceph.devel/11230.

Thanks & Regards,
Venkat


From: Shinobu [mailto:shinobu.kj@gmail.com]
Sent: Tuesday, August 25, 2015 5:35 PM
To: B, Naga Venkata
Cc: Ceph Development
Subject: Re: Errors attaching RBD image to a running VM

Where is original message?
Shinobu

On Tue, Aug 25, 2015 at 8:31 PM, venkat <naga.b@hp.com<mailto:naga.b@hp.com>> wrote:



same issue with libvirt version 1.2.9,
can somebody help me.

Thanks & Regards,
Venkat

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@vger.kernel.org<mailto:majordomo@vger.kernel.org>
More majordomo info at  http://vger.kernel.org/majordomo-info.html



--
Email:
 shinobu@linux.com<mailto:shinobu@linux.com>
 skinjo@redhat.com<mailto:skinjo@redhat.com>

 Life w/ Linux<http://i-shinobu.hatenablog.com/>

      reply	other threads:[~2015-08-27 13:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 21:22 Errors attaching RBD image to a running VM Michael Morgan
2012-12-07 22:50 ` Josh Durgin
2012-12-10 20:48   ` Michael Morgan
2012-12-10 21:12     ` Josh Durgin
2012-12-10 23:29       ` Michael Morgan
2015-08-25 11:31         ` venkat
2015-08-26 10:21           ` venkat
     [not found]           ` <CAFdRU73roiZmHu60ELVCFnV0M=WcPzk7Af1r1zSqiWSZE7yQEg@mail.gmail.com>
     [not found]             ` <85E6A9CA58484A42B4C2F91092BC19870849102F@G9W0733.americas.hpqcorp.net>
2015-08-26 12:23               ` Shinobu Kinjo
2015-08-27 10:12                 ` B, Naga Venkata
2015-08-27 12:30                   ` Shinobu Kinjo
2015-08-27 12:47                     ` B, Naga Venkata
2015-08-27 13:17                       ` Shinobu Kinjo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1402664490.9438072.1440681423773.JavaMail.zimbra@redhat.com \
    --to=skinjo@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=naga.b@hpe.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox