On 26.12.2011 16:32, Vladimir Stavrinov wrote: > On Mon, Dec 26, 2011 at 04:03:50PM +0400, Michael Tokarev wrote: > >> Please address this upstream. It wasn't my decision to remove scsi > > I hope they are reading debian bug reports.
Why should they? > It is well known: cutting off of head is best remedy for headache. > Again: I don't know the reason, why they are doing so, but it is hard > to understand and agree, if I have no problems with SCSI for years in > any environment. The reason extboot ever existed was because it wasn't possible to boot from virtio because seabios (bochsbios at that time) didn't support virtio devices. It was just a quick hack to let virtio going. Now the main user of it (virtio) does not need extboot anymore (real bios support exists), and noone (me included) cares about scsi which is broken in numerous ways. This attitude made me think. Initially I planned to just patch extboot back in, till some other solution emerges or the need for whole thing will phase out. But your comments really worked backwards, after reading them I didn't want to do that anymore, just for you to realize that there may be other opinions too. But here we go, I just reverted the changes which removed extboot, so scsi booting will be in the next release (1.0-3) of qemu-kvm uploaded to debian. Please understand that I will NOT let this patch go to wheezy, I plan to remove it before wheezy is out. Maybe at that time we will at least have ahci migration working, or maybe there will be real bios support for booting from scsi, -- who knows. Note again that using the bios from lsi logic works too. As of this bug, Marc, I cloned it into two halves, one about scsi and another about *bsd breakage. I haven't looked at that other part yet, and am sorry about that - hopefully will do in a few days. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
