On Thu, 19 Mar 2015 10:50:49 +0100
"Michael S. Tsirkin" wrote:
> On Wed, Mar 11, 2015 at 04:35:41PM +1100, David Gibson wrote:
> > > > > So it boils down to the fact that windows thinks it's RAM,
> > > > It thinks it's PCI Standard RAM Controller not RAM itself.
> > > >
> > > > > so it binds a g
On 19/03/2015 11:50, Michael S. Tsirkin wrote:
On Wed, Mar 11, 2015 at 04:35:41PM +1100, David Gibson wrote:
So it boils down to the fact that windows thinks it's RAM,
It thinks it's PCI Standard RAM Controller not RAM itself.
so it binds a generic driver to it, but then we get
According to
On Wed, Mar 11, 2015 at 04:35:41PM +1100, David Gibson wrote:
> > > > So it boils down to the fact that windows thinks it's RAM,
> > > It thinks it's PCI Standard RAM Controller not RAM itself.
> > >
> > > > so it binds a generic driver to it, but then we get
> > > According to device manager no d
On Wed, 4 Mar 2015 20:12:31 +0100
"Michael S. Tsirkin" wrote:
> On Wed, Mar 04, 2015 at 05:33:42PM +0100, Igor Mammedov wrote:
> > On Wed, 4 Mar 2015 16:31:39 +0100
> > "Michael S. Tsirkin" wrote:
> >
> > > On Wed, Mar 04, 2015 at 04:14:44PM +0100, Igor Mammedov wrote:
> > > > On Wed, 4 Mar 201
On Wed, 4 Mar 2015 20:12:31 +0100
"Michael S. Tsirkin" wrote:
> On Wed, Mar 04, 2015 at 05:33:42PM +0100, Igor Mammedov wrote:
> > On Wed, 4 Mar 2015 16:31:39 +0100
> > "Michael S. Tsirkin" wrote:
> >
> > > On Wed, Mar 04, 2015 at 04:14:44PM +0100, Igor Mammedov wrote:
> > > > On Wed, 4 Mar 201
On Wed, Mar 04, 2015 at 05:33:42PM +0100, Igor Mammedov wrote:
> On Wed, 4 Mar 2015 16:31:39 +0100
> "Michael S. Tsirkin" wrote:
>
> > On Wed, Mar 04, 2015 at 04:14:44PM +0100, Igor Mammedov wrote:
> > > On Wed, 4 Mar 2015 14:49:00 +0100
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > On Wed, M
On Wed, 4 Mar 2015 16:31:39 +0100
"Michael S. Tsirkin" wrote:
> On Wed, Mar 04, 2015 at 04:14:44PM +0100, Igor Mammedov wrote:
> > On Wed, 4 Mar 2015 14:49:00 +0100
> > "Michael S. Tsirkin" wrote:
> >
> > > On Wed, Mar 04, 2015 at 02:12:32PM +0100, Igor Mammedov wrote:
> > > > On Wed, 4 Mar 201
On Wed, Mar 04, 2015 at 04:14:44PM +0100, Igor Mammedov wrote:
> On Wed, 4 Mar 2015 14:49:00 +0100
> "Michael S. Tsirkin" wrote:
>
> > On Wed, Mar 04, 2015 at 02:12:32PM +0100, Igor Mammedov wrote:
> > > On Wed, 4 Mar 2015 13:11:48 +0100
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > On Tue, M
On Wed, 4 Mar 2015 14:49:00 +0100
"Michael S. Tsirkin" wrote:
> On Wed, Mar 04, 2015 at 02:12:32PM +0100, Igor Mammedov wrote:
> > On Wed, 4 Mar 2015 13:11:48 +0100
> > "Michael S. Tsirkin" wrote:
> >
> > > On Tue, Mar 03, 2015 at 09:33:51PM +0100, Igor Mammedov wrote:
> > > > On Tue, 3 Mar 201
Am 04.03.2015 um 14:49 schrieb Michael S. Tsirkin:
> On Wed, Mar 04, 2015 at 02:12:32PM +0100, Igor Mammedov wrote:
>> On Wed, 4 Mar 2015 13:11:48 +0100
>> "Michael S. Tsirkin" wrote:
>>> On Tue, Mar 03, 2015 at 09:33:51PM +0100, Igor Mammedov wrote:
On Tue, 3 Mar 2015 18:35:39 +0100
"Mi
On Wed, Mar 04, 2015 at 02:12:32PM +0100, Igor Mammedov wrote:
> On Wed, 4 Mar 2015 13:11:48 +0100
> "Michael S. Tsirkin" wrote:
>
> > On Tue, Mar 03, 2015 at 09:33:51PM +0100, Igor Mammedov wrote:
> > > On Tue, 3 Mar 2015 18:35:39 +0100
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > On Tue, M
On Wed, 4 Mar 2015 13:11:48 +0100
"Michael S. Tsirkin" wrote:
> On Tue, Mar 03, 2015 at 09:33:51PM +0100, Igor Mammedov wrote:
> > On Tue, 3 Mar 2015 18:35:39 +0100
> > "Michael S. Tsirkin" wrote:
> >
> > > On Tue, Mar 03, 2015 at 05:18:14PM +0100, Igor Mammedov wrote:
> > > > Based on Microsof
On Tue, Mar 03, 2015 at 09:33:51PM +0100, Igor Mammedov wrote:
> On Tue, 3 Mar 2015 18:35:39 +0100
> "Michael S. Tsirkin" wrote:
>
> > On Tue, Mar 03, 2015 at 05:18:14PM +0100, Igor Mammedov wrote:
> > > Based on Microsoft's sepecifications (paper can be dowloaded from
> > > http://go.microsoft.c
On Tue, 3 Mar 2015 18:35:39 +0100
"Michael S. Tsirkin" wrote:
> On Tue, Mar 03, 2015 at 05:18:14PM +0100, Igor Mammedov wrote:
> > Based on Microsoft's sepecifications (paper can be dowloaded from
> > http://go.microsoft.com/fwlink/?LinkId=260709), add a device
> > description to the SSDT ACPI ta
On Tue, Mar 03, 2015 at 05:18:14PM +0100, Igor Mammedov wrote:
> Based on Microsoft's sepecifications (paper can be dowloaded from
> http://go.microsoft.com/fwlink/?LinkId=260709), add a device
> description to the SSDT ACPI table and its implementation.
>
> The GUID is set using "vmgenid.uuid" pr
Based on Microsoft's sepecifications (paper can be dowloaded from
http://go.microsoft.com/fwlink/?LinkId=260709), add a device
description to the SSDT ACPI table and its implementation.
The GUID is set using "vmgenid.uuid" property.
Example of using vmgenid device:
-device vmgenid,id=FOO,uuid="3
16 matches
Mail list logo