gmane.linux.redhat.et-mgmt-tools

Michael DeHaan | 14 Aug 23:30

Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

I'm finding that RHEL 2 (last dot release) does not seem to have a 
virtual NIC of the type that Anaconda can discover.

Has anyone tested EL2, and if so, should I be sending something extra 
down to python virtinst for that?

--Michael

Cole Robinson | 14 Aug 23:55

Re: Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

Michael DeHaan wrote:
> I'm finding that RHEL 2 (last dot release) does not seem to have a 
> virtual NIC of the type that Anaconda can discover.
> 
> Has anyone tested EL2, and if so, should I be sending something extra 
> down to python virtinst for that?
> 
> --Michael
> 

Actually I just committed some work to virtinst that may help solve
this issue.

Try running qemu-kvm manually and testing out the -nic models. Try
'qemu-kvm -hda /any/old/file -net nic,model=?' to see a list of the
available ones. See if you can find a model that works, and we can
trivially put it in the virtinst os database. So if someone in
the future tries

virt-install --os-type linux --os-variant rhel2.1 --blah ...

We can automatically set the correct network model.

Also, if you already have a rhel2.1 libvirt vm that isn't
working, check out /var/log/libvirt/qemu/{vmname}.log to
see what the qemu-kvm command line libvirt is generating,
so you can just swap out the model, rather than trying to
recreate the whole qemu-kvm cl from scratch.

- Cole

(Continue reading)

Michael DeHaan | 15 Aug 00:00

Re: Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

Cole Robinson wrote:
> Michael DeHaan wrote:
>   
>> I'm finding that RHEL 2 (last dot release) does not seem to have a 
>> virtual NIC of the type that Anaconda can discover.
>>
>> Has anyone tested EL2, and if so, should I be sending something extra 
>> down to python virtinst for that?
>>
>> --Michael
>>
>>     
>
> Actually I just committed some work to virtinst that may help solve
> this issue.
>
> Try running qemu-kvm manually and testing out the -nic models. Try
> 'qemu-kvm -hda /any/old/file -net nic,model=?' to see a list of the
> available ones. See if you can find a model that works, and we can
> trivially put it in the virtinst os database. So if someone in
> the future tries
>
> virt-install --os-type linux --os-variant rhel2.1 --blah ...
>
> We can automatically set the correct network model.
>
> Also, if you already have a rhel2.1 libvirt vm that isn't
> working, check out /var/log/libvirt/qemu/{vmname}.log to
> see what the qemu-kvm command line libvirt is generating,
> so you can just swap out the model, rather than trying to

(Continue reading)

Michael DeHaan | 15 Aug 00:14

Re: Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

Michael DeHaan wrote:
> Cole Robinson wrote:
>> Michael DeHaan wrote:
>>> I'm finding that RHEL 2 (last dot release) does not seem to have a 
>>> virtual NIC of the type that Anaconda can discover.
>>>
>>> Has anyone tested EL2, and if so, should I be sending something 
>>> extra down to python virtinst for that?
>>>
>>> --Michael
>>>
>>
>> Actually I just committed some work to virtinst that may help solve
>> this issue.
>>
>> Try running qemu-kvm manually and testing out the -nic models. Try
>> 'qemu-kvm -hda /any/old/file -net nic,model=?' to see a list of the
>> available ones. See if you can find a model that works, and we can
>> trivially put it in the virtinst os database. So if someone in
>> the future tries
>>
>> virt-install --os-type linux --os-variant rhel2.1 --blah ...
>>
>> We can automatically set the correct network model.
>>
>> Also, if you already have a rhel2.1 libvirt vm that isn't
>> working, check out /var/log/libvirt/qemu/{vmname}.log to
>> see what the qemu-kvm command line libvirt is generating,
>> so you can just swap out the model, rather than trying to
>> recreate the whole qemu-kvm cl from scratch.

(Continue reading)

Cole Robinson | 17 Aug 20:50

Re: Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

Michael DeHaan wrote:
> Strike that backport bit, no qemu in RHEL. It's all good. Will test
> and get back with that...
>

It is still relevant actually: xen uses a forked qemu for device
emulation for
FV guests, and the network device model can be selected (see
/etc/xen/xmexample.hvm, search for 'model'). The libvirt support for
this isn't
in 5.2, but it isn't impossible that we could end up backporting or
rebasing it in.

- Cole

Daniel P. Berrange | 15 Aug 00:15

Re: Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

On Thu, Aug 14, 2008 at 05:55:51PM -0400, Cole Robinson wrote:
> Michael DeHaan wrote:
> > I'm finding that RHEL 2 (last dot release) does not seem to have a 
> > virtual NIC of the type that Anaconda can discover.
> > 
> > Has anyone tested EL2, and if so, should I be sending something extra 
> > down to python virtinst for that?
> > 
> > --Michael
> > 
> 
> Actually I just committed some work to virtinst that may help solve
> this issue.
> 
> Try running qemu-kvm manually and testing out the -nic models. Try
> 'qemu-kvm -hda /any/old/file -net nic,model=?' to see a list of the
> available ones. See if you can find a model that works, and we can
> trivially put it in the virtinst os database. So if someone in
> the future tries

I've got to imagine that the ne2k NIC wil do the job, though I'm kinda
suprised there's no rtl8139 support.

> virt-install --os-type linux --os-variant rhel2.1 --blah ...
> 
> We can automatically set the correct network model.

Excellant - I assume you've got that setup to use VirtIO for F9/10
and Ubuntu Hardy ?

(Continue reading)

Michael DeHaan | 15 Aug 00:21

Re: Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

Daniel P. Berrange wrote:
> On Thu, Aug 14, 2008 at 05:55:51PM -0400, Cole Robinson wrote:
>   
>> Michael DeHaan wrote:
>>     
>>> I'm finding that RHEL 2 (last dot release) does not seem to have a 
>>> virtual NIC of the type that Anaconda can discover.
>>>
>>> Has anyone tested EL2, and if so, should I be sending something extra 
>>> down to python virtinst for that?
>>>
>>> --Michael
>>>
>>>       
>> Actually I just committed some work to virtinst that may help solve
>> this issue.
>>
>> Try running qemu-kvm manually and testing out the -nic models. Try
>> 'qemu-kvm -hda /any/old/file -net nic,model=?' to see a list of the
>> available ones. See if you can find a model that works, and we can
>> trivially put it in the virtinst os database. So if someone in
>> the future tries
>>     
>
> I've got to imagine that the ne2k NIC wil do the job, though I'm kinda
> suprised there's no rtl8139 support.
>
>   
>> virt-install --os-type linux --os-variant rhel2.1 --blah ...
>>

(Continue reading)

Daniel P. Berrange | 15 Aug 00:29

Re: Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

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
--

-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

Michael DeHaan | 15 Aug 00:33

Re: Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

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.

(Continue reading)

Michael DeHaan | 18 Aug 16:15

Re: Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

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.
>

(Continue reading)

Cole Robinson | 18 Aug 16:21

Re: 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

(Continue reading)

Richard W.M. Jones | 15 Aug 15:20

Re: Installing RHEL 2 (yes, "2") inside a F9 KVM VM...

On Thu, Aug 14, 2008 at 05:32:00PM -0400, Michael DeHaan wrote:
> I'm finding that RHEL 2 (last dot release) does not seem to have a  
> virtual NIC of the type that Anaconda can discover.
>
> Has anyone tested EL2, and if so, should I be sending something extra  
> down to python virtinst for that?

I have tested RHL 6.2 in KVM and found the same problem and a few
others:

  http://marc.info/?l=kvm&m=121483789832440&w=2

Doubt it's worth changing virt-install to fix this though.

Rich.

--

-- 
Richard Jones, Emerging Technologies, Red Hat  http://et.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/

Return

Return to gmane.linux.redhat.et-mgmt-tools.

Advertisement

Project Web Page

Emerging Technologies Management Tools

Search Archive

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane