Am 05.04.2016 um 11:19 hat Richard W.M. Jones geschrieben:
> > > OK so this reminds me of the second problem. How to detect what
> > > bioses are available, given a qemu binary. It would be nice if qemu
> > > had an option like:
> > >
> > > qemu -bios \?
>
> I didn't really think this one
> > OK so this reminds me of the second problem. How to detect what
> > bioses are available, given a qemu binary. It would be nice if qemu
> > had an option like:
> >
> > qemu -bios \?
I didn't really think this one through. The extra time taken (in the
link loader) to run the above query
Am 05.04.2016 um 10:04 hat Richard W.M. Jones geschrieben:
> On Tue, Apr 05, 2016 at 06:38:36AM +0200, Kevin Wolf wrote:
> > Am 01.04.2016 um 13:20 hat Richard W.M. Jones geschrieben:
> > >
> > > My patch, plus the configuration and comments from your patch,
> > > combined. Plus I tested it with
On Tue, Apr 05, 2016 at 06:38:36AM +0200, Kevin Wolf wrote:
> Am 01.04.2016 um 13:20 hat Richard W.M. Jones geschrieben:
> >
> > My patch, plus the configuration and comments from your patch,
> > combined. Plus I tested it with libguestfs boot-analysis and it works
> > and is still fast.
> >
>
Am 01.04.2016 um 13:20 hat Richard W.M. Jones geschrieben:
>
> My patch, plus the configuration and comments from your patch,
> combined. Plus I tested it with libguestfs boot-analysis and it works
> and is still fast.
>
> Integrating this so it happens automatically when the user adds
>
On Fri, Apr 01, 2016 at 06:25:24PM -0400, Kevin O'Connor wrote:
> I'm getting different results. When you have time we should probably
> track down the discrepancy. Some of the difference is likely due to
> different hardware (I'm using kvm on an old AMD machine) and some is
> likely due to
On 01/04/2016 22:05, Kevin O'Connor wrote:
>
> I looked closer at your setup and it appears the SeaBIOS virtio-scsi
> driver is very slow because it does a full search of all 256 possible
> scsi targets. This full scan takes a lot of time. I put together a
> quick patch (see below) to stop
On Fri, Apr 01, 2016 at 09:46:05PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2016 at 04:05:46PM -0400, Kevin O'Connor wrote:
> > On Fri, Apr 01, 2016 at 07:41:31PM +0100, Richard W.M. Jones wrote:
> > > On Fri, Apr 01, 2016 at 11:35:40AM -0400, Kevin O'Connor wrote:
> > > > > +# general
On Fri, Apr 01, 2016 at 04:05:46PM -0400, Kevin O'Connor wrote:
> On Fri, Apr 01, 2016 at 07:41:31PM +0100, Richard W.M. Jones wrote:
> > On Fri, Apr 01, 2016 at 11:35:40AM -0400, Kevin O'Connor wrote:
> > > > +# general stuff
> > > > +CONFIG_QEMU=y
> > > > +CONFIG_ROM_SIZE=128
> > >
> > > Why
On Fri, Apr 01, 2016 at 03:44:14PM -0400, Kevin O'Connor wrote:
[...]
I ran all the tests again, but this time I ran the test program 3
times (so 30 passes for each setting). As you can see from the
results below the test is not very stable, so that could easily have
accounted for the variation
On Fri, Apr 01, 2016 at 07:41:31PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2016 at 11:35:40AM -0400, Kevin O'Connor wrote:
> > > +# general stuff
> > > +CONFIG_QEMU=y
> > > +CONFIG_ROM_SIZE=128
> >
> > Why force a size of 128K - I would think 64K would be fine.
>
> Agreed. Setting
On Fri, Apr 01, 2016 at 08:15:29PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2016 at 08:10:48PM +0100, Richard W.M. Jones wrote:
> > On Fri, Apr 01, 2016 at 03:04:15PM -0400, Kevin O'Connor wrote:
> > > Otherwise, it doesn't make
> > > sense that disabling CONFIG_BOOTORDER=n would change
On Fri, Apr 01, 2016 at 08:10:48PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2016 at 03:04:15PM -0400, Kevin O'Connor wrote:
> > Otherwise, it doesn't make
> > sense that disabling CONFIG_BOOTORDER=n would change the boot time.
>
> Could it be explained by it avoiding slow access to qemu
On Fri, Apr 01, 2016 at 03:04:15PM -0400, Kevin O'Connor wrote:
> On Fri, Apr 01, 2016 at 07:59:02PM +0100, Richard W.M. Jones wrote:
> > On Fri, Apr 01, 2016 at 07:41:31PM +0100, Richard W.M. Jones wrote:
> > > Below are some benchmarks of the other things you mentioned. These
> > > are complete
On Fri, Apr 01, 2016 at 07:59:02PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2016 at 07:41:31PM +0100, Richard W.M. Jones wrote:
> > Below are some benchmarks of the other things you mentioned. These
> > are complete appliance boot-to-shutdown times [*not* just SeaBIOS].
> > All
On Fri, Apr 01, 2016 at 07:41:31PM +0100, Richard W.M. Jones wrote:
> Below are some benchmarks of the other things you mentioned. These
> are complete appliance boot-to-shutdown times [*not* just SeaBIOS].
> All debugging has been disabled, and I'm using a slightly different
> kernel version, so
On Fri, Apr 01, 2016 at 11:35:40AM -0400, Kevin O'Connor wrote:
> > +# general stuff
> > +CONFIG_QEMU=y
> > +CONFIG_ROM_SIZE=128
>
> Why force a size of 128K - I would think 64K would be fine.
Agreed. Setting this to =0 seems the best thing, and it does fit fine
inside 64K.
> > +# no input, no
On 01/04/2016 17:35, Kevin O'Connor wrote:
> It's possible to build a third binary, but that seems like it would be
> a bit annoying for distributions.
I don't think that would be a problem. Fedora is already building 4
binaries (128k, 256k, CSM, coreboot), adding a fifth is not a big deal.
On Fri, Apr 01, 2016 at 12:49:47PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2016 at 01:32:51PM +0200, Gerd Hoffmann wrote:
> > > I think we were working on the same thing ... Attached is my
> > > version.
> > >
> > > Note that you must enable at least CONFIG_MPTABLE else virtio-scsi
>
On Fri, Apr 01, 2016 at 04:06:23PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2016 at 10:58:19AM -0400, Kevin O'Connor wrote:
> > On Fri, Apr 01, 2016 at 09:44:56AM +0100, Richard W.M. Jones wrote:
> > > On Fri, Apr 01, 2016 at 10:24:37AM +0200, Paolo Bonzini wrote:
> > > > On 01/04/2016
On Fri, Apr 01, 2016 at 01:07:55PM +0200, Gerd Hoffmann wrote:
> On Fr, 2016-04-01 at 11:17 +0100, Richard W.M. Jones wrote:
> > On Fri, Apr 01, 2016 at 11:18:30AM +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > I wonder how we can make use of this in qemu and downstream distros?
> > > >
On Fri, Apr 01, 2016 at 10:58:19AM -0400, Kevin O'Connor wrote:
> On Fri, Apr 01, 2016 at 09:44:56AM +0100, Richard W.M. Jones wrote:
> > On Fri, Apr 01, 2016 at 10:24:37AM +0200, Paolo Bonzini wrote:
> > > On 01/04/2016 10:14, Richard W.M. Jones wrote:
> > > > Found it: only CONFIG_MPTABLE=y was
On Fri, Apr 01, 2016 at 09:44:56AM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2016 at 10:24:37AM +0200, Paolo Bonzini wrote:
> > On 01/04/2016 10:14, Richard W.M. Jones wrote:
> > > Found it: only CONFIG_MPTABLE=y was necessary. It boots with:
> > >
> > > # CONFIG_PIRTABLE is not set
> >
On Fri, Apr 01, 2016 at 01:32:51PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > I think we were working on the same thing ... Attached is my
> > version.
> >
> > Note that you must enable at least CONFIG_MPTABLE else virtio-scsi
> > does not work in the guest. I also enabled ACPI & SMBIOS &
Hi,
> I think we were working on the same thing ... Attached is my
> version.
>
> Note that you must enable at least CONFIG_MPTABLE else virtio-scsi
> does not work in the guest. I also enabled ACPI & SMBIOS & PIRTABLE.
They are enabled by default, no need to explicitly say so ;)
cheers,
On Fri, Apr 01, 2016 at 01:21:38PM +0200, Paolo Bonzini wrote:
>
>
> On 01/04/2016 13:20, Richard W.M. Jones wrote:
> > +# MPTABLE is required by Linux kernel, the others add only a
> > +# couple of milliseconds so we might as well have them
> > +CONFIG_PIRTABLE=y
> > +CONFIG_MPTABLE=y
> >
On 01/04/2016 13:20, Richard W.M. Jones wrote:
> +# MPTABLE is required by Linux kernel, the others add only a
> +# couple of milliseconds so we might as well have them
> +CONFIG_PIRTABLE=y
> +CONFIG_MPTABLE=y
> +CONFIG_SMBIOS=y
> +CONFIG_ACPI=y
> +
MPTABLE is only required is you don't have
My patch, plus the configuration and comments from your patch,
combined. Plus I tested it with libguestfs boot-analysis and it works
and is still fast.
Integrating this so it happens automatically when the user adds
-kernel on x86 seems quite complicated. The only way I could do it
was by
On Fri, Apr 01, 2016 at 01:07:55PM +0200, Gerd Hoffmann wrote:
> On Fr, 2016-04-01 at 11:17 +0100, Richard W.M. Jones wrote:
> > On Fri, Apr 01, 2016 at 11:18:30AM +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > I wonder how we can make use of this in qemu and downstream distros?
> > > >
On Fr, 2016-04-01 at 11:17 +0100, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2016 at 11:18:30AM +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > > I wonder how we can make use of this in qemu and downstream distros?
> > > Can we have a bios-min.bin which is used with -kernel boots?
> >
> > We
On Fri, Apr 01, 2016 at 11:18:30AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > I wonder how we can make use of this in qemu and downstream distros?
> > Can we have a bios-min.bin which is used with -kernel boots?
>
> We already build two seabios roms: one full featued and one slightly
> stripped
Hi,
> I wonder how we can make use of this in qemu and downstream distros?
> Can we have a bios-min.bin which is used with -kernel boots?
We already build two seabios roms: one full featued and one slightly
stripped down to keep it below 128k, for backward compatibility with old
machine types.
* Richard W.M. Jones (rjo...@redhat.com) wrote:
> On Fri, Apr 01, 2016 at 10:24:37AM +0200, Paolo Bonzini wrote:
> > On 01/04/2016 10:14, Richard W.M. Jones wrote:
> > > Found it: only CONFIG_MPTABLE=y was necessary. It boots with:
> > >
> > > # CONFIG_PIRTABLE is not set
> > > CONFIG_MPTABLE=y
On 01/04/2016 10:57, Richard W.M. Jones wrote:
> That's the qemu option? Currently we use
> -nodefconfig -nodefaults -display none
> which I assumed would do the same thing (ie. not add any default
> devices). Does -vga none do more than this?
No, I missed the -nodefaults.
Paolo
On Fri, Apr 01, 2016 at 10:51:31AM +0200, Paolo Bonzini wrote:
>
>
> On 01/04/2016 10:47, Richard W.M. Jones wrote:
> > It's so we can handle error reports. When someone reports that
> > libguestfs "hangs", it's sometimes useful to know if the BIOS was
> > entered or not, since it points the
On 01/04/2016 10:47, Richard W.M. Jones wrote:
> It's so we can handle error reports. When someone reports that
> libguestfs "hangs", it's sometimes useful to know if the BIOS was
> entered or not, since it points the finger at either qemu, BIOS or
> kernel. (Remember we have to be able to run
2016-04-01 11:47 GMT+03:00 Paolo Bonzini :
> That's an interesting idea. We can look at it for 2.7.
That's fine =) I'm waiting too.
--
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
On 01/04/2016 10:44, Richard W.M. Jones wrote:
> On Fri, Apr 01, 2016 at 10:24:37AM +0200, Paolo Bonzini wrote:
>> On 01/04/2016 10:14, Richard W.M. Jones wrote:
>>> Found it: only CONFIG_MPTABLE=y was necessary. It boots with:
>>>
>>> # CONFIG_PIRTABLE is not set
>>> CONFIG_MPTABLE=y
>>> #
On Fri, Apr 01, 2016 at 10:03:10AM +0200, Paolo Bonzini wrote:
>
>
> On 01/04/2016 09:55, Richard W.M. Jones wrote:
> >>> > > I'd dearly love to get rid of the sgabios option ROM. It looks like
> >>> > > SeaBIOS nearly supports a full serial console now?
> >> >
> >> > Last I checked, one could
On Fri, Apr 01, 2016 at 10:24:37AM +0200, Paolo Bonzini wrote:
> On 01/04/2016 10:14, Richard W.M. Jones wrote:
> > Found it: only CONFIG_MPTABLE=y was necessary. It boots with:
> >
> > # CONFIG_PIRTABLE is not set
> > CONFIG_MPTABLE=y
> > # CONFIG_SMBIOS is not set
> > # CONFIG_ACPI is not set
On 01/04/2016 10:14, Richard W.M. Jones wrote:
>> > At least ACPI (I would also add mptable and SMBIOS).
> Found it: only CONFIG_MPTABLE=y was necessary. It boots with:
>
> # CONFIG_PIRTABLE is not set
> CONFIG_MPTABLE=y
> # CONFIG_SMBIOS is not set
> # CONFIG_ACPI is not set
If you add all
Minimal SeaBIOS (+ CONFIG_MPTABLE):
http://oirase.annexia.org/tmp/min-seabios.txt
Stock SeaBIOS from qemu:
http://oirase.annexia.org/tmp/stock-seabios.txt
Both files best viewed with `less -r'.
It does appear to considerably reduce SeaBIOS time.
Rich.
--
Richard Jones, Virtualization Group,
On Fri, Apr 01, 2016 at 10:11:46AM +0200, Paolo Bonzini wrote:
>
>
> On 01/04/2016 10:02, Richard W.M. Jones wrote:
> >> > echo -e
> >> >
On 01/04/2016 10:02, Richard W.M. Jones wrote:
>> > echo -e
>> > 'CONFIG_USB=n\nCONFIG_DRIVES=n\nCONFIG_KEYBOARD=n\nCONFIG_MOUSE=n\nCONFIG_WRITABLE_UPPERMEMORY=y\nCONFIG_TCGBIOS=n\nCONFIG_PIRTABLE=n\nCONFIG_MPTABLE=n\nCONFIG_SMBIOS=n\nCONFIG_ACPI=n\nCONFIG_DEBUG_LEVEL=0'
>> > > .config
>> >
On 01/04/2016 09:55, Richard W.M. Jones wrote:
>>> > > I'd dearly love to get rid of the sgabios option ROM. It looks like
>>> > > SeaBIOS nearly supports a full serial console now?
>> >
>> > Last I checked, one could disable the option rom by adding "-device
>> > VGA,romfile=" to the qemu
On Thu, Mar 31, 2016 at 06:44:32PM -0400, Kevin O'Connor wrote:
> I think you'll find that if you compile out some features from
> SeaBIOS, it will be of a similar speed to that "minimal BIOS". Try
> this:
>
> cd /path/to/seabios/
> echo -e
>
On Thu, Mar 31, 2016 at 06:44:32PM -0400, Kevin O'Connor wrote:
> On Thu, Mar 31, 2016 at 11:17:30PM +0100, Richard W.M. Jones wrote:
> > I'd dearly love to get rid of the sgabios option ROM. It looks like
> > SeaBIOS nearly supports a full serial console now?
>
> Last I checked, one could
On Thu, Mar 31, 2016 at 11:17:30PM +0100, Richard W.M. Jones wrote:
> On Thu, Mar 31, 2016 at 12:22:23PM -0400, Kevin O'Connor wrote:
> > On Thu, Mar 31, 2016 at 10:21:25AM +0100, Stefan Hajnoczi wrote:
> > > On Sat, Mar 19, 2016 at 08:31:24PM +, Richard W.M. Jones wrote:
> > > > Is there
[This time without the massive attachment]
On Thu, Mar 31, 2016 at 12:22:23PM -0400, Kevin O'Connor wrote:
> On Thu, Mar 31, 2016 at 10:21:25AM +0100, Stefan Hajnoczi wrote:
> > On Sat, Mar 19, 2016 at 08:31:24PM +, Richard W.M. Jones wrote:
> > > Is there something I'm missing, or for Linux
On Thu, Mar 31, 2016 at 10:21:25AM +0100, Stefan Hajnoczi wrote:
> On Sat, Mar 19, 2016 at 08:31:24PM +, Richard W.M. Jones wrote:
> > Is there something I'm missing, or for Linux + -kernel could we use a
> > much simpler BIOS?
>
> The data that Marc Mari collected when comparing qboot with
On Sat, Mar 19, 2016 at 08:31:24PM +, Richard W.M. Jones wrote:
> Is there something I'm missing, or for Linux + -kernel could we use a
> much simpler BIOS?
The data that Marc Mari collected when comparing qboot with an optimized
SeaBIOS/QEMU showed that there's no need for a separate
Hi,
> > And the bulk of that is loading the kernel from fw_cfg.
>
> Yes after further investigation that is correct. It looks like
> fw_cfg has grown a DMA interface, but it's not used on x86.
>
> There is still a considerable amount of SeaBIOS overhead. In
> particular, it scans the whole
On Mon, Mar 21, 2016 at 08:58:27AM +0100, Gerd Hoffmann wrote:
> On Sa, 2016-03-19 at 20:31 +, Richard W.M. Jones wrote:
> > I've been analyzing the libguestfs appliance[1] boot time. See
> > attached file, especially the end of it.
> >
> > About 50% of the boot time is because of SeaBIOS.
>
On Sa, 2016-03-19 at 20:31 +, Richard W.M. Jones wrote:
> I've been analyzing the libguestfs appliance[1] boot time. See
> attached file, especially the end of it.
>
> About 50% of the boot time is because of SeaBIOS.
And the bulk of that is loading the kernel from fw_cfg.
> I'm using the
I've been analyzing the libguestfs appliance[1] boot time. See
attached file, especially the end of it.
About 50% of the boot time is because of SeaBIOS.
I'm using the qemu -kernel option. I understand that the kernel needs
some BIOS features, eg. video stuff, E820. But kvmtool comes with a
55 matches
Mail list logo