11:40 p.m.
--_000_7fbb63dfa18c4b05af73e117062f6f83BN1PR04MB170namprd04pro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hello All,
I've been searching the archives and not yet managed to find anything on th=
e subject, so I'm hoping that someone can point me in the right direction.
I am using nodes with Intel 10G network cards. The driver for these cards =
has been tweaked to complain (and fail to start the interface) if a non-Int=
el approved optical transceiver is in use. It's easy to override with the =
following options:
ixgbe.allow_unsupported_sfp=3D1
The usual ways of doing this are either to place it on the kernel command l=
ine at boot time, or in /etc/modprobe.d/ixgbe.conf where it would read "opt=
ions ixgbe allow_unsupported_sfp=3D1". Unfortunately I have no idea how to=
make either of these permanent on an oVirt node.
I'm running the ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso image. It has an /=
etc/modprobe.d directory where changes do not persist across reboots. It a=
lso has /config/etc where I've added modprobe.d and modprobe.d/ixgbe.conf. =
By adding this file to /config/files, I've been able to make it appear in =
/etc/modprobe.d at boot time. This has no effect. It appears to take plac=
e after the ixgbe driver has already been started. If I "rmmod ixgbe" and =
"modprobe ixgbe" manually, it works fine.
So the general question is, how do I make configuration changes which persi=
st across reboots? Surely others have run into the same situation when try=
ing to support specific devices.
Thanks,
Allen Belletti
AVP Ed. Tech Engineering Innovation
Georgia Gwinnett College
678-407-5093
www.ggc.edu
--_000_7fbb63dfa18c4b05af73e117062f6f83BN1PR04MB170namprd04pro_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
<style type=3D"text/css"
id=3D"owaParaStyle" style=3D"">=0A=
<!--=0A=
p=0A=
{margin-top:0;=0A=
margin-bottom:0}=0A=
-->=0A=
P {margin-top:0;margin-bottom:0;}</style
</head <body dir=3D"ltr"
tabindex=3D"0" fpstyle=3D"1" aria-label=3D"Message body" <div name=3D"divtagdefaultwrapper"
id=3D"divtagdefaultwrapper" style=3D"fon=
t-family: Calibri,Arial,Helvetica,sans-serif; font-size: 12pt; color: #0000=
00; margin: 0" <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" Hello All,</div <div name=3D"divtagdefaultwrapper"
id=3D"divtagdefaultwrapper" style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" I've been searching the archives
and not yet managed to find anything on th=
e subject, so I'm hoping that someone can point me in the right direction.<=
/div <div name=3D"divtagdefaultwrapper"
id=3D"divtagdefaultwrapper" style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" I am using nodes with Intel 10G
network cards. The driver for these c=
ards has been tweaked to complain (and fail to start the interface) if a no=
n-Intel approved optical transceiver is in use. It's easy to override=
with the following options:</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0"
ixgbe.allow_unsupported_sfp=3D1</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" The usual ways of doing this are
either to place it on the kernel command l=
ine at boot time, or in /etc/modprobe.d/ixgbe.conf where it would read &quo=
t;options ixgbe allow_unsupported_sfp=3D1". Unfortunately I have=
no idea how to make either of these permanent on
an oVirt node.</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" I'm running
the ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso image. I=
t has an /etc/modprobe.d directory where changes do not persist across rebo=
ots. It also has /config/etc where I've added modprobe.d and modprobe=
.d/ixgbe.conf. By adding this file to /config/files,
I've been able to make it appear in /etc/modprobe.d at boot time. Th=
is has no effect. It appears to take place after the ixgbe driver has=
already been started. If I "rmmod ixgbe" and
"modprob=
e ixgbe" manually, it works fine.</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" So the general question is, how do I
make configuration changes which persi=
st across reboots? Surely others have run into the same situation whe=
n trying to support specific devices.</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" Thanks,</div <div name=3D"divtagdefaultwrapper"
id=3D"divtagdefaultwrapper" style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <div><br <div style=3D"font-family:Tahoma;
font-size:13px"><span lang=3D"en-US" <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">Allen Belletti<br
</span></font></div <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">AVP Ed. Tech Engineering Innovation<br </span></font></div <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">Georgia Gwinnett
College</span></font></div <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">678-407-5093</span></font></div <div style=3D"margin:0pt"><font
face=3D"Calibri,sans-serif" size=3D"2"><spa=
n style=3D"font-size:11pt">www.ggc.edu<br
</span></font></div
</span></div </div </div
</div </body </html
--_000_7fbb63dfa18c4b05af73e117062f6f83BN1PR04MB170namprd04pro_--
1:09 a.m.
--_000_53e9331019a1469ca6ce03e5a8b018d0BN1PR04MB170namprd04pro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Have since learned that what I did was equivalent to using the "persist" co=
mmand, and known not to work for modprobe and other things early in the boo=
t process.
Have also discovered that even mounting / read-write and using mount --bind=
to get at what's "under" /etc doesn't help. Am assuming that the
"live-rw=
" filesystem is created at boot time from an image, and can't be modified s=
hort of building from source. Is that correct?
It looks like perhaps what I want to do is install the ovirt-node packages =
onto my OS of choice (CentOS 6.4, currently.) Will do some reading and try=
ing to see if that's possible. I see that it's documented on FC19 but woul=
d prefer to remain with CentOS.
Any tips are appreciated of course!
Thanks,
Allen Belletti
AVP Ed. Tech Engineering Innovation
Georgia Gwinnett College
678-407-5093
www.ggc.edu
________________________________
From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> on behalf of Allen =
Belletti <allen(a)ggc.edu Sent: Wednesday, October 02, 2013
4:40 PM
To: users(a)ovirt.org
Subject: [Users] Customizing node configuration
Hello All,
I've been searching the archives and not yet managed to find anything on th=
e subject, so I'm hoping that someone can point me in the right direction.
I am using nodes with Intel 10G network cards. The driver for these cards =
has been tweaked to complain (and fail to start the interface) if a non-Int=
el approved optical transceiver is in use. It's easy to override with the =
following options:
ixgbe.allow_unsupported_sfp=3D1
The usual ways of doing this are either to place it on the kernel command l=
ine at boot time, or in /etc/modprobe.d/ixgbe.conf where it would read "opt=
ions ixgbe allow_unsupported_sfp=3D1". Unfortunately I have no idea how to=
make either of these permanent on an oVirt node.
I'm running the ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso image. It has an /=
etc/modprobe.d directory where changes do not persist across reboots. It a=
lso has /config/etc where I've added modprobe.d and modprobe.d/ixgbe.conf. =
By adding this file to /config/files, I've been able to make it appear in =
/etc/modprobe.d at boot time. This has no effect. It appears to take plac=
e after the ixgbe driver has already been started. If I "rmmod ixgbe" and =
"modprobe ixgbe" manually, it works fine.
So the general question is, how do I make configuration changes which persi=
st across reboots? Surely others have run into the same situation when try=
ing to support specific devices.
Thanks,
Allen Belletti
AVP Ed. Tech Engineering Innovation
Georgia Gwinnett College
678-407-5093
www.ggc.edu
--_000_53e9331019a1469ca6ce03e5a8b018d0BN1PR04MB170namprd04pro_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
<style type=3D"text/css"
id=3D"owaParaStyle" style=3D"display: none;">P {ma=
rgin-top:0;margin-bottom:0;}</style><style type=3D"text/css"
id=3D"owaParaS=
tyle" style=3D"">=0A=
<!--=0A=
p=0A=
{margin-top:0;=0A=
margin-bottom:0}=0A=
-->=0A=
</style </head <body dir=3D"ltr" fpstyle=3D"1"
aria-label=3D"Message body" tabindex=3D"0" <div name=3D"divtagdefaultwrapper"
id=3D"divtagdefaultwrapper" style=3D"fon=
t-family: Calibri,Arial,Helvetica,sans-serif; font-size: 12pt; color: #0000=
00; margin: 0" Have since learned that what I did
was equivalent to using the "persis=
t" command, and known not to work for modprobe and other things early =
in the boot process.
<div><br </div <div>Have also discovered that even mounting / read-write
and using mount -=
-bind to get at what's "under" /etc doesn't help. Am
assumi=
ng that the "live-rw" filesystem is created at boot time from an =
image, and can't be modified short of building from source.
Is that correct?</div
<div><br </div <div>It looks like perhaps what I want to do is install
the ovirt-node pack=
ages onto my OS of choice (CentOS 6.4, currently.) Will do some readi=
ng and trying to see if that's possible. I see that it's documented o=
n FC19 but would prefer to remain with CentOS.</div
<div><br </div <div>Any tips are appreciated of course!<br <br Thanks,</div <div <div><br <div style=3D"font-family:Tahoma;
font-size:13px"><span lang=3D"en-US" <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">Allen Belletti<br
</span></font></div <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">AVP Ed. Tech Engineering Innovation<br </span></font></div <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">Georgia Gwinnett
College</span></font></div <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">678-407-5093</span></font></div <div style=3D"margin:0pt"><font
face=3D"Calibri,sans-serif" size=3D"2"><spa=
n style=3D"font-size:11pt">www.ggc.edu<br
</span></font></div
</span></div </div <br <div dir=3D"ltr"
style=3D"color: rgb(40, 40, 40);" <hr
tabindex=3D"-1" style=3D"display:inline-block; width:98%" <div id=3D"divRplyFwdMsg"
dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b>
users-bounces(a)ovirt.o=
rg &lt;users-bounces(a)ovirt.org&gt; on behalf of Allen Belletti <allen@gg=
c.edu><br <b>Sent:</b> Wednesday,
October 02, 2013 4:40 PM<br <b>To:</b>
users(a)ovirt.org<br <b>Subject:</b> [Users]
Customizing node configuration</font
<div> </div
</div <div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" Hello All,</div <div name=3D"divtagdefaultwrapper"
id=3D"divtagdefaultwrapper" style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" I've been searching the archives
and not yet managed to find anything on th=
e subject, so I'm hoping that someone can point me in the right direction.<=
/div <div name=3D"divtagdefaultwrapper"
id=3D"divtagdefaultwrapper" style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" I am using nodes with Intel 10G
network cards. The driver for these c=
ards has been tweaked to complain (and fail to start the interface) if a no=
n-Intel approved optical transceiver is in use. It's easy to override=
with the following options:</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0"
ixgbe.allow_unsupported_sfp=3D1</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" The usual ways of doing this are
either to place it on the kernel command l=
ine at boot time, or in /etc/modprobe.d/ixgbe.conf where it would read &quo=
t;options ixgbe allow_unsupported_sfp=3D1". Unfortunately I have=
no idea how to make either of these permanent on
an oVirt node.</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" I'm running
the ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso image. I=
t has an /etc/modprobe.d directory where changes do not persist across rebo=
ots. It also has /config/etc where I've added modprobe.d and modprobe=
.d/ixgbe.conf. By adding this file to /config/files,
I've been able to make it appear in /etc/modprobe.d at boot time. Th=
is has no effect. It appears to take place after the ixgbe driver has=
already been started. If I "rmmod ixgbe" and
"modprob=
e ixgbe" manually, it works fine.</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" So the general question is, how do I
make configuration changes which persi=
st across reboots? Surely others have run into the same situation whe=
n trying to support specific devices.</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <br
</div <div
name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper"
style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" Thanks,</div <div name=3D"divtagdefaultwrapper"
id=3D"divtagdefaultwrapper" style=3D"fon=
t-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:#000000;=
margin:0" <div><br <div style=3D"font-family:Tahoma;
font-size:13px"><span lang=3D"en-US" <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">Allen Belletti<br
</span></font></div <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">AVP Ed. Tech Engineering Innovation<br </span></font></div <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">Georgia Gwinnett
College</span></font></div <div
style=3D"margin:0pt"><font face=3D"Calibri,sans-serif"
size=3D"2"><spa=
n style=3D"font-size:11pt">678-407-5093</span></font></div <div style=3D"margin:0pt"><font
face=3D"Calibri,sans-serif" size=3D"2"><spa=
n style=3D"font-size:11pt">www.ggc.edu<br
</span></font></div
</span></div </div </div
</div </div </div
</div </div </body
</html
--_000_53e9331019a1469ca6ce03e5a8b018d0BN1PR04MB170namprd04pro_--
1:56 a.m.
On Thu, Oct 3, 2013 at 12:09 AM, Allen Belletti wrote:
By adding this file to /config/files, I've been able to make it
appear in
/etc/modprobe.d at boot time. This has no effect. It appears to take place
after the ixgbe driver has already been started. If I "rmmod ixgbe" and
"modprobe ixgbe" manually, it works fine.
If I remember correctly the file /etc/rc.d/rc.local is
persisted/persistable, so if it's still true in the mean time you can
put as a workaround in it
modprobe -r ixgbe
modprobe ixgbe
HIH,
Gianluca
4:24 a.m.
Thanks Gianluca! As it turns out, I reinstalled the node with CentOS 6.4 and was then
able to configure it from within ovirt-engine 3.3. The only glitch was having to change
the cluster's emulated machine type from pc-1.0 to pc, since I've got 3.1 (or
3.0?) level nodes, and the ovirt-engine was upgraded from 3.1 to 3.3 the other day.
Up and running VMs on the new node, at least to test!
Allen Belletti
AVP Ed. Tech Engineering Innovation
Georgia Gwinnett College
678-407-5093
www.ggc.edu
________________________________________
From: Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
Sent: Wednesday, October 02, 2013 6:56 PM
To: Allen Belletti
Cc: users(a)ovirt.org
Subject: Re: [Users] Customizing node configuration
On Thu, Oct 3, 2013 at 12:09 AM, Allen Belletti wrote:
By adding this file to /config/files, I've been able to make it
appear in
/etc/modprobe.d at boot time. This has no effect. It appears to take place
after the ixgbe driver has already been started. If I "rmmod ixgbe" and
"modprobe ixgbe" manually, it works fine.
If I remember correctly the file /etc/rc.d/rc.local is
persisted/persistable, so if it's still true in the mean time you can
put as a workaround in it
modprobe -r ixgbe
modprobe ixgbe
HIH,
Gianluca
2:44 p.m.
On 10/03/2013 01:09 AM, Allen Belletti wrote:
Have since learned that what I did was equivalent to using the
"persist"
command, and known not to work for modprobe and other things early in
the boot process.
Have also discovered that even mounting / read-write and using mount
--bind to get at what's "under" /etc doesn't help. Am assuming that
the
"live-rw" filesystem is created at boot time from an image, and can't be
modified short of building from source. Is that correct?
It looks like perhaps what I want to do is install the ovirt-node
packages onto my OS of choice (CentOS 6.4, currently.) Will do some
reading and trying to see if that's possible. I see that it's
documented on FC19 but would prefer to remain with CentOS.
you don't need to "install packages from node" into centos, just point
ovirt-engine add-host dialog to the host and it will bootstrap with all
needed packages (assuming the target host has the relevant repo configured).
to change something in the node you can build your own node as well
Any tips are appreciated of course!
Thanks,
Allen Belletti
AVP Ed. Tech Engineering Innovation
Georgia Gwinnett College
678-407-5093
www.ggc.edu
------------------------------------------------------------------------
*From:* users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> on behalf of
Allen Belletti <allen(a)ggc.edu>
*Sent:* Wednesday, October 02, 2013 4:40 PM
*To:* users(a)ovirt.org
*Subject:* [Users] Customizing node configuration
Hello All,
I've been searching the archives and not yet managed to find anything on
the subject, so I'm hoping that someone can point me in the right direction.
I am using nodes with Intel 10G network cards. The driver for these
cards has been tweaked to complain (and fail to start the interface) if
a non-Intel approved optical transceiver is in use. It's easy to
override with the following options:
ixgbe.allow_unsupported_sfp=1
The usual ways of doing this are either to place it on the kernel
command line at boot time, or in /etc/modprobe.d/ixgbe.conf where it
would read "options ixgbe allow_unsupported_sfp=1". Unfortunately I
have no idea how to make either of these permanent on an oVirt node.
I'm running the ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso image. It has
an /etc/modprobe.d directory where changes do not persist across
reboots. It also has /config/etc where I've added modprobe.d and
modprobe.d/ixgbe.conf. By adding this file to /config/files, I've been
able to make it appear in /etc/modprobe.d at boot time. This has no
effect. It appears to take place after the ixgbe driver has already
been started. If I "rmmod ixgbe" and "modprobe ixgbe" manually, it
works fine.
So the general question is, how do I make configuration changes which
persist across reboots? Surely others have run into the same situation
when trying to support specific devices.
Thanks,
Allen Belletti
AVP Ed. Tech Engineering Innovation
Georgia Gwinnett College
678-407-5093
www.ggc.edu
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
11:49 a.m.
Hi,
this sounds interesting! We look into something similar.
So just for clarification, we can setup our own customized
CentOS, enable the ovirt-repos, and when we add the host via
engine, it will automatically setup the correct corresponding
vdsm version on the compute node?
E.g. we run ovirt 3.2 on the management node, will it pull
the current version or the corresponding version?
We have some problems with 3.0.1 compute nodes and 3.2 management
nodes but the node-iso 2.6.1 runs well.
thanks in advance
Sven
On 04.10.2013 13:44, Itamar Heim wrote:
>
> you don't need to "install packages from node" into centos, just point
> ovirt-engine add-host dialog to the host and it will bootstrap with all
> needed packages (assuming the target host has the relevant repo
> configured).
>
> to change something in the node you can build your own node as well
>
12:07 p.m.
On 10/07/2013 11:49 AM, Sven Kieske wrote:
Hi,
this sounds interesting! We look into something similar.
So just for clarification, we can setup our own customized
CentOS, enable the ovirt-repos, and when we add the host via
engine, it will automatically setup the correct corresponding
vdsm version on the compute node?
yes.
ovirt supports both the "slimmed down" ovirt-node, or full blown hosts.
E.g. we run ovirt 3.2 on the management node, will it pull
the current version or the corresponding version?
it will always install latest versions it finds in the repos. they
should all be backward compatible.
We have some problems with 3.0.1 compute nodes and 3.2 management
nodes but the node-iso 2.6.1 runs well.
thanks in advance
Sven
On 04.10.2013 13:44, Itamar Heim wrote:
>
> you don't need to "install packages from node" into centos, just point
> ovirt-engine add-host dialog to the host and it will bootstrap with all
> needed packages (assuming the target host has the relevant repo
> configured).
>
> to change something in the node you can build your own node as well
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
6:55 p.m.
Hi,
thanks again for the answer, we were able to install ovirt-node onto
centos 6.4 minimal successfully!
On 07.10.2013 11:07, Itamar Heim wrote:
yes.
ovirt supports both the "slimmed down" ovirt-node, or full blown hosts.
it will always install latest versions it finds in the repos. they
should all be backward compatible.
> We have some problems with 3.0.1 compute nodes and 3.2 management
> nodes but the node-iso 2.6.1 runs well.
I just wanted to add some information on the problems we ran into
when we tried management version 3.2 with ovirt-node 3.0.1:
We were able to register the computenode, but when we tried to deploy
a new vm, which was CentOS based we got the following error:
Unsupported OS-Version Supported machines are:
pc RHEL 6.2.0 PC (alias of rhel6.2.0)
rhel6.2.0 RHEL 6.2.0 PC (default)
rhel6.1.0 RHEL 6.1.0 PC
rhel6.0.0 RHEL 6.0.0 PC
rhel5.5.0 RHEL 5.5.0 PC
rhel5.4.4 RHEL 5.4.4 PC
rhel5.4.0 RHEL 5.4.0 PC
Maybe you can shed some light on this?
Unfortunately I can't provide any logs from the host side as these got
replaced with ovirt node 2.6.1, but I can dig into the management-logs
if you need additional information.
Thanks
Sven
8:07 p.m.
On 10/07/2013 06:55 PM, Sven Kieske wrote:
Hi,
thanks again for the answer, we were able to install ovirt-node onto
centos 6.4 minimal successfully!
to avoid confusion, we'd call this a "host" and install vdsm onto it.
we call ovirt-node only the trimmed down one.
On 07.10.2013 11:07, Itamar Heim wrote:
> yes.
> ovirt supports both the "slimmed down" ovirt-node, or full blown hosts.
>
>
> it will always install latest versions it finds in the repos. they
> should all be backward compatible.
>
>> We have some problems with 3.0.1 compute nodes and 3.2 management
>> nodes but the node-iso 2.6.1 runs well.
I just wanted to add some information on the problems we ran into
when we tried management version 3.2 with ovirt-node 3.0.1:
We were able to register the computenode, but when we tried to deploy
a new vm, which was CentOS based we got the following error:
Unsupported OS-Version Supported machines are:
pc RHEL 6.2.0 PC (alias of rhel6.2.0)
rhel6.2.0 RHEL 6.2.0 PC (default)
mike/fabian - which centos is ovirt-node based of? this seems 6.2, not 6.4?
rhel6.1.0 RHEL 6.1.0 PC
rhel6.0.0 RHEL 6.0.0 PC
rhel5.5.0 RHEL 5.5.0 PC
rhel5.4.4 RHEL 5.4.4 PC
rhel5.4.0 RHEL 5.4.0 PC
Maybe you can shed some light on this?
Unfortunately I can't provide any logs from the host side as these got
replaced with ovirt node 2.6.1, but I can dig into the management-logs
if you need additional information.
Thanks
Sven
1:11 p.m.
Hi,
ok I was able to reproduce this bug, here is some information:
ManagementNode: oVirt Engine 3.2.3-1.el6
ManagementNode OS: CentOS 6.4 x64_86
We have various "local storage" datacenters on this management node, one
being "LocalCenter_v3" with a single host in it.
This Host runs CentOS 6.4 x64 minimal, we installed the ovirt-stable
repo on it and installed then vdsm through the managementnode webadmin.
this was successful, here are the vdsm-versions from the host:
rpm -qa | grep vdsm
vdsm-python-4.12.1-2.el6.x86_64
vdsm-xmlrpc-4.12.1-2.el6.noarch
vdsm-4.12.1-2.el6.x86_64
vdsm-cli-4.12.1-2.el6.noarch
vdsm-python-cpopen-4.12.1-2.el6.x86_64
So I created a VM with the following settings through webadmin portal:
Memory 2048MB, Total Virtual CPUs: 2
Operating System "Red Hat Enterprise Linux 6.x x64"
Console Protocol VNC
Boot Options: Attach CD: CentOS 6.4-x86_64-LiveCD.os
All other values were left on default.
I created and attached a 10 GB virtual disk (VirtIO)
and a VirtIO nic connected to default "ovirtmgmt".
When I try to start this vm via Webadmin I get:
VM TestSven_v3_Test1 was started by admin@internal (Host: server3).
VM TestSven_v3_Test1 is down. Exit message: internal error process
exited while connecting to monitor: Supported machines are: pc RHEL
6.4.0 PC (alias of rhel6.4.0) rhel6.4.0 RHEL 6.4.0 PC (default)
rhel6.3.0 RHEL 6.3.0 PC rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC
rhel6.0.0 RHEL 6.0.0 PC rhel5.5.0 RHEL 5.5.0 PC rhel5.4.4 RHEL 5.4.4 PC
rhel5.4.0 RHEL 5.4.0 PC .
Failed to run VM TestSven_v3_Test1 on Host server3
Please let me know what logs you need.
On older vdsm-versions (ovirt-node 2.6.1., different datacenter, same
mangementnode) everything works fine (creating and starting vms).
The same VM exported via export-domain to this datacenter fails with the
same error.
Thanks in advance
Sven
PS: The iso-domain resides on the management node.
On 07.10.2013 19:07, Itamar Heim wrote:
On 10/07/2013 06:55 PM, Sven Kieske wrote:
> Hi,
>
> thanks again for the answer, we were able to install ovirt-node onto
> centos 6.4 minimal successfully!
to avoid confusion, we'd call this a "host" and install vdsm onto it.
we call ovirt-node only the trimmed down one.
>
> mike/fabian - which centos is ovirt-node based of? this seems 6.2, not 6.4?
2:05 p.m.
Hi,
if I may, I believe you've hit this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=927874
for 3.2 there's workaround:
issue "engine-config -s EmulatedMachine=rhel6.4.0 --cver=3.2" and
restart engine
Yuriy Demchenko
On 10/08/2013 02:11 PM, Sven Kieske wrote:
Hi,
ok I was able to reproduce this bug, here is some information:
ManagementNode: oVirt Engine 3.2.3-1.el6
ManagementNode OS: CentOS 6.4 x64_86
We have various "local storage" datacenters on this management node, one
being "LocalCenter_v3" with a single host in it.
This Host runs CentOS 6.4 x64 minimal, we installed the ovirt-stable
repo on it and installed then vdsm through the managementnode webadmin.
this was successful, here are the vdsm-versions from the host:
rpm -qa | grep vdsm
vdsm-python-4.12.1-2.el6.x86_64
vdsm-xmlrpc-4.12.1-2.el6.noarch
vdsm-4.12.1-2.el6.x86_64
vdsm-cli-4.12.1-2.el6.noarch
vdsm-python-cpopen-4.12.1-2.el6.x86_64
So I created a VM with the following settings through webadmin portal:
Memory 2048MB, Total Virtual CPUs: 2
Operating System "Red Hat Enterprise Linux 6.x x64"
Console Protocol VNC
Boot Options: Attach CD: CentOS 6.4-x86_64-LiveCD.os
All other values were left on default.
I created and attached a 10 GB virtual disk (VirtIO)
and a VirtIO nic connected to default "ovirtmgmt".
When I try to start this vm via Webadmin I get:
VM TestSven_v3_Test1 was started by admin@internal (Host: server3).
VM TestSven_v3_Test1 is down. Exit message: internal error process
exited while connecting to monitor: Supported machines are: pc RHEL
6.4.0 PC (alias of rhel6.4.0) rhel6.4.0 RHEL 6.4.0 PC (default)
rhel6.3.0 RHEL 6.3.0 PC rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC
rhel6.0.0 RHEL 6.0.0 PC rhel5.5.0 RHEL 5.5.0 PC rhel5.4.4 RHEL 5.4.4 PC
rhel5.4.0 RHEL 5.4.0 PC .
Failed to run VM TestSven_v3_Test1 on Host server3
Please let me know what logs you need.
On older vdsm-versions (ovirt-node 2.6.1., different datacenter, same
mangementnode) everything works fine (creating and starting vms).
The same VM exported via export-domain to this datacenter fails with the
same error.
Thanks in advance
Sven
PS: The iso-domain resides on the management node.
On 07.10.2013 19:07, Itamar Heim wrote:
> On 10/07/2013 06:55 PM, Sven Kieske wrote:
>> Hi,
>>
>> thanks again for the answer, we were able to install ovirt-node onto
>> centos 6.4 minimal successfully!
> to avoid confusion, we'd call this a "host" and install vdsm onto it.
> we call ovirt-node only the trimmed down one.
>
> mike/fabian - which centos is ovirt-node based of? this seems 6.2, not 6.4?
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
2:18 p.m.
Hi,
I can confirm that this fix works, thanks!
Shouldn't this small patch get backported for version 3.2?
It doesn't seem to be much work?
Regards
Sven
9:46 p.m.
On 10/08/2013 02:18 PM, Sven Kieske wrote:
Hi,
I can confirm that this fix works, thanks!
Shouldn't this small patch get backported for version 3.2?
this isn't "the patch". its the workaround.
before .el6 support was added to ovirt, it only supported fedora out of
the box, and for .el6 you had to run this config change.
(3.2.0 was released fedora only iirc. 3.2.1 added .el6 support and
requires this one liner workaround).
in 3.3 we added automatic detection of the emulation level, as reported
by the first host added to the cluster.
It doesn't seem to be much work?
that's a series of 7 patches...
3.3 should have this behavior (detect fedora or rhel emulation level by
first host) automatically.
Regards
Sven
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3:19 p.m.
Am Montag, den 07.10.2013, 20:07 +0300 schrieb Itamar Heim:
On 10/07/2013 06:55 PM, Sven Kieske wrote:
> Hi,
>
> thanks again for the answer, we were able to install ovirt-node onto
> centos 6.4 minimal successfully!
to avoid confusion, we'd call this a "host" and install vdsm onto it.
we call ovirt-node only the trimmed down one.
>
> On 07.10.2013 11:07, Itamar Heim wrote:
>> yes.
>> ovirt supports both the "slimmed down" ovirt-node, or full blown
hosts.
>>
>>
>> it will always install latest versions it finds in the repos. they
>> should all be backward compatible.
>>
>>> We have some problems with 3.0.1 compute nodes and 3.2 management
>>> nodes but the node-iso 2.6.1 runs well.
>
> I just wanted to add some information on the problems we ran into
> when we tried management version 3.2 with ovirt-node 3.0.1:
>
> We were able to register the computenode, but when we tried to deploy
> a new vm, which was CentOS based we got the following error:
>
> Unsupported OS-Version Supported machines are:
> pc RHEL 6.2.0 PC (alias of rhel6.2.0)
> rhel6.2.0 RHEL 6.2.0 PC (default)
mike/fabian - which centos is ovirt-node based of? this seems 6.2, not 6.4?
The latest el6 build is based on CentOS 6.4.
- fabian
> rhel6.1.0 RHEL 6.1.0 PC
> rhel6.0.0 RHEL 6.0.0 PC
> rhel5.5.0 RHEL 5.5.0 PC
> rhel5.4.4 RHEL 5.4.4 PC
> rhel5.4.0 RHEL 5.4.0 PC
>
> Maybe you can shed some light on this?
> Unfortunately I can't provide any logs from the host side as these got
> replaced with ovirt node 2.6.1, but I can dig into the management-logs
> if you need additional information.
>
> Thanks
> Sven
>
3869
days inactive
3875
days old
13 comments
6 participants
participants (6)
-
Allen Belletti -
Fabian Deutsch -
Gianluca Cecchi -
Itamar Heim -
Sven Kieske -
Yuriy Demchenko