Comment # 8 on bug 957547 from Takashi Iwai

Thanks.  I tested the latest TW with KVM here, too, and S4 works there.  So S4
isn't broken generally, at least.

Just to be sure: you tested with "systemctl hibernate" command?

Also, boot 4.3 kernel with no_console_suspend option, go to Linux console
(VT1), and run "systemctl hibernate" there.  Does it show writing the image?

If a hibernation image has been really written, you can inspect it by booting a
recovery DVD or USB.  Then you can copy the swap partition via dd command.  At
least, you can copy some first bytes to see whether it has a S4 signature the
kernel checks.