On Tue, Feb 16, 2016 at 02:36:49PM +0200, Marcel Apfelbaum wrote:
> >>2. PCI devices with no driver installed are not re-mapped. This can be OK
> >> from the Windows point of view because Resources Window does not show
> >> the MMIO range
> >> for this device.
> >>
> >> If the other (r
On Tue, Feb 16, 2016 at 02:51:25PM +0100, Igor Mammedov wrote:
> On Tue, 16 Feb 2016 14:36:49 +0200
> Marcel Apfelbaum wrote:
>
> > On 02/16/2016 02:17 PM, Igor Mammedov wrote:
> > > On Tue, 16 Feb 2016 12:05:33 +0200
> > > Marcel Apfelbaum wrote:
> > >
> > >> On 02/11/2016 06:30 PM, Michael S
On Tue, 16 Feb 2016 14:36:49 +0200
Marcel Apfelbaum wrote:
> On 02/16/2016 02:17 PM, Igor Mammedov wrote:
> > On Tue, 16 Feb 2016 12:05:33 +0200
> > Marcel Apfelbaum wrote:
> >
> >> On 02/11/2016 06:30 PM, Michael S. Tsirkin wrote:
> >>> On Thu, Feb 11, 2016 at 04:16:05PM +0100, Igor Mammedo
On 02/16/2016 02:17 PM, Igor Mammedov wrote:
On Tue, 16 Feb 2016 12:05:33 +0200
Marcel Apfelbaum wrote:
On 02/11/2016 06:30 PM, Michael S. Tsirkin wrote:
On Thu, Feb 11, 2016 at 04:16:05PM +0100, Igor Mammedov wrote:
On Tue, 9 Feb 2016 14:17:44 +0200
"Michael S. Tsirkin" wrote:
On Tue, Fe
On Tue, 16 Feb 2016 12:05:33 +0200
Marcel Apfelbaum wrote:
> On 02/11/2016 06:30 PM, Michael S. Tsirkin wrote:
> > On Thu, Feb 11, 2016 at 04:16:05PM +0100, Igor Mammedov wrote:
> >> On Tue, 9 Feb 2016 14:17:44 +0200
> >> "Michael S. Tsirkin" wrote:
> >>
> >>> On Tue, Feb 09, 2016 at 11:46:0
On 02/11/2016 06:30 PM, Michael S. Tsirkin wrote:
On Thu, Feb 11, 2016 at 04:16:05PM +0100, Igor Mammedov wrote:
On Tue, 9 Feb 2016 14:17:44 +0200
"Michael S. Tsirkin" wrote:
On Tue, Feb 09, 2016 at 11:46:08AM +0100, Igor Mammedov wrote:
So the linker interface solves this rather neatly:
bio
On Mon, 15 Feb 2016 13:26:29 +0200
"Michael S. Tsirkin" wrote:
> On Mon, Feb 15, 2016 at 11:30:24AM +0100, Igor Mammedov wrote:
> > On Thu, 11 Feb 2016 18:30:19 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Thu, Feb 11, 2016 at 04:16:05PM +0100, Igor Mammedov wrote:
> > > > On Tue, 9 F
On Mon, Feb 15, 2016 at 11:30:24AM +0100, Igor Mammedov wrote:
> On Thu, 11 Feb 2016 18:30:19 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Feb 11, 2016 at 04:16:05PM +0100, Igor Mammedov wrote:
> > > On Tue, 9 Feb 2016 14:17:44 +0200
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > On Tue
On Thu, 11 Feb 2016 18:30:19 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Feb 11, 2016 at 04:16:05PM +0100, Igor Mammedov wrote:
> > On Tue, 9 Feb 2016 14:17:44 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Tue, Feb 09, 2016 at 11:46:08AM +0100, Igor Mammedov wrote:
> > > > > So the lin
On Thu, Feb 11, 2016 at 07:34:52PM +0200, Marcel Apfelbaum wrote:
> On 02/11/2016 06:30 PM, Michael S. Tsirkin wrote:
> >On Thu, Feb 11, 2016 at 04:16:05PM +0100, Igor Mammedov wrote:
> >>On Tue, 9 Feb 2016 14:17:44 +0200
> >>"Michael S. Tsirkin" wrote:
> >>
> >>>On Tue, Feb 09, 2016 at 11:46:08AM
On 02/11/2016 06:30 PM, Michael S. Tsirkin wrote:
On Thu, Feb 11, 2016 at 04:16:05PM +0100, Igor Mammedov wrote:
On Tue, 9 Feb 2016 14:17:44 +0200
"Michael S. Tsirkin" wrote:
On Tue, Feb 09, 2016 at 11:46:08AM +0100, Igor Mammedov wrote:
So the linker interface solves this rather neatly:
bio
On Thu, Feb 11, 2016 at 04:16:05PM +0100, Igor Mammedov wrote:
> On Tue, 9 Feb 2016 14:17:44 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Tue, Feb 09, 2016 at 11:46:08AM +0100, Igor Mammedov wrote:
> > > > So the linker interface solves this rather neatly:
> > > > bios allocates memory, bios pass
On Tue, 9 Feb 2016 14:17:44 +0200
"Michael S. Tsirkin" wrote:
> On Tue, Feb 09, 2016 at 11:46:08AM +0100, Igor Mammedov wrote:
> > > So the linker interface solves this rather neatly:
> > > bios allocates memory, bios passes memory map to guest.
> > > Served us well for several years without need
On 02/10/16 10:28, Michael S. Tsirkin wrote:
> On Wed, Feb 10, 2016 at 10:51:47AM +0200, Michael S. Tsirkin wrote:
>> So maybe we should
>> leave this alone, wait until we see an actual user - this way we can
>> figure out the implementation constraints better.
>
> What I'm definitely interested i
On Wed, Feb 10, 2016 at 10:51:47AM +0200, Michael S. Tsirkin wrote:
> So maybe we should
> leave this alone, wait until we see an actual user - this way we can
> figure out the implementation constraints better.
What I'm definitely interested in seeing is improving the
bios_linker_loader API withi
On Tue, Feb 09, 2016 at 11:46:08AM +0100, Igor Mammedov wrote:
> > > > > 2. ACPI approach consumes guest usable RAM to allocate buffer
> > > > >and then makes device to DMA data in that RAM.
> > > > >That's a design point I don't agree with.
> > > >
> > > > Blame the broken VM GEN ID s
On Tue, Feb 09, 2016 at 11:46:08AM +0100, Igor Mammedov wrote:
> > So the linker interface solves this rather neatly:
> > bios allocates memory, bios passes memory map to guest.
> > Served us well for several years without need for extensions,
> > and it does solve the VM GEN ID problem, even thoug
On Tue, 2 Feb 2016 13:16:38 +0200
"Michael S. Tsirkin" wrote:
> On Tue, Feb 02, 2016 at 10:59:53AM +0100, Igor Mammedov wrote:
> > On Sun, 31 Jan 2016 18:22:13 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Fri, Jan 29, 2016 at 12:13:59PM +0100, Igor Mammedov wrote:
> > > > On Thu, 28 J
On Tue, Feb 02, 2016 at 10:59:53AM +0100, Igor Mammedov wrote:
> On Sun, 31 Jan 2016 18:22:13 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Fri, Jan 29, 2016 at 12:13:59PM +0100, Igor Mammedov wrote:
> > > On Thu, 28 Jan 2016 14:59:25 +0200
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > On Th
On Sun, 31 Jan 2016 18:22:13 +0200
"Michael S. Tsirkin" wrote:
> On Fri, Jan 29, 2016 at 12:13:59PM +0100, Igor Mammedov wrote:
> > On Thu, 28 Jan 2016 14:59:25 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Thu, Jan 28, 2016 at 01:03:16PM +0100, Igor Mammedov wrote:
> > > > On Thu, 28
On Fri, Jan 29, 2016 at 12:13:59PM +0100, Igor Mammedov wrote:
> On Thu, 28 Jan 2016 14:59:25 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Jan 28, 2016 at 01:03:16PM +0100, Igor Mammedov wrote:
> > > On Thu, 28 Jan 2016 13:13:04 +0200
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > On Th
On Thu, 28 Jan 2016 14:59:25 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Jan 28, 2016 at 01:03:16PM +0100, Igor Mammedov wrote:
> > On Thu, 28 Jan 2016 13:13:04 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Thu, Jan 28, 2016 at 11:54:25AM +0100, Igor Mammedov wrote:
> > > > Based on Mi
On 01/28/16 12:13, Michael S. Tsirkin wrote:
> On Thu, Jan 28, 2016 at 11:54:25AM +0100, Igor Mammedov wrote:
>> Based on Microsoft's specifications (paper can be
>> downloaded from http://go.microsoft.com/fwlink/?LinkId=260709,
>> easily found by "Virtual Machine Generation ID" keywords),
>> add a
On Thu, Jan 28, 2016 at 01:03:16PM +0100, Igor Mammedov wrote:
> On Thu, 28 Jan 2016 13:13:04 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Jan 28, 2016 at 11:54:25AM +0100, Igor Mammedov wrote:
> > > Based on Microsoft's specifications (paper can be
> > > downloaded from http://go.microsoft.
On Thu, 28 Jan 2016 13:13:04 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Jan 28, 2016 at 11:54:25AM +0100, Igor Mammedov wrote:
> > Based on Microsoft's specifications (paper can be
> > downloaded from http://go.microsoft.com/fwlink/?LinkId=260709,
> > easily found by "Virtual Machine Generation
On Thu, Jan 28, 2016 at 11:54:25AM +0100, Igor Mammedov wrote:
> Based on Microsoft's specifications (paper can be
> downloaded from http://go.microsoft.com/fwlink/?LinkId=260709,
> easily found by "Virtual Machine Generation ID" keywords),
> add a PCI device with corresponding description in
> SSD
Based on Microsoft's specifications (paper can be
downloaded from http://go.microsoft.com/fwlink/?LinkId=260709,
easily found by "Virtual Machine Generation ID" keywords),
add a PCI device with corresponding description in
SSDT ACPI table.
The GUID is set using "vmgenid.guid" property or
a corresp
27 matches
Mail list logo
