Re: [Qemu-devel] [PATCH 1/1 v2] Allow machines to configure the QEMU_VERSION that's exposed via hardware

2012-04-11 Thread Anthony Liguori
On 04/11/2012 02:14 AM, Peter Maydell wrote: On 11 April 2012 02:50, Anthony Liguori wrote: On 04/10/2012 04:24 PM, Peter Maydell wrote: This is still changing the version printed in a bunch of user facing usage and help messages. Please drop those. Why? Changing the help messages is not ne

Re: [Qemu-devel] [PATCH 1/1 v2] Allow machines to configure the QEMU_VERSION that's exposed via hardware

2012-04-11 Thread Peter Maydell
On 11 April 2012 02:50, Anthony Liguori wrote: > On 04/10/2012 04:24 PM, Peter Maydell wrote: >> This is still changing the version printed in a bunch of user >> facing usage and help messages. Please drop those. > > > Why? Changing the help messages is not necessary or useful.  We just need to >

Re: [Qemu-devel] [PATCH 1/1 v2] Allow machines to configure the QEMU_VERSION that's exposed via hardware

2012-04-10 Thread Anthony Liguori
On 04/10/2012 04:24 PM, Peter Maydell wrote: On 10 April 2012 21:16, Crístian Viana wrote: Based on the following conversation: http://mid.gmane.org/4f69f05b.5010...@codemonkey.ws Which reminds me - qemu sticks the release version in guest visible places like CPU version. This is wrong and c

Re: [Qemu-devel] [PATCH 1/1 v2] Allow machines to configure the QEMU_VERSION that's exposed via hardware

2012-04-10 Thread Peter Maydell
On 10 April 2012 21:16, Crístian Viana wrote: > Based on the following conversation: > > http://mid.gmane.org/4f69f05b.5010...@codemonkey.ws > >> Which reminds me - qemu sticks the release version in >> guest visible places like CPU version. >> This is wrong and causes windows guests to print mess

[Qemu-devel] [PATCH 1/1 v2] Allow machines to configure the QEMU_VERSION that's exposed via hardware

2012-04-10 Thread Crístian Viana
Based on the following conversation: http://mid.gmane.org/4f69f05b.5010...@codemonkey.ws > Which reminds me - qemu sticks the release version in > guest visible places like CPU version. > This is wrong and causes windows guests to print messages > about driver updates when you switch. > We should