qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/5] boot order specification


From: Bernhard Kohl
Subject: Re: [Qemu-devel] [PATCH 0/5] boot order specification
Date: Tue, 26 Oct 2010 15:35:38 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.12) Gecko/20100907 Fedora/3.0.7-1.fc12 Mnenhy/0.8.3 Thunderbird/3.0.7

Am 26.10.2010 15:07, schrieb ext Gleb Natapov:
On Tue, Oct 26, 2010 at 02:40:51PM +0200, Bernhard Kohl wrote:
Am 26.10.2010 12:48, schrieb ext Gleb Natapov:
This is current sate of the patch series for people to comment on.
I dropped ioport double reservation checking from isa-bus and added
bus_id field for IDE bus since as Markus pointed out unit has different
meaning there.

This patch series produce names like:

address@hidden,03f7/address@hidden
address@hidden,03f7/address@hidden
address@hidden:00:01.1/address@hidden:0
address@hidden:00:01.1/address@hidden:1
address@hidden:00:03.0/address@hidden
address@hidden:00:04.0/address@hidden
Are PCI pass-through devices (SR-IOV NICs) also supported?
Don't see any problem. They are regular PCI devices as seen by
guest, correct?

Yes, that's true. And we add a bootrom on the qemu command line.
But this is already working and would not be changed.

So I expect path to them will look like this:
address@hidden:00:04.0/address@hidden

Yes, that would be fine. I assume that each boot NIC,
e.g. e1000 gets its name here.

I assume that hw/device-assignment.c is missing from the changed files.
Our systems highly depend on PXE booting from these devices.

The patch is only an example. I converted only virtio-net to support
bootindex ATM.

--
                        Gleb.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]