All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Eddie Dong <eddie.dong@intel.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/hvm: implement save/restore for posted interrupts
Date: Wed, 1 Oct 2014 22:13:02 +0200	[thread overview]
Message-ID: <20141001201302.GA30085@aepfle.de> (raw)
In-Reply-To: <542BD772020000780003B5ED@mail.emea.novell.com>

On Wed, Oct 01, Jan Beulich wrote:

> But I though it's not so much that you need a test system than
> you describing to Intel folks the precise conditions needed for
> reproduction.

Finally I got access to a system, perhaps I can use it for a while.

It has sles11sp3 installed. So I installed the latest kernel and xen
packages from sles11sp3, and used this domU.cfg:


name="sles11sp3_full_bug866902_nfsroot"
uuid="071cdcce-4c2c-48ba-b09a-6984ac91692b"
memory=512
vcpus=1
on_poweroff="destroy"
on_reboot="restart"
on_crash="coredump-destroy"
localtime=0
keymap="de"

builder="hvm"
device_model="/usr/lib/xen/bin/qemu-dm"
kernel="/usr/lib/xen/boot/hvmloader"
boot="d"
disk=[ 
        'file:/nfsmnt/bug866902/vdisk-sles11sp3_full_bug866902_nfsroot-disk0,hda,w',
        'file:/nfsmnt/iso/SLES-11-SP3-DVD-x86_64-GM-DVD1.iso,hdc:cdrom,r'
]
vif=[ 'bridge=br0,type=netfront,mac=00:16:3e:4e:7c:4b', ]
stdvga=0
vnc=1
vncunused=1
viridian=0
acpi=1
pae=1
apic=1

serial="pty"


Then these commands to boot the HVM guest into the provided iso image:

xm new ~/ohering/sles11sp3_full_bug866902_nfsroot.cfg
xm start sles11sp3_full_bug866902_nfsroot
xm vnc sles11sp3_full_bug866902_nfsroot &

 -> select "Rescue system"
 -> set cmdline to "netsetup=dhcp sysrq_always_enabled"
 -> RETURN
 -> wait until login prompt appears, login as root with no password
 -> run dmesg, its nearly empty

xm sysrq sles11sp3_full_bug866902_nfsroot s
 
 -> run dmesg, should show the sysrequest
 -> remember dmesg timestamp

xm save -f sles11sp3_full_bug866902_nfsroot /dev/shm/sles11sp3_full_bug866902_nfsroot.dump
xm restore /dev/shm/sles11sp3_full_bug866902_nfsroot.dump
xm sysrq sles11sp3_full_bug866902_nfsroot s
xm vnc sles11sp3_full_bug866902_nfsroot &

 -> run dmesg, there is suspend/resume output but just a single sysrequest
 -> expected are two sysrequest entries

xm destroy sles11sp3_full_bug866902_nfsroot


If I use openSUSE-13.1-DVD-x86_64.iso instead of the sles11sp3.iso the
guest is frozen, no cursor blinking, no input possible. Not sure why that happens.


Then I tried todays staging branch + v5 of my --prefix series:

insserv -r xendomains
insserv -r xencommons
rpm -Uvh xen-upstream.rpm
cp -avLt /boot --parents /opt/xen/staging-upstream/boot/xen.gz
vi /boot/grub/menu.lst
/opt/xen/staging-upstream/etc/init.d/xencommons start
/opt/xen/staging-upstream/sbin/xl -vvvv create -ddddd -V ~/ohering/sles11sp3_full_bug866902_nfsroot.cfg

 -> select "Rescue system"
 -> set cmdline to "netsetup=dhcp sysrq_always_enabled"
 -> RETURN
 -> wait until login prompt appears, login as root with no password
 -> run dmesg, its nearly empty

/opt/xen/staging-upstream/sbin/xl -vvvv sysrq sles11sp3_full_bug866902_nfsroot s

 -> run dmesg, should show the sysrequest
 -> remember dmesg timestamp

/opt/xen/staging-upstream/sbin/xl -vvvv save -f sles11sp3_full_bug866902_nfsroot /dev/shm/sles11sp3_full_bug866902_nfsroot.dump
/opt/xen/staging-upstream/sbin/xl -vvvv restore /dev/shm/sles11sp3_full_bug866902_nfsroot.dump
/opt/xen/staging-upstream/sbin/xl -vvvv sysrq sles11sp3_full_bug866902_nfsroot s
/opt/xen/staging-upstream/sbin/xl -vvvv vnc sles11sp3_full_bug866902_nfsroot &

 -> run dmesg, there is suspend/resume output but just a single sysrequest
 -> expected are two sysrequest entries

/opt/xen/staging-upstream/sbin/xl -vvvv destroy sles11sp3_full_bug866902_nfsroot


So this is my repro case. Hopefully this will work for folks at Intel.

Tomorrow I will try if any of the suggested patches will fix xen-upsteam.


One thing I'm not sure about is the firmware of such IvyBridge system.
The firmware of the system I can use for testing dumps alot to serial
during startup. Not sure if its EFI or not. At least it boots into
grub1, so I suspect it has a legacy BIOS. If an EFI system is used,
would that change anything? The initial report I got was appearently
also with legacy BIOS. Did Intel test with EFI by any chance?

What I have is some Intel Romley box with "Intel(R) Xeon(R) CPU E5-2697
v2 @ 2.70GHz", dmesg has:
<7>DMI: Intel Corporation S2600CP/S2600CP, BIOS RMLSDP.86I.R3.27.D685.1305151734 05/15/2013


Olaf

  reply	other threads:[~2014-10-01 20:13 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 15:09 [PATCH] x86/hvm: implement save/restore for posted interrupts Olaf Hering
2014-07-03 15:27 ` Jan Beulich
2014-07-09 11:24 ` Zhang, Yang Z
2014-07-09 21:14   ` Tian, Kevin
2014-07-16 14:28     ` Olaf Hering
2014-07-16 16:11       ` Tian, Kevin
2014-07-17  7:11         ` Olaf Hering
2014-07-17  9:29           ` Zhang, Yang Z
2014-07-18 13:58             ` Olaf Hering
2014-07-22 23:06               ` Zhang, Yang Z
2014-07-23  8:03                 ` Olaf Hering
2014-07-25 21:38             ` Tian, Kevin
2014-07-28  6:52               ` Olaf Hering
2014-07-29  7:48                 ` Zhang, Yang Z
2014-07-29  8:27                   ` Jan Beulich
2014-08-02 10:59                   ` Olaf Hering
2014-08-04  1:08                     ` Zhang, Yang Z
2014-08-04  7:50                       ` Olaf Hering
2014-08-04  7:57                         ` Zhang, Yang Z
2014-08-05 10:32                           ` Olaf Hering
2014-08-08  0:18                             ` Zhang, Yang Z
2014-09-01  6:44                             ` Zhang, Yang Z
2014-09-18  3:29                             ` Zhang, Yang Z
2014-09-19 13:32                               ` Olaf Hering
2014-09-19 13:39                                 ` Jan Beulich
2014-09-19 17:51                                   ` Andrew Cooper
2014-09-22 22:43                                     ` Tian, Kevin
2014-09-24 16:26                                       ` Malcolm Crossley
2014-09-30 16:19                                 ` Jan Beulich
2014-10-01  8:07                                   ` Olaf Hering
2014-10-01  8:29                                     ` Jan Beulich
2014-10-01 20:13                                       ` Olaf Hering [this message]
2014-10-02  6:51                                         ` Jan Beulich
2014-10-02  8:10                                           ` Andrew Cooper
2014-10-02  8:20                                             ` Olaf Hering
2014-10-08  7:37                                         ` Zhang, Yang Z
2014-10-08  7:40                                           ` Olaf Hering
2014-10-08  7:55                                             ` Zhang, Yang Z
2014-10-08  8:28                                           ` Olaf Hering
2014-10-08  8:35                                             ` Zhang, Yang Z
2014-10-08  8:54                                               ` Olaf Hering
2014-10-09  7:24                                                 ` Zhang, Yang Z
2014-10-09  8:41                                                   ` Fabio Fantoni
2014-10-09  8:43                                                     ` Zhang, Yang Z
2014-10-09 12:49                                                       ` Fabio Fantoni
2014-10-09 11:35                                                   ` Malcolm Crossley
2014-10-09 13:19                                                   ` Andrew Cooper
2014-10-10  0:48                                                     ` Zhang, Yang Z
2014-10-09 13:31                                                   ` Olaf Hering
2014-10-09 14:11                                                     ` Olaf Hering
2014-10-10  0:52                                                       ` Zhang, Yang Z
2014-07-25  9:40 ` Jan Beulich
2014-07-25 12:49   ` Tian, Kevin
2014-07-25 13:59     ` Jan Beulich
2014-07-25 21:31       ` Tian, Kevin
2014-07-28  6:46         ` Jan Beulich
2014-07-28  7:52           ` Wu, Feng
2014-07-28  8:17           ` Zhang, Yang Z
2014-07-28  9:02             ` Jan Beulich
2014-07-28  9:50               ` Liuqiming (John)

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=20141001201302.GA30085@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=JBeulich@suse.com \
    --cc=eddie.dong@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yang.z.zhang@intel.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.