From: "Jan Beulich" <JBeulich@suse.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen-unstable 4.8: HVM domain_crash called from emulate.c:144 RIP: c000:[<000000000000336a>]
Date: Wed, 15 Jun 2016 08:07:18 -0600 [thread overview]
Message-ID: <57617D3602000078000F55CD@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1792258725.20160615155834@eikelenboom.it>
>>> On 15.06.16 at 15:58, <linux@eikelenboom.it> wrote:
> Wednesday, June 15, 2016, 2:48:55 PM, you wrote:
>> Apart from that, and just to see whether there are other differences
>> between your guest(s) and mine, could you post a guest config from
>> one that's affected?
>
> Hope you are not too disappointed it's rather sparse:
In no way.
> builder='hvm'
> device_model_version = 'qemu-xen'
> device_model_user = 'root'
> memory = 512
> name = 'test_guest'
> vcpus = 4
> cpu_weight = 768
> vif = [ 'bridge=xen_bridge, ip=192.168.1.15, mac=00:16:3E:C4:72:83,
> model=e1000' ]
> disk = [ 'phy:/dev/xen_vms/test_guest1,hda,w',
> 'phy:/dev/xen_vms/test_guest2,hdb,w' ]
> on_crash = 'preserve'
> boot='c'
> vnc=0
> serial='pty'
I wonder whether mine having
stdvga=0
matters. Albeit a quick test passing stdvga=1 works here. And I
don't think the vnc= setting should have an effect here.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-15 14:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 23:49 Xen-unstable 4.8: HVM domain_crash called from emulate.c:144 RIP: c000:[<000000000000336a>] linux
2016-06-15 8:29 ` Jan Beulich
2016-06-15 8:57 ` Sander Eikelenboom
2016-06-15 9:38 ` Sander Eikelenboom
2016-06-15 10:12 ` Jan Beulich
2016-06-15 12:00 ` Sander Eikelenboom
2016-06-15 12:48 ` Jan Beulich
2016-06-15 13:58 ` Sander Eikelenboom
2016-06-15 14:07 ` Jan Beulich [this message]
2016-06-15 14:20 ` Boris Ostrovsky
2016-06-15 14:32 ` Boris Ostrovsky
2016-06-15 14:39 ` Jan Beulich
2016-06-15 14:56 ` Boris Ostrovsky
2016-06-15 15:22 ` Jan Beulich
2016-06-15 15:29 ` Paul Durrant
2016-06-15 15:43 ` Jan Beulich
2016-06-15 15:46 ` Paul Durrant
2016-06-15 15:54 ` Jan Beulich
2016-06-15 16:46 ` Boris Ostrovsky
2016-06-16 8:03 ` Jan Beulich
2016-06-15 14:35 ` Jan Beulich
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=57617D3602000078000F55CD@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=linux@eikelenboom.it \
--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).