A new stable release of SeaBIOS (version 1.7.2.2) has been tagged. This release contains bug fixes.
The release is available via git: git clone git://git.seabios.org/seabios -b 1.7.2-stable
-Kevin
Asias He (2): virtio-scsi: Pack struct virtio_scsi_{req_cmd,resp_cmd} virtio-scsi: Set _DRIVER_OK flag before scsi target scanning
Kevin O'Connor (1): Cache boot-fail-wait to avoid romfile access after POST.
boot.c | 15 +++++++++------ virtio-scsi.c | 5 +++-- virtio-scsi.h | 4 ++-- 3 files changed, 14 insertions(+), 10 deletions(-)
27.05.2013 16:59, Kevin O'Connor wrote:
A new stable release of SeaBIOS (version 1.7.2.2) has been tagged. This release contains bug fixes.
The release is available via git: git clone git://git.seabios.org/seabios -b 1.7.2-stable
Just.. curious -- why there are no tarballs for the dotdot-point releases like this one? Not that it's hugely important to have the tarballs but... :)
Thanks,
/mjt
On Mon, May 27, 2013 at 05:11:46PM +0400, Michael Tokarev wrote:
27.05.2013 16:59, Kevin O'Connor wrote:
A new stable release of SeaBIOS (version 1.7.2.2) has been tagged. This release contains bug fixes.
The release is available via git: git clone git://git.seabios.org/seabios -b 1.7.2-stable
Just.. curious -- why there are no tarballs for the dotdot-point releases like this one? Not that it's hugely important to have the tarballs but... :)
I thought the stable releases would have a smaller audience, so didn't think it was needed.
I tried to push the tar file up to the server, but I am having a difficulty pushing files right now. Hopefully I'll get the 1.7.2.2 tar up in a few days.
-Kevin
于 2013-5-29 8:08, Kevin O'Connor 写道:
On Mon, May 27, 2013 at 05:11:46PM +0400, Michael Tokarev wrote:
27.05.2013 16:59, Kevin O'Connor wrote:
A new stable release of SeaBIOS (version 1.7.2.2) has been tagged. This release contains bug fixes.
The release is available via git: git clone git://git.seabios.org/seabios -b 1.7.2-stable
Just.. curious -- why there are no tarballs for the dotdot-point releases like this one? Not that it's hugely important to have the tarballs but... :)
I thought the stable releases would have a smaller audience, so didn't think it was needed.
I tried to push the tar file up to the server, but I am having a difficulty pushing files right now. Hopefully I'll get the 1.7.2.2 tar up in a few days.
-Kevin
Hi, Kevin I found my guest can't boot up in nested KVM env, while using old bios it succeed:
Kernel panic - not syncing: Attempted to kill init! ? panic ? do_exit ? fput ? do_group_exit ? sys_exit_group ? system_call_fastpath
* RH6.4(no cpu specifed, kernel 3.10, latest qemu, latest seabios) | RH6.4(CPU KVM-64, kernel 3.10) | Fedora18(kernel, kernel 3.8.11) | intel vmx
I simply supplied the parameter -bios to replace bios.bin in qemu command line, did I miss something?
于 2013-5-29 12:43, Wenchao Xia 写道:
于 2013-5-29 8:08, Kevin O'Connor 写道:
On Mon, May 27, 2013 at 05:11:46PM +0400, Michael Tokarev wrote:
27.05.2013 16:59, Kevin O'Connor wrote:
A new stable release of SeaBIOS (version 1.7.2.2) has been tagged. This release contains bug fixes.
The release is available via git: git clone git://git.seabios.org/seabios -b 1.7.2-stable
Just.. curious -- why there are no tarballs for the dotdot-point releases like this one? Not that it's hugely important to have the tarballs but... :)
I thought the stable releases would have a smaller audience, so didn't think it was needed.
I tried to push the tar file up to the server, but I am having a difficulty pushing files right now. Hopefully I'll get the 1.7.2.2 tar up in a few days.
-Kevin
Hi, Kevin I found my guest can't boot up in nested KVM env, while using old bios it succeed:
Kernel panic - not syncing: Attempted to kill init! ? panic ? do_exit ? fput ? do_group_exit ? sys_exit_group ? system_call_fastpath
RH6.4(no cpu specifed, kernel 3.10, latest qemu, latest seabios) | RH6.4(CPU KVM-64, kernel 3.10) | Fedora18(kernel, kernel 3.8.11) | intel vmx
I simply supplied the parameter -bios to replace bios.bin in qemu
command line, did I miss something?
It works normal after replacing bios.bin as README in a directory, pls ignore above mail, sorry for disturb.
On 05/29/13 02:08, Kevin O'Connor wrote:
On Mon, May 27, 2013 at 05:11:46PM +0400, Michael Tokarev wrote:
27.05.2013 16:59, Kevin O'Connor wrote:
A new stable release of SeaBIOS (version 1.7.2.2) has been tagged. This release contains bug fixes.
The release is available via git: git clone git://git.seabios.org/seabios -b 1.7.2-stable
Just.. curious -- why there are no tarballs for the dotdot-point releases like this one? Not that it's hugely important to have the tarballs but... :)
I thought the stable releases would have a smaller audience, so didn't think it was needed.
qemu upstream project doesn't need tarballs as it simply uses a git submodule.
distros usually compile seabios from source instead of using the prebuild binary included in the qemu tarball (for gpl compliance and other reasons). So having tarballs even for minor releases is useful.
While talking about releases: There are quite some changes accumulated in master, time to cut a new release I think. Given that sorting the acpi table issue seems to take more time than expected, how about freeze + call for patches _now_, release 1.7.3 some-when in June, then plan to merge the apci changes (however it works out) for 1.7.4?
cheers, Gerd
On Wed, May 29, 2013 at 09:27:16AM +0200, Gerd Hoffmann wrote:
While talking about releases: There are quite some changes accumulated in master, time to cut a new release I think. Given that sorting the acpi table issue seems to take more time than expected, how about freeze
- call for patches _now_, release 1.7.3 some-when in June, then plan to
merge the apci changes (however it works out) for 1.7.4?
Makes sense.
-Kevin
-
Gerd Hoffmann -
Kevin O'Connor -
Michael Tokarev -
Wenchao Xia