From: Michael Tokarev <mjt@tls.msk.ru>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Daniel Guillermo Bareiro <daniel-listas@gmx.net>, kvm@vger.kernel.org
Subject: Re: Unable to boot from SCSI disk
Date: Tue, 28 May 2013 13:59:37 +0400 [thread overview]
Message-ID: <51A48009.1040602@msgid.tls.msk.ru> (raw)
In-Reply-To: <51A47112.5020904@redhat.com>
28.05.2013 12:55, Paolo Bonzini wrote:
> Il 27/05/2013 23:25, Michael Tokarev ha scritto:
[]
>> but it is wheezy, which ships with seabios 1.7.0, which does not
>> have scsi boot support. So in order to boot from scsi, you have
>> to use old ,boot=on device property, which has been forward-ported
>> from older qemu-kvm version to 1.1 version used on debian, because
>> it was the only way at that time to boot from an scsi disk without
>> resorting to using proprietary firmware.
>
> Why don't you forward port the SCSI boot patches?
That'd be back-porting, not forward-porting.
Anyway, in Debian we use a bit different approach usually. Namely,
instead of backporting lots of stuff resulting in a BigMess(tm),
we provide more recent upstream versions of the software but
compiled for previous (stable) debian release. This mechanism
is named "debian backports".
The stable release itself does not receive any large feature
updates. It receives bugfixes, but only important ones.
Besides, this scsi stuff doesn't really matter much -- it
helps in some very rare situations (for example, sometimes
this way it's easier to migrate from vmware to qemu), but
that's about it. So I don't consider doing backports
especially for scsi. If the new version backported to
debian _also_ fixes scsi issues, that's just a side-effect.
Thanks,
/mjt
next prev parent reply other threads:[~2013-05-28 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 20:53 Unable to boot from SCSI disk Daniel Guillermo Bareiro
2013-05-27 20:59 ` Paolo Bonzini
2013-05-27 21:25 ` Michael Tokarev
2013-05-28 7:07 ` Michael Tokarev
2013-05-28 8:55 ` Paolo Bonzini
2013-05-28 9:59 ` Michael Tokarev [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-29 11:11 Daniel Guillermo Bareiro
2013-05-30 12:59 ` Alexandre DERUMIER
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51A48009.1040602@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=daniel-listas@gmx.net \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox