From: Gerry Reno <greno@verizon.net>
To: xen-devel@lists.xensource.com
Subject: Re: Xen 4 + 2.6.32.12: domU guest boots but shows 'close blk'
Date: Fri, 14 May 2010 18:09:02 -0400 [thread overview]
Message-ID: <4BEDC9FE.5090809@verizon.net> (raw)
In-Reply-To: <304904.10826.qm@web56105.mail.re3.yahoo.com>
[-- Attachment #1.1: Type: text/plain, Size: 1100 bytes --]
On 05/14/2010 02:36 PM, Boris Derzhavets wrote:
> Does this message appear in dmesg > log ?
>
> Boris.
>
> --- On *Thu, 5/13/10, Gerry Reno /<greno@verizon.net>/* wrote:
>
>
> From: Gerry Reno <greno@verizon.net>
> Subject: [Xen-devel] Xen 4 + 2.6.32.12: domU guest boots but shows
> 'close blk'
> To: xen-devel@lists.xensource.com
> Date: Thursday, May 13, 2010, 11:43 PM
>
> I have Lucid running using Xen 4.0.0-rc8 + pv_ops dom0 2.6.32.12
> on my host machine.
>
> When I boot a Lucid domU guest running 2.6.32-22-server kernel I
> see this message at boot:
> close blk: backend=/local/domain/0/backend/vbd/5/51712
> node=device/vbd/51712
>
> What is this telling me? And do I need to do something to fix it?
>
> -Gerry
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> </mc/compose?to=Xen-devel@lists.xensource.com>
> http://lists.xensource.com/xen-devel
>
>
>
No, it is not in dmesg. It appears on the console right ahead of the
login prompt.
-Gerry
[-- Attachment #1.2: Type: text/html, Size: 2495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-14 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 3:43 Xen 4 + 2.6.32.12: domU guest boots but shows 'close blk' Gerry Reno
2010-05-14 18:36 ` Boris Derzhavets
2010-05-14 22:09 ` Gerry Reno [this message]
2010-05-15 9:31 ` Nerijus Narmontas
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=4BEDC9FE.5090809@verizon.net \
--to=greno@verizon.net \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.