xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Fanny Dwargee <fdwargee6@gmail.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Stub domain crash on Xen v4.6.1
Date: Mon, 11 Apr 2016 12:06:38 +0100	[thread overview]
Message-ID: <20160411110638.GD1346@citrix.com> (raw)
In-Reply-To: <CAOz6fc_q+CGHCpqY+zWn4OdO4pNog-i4FFv2Y2m36dRs0h=wCw@mail.gmail.com>

On Thu, Apr 07, 2016 at 06:51:11PM +0200, Fanny Dwargee wrote:
> I'm sorry but this is my first attempt to use stubdom.
> 
> This is a test machine so feel free to propose xen recompilation adding
> printk's/obscured options or settings modification.
> 
> With regards,

Sorry for the late reply.

In the case successfully booting DomU, do you see similar error like
this in xl dmesg?

(d21) read error -1 on /local/domain/21/device/vbd/768 at offset 0, num bytes 512
(XEN) grant_table.c:525:d0v0 Bad flags (0) or dom (0). (expected dom 0)
(d21) read error -1 on /local/domain/21/device/vbd/768 at offset 0, num bytes 512
(XEN) grant_table.c:525:d0v0 Bad flags (0) or dom (0). (expected dom 0)

Another thing to try is to add to your config without
device_model_override=xxx,

  device_model_version="qemu-xen-traditional"

and see if it still works.

Here is why: the default device model is upstream qemu, but when you
need to use stubdom, the device model is another version of qemu
(qemu-trad). The newly added config option forces Xen to use the same
qemu that would be used when stubdom is in use. It's useful to figure
out if qemu-trad is not functioning.


Wei.

> 
> Fanny
> 
> 2016-04-07 18:13 GMT+02:00 Wei Liu <wei.liu2@citrix.com>:
> 
> > On Wed, Apr 06, 2016 at 02:49:19PM +0200, Fanny Dwargee wrote:
> > > Hi Wei,
> > >
> > > first: thanks for your effort. :)
> > >
> > > Find attached the 'xl create' output and the
> > > /var/log/xen/console/hypervisor.log
> > > files after creating the same domain without the
> > > 'device_model_stubdomain_override' configuration option.
> > >
> > > 'xl list' command output...
> > > Name                 ID   Mem VCPUs      State   Time(s)
> > > Domain-0              0  1023     2     r-----   11608.1
> > > win7-sp1-x64-2       28  2048     1     ------       0.4
> > >
> >
> > I was hoping that you somehow had a running setup with stubdom enabled.
> > Have you tried earlier version of Xen or is this your first attempt to
> > use stubdom?
> >
> > Wei.
> >
> > > Regards,
> > >
> > > Fanny
> > >
> > >
> > >
> > >
> > > 2016-04-06 13:12 GMT+02:00 Wei Liu <wei.liu2@citrix.com>:
> > >
> > > > On Tue, Apr 05, 2016 at 05:17:00PM +0200, Fanny Dwargee wrote:
> > > > > Hi,
> > > > >
> > > > > after adding the 'device_model_stubdomain_override = 1' to an
> > otherwise
> > > > > fine configuration the domain crashes on start.
> > > > >
> > > > > Xen is v4.6.1 compiled from source on Debian Jessie 64bits this way:
> > > > >
> > > > >    - ./configure --enable-stubdom --enable-githttp
> > > > >    - make dist-xen
> > > > >    - make dist-tools
> > > > >    - make dist-stubdom
> > > > >    - make install-xen
> > > > >    - make install-tools
> > > > >    - make install-stubdom
> > > > >
> > > > > As pointed out before the same configuration file without the '
> > > > > device_model_stubdomain_override' works flawlessly.
> > > > >
> > > > > This is the 'xl list' command output while the domain is starting:
> > > > >
> > > > > Name                    ID   Mem VCPUs      State   Time(s)
> > > > > Domain-0                 0  1022     2     r-----     318.3
> > > > > win7-sp1-x64-2          20  2048     1     r-----       5.5
> > > > > win7-sp1-x64-2-dm       21    44     1     r-----       6.0
> > > > >
> > > > >
> > > > > As you can see both domains are started (the stub and the original
> > > > domain)
> > > > >
> > > > > Find attached the domain configuration file, 'xl info' output, 'xl
> > > > create'
> > > > > output and the /var/log/xen/console/hypervisor.log file, notice the
> > grant
> > > > > table error on console-hypervisor.log
> > > > >
> > > > > I'd very grateful for any help finding the cause of this problem.
> > > > >
> > > >
> > > >
> > > > The hypervsior log show some error, but unfortunately it is not
> > > > immediately clear what went wrong.
> > > >
> > > > Do you have a working base line setup so that I can compare the
> > > > difference?
> > > >
> > > > Wei.
> > > >
> > > > > Best regards,
> > > > >
> > > > > Fanny
> > > >
> > > >
> >
> >
> >
> >

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-04-11 11:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 15:17 Stub domain crash on Xen v4.6.1 Fanny Dwargee
2016-04-06 11:12 ` Wei Liu
2016-04-06 12:49   ` Fanny Dwargee
2016-04-07 16:13     ` Wei Liu
2016-04-07 16:51       ` Fanny Dwargee
2016-04-11 11:06         ` Wei Liu [this message]
2016-04-12  8:36 ` Wei Liu
2016-04-12  9:44   ` Fanny Dwargee
2016-04-12  9:49     ` Wei Liu
2016-04-12  8:27 Fanny Dwargee

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=20160411110638.GD1346@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=fdwargee6@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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;
as well as URLs for NNTP newsgroup(s).