qemu-kvm: Inconsistent vgabios reference

qemu-kvm: Inconsistent vgabios reference

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 250 bytes --]

Hi all,

the vgabios hash qemu-kvm points to does not exist in the referenced
repository. I was trying to find out the status of qemu-kvm's bios
binaries and relevance of what is in the kvm/ folder. Looks like this is
"a bit" messy...

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: qemu-kvm: Inconsistent vgabios reference

[Avi Kivity]

On 01/15/2012 01:14 PM, Jan Kiszka wrote:
> Hi all,
>
> the vgabios hash qemu-kvm points to does not exist in the referenced
> repository. I was trying to find out the status of qemu-kvm's bios
> binaries and relevance of what is in the kvm/ folder. Looks like this is
> "a bit" messy...

I have 19ea12c230ded95 for that hash, and pushing it tells me everything
is up to date.  What hash do you see?




-- 
error compiling committee.c: too many arguments to function

Re: qemu-kvm: Inconsistent vgabios reference

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

On 2012-01-15 13:33, Avi Kivity wrote:
> On 01/15/2012 01:14 PM, Jan Kiszka wrote:
>> Hi all,
>>
>> the vgabios hash qemu-kvm points to does not exist in the referenced
>> repository. I was trying to find out the status of qemu-kvm's bios
>> binaries and relevance of what is in the kvm/ folder. Looks like this is
>> "a bit" messy...
> 
> I have 19ea12c230ded95 for that hash, and pushing it tells me everything
> is up to date.  What hash do you see?

qemu-kvm master points to ca056d8e77a534f4f90548bc8cee166a378c1454,
after f6f8864b9b3ae1ea151c2b781792a5e72baaa178 I think.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: qemu-kvm: Inconsistent vgabios reference

[Avi Kivity]

On 01/15/2012 02:39 PM, Jan Kiszka wrote:
> On 2012-01-15 13:33, Avi Kivity wrote:
> > On 01/15/2012 01:14 PM, Jan Kiszka wrote:
> >> Hi all,
> >>
> >> the vgabios hash qemu-kvm points to does not exist in the referenced
> >> repository. I was trying to find out the status of qemu-kvm's bios
> >> binaries and relevance of what is in the kvm/ folder. Looks like this is
> >> "a bit" messy...
> > 
> > I have 19ea12c230ded95 for that hash, and pushing it tells me everything
> > is up to date.  What hash do you see?
>
> qemu-kvm master points to ca056d8e77a534f4f90548bc8cee166a378c1454,
> after f6f8864b9b3ae1ea151c2b781792a5e72baaa178 I think.
>

Ah, yes, I was behind.  Somehow 'git submodule update' found the new
commit from me, and it's pushed now.  Please try again after waiting for
git.kernel.org to catch up.

-- 
error compiling committee.c: too many arguments to function

Re: qemu-kvm: Inconsistent vgabios reference

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

On 2012-01-15 13:42, Avi Kivity wrote:
> On 01/15/2012 02:39 PM, Jan Kiszka wrote:
>> On 2012-01-15 13:33, Avi Kivity wrote:
>>> On 01/15/2012 01:14 PM, Jan Kiszka wrote:
>>>> Hi all,
>>>>
>>>> the vgabios hash qemu-kvm points to does not exist in the referenced
>>>> repository. I was trying to find out the status of qemu-kvm's bios
>>>> binaries and relevance of what is in the kvm/ folder. Looks like this is
>>>> "a bit" messy...
>>>
>>> I have 19ea12c230ded95 for that hash, and pushing it tells me everything
>>> is up to date.  What hash do you see?
>>
>> qemu-kvm master points to ca056d8e77a534f4f90548bc8cee166a378c1454,
>> after f6f8864b9b3ae1ea151c2b781792a5e72baaa178 I think.
>>
> 
> Ah, yes, I was behind.  Somehow 'git submodule update' found the new
> commit from me, and it's pushed now.  Please try again after waiting for
> git.kernel.org to catch up.

OK, thanks.

As that repos is now the vgabios reference, nothing valuable can be lost
when we drop the kvm/ folder, right?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: qemu-kvm: Inconsistent vgabios reference

[Avi Kivity]

On 01/15/2012 02:44 PM, Jan Kiszka wrote:
> OK, thanks.
>
> As that repos is now the vgabios reference, nothing valuable can be lost
> when we drop the kvm/ folder, right?
>

I guess so.

What about extboot w/ -M pc-0.foo?  I guess we'll boot with a newer
seabios in any case, but we probably will have boot order issues.  Maybe
we should make boot=on talk to the boot order code.

-- 
error compiling committee.c: too many arguments to function

Re: qemu-kvm: Inconsistent vgabios reference

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 530 bytes --]

On 2012-01-15 13:49, Avi Kivity wrote:
> On 01/15/2012 02:44 PM, Jan Kiszka wrote:
>> OK, thanks.
>>
>> As that repos is now the vgabios reference, nothing valuable can be lost
>> when we drop the kvm/ folder, right?
>>
> 
> I guess so.
> 
> What about extboot w/ -M pc-0.foo?  I guess we'll boot with a newer
> seabios in any case, but we probably will have boot order issues.  Maybe
> we should make boot=on talk to the boot order code.

extboot is history since 2a06024dc1b1e27b1be0266379af397e61b4a9ad

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: qemu-kvm: Inconsistent vgabios reference

[Avi Kivity]

On 01/15/2012 02:50 PM, Jan Kiszka wrote:
> On 2012-01-15 13:49, Avi Kivity wrote:
> > On 01/15/2012 02:44 PM, Jan Kiszka wrote:
> >> OK, thanks.
> >>
> >> As that repos is now the vgabios reference, nothing valuable can be lost
> >> when we drop the kvm/ folder, right?
> >>
> > 
> > I guess so.
> > 
> > What about extboot w/ -M pc-0.foo?  I guess we'll boot with a newer
> > seabios in any case, but we probably will have boot order issues.  Maybe
> > we should make boot=on talk to the boot order code.
>
> extboot is history since 2a06024dc1b1e27b1be0266379af397e61b4a9ad
>

Yeah, but it isn't history for people running older qemu-kvm's.  We
don't need extboot itself, but we do need to keep the boot option (as
2a06 does).  The question is do we need to preserve its meaning too
(with the seabios implementation instead of extboot's).

-- 
error compiling committee.c: too many arguments to function

Re: qemu-kvm: Inconsistent vgabios reference

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

On 2012-01-15 13:53, Avi Kivity wrote:
> On 01/15/2012 02:50 PM, Jan Kiszka wrote:
>> On 2012-01-15 13:49, Avi Kivity wrote:
>>> On 01/15/2012 02:44 PM, Jan Kiszka wrote:
>>>> OK, thanks.
>>>>
>>>> As that repos is now the vgabios reference, nothing valuable can be lost
>>>> when we drop the kvm/ folder, right?
>>>>
>>>
>>> I guess so.
>>>
>>> What about extboot w/ -M pc-0.foo?  I guess we'll boot with a newer
>>> seabios in any case, but we probably will have boot order issues.  Maybe
>>> we should make boot=on talk to the boot order code.
>>
>> extboot is history since 2a06024dc1b1e27b1be0266379af397e61b4a9ad
>>
> 
> Yeah, but it isn't history for people running older qemu-kvm's.  We
> don't need extboot itself, but we do need to keep the boot option (as
> 2a06 does).  The question is do we need to preserve its meaning too
> (with the seabios implementation instead of extboot's).

Possibly. But that is unrelated to any of the historic bits in kvm/.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: qemu-kvm: Inconsistent vgabios reference

[Avi Kivity]

On 01/15/2012 02:55 PM, Jan Kiszka wrote:
> > Yeah, but it isn't history for people running older qemu-kvm's.  We
> > don't need extboot itself, but we do need to keep the boot option (as
> > 2a06 does).  The question is do we need to preserve its meaning too
> > (with the seabios implementation instead of extboot's).
>
> Possibly. But that is unrelated to any of the historic bits in kvm/.

Right.

-- 
error compiling committee.c: too many arguments to function

Re: qemu-kvm: Inconsistent vgabios reference

[Michael Tokarev]

On 15.01.2012 16:53, Avi Kivity wrote:
> On 01/15/2012 02:50 PM, Jan Kiszka wrote:
[]
>> extboot is history since 2a06024dc1b1e27b1be0266379af397e61b4a9ad
> 
> Yeah, but it isn't history for people running older qemu-kvm's.  We
> don't need extboot itself, but we do need to keep the boot option (as
> 2a06 does).  The question is do we need to preserve its meaning too
> (with the seabios implementation instead of extboot's).

FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because
of lack of boot support from scsi (and no alternative), and because
many people's scripts who used boot= broke.  I thought it is better
to let users to have a chance to perform a smoother transition than
to break their stuff.

Now, I've a question: what seabios implementation of extboot we're
talking about?  -option-rom which is impossible to select as a first
boot device?

Thanks,

/mjt

Re: qemu-kvm: Inconsistent vgabios reference

[Avi Kivity]

On 01/15/2012 03:10 PM, Michael Tokarev wrote:
> On 15.01.2012 16:53, Avi Kivity wrote:
> > On 01/15/2012 02:50 PM, Jan Kiszka wrote:
> []
> >> extboot is history since 2a06024dc1b1e27b1be0266379af397e61b4a9ad
> > 
> > Yeah, but it isn't history for people running older qemu-kvm's.  We
> > don't need extboot itself, but we do need to keep the boot option (as
> > 2a06 does).  The question is do we need to preserve its meaning too
> > (with the seabios implementation instead of extboot's).
>
> FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because
> of lack of boot support from scsi (and no alternative), and because
> many people's scripts who used boot= broke.  I thought it is better
> to let users to have a chance to perform a smoother transition than
> to break their stuff.

It's really sad that people have to use lsi scsi.  Luckily qemu 1.1 will
feature virtio-scsi, though of course that doesn't help already
installed guests or non Windows/Linux guests.  Do you know what the use
cases requiring scsi boot are?

> Now, I've a question: what seabios implementation of extboot we're
> talking about?  -option-rom which is impossible to select as a first
> boot device?

seabios has native support for booting from virtio-blk, and will
natively support virtio-scsi as well.

-- 
error compiling committee.c: too many arguments to function

Re: qemu-kvm: Inconsistent vgabios reference

[Michael Tokarev]

On 15.01.2012 17:18, Avi Kivity wrote:
> On 01/15/2012 03:10 PM, Michael Tokarev wrote:
[]
>> FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because
>> of lack of boot support from scsi (and no alternative), and because
>> many people's scripts who used boot= broke.  I thought it is better
>> to let users to have a chance to perform a smoother transition than
>> to break their stuff.
> 
> It's really sad that people have to use lsi scsi.  Luckily qemu 1.1 will
> feature virtio-scsi, though of course that doesn't help already
> installed guests or non Windows/Linux guests.  Do you know what the use
> cases requiring scsi boot are?

I've one (not very pleasant) bugreport handy, http://bugs.debian.org/652447
and a few private messages asking me for ways to restore booting from scsi,
all talking about older/custom systems which worked for years in kvm.
As you can see in the bugreport mentioned, I know that scsi is broken
and should not be used and so on, and suggested switching from it on
every chance.

>> Now, I've a question: what seabios implementation of extboot we're
>> talking about?  -option-rom which is impossible to select as a first
>> boot device?
> 
> seabios has native support for booting from virtio-blk, and will
> natively support virtio-scsi as well.

Ah.  Well, I thought especially about lsi emulated scsi.  I wasn't
able to boot from it even with their bios -- once there's at least
one other bootable device present (including the NIC) it refuses
to boot from lsi emulated scsi drive.

Thanks,

/mjt

Re: qemu-kvm: Inconsistent vgabios reference

[Gleb Natapov]

On Sun, Jan 15, 2012 at 05:27:39PM +0400, Michael Tokarev wrote:
> On 15.01.2012 17:18, Avi Kivity wrote:
> > On 01/15/2012 03:10 PM, Michael Tokarev wrote:
> []
> >> FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because
> >> of lack of boot support from scsi (and no alternative), and because
> >> many people's scripts who used boot= broke.  I thought it is better
> >> to let users to have a chance to perform a smoother transition than
> >> to break their stuff.
> > 
> > It's really sad that people have to use lsi scsi.  Luckily qemu 1.1 will
> > feature virtio-scsi, though of course that doesn't help already
> > installed guests or non Windows/Linux guests.  Do you know what the use
> > cases requiring scsi boot are?
> 
> I've one (not very pleasant) bugreport handy, http://bugs.debian.org/652447
> and a few private messages asking me for ways to restore booting from scsi,
> all talking about older/custom systems which worked for years in kvm.
> As you can see in the bugreport mentioned, I know that scsi is broken
> and should not be used and so on, and suggested switching from it on
> every chance.
> 
> >> Now, I've a question: what seabios implementation of extboot we're
> >> talking about?  -option-rom which is impossible to select as a first
> >> boot device?
> > 
> > seabios has native support for booting from virtio-blk, and will
> > natively support virtio-scsi as well.
> 
> Ah.  Well, I thought especially about lsi emulated scsi.  I wasn't
> able to boot from it even with their bios -- once there's at least
> one other bootable device present (including the NIC) it refuses
> to boot from lsi emulated scsi drive.
> 
Kevin is going to include a patch to Seabios to fix that. Meanwhile
you can use bootindex to specify boot order.

--
			Gleb.

Re: qemu-kvm: Inconsistent vgabios reference

[Avi Kivity]

On 01/15/2012 03:27 PM, Michael Tokarev wrote:
> On 15.01.2012 17:18, Avi Kivity wrote:
> > On 01/15/2012 03:10 PM, Michael Tokarev wrote:
> []
> >> FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because
> >> of lack of boot support from scsi (and no alternative), and because
> >> many people's scripts who used boot= broke.  I thought it is better
> >> to let users to have a chance to perform a smoother transition than
> >> to break their stuff.
> > 
> > It's really sad that people have to use lsi scsi.  Luckily qemu 1.1 will
> > feature virtio-scsi, though of course that doesn't help already
> > installed guests or non Windows/Linux guests.  Do you know what the use
> > cases requiring scsi boot are?
>
> I've one (not very pleasant) bugreport handy, http://bugs.debian.org/652447
> and a few private messages asking me for ways to restore booting from scsi,
> all talking about older/custom systems which worked for years in kvm.
> As you can see in the bugreport mentioned, I know that scsi is broken
> and should not be used and so on, and suggested switching from it on
> every chance.

Well we don't want to break people's guests.  If the fix Gleb alluded to
doesn't work, we'll have to restore extboot or something similar.  Let
us know.

-- 
error compiling committee.c: too many arguments to function

Re: qemu-kvm: Inconsistent vgabios reference

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]

On 2012-01-15 14:39, Avi Kivity wrote:
> On 01/15/2012 03:27 PM, Michael Tokarev wrote:
>> On 15.01.2012 17:18, Avi Kivity wrote:
>>> On 01/15/2012 03:10 PM, Michael Tokarev wrote:
>> []
>>>> FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because
>>>> of lack of boot support from scsi (and no alternative), and because
>>>> many people's scripts who used boot= broke.  I thought it is better
>>>> to let users to have a chance to perform a smoother transition than
>>>> to break their stuff.
>>>
>>> It's really sad that people have to use lsi scsi.  Luckily qemu 1.1 will
>>> feature virtio-scsi, though of course that doesn't help already
>>> installed guests or non Windows/Linux guests.  Do you know what the use
>>> cases requiring scsi boot are?
>>
>> I've one (not very pleasant) bugreport handy, http://bugs.debian.org/652447
>> and a few private messages asking me for ways to restore booting from scsi,
>> all talking about older/custom systems which worked for years in kvm.
>> As you can see in the bugreport mentioned, I know that scsi is broken
>> and should not be used and so on, and suggested switching from it on
>> every chance.
> 
> Well we don't want to break people's guests.  If the fix Gleb alluded to
> doesn't work, we'll have to restore extboot or something similar.  Let
> us know.

I would vote for proper seabios support or a free option rom. That would
allow us to make progress with obsoleting qemu-kvm instead of making a
step back again.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: qemu-kvm: Inconsistent vgabios reference

[Gleb Natapov]

On Sun, Jan 15, 2012 at 03:21:45PM +0100, Jan Kiszka wrote:
> On 2012-01-15 14:39, Avi Kivity wrote:
> > On 01/15/2012 03:27 PM, Michael Tokarev wrote:
> >> On 15.01.2012 17:18, Avi Kivity wrote:
> >>> On 01/15/2012 03:10 PM, Michael Tokarev wrote:
> >> []
> >>>> FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because
> >>>> of lack of boot support from scsi (and no alternative), and because
> >>>> many people's scripts who used boot= broke.  I thought it is better
> >>>> to let users to have a chance to perform a smoother transition than
> >>>> to break their stuff.
> >>>
> >>> It's really sad that people have to use lsi scsi.  Luckily qemu 1.1 will
> >>> feature virtio-scsi, though of course that doesn't help already
> >>> installed guests or non Windows/Linux guests.  Do you know what the use
> >>> cases requiring scsi boot are?
> >>
> >> I've one (not very pleasant) bugreport handy, http://bugs.debian.org/652447
> >> and a few private messages asking me for ways to restore booting from scsi,
> >> all talking about older/custom systems which worked for years in kvm.
> >> As you can see in the bugreport mentioned, I know that scsi is broken
> >> and should not be used and so on, and suggested switching from it on
> >> every chance.
> > 
> > Well we don't want to break people's guests.  If the fix Gleb alluded to
> > doesn't work, we'll have to restore extboot or something similar.  Let
> > us know.
> 
> I would vote for proper seabios support or a free option rom. That would
> allow us to make progress with obsoleting qemu-kvm instead of making a
> step back again.
> 
It is not enough to vote, somebody has to send patches :) And it seams
there are two kind of people: those who can make such a patch, but don't
because they know enough to avoid qemu lsi emulation and those who can't
make it and use lsi qemu emulation.
 
--
			Gleb.

Re: qemu-kvm: Inconsistent vgabios reference

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]

On 2012-01-15 15:29, Gleb Natapov wrote:
> On Sun, Jan 15, 2012 at 03:21:45PM +0100, Jan Kiszka wrote:
>> On 2012-01-15 14:39, Avi Kivity wrote:
>>> On 01/15/2012 03:27 PM, Michael Tokarev wrote:
>>>> On 15.01.2012 17:18, Avi Kivity wrote:
>>>>> On 01/15/2012 03:10 PM, Michael Tokarev wrote:
>>>> []
>>>>>> FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because
>>>>>> of lack of boot support from scsi (and no alternative), and because
>>>>>> many people's scripts who used boot= broke.  I thought it is better
>>>>>> to let users to have a chance to perform a smoother transition than
>>>>>> to break their stuff.
>>>>>
>>>>> It's really sad that people have to use lsi scsi.  Luckily qemu 1.1 will
>>>>> feature virtio-scsi, though of course that doesn't help already
>>>>> installed guests or non Windows/Linux guests.  Do you know what the use
>>>>> cases requiring scsi boot are?
>>>>
>>>> I've one (not very pleasant) bugreport handy, http://bugs.debian.org/652447
>>>> and a few private messages asking me for ways to restore booting from scsi,
>>>> all talking about older/custom systems which worked for years in kvm.
>>>> As you can see in the bugreport mentioned, I know that scsi is broken
>>>> and should not be used and so on, and suggested switching from it on
>>>> every chance.
>>>
>>> Well we don't want to break people's guests.  If the fix Gleb alluded to
>>> doesn't work, we'll have to restore extboot or something similar.  Let
>>> us know.
>>
>> I would vote for proper seabios support or a free option rom. That would
>> allow us to make progress with obsoleting qemu-kvm instead of making a
>> step back again.
>>
> It is not enough to vote, somebody has to send patches :) And it seams
> there are two kind of people: those who can make such a patch, but don't
> because they know enough to avoid qemu lsi emulation and those who can't
> make it and use lsi qemu emulation.

I'm pretty sure there is also a set of people who need to use LSI and
can write the proper support.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: qemu-kvm: Inconsistent vgabios reference

[Gerd Hoffmann]

  Hi,

> Now, I've a question: what seabios implementation of extboot we're
> talking about?

seabios boots natively from virtio now, so for that use case extboot
isn't needed any more.

>  -option-rom which is impossible to select as a first
> boot device?

'qemu-kvm -option-rom romfile=/root/roms/8xx_64.rom,bootindex=1' will do.

HTH,
  Gerd