qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yaniv Kaul <ykaul@redhat.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: kevin@koconnor.net, qemu-devel@nongnu.org,
	Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH][SEABIOS] Make SMBIOS table pass MS SVVP test
Date: Sun, 22 Nov 2009 21:58:33 +0200	[thread overview]
Message-ID: <4B0997E9.4040505@redhat.com> (raw)
In-Reply-To: <38AF5F086DB24529A1D605A0E2414FD0@FSCPC>

On 11/22/2009 7:39 PM, Sebastian Herbszt wrote:


<SNIP>
>>>
>>> >/* Type 16 -- Physical Memory Array */
>>> >@@ -239,7 +240,7 @@ smbios_init_type_16(void *start, u32 
>>> memory_size_mb, int nr_mem_devs)
>>> >
>>> >    p->location = 0x01; /* other */
>>> >    p->use = 0x03; /* system memory */
>>> >-    p->error_correction = 0x01; /* other */
>>> >+    p->error_correction = 0x06; /* Multi-bit ECC to make Microsoft 
>>> happy */
>>> >    p->maximum_capacity = memory_size_mb * 1024;
>>> >    p->memory_error_information_handle = 0xfffe; /* none provided */
>>> >    p->number_of_memory_devices = nr_mem_devs;
>>>
>>> Does it happen to work with "Unknown" or "None"?
>>>
>> No. They explicitly request single or multi-bit ECC. Though I was told
>> that Microsoft gives exception for this requirement.
>
> Odd. Why do they care whether the VM reports (non existent) error 
> correction support.


The test probably does not realize it's a VM and SVVP runs the 2008R2 
system tests - which requires ECC memory (and PCI express bus for 
network and block devices, but that's another exception).
Y.

>
>> -- 
>> Gleb.
>
> - Sebastian
>
>
>

  parent reply	other threads:[~2009-11-22 19:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 14:08 [Qemu-devel] [PATCH][SEABIOS] Make SMBIOS table pass MS SVVP test Gleb Natapov
2009-11-22 16:51 ` [Qemu-devel] " Sebastian Herbszt
2009-11-22 17:21   ` Gleb Natapov
2009-11-22 17:39     ` Sebastian Herbszt
2009-11-22 19:51       ` Gleb Natapov
2009-11-22 20:41         ` Sebastian Herbszt
2009-11-23  7:28           ` Gleb Natapov
2009-11-23 18:15             ` Sebastian Herbszt
2009-11-23 18:30               ` Gleb Natapov
2009-11-23 18:48                 ` Sebastian Herbszt
2009-11-23 19:39                   ` Gleb Natapov
2009-11-24  8:18                     ` Gleb Natapov
2009-11-24 15:57                 ` Kevin O'Connor
2009-11-24 16:59                   ` Gleb Natapov
2009-11-24 17:53                     ` Kevin O'Connor
2009-11-24 18:41                       ` Gleb Natapov
2009-11-24 20:30                         ` Kevin O'Connor
2009-11-25 20:09                     ` Sebastian Herbszt
2009-11-26  7:39                       ` Gleb Natapov
2009-11-26 21:38                         ` Sebastian Herbszt
2009-11-22 19:58       ` Yaniv Kaul [this message]
2009-11-22 23:57       ` Carl-Daniel Hailfinger
2009-11-23  6:28         ` Gleb Natapov
2009-11-23 18:02           ` Sebastian Herbszt
2009-11-23 11:56       ` Gleb Natapov
2009-11-22 17:07 ` Kevin O'Connor
2009-11-23 11:08   ` Gleb Natapov
2009-11-24 14:40     ` Kevin O'Connor

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=4B0997E9.4040505@redhat.com \
    --to=ykaul@redhat.com \
    --cc=gleb@redhat.com \
    --cc=herbszt@gmx.de \
    --cc=kevin@koconnor.net \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).