Hi,
> I don't mind the allocation of guest memory issue, the fact that guest
> memory is consumed by built-in devices is exactly what happens on bare
> metal.
And following in qemu what happens on bare metal usually works best
long-term.
> to pre-populate it, we could. It at least puts QEMU i
On Mon, Feb 15, 2016 at 02:50:41PM -0500, Kevin O'Connor wrote:
> On Mon, Feb 15, 2016 at 09:29:26PM +0200, Michael S. Tsirkin wrote:
> > I can build a generic interface to pass addresses
> > allocated by bios back to QEMU. It looks like this would
> > be useful for other purposes as well. Interes
On Mon, 15 Feb 2016 21:29:26 +0200
"Michael S. Tsirkin" wrote:
> On Mon, Feb 15, 2016 at 12:20:23PM -0700, Alex Williamson wrote:
> > On Mon, 15 Feb 2016 10:54:51 +0100
> > Igor Mammedov wrote:
> >
> > > On Sat, 13 Feb 2016 18:03:31 -0700
> > > Alex Williamson wrote:
> > >
> > > > On Sat,
On Mon, Feb 15, 2016 at 09:29:26PM +0200, Michael S. Tsirkin wrote:
> I can build a generic interface to pass addresses
> allocated by bios back to QEMU. It looks like this would
> be useful for other purposes as well. Interested?
If this is undertaken, I suggest extending fw_cfg to support "writ
On Mon, Feb 15, 2016 at 12:20:23PM -0700, Alex Williamson wrote:
> On Mon, 15 Feb 2016 10:54:51 +0100
> Igor Mammedov wrote:
>
> > On Sat, 13 Feb 2016 18:03:31 -0700
> > Alex Williamson wrote:
> >
> > > On Sat, 13 Feb 2016 19:20:32 -0500
> > > "Kevin O'Connor" wrote:
> > >
> > > > On Sat, F
On Mon, 15 Feb 2016 10:54:51 +0100
Igor Mammedov wrote:
> On Sat, 13 Feb 2016 18:03:31 -0700
> Alex Williamson wrote:
>
> > On Sat, 13 Feb 2016 19:20:32 -0500
> > "Kevin O'Connor" wrote:
> >
> > > On Sat, Feb 13, 2016 at 01:57:09PM -0700, Alex Williamson wrote:
> > > > On Sat, 13 Feb 20
On Mon, 15 Feb 2016 11:31:41 +0100
Gerd Hoffmann wrote:
> Hi,
>
> > The issue is in the VM and it occurs every time the option ROM is
> > executed. Standard VGA text mode displays fine (ex. SeaBIOS version
> > string and boot menu), but any sort of extended graphics mode (ex. live
> > CD boot
On Sat, Feb 13, 2016 at 06:03:31PM -0700, Alex Williamson wrote:
> On Sat, 13 Feb 2016 19:20:32 -0500
> "Kevin O'Connor" wrote:
> > This confuses me - why didn't the host system BIOS turn on the LCD
> > panel during host bootup?
>
> It turns off when we reset the device between VM instances or be
Hi,
> The issue is in the VM and it occurs every time the option ROM is
> executed. Standard VGA text mode displays fine (ex. SeaBIOS version
> string and boot menu), but any sort of extended graphics mode (ex. live
> CD boot menu) tries to make use of the host memory area which
> corresponds t
On Sat, 13 Feb 2016 18:03:31 -0700
Alex Williamson wrote:
> On Sat, 13 Feb 2016 19:20:32 -0500
> "Kevin O'Connor" wrote:
>
> > On Sat, Feb 13, 2016 at 01:57:09PM -0700, Alex Williamson wrote:
> > > On Sat, 13 Feb 2016 15:05:09 -0500
> > > "Kevin O'Connor" wrote:
> > > > On Sat, Feb 13, 2
On Sat, 13 Feb 2016 19:20:32 -0500
"Kevin O'Connor" wrote:
> On Sat, Feb 13, 2016 at 01:57:09PM -0700, Alex Williamson wrote:
> > On Sat, 13 Feb 2016 15:05:09 -0500
> > "Kevin O'Connor" wrote:
> > > On Sat, Feb 13, 2016 at 11:51:51AM -0700, Alex Williamson wrote:
> > > > On Sat, 13 Feb 2016
On Sat, Feb 13, 2016 at 01:57:09PM -0700, Alex Williamson wrote:
> On Sat, 13 Feb 2016 15:05:09 -0500
> "Kevin O'Connor" wrote:
> > On Sat, Feb 13, 2016 at 11:51:51AM -0700, Alex Williamson wrote:
> > > On Sat, 13 Feb 2016 13:18:39 -0500
> > > "Kevin O'Connor" wrote:
> > > > On Sat, Feb 13, 201
On Sat, 13 Feb 2016 15:05:09 -0500
"Kevin O'Connor" wrote:
> On Sat, Feb 13, 2016 at 11:51:51AM -0700, Alex Williamson wrote:
> > On Sat, 13 Feb 2016 13:18:39 -0500
> > "Kevin O'Connor" wrote:
> > > On Sat, Feb 13, 2016 at 08:12:09AM -0700, Alex Williamson wrote:
> > > > On Fri, 12 Feb 2016
On Sat, Feb 13, 2016 at 11:51:51AM -0700, Alex Williamson wrote:
> On Sat, 13 Feb 2016 13:18:39 -0500
> "Kevin O'Connor" wrote:
> > On Sat, Feb 13, 2016 at 08:12:09AM -0700, Alex Williamson wrote:
> > > On Fri, 12 Feb 2016 21:49:04 -0500
> > > "Kevin O'Connor" wrote:
> > > > On Fri, Feb 12, 201
On Sat, 13 Feb 2016 13:18:39 -0500
"Kevin O'Connor" wrote:
> On Sat, Feb 13, 2016 at 08:12:09AM -0700, Alex Williamson wrote:
> > On Fri, 12 Feb 2016 21:49:04 -0500
> > "Kevin O'Connor" wrote:
> > > On Fri, Feb 12, 2016 at 05:23:18PM -0700, Alex Williamson wrote:
> > > > Intel IGD makes use
On Sat, Feb 13, 2016 at 08:12:09AM -0700, Alex Williamson wrote:
> On Fri, 12 Feb 2016 21:49:04 -0500
> "Kevin O'Connor" wrote:
> > On Fri, Feb 12, 2016 at 05:23:18PM -0700, Alex Williamson wrote:
> > > Intel IGD makes use of memory allocated and marked reserved by the
> > > BIOS as a stolen memor
Hi Kevin,
On Fri, 12 Feb 2016 21:49:04 -0500
"Kevin O'Connor" wrote:
> On Fri, Feb 12, 2016 at 05:23:18PM -0700, Alex Williamson wrote:
> > Intel IGD makes use of memory allocated and marked reserved by the
> > BIOS as a stolen memory range. For the most part, guest drivers don't
> > make use o
On Fri, Feb 12, 2016 at 05:23:18PM -0700, Alex Williamson wrote:
> Intel IGD makes use of memory allocated and marked reserved by the
> BIOS as a stolen memory range. For the most part, guest drivers don't
> make use of this, but our achilles heel is the vBIOS. The vBIOS
> programs the device to
Intel IGD makes use of memory allocated and marked reserved by the
BIOS as a stolen memory range. For the most part, guest drivers don't
make use of this, but our achilles heel is the vBIOS. The vBIOS
programs the device to use the host stolen memory range and it's used
in the pre-boot environmen
19 matches
Mail list logo
