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

Re: [et-mgmt-tools] Installing RHEL 2 (yes, "*2*") inside a F9 KVM VM...

Michael DeHaan wrote:
> Michael DeHaan wrote:
>> Daniel P. Berrange wrote:
>>> On Thu, Aug 14, 2008 at 06:21:58PM -0400, Michael DeHaan wrote:
>>>> I'm not passing down variant now for virtinst API calls (but can 
>>>> probably do this in a future
>>>> release if the user supplies it). Is there a suggestion to just make 
>>>> it default to the compatible NIC that would
>>>> be good for all Fedora/RHEL (or are there performance issues in 
>>>> doing this or something)?
>>> That's the situation we've got already - we compile Xen and KVM to use
>>> the rtl8139 nic since that's the best lowest-common denominator. It was
>>> a barely passable approach so far, but with VirtIO it is now past its 
>>> sell
>>> by date and we have to key off os type/variant. If we don't then we'll
>>> be limiting guests to 1/100 of the their potential performance. Not cool
>>> Daniel
>> Yikes :)
>> I'll do some more manual creation tests tomorrow using the qemu 
>> command line.
>> Passing in the OS version is doable as we should soon have "cobbler 
>> import" storing that data.
>> Right now, it stores the name "RHEL5.2", etc, but that's not hard 
>> enough to key off of.
>> --Michael
> Ok, so friday I tried walking through this with virt-manager and chose 
> the OS/variant as 2.1, and it picked the wrong network
> driver there too and could not install 2.1.
> --Michael

Virt-manager just calls out to virtinst for this, so all
the choosing is centralized.

Also, prior to a week ago upstream we weren't doing any
distro specific hardware selection for networking, everything
was just using the default nic model rtl8139.

- Cole

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