From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36595) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aR4Ao-000767-4Q for qemu-devel@nongnu.org; Wed, 03 Feb 2016 15:37:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aR4Aj-0006PE-Ak for qemu-devel@nongnu.org; Wed, 03 Feb 2016 15:37:10 -0500 Received: from mx1.redhat.com ([209.132.183.28]:37375) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aR4Aj-0006P2-5J for qemu-devel@nongnu.org; Wed, 03 Feb 2016 15:37:05 -0500 Date: Wed, 3 Feb 2016 20:37:02 +0000 From: "Richard W.M. Jones" Message-ID: <20160203203702.GL1766@redhat.com> References: <1453126333-19474-1-git-send-email-lersek@redhat.com> <56A90CEE.4020100@redhat.com> <56B24C26.8070501@redhat.com> <56B24ED0.8050304@msgid.tls.msk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56B24ED0.8050304@msgid.tls.msk.ru> Subject: Re: [Qemu-devel] [PATCH v2 0/4] set the OEM fields in the RSDT and the FADT from the SLIC List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Tokarev Cc: Aleksei Kovura , Xiao Guangrong , Steven Newbury , "Michael S. Tsirkin" , qemu-devel@nongnu.org, Paolo Bonzini , Shannon Zhao , Igor Mammedov , Laszlo Ersek On Wed, Feb 03, 2016 at 10:02:40PM +0300, Michael Tokarev wrote: > 03.02.2016 21:51, Laszlo Ersek wrote: > > Ping #2. > > I think I asked this before, but somehow I don't see anyone > answered. Is this thing worth to have now, when windows7 is > 2 releases away, everyone is moving to windows8 or 10 rapidly, > and these OSes don't benefit from this patch due to different > activation scheme and different licensing terms? > > Is it useful for anything but win7 (or 2008) ? > > It was definitely useful when I dealt with this issue back > when win7 come out, at that time it received no interest. > Now, I think, it is of very limited/questionable use... Given the limitation that I cannot reproduce this, if it's a real problem then it's certainly something we would need for virt-p2v. The aim of virt-p2v is to virtualize existing Windows hosts, for VDI, to extend the life of hardware, or just generally to get the usual benefits of virtualization. Enterprises often don't want to upgrade Windows frequently, and Windows 7 is supported by Microsoft until 2020-01-14 -- another 4 years. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/