On Wed, May 02, 2012 at 03:42:51PM +0200, Gerd Hoffmann wrote:
Hi,
Is this just a matter of removing the if (pci_bdf_to_bus(pci-bdf) !=
0) break from pci_bios_init_devices()?
Seems to do the trick, at least the disks connected appear in the boot
menu now and the seabios log file looks
Hi,
Is this just a matter of removing the if (pci_bdf_to_bus(pci-bdf) !=
0) break from pci_bios_init_devices()?
Seems to do the trick, at least the disks connected appear in the boot
menu now and the seabios log file looks sane.
The guest kernel has no virtio-scsi drivers though, need to
On 27/04/12 00:45, Kevin O'Connor wrote:
On Wed, Apr 25, 2012 at 05:29:04PM +0200, Gerd Hoffmann wrote:
Issue #1: seabios can't boot from a virtio-scsi disk if the controller
is behind a pci bridge. I think the reason simply is that (according to
the seabios log) only root bus pci devices
Hi,
Issue #1: seabios can't boot from a virtio-scsi disk if the controller
is behind a pci bridge. I think the reason simply is that (according to
the seabios log) only root bus pci devices are initialized. Probably
even isn't related to this patch set, just trapped into this while
On Wed, Apr 25, 2012 at 05:29:04PM +0200, Gerd Hoffmann wrote:
Issue #1: seabios can't boot from a virtio-scsi disk if the controller
is behind a pci bridge. I think the reason simply is that (according to
the seabios log) only root bus pci devices are initialized. Probably
even isn't
On Thu, Apr 26, 2012 at 07:12:22PM +1200, Alexey Korolev wrote:
On 26/04/12 03:29, Gerd Hoffmann wrote:
Okay - I missed that. I think the patches look okay to be committed -
any additional changes can be made on top. Gerd - do you have any
comments?
These are certainly no blockers and
On 04/25/12 14:51, Kevin O'Connor wrote:
On Wed, Apr 25, 2012 at 06:25:07PM +1200, Alexey Korolev wrote:
On 25/04/12 13:48, Kevin O'Connor wrote:
On Tue, Apr 24, 2012 at 06:25:39PM +1200, Alexey Korolev wrote:
+pci_region_map_entries(busses, r64_mem);
+
