From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Artur Baruchi <mail.baruchi@gmail.com>
Cc: Xen-devel@lists.xensource.com,
xen-users <Xen-users@lists.xensource.com>,
"Fajar A. Nugraha" <list@fajar.net>
Subject: Re: VM Hanging after reboot
Date: Thu, 1 Dec 2011 10:21:54 -0400 [thread overview]
Message-ID: <20111201142154.GA336@andromeda.dapyr.net> (raw)
In-Reply-To: <CAAiDW_SRBf2jx_q=CysoQq8c=JDM6gXSfnpBvOi-z6=wSCmaDg@mail.gmail.com>
On Thu, Dec 01, 2011 at 08:41:20AM -0200, Artur Baruchi wrote:
> Hi.
>
> The error is within the guest (HVM virtual machine).
>
OK, then ata messages.. point to it being the HVM driver - so no
usage of the PV drivers. Unless there is a switch-over happening where
the guest tells QEMU: "Hey, I am done with the HVM driver, please
disconnect it" and it switches the PV driver on.
Just to remove that possiblity, did you boot the guest with
'xen_emul_unplug=never' ?
Hmm, and the comment about "went away after I used vanilla 3.1.0"
is rather strange. Did you also switch the hypervisor and the tools?
Or did youkeep on using the ones provided by the distro?
Either way, happy to see that the vanilla 3.1 kernel fixes the issue.
> Thanks.
>
> Att.
> Artur Baruchi
>
>
>
> On Thu, Dec 1, 2011 at 1:28 AM, Fajar A. Nugraha <list@fajar.net> wrote:
> > On Thu, Dec 1, 2011 at 10:16 AM, Konrad Rzeszutek Wilk
> > <konrad@darnok.org> wrote:
> >> On Wed, Nov 30, 2011 at 09:09:58PM -0200, Artur Baruchi wrote:
> >>> Hi Konrad.
> >>>
> >>> That was my first though (disk going bad). But I create another VM in
> >>> a different host and faced the same error. I tried to create another
> >>
> >> So is the error from within the guest or from the dom0?
> >>
> >
> > As Konrad asked, is the error in dom0 or domU?
> >
> > If dom0, then most likely it's disk problem. One way to diagnose it is
> > by reading from the disk (dd_rescue is nice) and see if at least it's
> > able to read the disk completely.
> >
> > If domU, then it's probably a bug in dom0 kernel (the blkback driver,
> > perhaps). In which case novell guys might be able to help you more. I
> > recall something like this when using older kernel for dom0 (forgot
> > the exact version, sorry), but the error went away after I used
> > vanilla 3.1.0 for dom0 kernel.
> >
> > --
> > Fajar
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-12-01 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 13:48 VM Hanging after reboot Artur Baruchi
2011-11-30 18:46 ` Artur Baruchi
2011-11-30 22:15 ` Konrad Rzeszutek Wilk
2011-11-30 23:09 ` Artur Baruchi
2011-12-01 3:16 ` Konrad Rzeszutek Wilk
2011-12-01 3:28 ` Fajar A. Nugraha
2011-12-01 10:41 ` Artur Baruchi
2011-12-01 14:21 ` Konrad Rzeszutek Wilk [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=20111201142154.GA336@andromeda.dapyr.net \
--to=konrad@darnok.org \
--cc=Xen-devel@lists.xensource.com \
--cc=Xen-users@lists.xensource.com \
--cc=list@fajar.net \
--cc=mail.baruchi@gmail.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.