From: Sarah Newman <srn@prgmr.com>
To: xen-devel@lists.xen.org
Subject: Re: Severe guest disk corruption with device_model_stubdomain_override=1...
Date: Wed, 23 Mar 2016 21:26:17 -0700 [thread overview]
Message-ID: <56F36C69.3070204@prgmr.com> (raw)
In-Reply-To: <56F30EBE.90407@prgmr.com>
On 03/23/2016 02:46 PM, Sarah Newman wrote:
> On 03/22/2016 11:03 PM, Sarah Newman wrote:
>> And nested xen.
>>
>> CPU: AMD Opteron 2352
>> Outer configuration: Xen4CentOS 6 xen 4.6.1-2.el6, linux 3.18.25-18.el6.x86_64
>> Inner configuration: Xen4CentOS 6 xen 4.6.1-2.el6, linux 3.18.25-19.el6.x86_64
>> Inner xen command line: cpuinfo loglvl=all guest_loglvl=error dom0_mem=512M,max:512M com1=115200,8n1 console=com1 dom0_max_vcpus=1 dom0_vcpus_pin=true
>> Inner linux command line: ro root=LABEL=DISK rootflags=barrier=0 swiotlb=32768 console=hvc0
>
>> xen_platform_pci seems to be ignored with device_model_stubdomain_override=1. So I don't think I can test what happens with the 3.18.25-19.el6.x86_64
>> kernel, no nested xen, and non-paravirtual block devices.
>
> The patch submitted in http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg03080.html appears to fix the issue.
FYI, I also had to run "ethtool -K <vifname>-emu tx off" or tcp did not work for intra-host communications (off-host worked OK.) I'm not sure if
that's a known issue or not.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-24 4:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 6:03 Severe guest disk corruption with device_model_stubdomain_override=1 Sarah Newman
2016-03-23 21:46 ` Sarah Newman
2016-03-24 4:26 ` Sarah Newman [this message]
2016-03-24 9:55 ` George Dunlap
2016-03-24 17:20 ` Sarah Newman
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=56F36C69.3070204@prgmr.com \
--to=srn@prgmr.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 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.