[ovirt-users] hosted-engine --deploy using vmfex, not bridged mode ?
Hi All, I'm starting to review/test ovirt to see if its suitable to use in our organisation. I'm following some guides but I'm having trouble with the hosted-engine --deploy section. I want to use VM-FEX to setup this initial host, as when I go bridged mode it breaks the networking on the host and I am unable to configure/correctly setup everything. Is there a way I can perform the hosted-engine setup using this method of telling it to use a vm-fex defined network pool? I might need to configure this myself before running hosted-engine deploy.. which is fine but I can't touch or edit the virsh settings as there's a password - and I'm not sure how to get that to modify the networking myself after the initial setup. FYI - this is the guide I'm following, as we are interested in the gluster replication (http://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/) Any suggestions/tips would be appreciated. Regards David This email and any attachments may contain confidential and proprietary information of Blackboard that is for the sole use of the intended recipient. If you are not the intended recipient, disclosure, copying, re-distribution or other use of any of this information is strictly prohibited. Please immediately notify the sender and delete this transmission if you received this email in error. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] AAA/ldap/3.6 Issues - WARNING [ovirt-engine-extension-aaa-ldap.authn::LDAP-authn] Cannot initialize LDAP framework, deferring initialization.
Hey, I'm running into an issue which I'm not sure where to go from here. I'm trying to use LDAP authentication and am following the setup guide from here https://gerrit.ovirt.org/gitweb?p=ovirt-engine-extension-aaa-ldap.git;a=blob;f=README;hb=HEAD I have tested the ldap credentials manually using ldapsearch, and I get results as expected with the user I'm binding with - but when I use ovirt I run into problems. I hope someone can provide me some guidance, or other things to try! DNS resolves; Can manually do ldap lookups using ldapsearch Can telnet to hostname 389 successfully Below are the steps taken; # ovirt-engine-extension-aaa-ldap-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-extension-aaa-ldap-setup.conf.d/10-packaging.conf'] Log file: /tmp/ovirt-engine-extension-aaa-ldap-setup-20160115151231-o0d7hp.log Version: otopi-1.4.0 (otopi-1.4.0-1.el7.centos) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment customization Welcome to LDAP extension configuration program Please specify profile name that will be visible to users: LDAP Available LDAP implementations: 1 - 389ds 2 - 389ds RFC-2307 Schema 3 - Active Directory 4 - IPA 5 - Novell eDirectory RFC-2307 Schema 6 - OpenLDAP RFC-2307 Schema 7 - OpenLDAP Standard Schema 8 - Oracle Unified Directory RFC-2307 Schema 9 - RFC-2307 Schema (Generic) 10 - RHDS 11 - RHDS RFC-2307 Schema 12 - iPlanet Please select: 1 NOTE: It is highly recommended to use DNS resolution for LDAP server. If for some reason you intend to use hosts or plain address disable DNS usage. Use DNS (Yes, No) [Yes]: Available policy method: 1 - Single server 2 - DNS domain LDAP SRV record 3 - Round-robin between multiple hosts 4 - Failover between multiple hosts Please select: 1 Please enter host address: ldap-test-server [ INFO ] Trying to resolve host 'ldap-test-server' NOTE: It is highly recommended to use secure protocol to access the LDAP server. Protocol startTLS is the standard recommended method to do so. Only in cases in which the startTLS is not supported, fallback to non standard ldaps protocol. Use plain for test environments only. Please select protocol to use (startTLS, ldaps, plain) [startTLS]: plain [ INFO ] Connecting to LDAP using 'ldap://ldap-test-server:389' [ INFO ] Connection succeeded Enter search user DN (empty for anonymous): uid=ovirt-test,ou=Special Users,dc=test Enter search user password: [ INFO ] Attempting to bind using 'uid=ovirt-test,ou=Special Users,dc=test' [ INFO ] Stage: Setup validation NOTE: It is highly recommended to test drive the configuration before applying it into engine. Perform at least one Login sequence and one Search sequence. Select test sequence to execute (Done, Abort, Login, Search) [Abort]: Login Enter search user name: uid=ovirt-test,ou=Special Users,dc=test Enter search user password: [ INFO ] Executing login sequence... Login output: 2016-01-15 15:13:25 INFO 2016-01-15 15:13:25 INFO Initialization 2016-01-15 15:13:25 INFO 2016-01-15 15:13:25 INFOLoading extension 'LDAP-authn' 2016-01-15 15:13:25 INFOExtension 'LDAP-authn' loaded 2016-01-15 15:13:25 INFOLoading extension 'LDAP-authz' 2016-01-15 15:13:25 INFOExtension 'LDAP-authz' loaded 2016-01-15 15:13:25 INFOInitializing extension 'LDAP-authn' 2016-01-15 15:13:25 INFO [ovirt-engine-extension-aaa-ldap.authn::LDAP-authn] Creating LDAP pool 'authz' 2016-01-15 15:13:25 WARNING [ovirt-engine-extension-aaa-ldap.authn::LDAP-authn] Cannot initialize LDAP framework, deferring initialization. Error: An error occurred while attempting to connect to server ldap-test-server:389: java.io.IOException: LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap-test-server/::xxx:x::xx:xx48:dcc0:389: java.net.UnknownHostException: ldap-test-server') caused by LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to establish a connection to server ldap-test-server/::xxx:x::xx:xx48:dcc0:389: java.net.UnknownHostExcep
Re: [ovirt-users] AAA/ldap/3.6 Issues - WARNING [ovirt-engine-extension-aaa-ldap.authn::LDAP-authn] Cannot initialize LDAP framework, deferring initialization.
Hi, Thanks for this information - I have managed to get further now. The missing key was IPv6 & using pool.default.socketfactory.resolver.supportIPv6 = true Regards David -Original Message- From: Ondra Machacek [mailto:omach...@redhat.com] Sent: Friday, January 15, 2016 19:57 To: David LeVene ; users@ovirt.org Subject: Re: [ovirt-users] AAA/ldap/3.6 Issues - WARNING [ovirt-engine-extension-aaa-ldap.authn::LDAP-authn] Cannot initialize LDAP framework, deferring initialization. Hi, if I read your logs correctly than you are using IPv6 and no IPv4, right? ovirt-engine-extension-aaa-ldap-setup was designed to be easy and support only very basic setups, so there is not support to properly configure it. If the above is true, you have two options, which should help you. 1) Do what you did below, and apply the configuration, then add to file: /etc/ovirt-engine/aaa/ldap-test-server.properties this line: pool.default.socketfactory.resolver.supportIPv6 = true 2) In question: "Use DNS (Yes, No) [Yes]:" answer "no" Hope it will help you, Ondra On 01/15/2016 05:50 AM, David LeVene wrote: > Hey, > > I'm running into an issue which I'm not sure where to go from here. > I'm trying to use LDAP authentication and am following the setup guide > from here > > https://gerrit.ovirt.org/gitweb?p=ovirt-engine-extension-aaa-ldap.git; > a=blob;f=README;hb=HEAD > > I have tested the ldap credentials manually using ldapsearch, and I > get results as expected with the user I'm binding with - but when I > use ovirt I run into problems. > > I hope someone can provide me some guidance, or other things to try! > > DNS resolves; > > Can manually do ldap lookups using ldapsearch > > Can telnet to hostname 389 successfully > > Below are the steps taken; > > # ovirt-engine-extension-aaa-ldap-setup > > [ INFO ] Stage: Initializing > > [ INFO ] Stage: Environment setup > >Configuration files: > ['/etc/ovirt-engine-extension-aaa-ldap-setup.conf.d/10-packaging.conf' > ] > >Log file: > /tmp/ovirt-engine-extension-aaa-ldap-setup-20160115151231-o0d7hp.log > >Version: otopi-1.4.0 (otopi-1.4.0-1.el7.centos) > > [ INFO ] Stage: Environment packages setup > > [ INFO ] Stage: Programs detection > > [ INFO ] Stage: Environment customization > >Welcome to LDAP extension configuration program > >Please specify profile name that will be visible to users: > LDAP > >Available LDAP implementations: > > 1 - 389ds > > 2 - 389ds RFC-2307 Schema > > 3 - Active Directory > > 4 - IPA > > 5 - Novell eDirectory RFC-2307 Schema > > 6 - OpenLDAP RFC-2307 Schema > > 7 - OpenLDAP Standard Schema > > 8 - Oracle Unified Directory RFC-2307 Schema > > 9 - RFC-2307 Schema (Generic) > >10 - RHDS > >11 - RHDS RFC-2307 Schema > >12 - iPlanet > >Please select: 1 > >NOTE: > >It is highly recommended to use DNS resolution for LDAP server. > >If for some reason you intend to use hosts or plain address > disable DNS usage. > >Use DNS (Yes, No) [Yes]: > >Available policy method: > > 1 - Single server > > 2 - DNS domain LDAP SRV record > > 3 - Round-robin between multiple hosts > > 4 - Failover between multiple hosts > >Please select: 1 > >Please enter host address: ldap-test-server > > [ INFO ] Trying to resolve host 'ldap-test-server' > >NOTE: > >It is highly recommended to use secure protocol to access > the LDAP server. > >Protocol startTLS is the standard recommended method to do so. > >Only in cases in which the startTLS is not supported, > fallback to non standard ldaps protocol. > >Use plain for test environments only. > >Please select protocol to use (startTLS, ldaps, plain) > [startTLS]: plain > > [ INFO ] Connecting to LDAP using 'ldap://ldap-test-server:389' > > [ INFO ] Connection succeeded > >Enter search user DN (empty for anonymous): > uid=ovirt-test,ou=Special Users,dc=test > >Enter search user password: > > [ INFO ] Attempting to bind using 'uid=ovirt-test,ou=Special Users,dc=test' > > [ INFO ] Stage: Setup validation > >NOTE: > >It is highly
[ovirt-users] UCS Integration (vmfex/SRIOV)
Hey All,
I've got a test instance and would like to get vmfex working. I'm very new to
ovirt, so some of the basics are still new to me.
I currently have a 3 node setup which are all configured without vmfex, what
I'd like to do is convert the hosts one by one to use vmfex.
>From the UCS side of things it works and I'm presented with the SRIOV devices
>in the host.. but I can't get the network config in the ovirt admin setup..
I'm following this guide, but not getting very far...
http://www.ovirt.org/Features/UCS_Integration
This step says to do this, which is fine.. but when I do this I overwrite the
current attribute in there.
engine-config -s
CustomDeviceProperties='{type=interface;prop={vmfex=^[a-zA-Z0-9_.-]{2,32}$}}'
which is...
# engine-config -g CustomDeviceProperties
CustomDeviceProperties: version: 3.0
CustomDeviceProperties: version: 3.1
CustomDeviceProperties: version: 3.2
CustomDeviceProperties: version: 3.3
CustomDeviceProperties:
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
*)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.4
CustomDeviceProperties:
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
*)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.5
CustomDeviceProperties:
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
*)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.6
When I update it using the command above, it replaces it...
When I append the 2 together, I get see vmfex & prop in the ovirt-engine
(screen shot) side of things.. so can someone please check my command to ensure
I'm not missing something!
engine-config -s
CustomDeviceProperties='{type=interface;prop={vmfex=^[a-zA-Z0-9_.-]{2,32}$}}{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
*)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}}'
# engine-config -g CustomDeviceProperties
CustomDeviceProperties: version: 3.0
CustomDeviceProperties: version: 3.1
CustomDeviceProperties: version: 3.2
CustomDeviceProperties: version: 3.3
CustomDeviceProperties:
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
*)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.4
CustomDeviceProperties:
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
*)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.5
CustomDeviceProperties:
{type=interface;prop={vmfex=^[a-zA-Z0-9_.-]{2,32}$}}{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
*)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.6
[cid:image001.png@01D16989.E4952270]
As soon as I enable vmfex on a host that was previously working.. it stops
working and the network no longer works on the host... (this is not using any
of the config above.. just enabled the vmfex in the UCS manager)
What is the "correct" way to bring a Host in ovirt using vmfex?
Regards
David
This email and any attachments may contain confidential and proprietary
information of Blackboard that is for the sole use of the intended recipient.
If you are not the intended recipient, disclosure, copying, re-distribution or
other use of any of this information is strictly prohibited. Please immediately
notify the sender and delete this transmission if you received this email in
error.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] UCS Integration (vmfex/SRIOV)
Hi Michael,
Thanks for this information - it's great, the guide should be updated on the
ovirt webpage to reflect the information you've provided below.
Just to hopefully help someone else out in the future - we had only 1 vNIC
defined in the UCS Service Profile, this caused problems when we enabled
dynamic vnic's on that host.
The resolution was leave the initial interface as it is.. and as a management
interface and setup another interface for the dynamic vnics. Ensure that your
"vNIC/vHBA Placement" doesn't change either!
[cid:image001.png@01D16A5D.E23F0A20]
So in this case eth0 = ovirtmgmt bridge, and ovirt device is the vNICs.
When the system reboots after this change I’ve lost my bridge and vdsmd failed
to start.
I manually setup the first interface again so I can talk to it again and I’ve
even setup the bridge but I can’t get it working again? Below is what I see
in the logs. I’ve even tried a re-installation(ovirt maint/reinstall) but no
joy..
I’ve managed to get this working on 1 host.. but no idea what I did that was
different!?.. If I remove the vNIC ovirt it starts working as expected - where
can I find out some more information on what vdsm is doing?
systemd: Started Auxiliary vdsm service for running helper functions as root.
systemd: Starting Auxiliary vdsm service for running helper functions as root...
systemd: Starting Virtualization daemon...
journal: libvirt version: 1.2.17, package: 13.el7_2.2 (CentOS BuildSystem
<http://bugs.centos.org>, 2015-12-09-13:08:22, worker1.bsys.centos.org)
journal: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so not
accessible
systemd: Started Virtualization daemon.
systemd: Starting Virtual Desktop Server Manager network restoration...
vdsm-tool: Traceback (most recent call last):
vdsm-tool: File "/usr/share/vdsm/vdsm-restore-net-config", line 425, in
vdsm-tool: restore(args)
vdsm-tool: File "/usr/share/vdsm/vdsm-restore-net-config", line 388, in restore
vdsm-tool: unified_restoration()
vdsm-tool: File "/usr/share/vdsm/vdsm-restore-net-config", line 110, in
unified_restoration
vdsm-tool: _remove_networks_in_running_config()
vdsm-tool: File "/usr/share/vdsm/vdsm-restore-net-config", line 195, in
_remove_networks_in_running_config
vdsm-tool: _inRollback=True)
vdsm-tool: File "/usr/share/vdsm/network/api.py", line 932, in setupNetworks
vdsm-tool: "system" % network)
vdsm-tool: network.errors.ConfigNetworkError: (27, "Cannot delete network
'ovirtmgmt': It doesn't exist in the system")
vdsm-tool: Traceback (most recent call last):
vdsm-tool: File "/usr/bin/vdsm-tool", line 219, in main
vdsm-tool: return tool_command[cmd]["command"](*args)
vdsm-tool: File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py",
line 41, in restore_command
vdsm-tool: exec_restore(cmd)
vdsm-tool: File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py",
line 54, in exec_restore
vdsm-tool: raise EnvironmentError('Failed to restore the persisted networks')
vdsm-tool: EnvironmentError: Failed to restore the persisted networks
systemd: vdsm-network.service: main process exited, code=exited,
status=1/FAILURE
systemd: Failed to start Virtual Desktop Server Manager network restoration.
systemd: Dependency failed for Virtual Desktop Server Manager.
systemd: Dependency failed for MOM instance configured for VDSM purposes.
systemd: Job mom-vdsm.service/start failed with result 'dependency'.
systemd: Job vdsmd.service/start failed with result 'dependency'.
systemd: Unit vdsm-network.service entered failed state.
systemd: vdsm-network.service failed.
systemd-logind: Removed session 5.
Cheers
David
-Original Message-
From: Michael Burman [mailto:mbur...@redhat.com]
Sent: Wednesday, February 17, 2016 16:56
To: David LeVene
mailto:david.lev...@blackboard.com>>
Cc: users@ovirt.org<mailto:users@ovirt.org>
Subject: Re: [ovirt-users] UCS Integration (vmfex/SRIOV)
HI David)
If everything configured properly on your UCS side and you have a working Port
Profile id/name your next steps should be:
1) Run for example:
engine-config -s
CustomDeviceProperties="{type=interface;prop={ifacemacspoof=^(true|false)$;queues=[1-9][0-9]*;vmfex=^[a-zA-Z0-9_.-]{2,32}$;SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
*)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}}" --cver=3.5
- Restart your ovirt-engine service
- with --cver=3.5 you can specify your cluster version level. ^^
- If you don't want that it will overwrite your current attributes, you have to
send them all as well(like on my example above). ^^
2) Install vdsm-hook-vmfex-dev on your nodes
3) In ovirt engine you can verify that host have the ho
Re: [ovirt-users] UCS Integration (vmfex/SRIOV)
So I found some additional logs.. and from what I understand it’s trying to
delete the ovirtmgmt network from libvirt setup.. but there’s no network
configs in there..
ConfigNetworkError: (27, "Cannot delete network 'ovirtmgmt': It doesn't exist
in the system")
restore-net::DEBUG::2016-02-18
15:53:01,883::libvirtconnection::160::root::(get) trying to connect libvirt
restore-net::INFO::2016-02-18
15:53:02,090::vdsm-restore-net-config::86::root::(_restore_sriov_numvfs) SRIOV
network device which is not persisted found at: :07:00.0.
restore-net::INFO::2016-02-18
15:53:02,090::vdsm-restore-net-config::385::root::(restore) starting network
restoration.
restore-net::DEBUG::2016-02-18
15:53:02,090::vdsm-restore-net-config::193::root::(_remove_networks_in_running_config)
Removing all networks ({'ovirtmgmt': {'remove': True}}) and bonds ({}) in
running config.
restore-net::DEBUG::2016-02-18
15:53:02,091::api::886::setupNetworks::(setupNetworks) Setting up network
according to configuration: networks:{'ovirtmgmt': {'remove': True}},
bondings:{}, options:{'_inRollback': True, 'connectivityCheck': False}
restore-net::DEBUG::2016-02-18 15:53:02,091::api::890::root::(setupNetworks)
Validating configuration
restore-net::DEBUG::2016-02-18
15:53:02,239::api::900::setupNetworks::(setupNetworks) Applying...
restore-net::INFO::2016-02-18
15:53:02,239::netconfpersistence::73::root::(setBonding) Adding bond0({'nics':
[], 'options': 'mode=0'})
restore-net::ERROR::2016-02-18 15:53:02,240::__init__::58::root::(__exit__)
Failed rollback transaction last known good network.
Traceback (most recent call last):
File "/usr/share/vdsm/network/api.py", line 932, in setupNetworks
"system" % network)
ConfigNetworkError: (27, "Cannot delete network 'ovirtmgmt': It doesn't exist
in the system")
restore-net::ERROR::2016-02-18
15:53:02,240::vdsm-restore-net-config::393::root::(restore) unified restoration
failed.
Traceback (most recent call last):
File "/usr/share/vdsm/vdsm-restore-net-config", line 388, in restore
unified_restoration()
File "/usr/share/vdsm/vdsm-restore-net-config", line 110, in
unified_restoration
_remove_networks_in_running_config()
File "/usr/share/vdsm/vdsm-restore-net-config", line 195, in
_remove_networks_in_running_config
_inRollback=True)
File "/usr/share/vdsm/network/api.py", line 932, in setupNetworks
"system" % network)
ConfigNetworkError: (27, "Cannot delete network 'ovirtmgmt': It doesn't exist
in the system")
So.. I manually edited the /etc/sysconfig/network-scripts and setup the device
& bridge as expected.. but vdsm didn’t like it.. it was still trying to delete
the ovirtmgmt device.
What I ended up doing in the end is defining the network in virsh (creating
myself an account via saslpasswd2 -a libvirt USERNAME) then creating the
ovirtmgmt bridge
# cat vdsm-ovirtmgmt.xml
vdsm-ovirtmgmt
#virsh net-define vdsm-ovirtmgmt.xml
#virsh net-start vdsm-ovirtmgmt
Something still wasn’t right here.. so I ended up rebooting the host… and then
it was working.. I’m still not entirely sure what I did to fix it.. but it’s
working now…
I’ll continue on the journey and keep this thread updated incase anyone else
runs into the same issues!
Cheers
David
From: David LeVene
Sent: Thursday, February 18, 2016 15:22
To: 'Michael Burman'
Cc: users@ovirt.org
Subject: RE: [ovirt-users] UCS Integration (vmfex/SRIOV)
Hi Michael,
Thanks for this information - it's great, the guide should be updated on the
ovirt webpage to reflect the information you've provided below.
Just to hopefully help someone else out in the future - we had only 1 vNIC
defined in the UCS Service Profile, this caused problems when we enabled
dynamic vnic's on that host.
The resolution was leave the initial interface as it is.. and as a management
interface and setup another interface for the dynamic vnics. Ensure that your
"vNIC/vHBA Placement" doesn't change either!
[cid:image001.png@01D16A64.FCDB9D60]
So in this case eth0 = ovirtmgmt bridge, and ovirt device is the vNICs.
When the system reboots after this change I’ve lost my bridge and vdsmd failed
to start.
I manually setup the first interface again so I can talk to it again and I’ve
even setup the bridge but I can’t get it working again? Below is what I see
in the logs. I’ve even tried a re-installation(ovirt maint/reinstall) but no
joy..
I’ve managed to get this working on 1 host.. but no idea what I did that was
different!?.. If I remove the vNIC ovirt it starts working as expected - where
can I find out some more information on what vdsm is doing?
systemd: Started Auxiliary vdsm service for running hel
Re: [ovirt-users] UCS Integration (vmfex/SRIOV)
Hi Michael,
I've made progress, but it's still not 100% working but I'm nearly there. As
this is currently an investigation/side project I haven't had time to progress
further.
I did setup the 2 vNIC's in the UCS and that's working fine, and my setup isn't
far off of what you have shown me in your screen shots (really helpful,
thankyou!)
And I'll post again if I come across any further issues that I get stuck on.
Thanks again for your help so far.
Regards
David
-Original Message-
From: Michael Burman [mailto:mbur...@redhat.com]
Sent: Monday, February 22, 2016 20:20
To: David LeVene
Cc: users@ovirt.org; Dan Kenigsberg
Subject: Re: [ovirt-users] UCS Integration (vmfex/SRIOV)
Hi David,
I hope that everything working for you)
From your description it seems like you have only 1 vNIC on your UCS blade and
that it is a problem. You should enable an extra vNIC on your UCS blade(service
profile).
I'm not sure i understood what exactly happened on your setup, but i think it
is because you have only 1 vNIC and you trying to use it as the management
network and the vmfex hook.
you should have 1 vNIC for the management network --> eth0=ovirtmgmt and 1 vNIC
for the network with a vmfex profile --> eth1='vmfex network'(network with
vmfex=PortProfile)
Attaching screenshots as an example of how it should look like.
Michael B
- Original Message -
From: "David LeVene"
To: "Michael Burman"
Cc: users@ovirt.org
Sent: Thursday, February 18, 2016 7:52:25 AM
Subject: RE: [ovirt-users] UCS Integration (vmfex/SRIOV)
So I found some additional logs.. and from what I understand it’s trying to
delete the ovirtmgmt network from libvirt setup.. but there’s no network
configs in there..
ConfigNetworkError: (27, "Cannot delete network 'ovirtmgmt': It doesn't exist
in the system")
restore-net::DEBUG::2016-02-18
15:53:01,883::libvirtconnection::160::root::(get) trying to connect libvirt
restore-net::INFO::2016-02-18
15:53:02,090::vdsm-restore-net-config::86::root::(_restore_sriov_numvfs) SRIOV
network device which is not persisted found at: :07:00.0.
restore-net::INFO::2016-02-18
15:53:02,090::vdsm-restore-net-config::385::root::(restore) starting network
restoration.
restore-net::DEBUG::2016-02-18
15:53:02,090::vdsm-restore-net-config::193::root::(_remove_networks_in_running_config)
Removing all networks ({'ovirtmgmt': {'remove': True}}) and bonds ({}) in
running config.
restore-net::DEBUG::2016-02-18
15:53:02,091::api::886::setupNetworks::(setupNetworks) Setting up network
according to configuration: networks:{'ovirtmgmt': {'remove': True}},
bondings:{}, options:{'_inRollback': True, 'connectivityCheck': False}
restore-net::DEBUG::2016-02-18 15:53:02,091::api::890::root::(setupNetworks)
Validating configuration
restore-net::DEBUG::2016-02-18
15:53:02,239::api::900::setupNetworks::(setupNetworks) Applying...
restore-net::INFO::2016-02-18
15:53:02,239::netconfpersistence::73::root::(setBonding) Adding bond0({'nics':
[], 'options': 'mode=0'})
restore-net::ERROR::2016-02-18 15:53:02,240::__init__::58::root::(__exit__)
Failed rollback transaction last known good network.
Traceback (most recent call last):
File "/usr/share/vdsm/network/api.py", line 932, in setupNetworks
"system" % network)
ConfigNetworkError: (27, "Cannot delete network 'ovirtmgmt': It doesn't exist
in the system")
restore-net::ERROR::2016-02-18
15:53:02,240::vdsm-restore-net-config::393::root::(restore) unified restoration
failed.
Traceback (most recent call last):
File "/usr/share/vdsm/vdsm-restore-net-config", line 388, in restore
unified_restoration()
File "/usr/share/vdsm/vdsm-restore-net-config", line 110, in
unified_restoration
_remove_networks_in_running_config()
File "/usr/share/vdsm/vdsm-restore-net-config", line 195, in
_remove_networks_in_running_config
_inRollback=True)
File "/usr/share/vdsm/network/api.py", line 932, in setupNetworks
"system" % network)
ConfigNetworkError: (27, "Cannot delete network 'ovirtmgmt': It doesn't exist
in the system")
So.. I manually edited the /etc/sysconfig/network-scripts and setup the device
& bridge as expected.. but vdsm didn’t like it.. it was still trying to delete
the ovirtmgmt device.
What I ended up doing in the end is defining the network in virsh (creating
myself an account via saslpasswd2 -a libvirt USERNAME) then creating the
ovirtmgmt bridge # cat vdsm-ovirtmgmt.xml
vdsm-ovirtmgmt
#virsh net-define vdsm-ovirtmgmt.xml
#virsh net-start vdsm-ovirtmgmt
Something still wasn’t right here.. so I ended up rebooting the host… and then
it was working.. I’m still not entirely sure what I did t
Re: [ovirt-users] UCS Integration (vmfex/SRIOV)
Hi Michael,
Something weird is happening with the networking on the vmhost.
I run the setup and vdsmd comes up ok.. I see ovirtmgmt connected to the non
vmfex device and the vmfex device is unconfifuged as it’s a new host.
When I reboot the host.. it fails to start vdsm and I get errors like this -
and its deleted all related networking information that was present before.
Feb 25 14:39:50 test_host_c systemd: Starting Virtual Desktop Server Manager
network restoration...
Feb 25 14:39:51 test_host_c vdsm-tool: Traceback (most recent call last):
Feb 25 14:39:51 test_host_c vdsm-tool: File
"/usr/share/vdsm/vdsm-restore-net-config", line 425, in
Feb 25 14:39:51 test_host_c vdsm-tool: restore(args)
Feb 25 14:39:51 test_host_c vdsm-tool: File
"/usr/share/vdsm/vdsm-restore-net-config", line 388, in restore
Feb 25 14:39:51 test_host_c vdsm-tool: unified_restoration()
Feb 25 14:39:51 test_host_c vdsm-tool: File
"/usr/share/vdsm/vdsm-restore-net-config", line 110, in unified_restoration
Feb 25 14:39:51 test_host_c vdsm-tool: _remove_networks_in_running_config()
Feb 25 14:39:51 test_host_c vdsm-tool: File
"/usr/share/vdsm/vdsm-restore-net-config", line 195, in
_remove_networks_in_running_config
Feb 25 14:39:51 test_host_c vdsm-tool: _inRollback=True)
Feb 25 14:39:51 test_host_c vdsm-tool: File "/usr/share/vdsm/network/api.py",
line 932, in setupNetworks
Feb 25 14:39:51 test_host_c vdsm-tool: "system" % network)
Feb 25 14:39:51 test_host_c vdsm-tool: network.errors.ConfigNetworkError: (27,
"Cannot delete network 'ovirtmgmt': It doesn't exist in the system")
Feb 25 14:39:51 test_host_c vdsm-tool: Traceback (most recent call last):
Feb 25 14:39:51 test_host_c vdsm-tool: File "/usr/bin/vdsm-tool", line 219, in
main
Feb 25 14:39:51 test_host_c vdsm-tool: return
tool_command[cmd]["command"](*args)
Feb 25 14:39:51 test_host_c vdsm-tool: File
"/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line 41, in
restore_command
Feb 25 14:39:51 test_host_c vdsm-tool: exec_restore(cmd)
Feb 25 14:39:51 test_host_c vdsm-tool: File
"/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line 54, in
exec_restore
Feb 25 14:39:51 test_host_c vdsm-tool: raise EnvironmentError('Failed to
restore the persisted networks')
Feb 25 14:39:51 test_host_c vdsm-tool: EnvironmentError: Failed to restore the
persisted networks
Feb 25 14:39:51 test_host_c systemd: vdsm-network.service: main process exited,
code=exited, status=1/FAILURE
Feb 25 14:39:51 test_host_c systemd: Failed to start Virtual Desktop Server
Manager network restoration.
Feb 25 14:39:51 test_host_c systemd: Dependency failed for Virtual Desktop
Server Manager.
Feb 25 14:39:51 test_host_c systemd: Dependency failed for MOM instance
configured for VDSM purposes.
Feb 25 14:39:51 test_host_c systemd: Job mom-vdsm.service/start failed with
result 'dependency'.
Feb 25 14:39:51 test_host_c systemd: Job vdsmd.service/start failed with result
'dependency'.
Feb 25 14:39:51 test_host_c systemd: Unit vdsm-network.service entered failed
state.
Feb 25 14:39:51 test_host_c systemd: vdsm-network.service failed.
Any ideas?
Cheers
David
-Original Message-
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of
David LeVene
Sent: Tuesday, February 23, 2016 09:13
To: Michael Burman
Cc: users@ovirt.org
Subject: Re: [ovirt-users] UCS Integration (vmfex/SRIOV)
Hi Michael,
I've made progress, but it's still not 100% working but I'm nearly there. As
this is currently an investigation/side project I haven't had time to progress
further.
I did setup the 2 vNIC's in the UCS and that's working fine, and my setup isn't
far off of what you have shown me in your screen shots (really helpful,
thankyou!)
And I'll post again if I come across any further issues that I get stuck on.
Thanks again for your help so far.
Regards
David
-Original Message-
From: Michael Burman [mailto:mbur...@redhat.com]
Sent: Monday, February 22, 2016 20:20
To: David LeVene
Cc: users@ovirt.org; Dan Kenigsberg
Subject: Re: [ovirt-users] UCS Integration (vmfex/SRIOV)
Hi David,
I hope that everything working for you)
From your description it seems like you have only 1 vNIC on your UCS blade and
that it is a problem. You should enable an extra vNIC on your UCS blade(service
profile).
I'm not sure i understood what exactly happened on your setup, but i think it
is because you have only 1 vNIC and you trying to use it as the management
network and the vmfex hook.
you should have 1 vNIC for the management network --> eth0=ovirtmgmt and 1 vNIC
for the network with a vmfex profile --> eth1='vmfex network'(network with
vmfex=PortProfile)
Attaching screenshots as an example of how it should look like.
Michael B
- Original Message
Re: [ovirt-users] 3.6 looses network on reboot
Hi Dan,
I missed the email as the subject line changed!
So we use and run IPv6 in our network - not sure if this is related. The
Addresses are handed out via SLAAC so that would be where the IPv6 address is
coming from.
My memory is a bit sketchy... but I think if I remove the vmfex/SRIOV vNIC and
only run with the one vNIC it works fine, it's when I bring the second NIC into
play with SRIOV the issues arise.
Answers inline.
-Original Message-
From: Dan Kenigsberg [mailto:dan...@redhat.com]
Sent: Tuesday, March 01, 2016 00:28
To: David LeVene
Cc: edwa...@redhat.com; users@ovirt.org
Subject: Re: [ovirt-users] 3.6 looses network on reboot
This sounds very bad. Changing the subject, so the wider, more problematic
issue is visible.
Did any other user see this behavior?
On Mon, Feb 29, 2016 at 06:27:46AM +0000, David LeVene wrote:
> Hi Dan,
>
> Answers as follows;
>
> # rpm -qa | grep -i vdsm
> vdsm-jsonrpc-4.17.18-1.el7.noarch
> vdsm-hook-vmfex-4.17.18-1.el7.noarch
> vdsm-infra-4.17.18-1.el7.noarch
> vdsm-4.17.18-1.el7.noarch
> vdsm-python-4.17.18-1.el7.noarch
> vdsm-yajsonrpc-4.17.18-1.el7.noarch
> vdsm-cli-4.17.18-1.el7.noarch
> vdsm-xmlrpc-4.17.18-1.el7.noarch
> vdsm-hook-vmfex-dev-4.17.18-1.el7.noarch
>
>
> There was in this folder ifcfg-ovirtmgnt bridge setup, and also
> route-ovirtmgnt & rule-ovirtmgmt.. but they were removed after the reboot.
>
> # ls -althr | grep ifcfg
> -rw-r--r--. 1 root root 254 Sep 16 21:21 ifcfg-lo -rw-r--r--. 1 root
> root 120 Feb 25 14:07 ifcfg-enp7s0f0 -rw-rw-r--. 1 root root 174 Feb
> 25 14:40 ifcfg-enp6s0
>
> I think I modified ifcfg-enp6s0 to get networking up again (eg was set to
> bridge.. but the bridge wasn't configured).. it was a few days ago.. if it's
> important I can reboot the box again to see what state it comes up with.
>
> # cat ifcfg-enp6s0
> BOOTPROTO="none"
> IPADDR="10.80.10.117"
> NETMASK="255.255.255.0"
> GATEWAY="10.80.10.1"
> DEVICE="enp6s0"
> HWADDR="00:25:b5:00:0b:4f"
> ONBOOT=yes
> PEERDNS=yes
> PEERROUTES=yes
> MTU=1500
>
> # cat ifcfg-enp7s0f0
> # Generated by VDSM version 4.17.18-1.el7
> DEVICE=enp7s0f0
> ONBOOT=yes
> MTU=1500
> HWADDR=00:25:b5:00:0b:0f
> NM_CONTROLLED=no
>
> # find /var/lib/vdsm/persistence
> /var/lib/vdsm/persistence
> /var/lib/vdsm/persistence/netconf
> /var/lib/vdsm/persistence/netconf.1456371473833165545
> /var/lib/vdsm/persistence/netconf.1456371473833165545/nets
> /var/lib/vdsm/persistence/netconf.1456371473833165545/nets/ovirtmgmt
>
> # cat
> /var/lib/vdsm/persistence/netconf.1456371473833165545/nets/ovirtmgmt
> {
> "nic": "enp6s0",
> "ipaddr": "10.80.10.117",
> "mtu": "1500",
> "netmask": "255.255.255.0",
> "STP": "no",
> "bridged": "true",
> "gateway": "10.80.10.1",
> "defaultRoute": true
> }
>
> Supervdsm log is attached.
Have you editted ifcfg-ovirtmgmt manually?
Nope
Can you somehow reproduce it, and share its content?
Yea, I should be able to reproduce it - just gotta fix it first (create the
networking manually and get VDSM on-line). Also it’s a side
project/investigation at the moment so time isn't on my side...
Would it help if I take an sosreport before and after? I don’t' mine emailing
these directly to yourself.
Do you have NetworkManager running? which version?
NM is disabled, but the version is...
# rpm -q NetworkManager
NetworkManager-1.0.6-27.el7.x86_64
# systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled;
vendor preset: enabled)
Active: inactive (dead)
It seems that Vdsm has two bugs: on boot, initscripts end up setting an
ipv6 address that Vdsm never requested
As mentioned above this would have come from SLAAC which we have setup in our
network
restore-net::INFO::2016-02-25
14:14:58,024::vdsm-restore-net-config::261::root::(_find_changed_or_missing)
ovirtmgmt is different or missing from persistent configuration. current:
{'nic': 'enp6s0', 'dhcpv6': False, 'ipaddr': '10.80.10.117', 'mtu': '1500',
'netmask': '255.255.255.0', 'bootproto': 'none', 'stp': False, 'bridged': True,
'ipv6addr': ['2400:7d00:110:3:225:b5ff:fe00:b4f/64'], 'gateway': '10.80.10.1',
'defaultRoute': True}, persisted: {u'nic': u'enp6s0', 'dhcpv6': False,
u'ipaddr': u'10.80.10.117&
Re: [ovirt-users] 3.6 looses network on reboot
-Original Message- From: Dan Kenigsberg [mailto:dan...@redhat.com] Sent: Thursday, March 03, 2016 17:36 To: David LeVene Cc: edwa...@redhat.com; sab...@redhat.com; users@ovirt.org Subject: Re: [ovirt-users] 3.6 looses network on reboot On Thu, Mar 03, 2016 at 12:54:25AM +, David LeVene wrote: > > Can you check our patches? They should resolve the problem we saw in > the > log: https://gerrit.ovirt.org/#/c/54237 (based on oVirt-3.6.3) > > -- I've manually applied the patch to the node that I was testing on > and the networking comes on-line correctly - now I'm encountering a > gluster issue with cannot find master domain. You are most welcome to share your logs (preferably on a different thread, to avoid confusion) --- Will do - I'll start a new thread after I've done some more investigation with the pointers given so far in this thread & by Nir in the next reply. > > Without the fixes, as a workaround, I would suggest (if possible) to disable > IPv6 on your host boot line and check if all works out for you. > -- Ok, but as I can manually apply the patch its good now. Do you know > what version are we hoping to have this put into as I won't perform an > ovirt/vdsm update until its part of the upstream RPM's The fix has been proposed to ovirt-3.6.4. I'll make sure it's accepted. -- Great thanks! > > Do you need IPv6 connectivity? If so, you'll need to use a vdsm hook or > another interface that is not controlled by oVirt. > -- Ideally I'd prefer not to have it, but the way our network has been > configured some hosts are IPv6 only, so at a min the guests need it.. > the hypervisors not so much. May I tap to what your IPv6 experience? (only if you feel confortable sharing this publically). What does these IPv6-only servers do? What does the guest do with them? -- The group I work with has implemented dual stack & if a v4 address is not required.. it's not given.. The IPv6 servers will run an application of some kind.. could be a webserver, anything really. As they sit behind LB's they handle the v4 If required. My personal opinion only: is that it's too much hassle for what its worth at this point and I'd prefer it if we only used v4/v6 address's at the entry points and v4 internally or all dual stack. -- My option is based on the fact that I've come across too many pieces of software that require tweaking, &/or additional configuration &/or special compilation to enable it. It also adds an addition layer of complication when troubleshooting applications if v6 isn't working and there's no v4 address to test on. -- A recent example.. downloads.ceph.com advertises v4 and v6 address. On an IPv6 only host it fails to connect to the repo because the v6 address fails.. and there's a V4 address so NAT64 isn't performed. This breaks yum. Workaround.. fd64::IPv4 Address. > > -- I've now hit an issue with it not starting up the master storage > gluster domain - as it’s a separate issue I'll review the mailing > lists & create a new item if its related.. I've attached the > supervdsm.log incase you can save me some time and point me in the > right direction! All I see is this MainProcess|jsonrpc.Executor/4::ERROR::2016-03-03 MainProcess|11:15:04,699::supervdsmServer::118::SuperVdsm.ServerCallback MainProcess|::(wrapper) Error in wrapper Traceback (most recent call last): File "/usr/share/vdsm/supervdsmServer", line 116, in wrapper res = func(*args, **kwargs) File "/usr/share/vdsm/supervdsmServer", line 531, in wrapper return func(*args, **kwargs) File "/usr/share/vdsm/gluster/cli.py", line 496, in volumeInfo xmltree = _execGlusterXml(command) File "/usr/share/vdsm/gluster/cli.py", line 108, in _execGlusterXml raise ge.GlusterCmdExecFailedException(rc, out, err) GlusterCmdExecFailedException: Command execution failed return code: 2 which tells me very little. Please share your vdsm.log and gluster logs (possibly /var/log/messages as well) to understand what has happened. Make sure to include sabose at redhat.com on the thread. In the past we heard that network disconnections causes glusterd to crash, so it might be the case again. -- I'll investigate further when I have time, and post again under a different topic. Cheers for the tips/logs to review. Regards, Dan. This email and any attachments may contain confidential and proprietary information of Blackboard that is for the sole use of the intended recipient. If you are not the intended recipient, disclosure, copying, re-distribution or other use of any of this information is strictly prohibited. Please immediately notify the sender and delete this transmission if you received this email in error. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] 3.6 looses network on reboot
Hi Nir, Thanks for your help. I’m going to start up another thread as to not pollute what this thread was initially about. I’ll test your patch, and I suspect it’s the gluster version that is causing the problem as I did update the host. When I create the thread I’ll make sure to include everyone already present (It might be a week or so, as my time Is limited atm) Cheers David From: Nir Soffer [mailto:nsof...@redhat.com] Sent: Thursday, March 03, 2016 17:59 To: Dan Kenigsberg ; Sahina Bose ; Ala Hino Cc: David LeVene ; users@ovirt.org Subject: Re: [ovirt-users] 3.6 looses network on reboot On Thu, Mar 3, 2016 at 9:06 AM, Dan Kenigsberg mailto:dan...@redhat.com>> wrote: > > On Thu, Mar 03, 2016 at 12:54:25AM +, David LeVene wrote: > > > > Can you check our patches? They should resolve the problem we saw in the > > log: https://gerrit.ovirt.org/#/c/54237 (based on oVirt-3.6.3) > > > > -- I've manually applied the patch to the node that I was testing on > > and the networking comes on-line correctly - now I'm encountering a > > gluster issue with cannot find master domain. > > You are most welcome to share your logs (preferably on a different > thread, to avoid confusion) > > > > > Without the fixes, as a workaround, I would suggest (if possible) to > > disable IPv6 on your host boot line and check if all works out for you. > > -- Ok, but as I can manually apply the patch its good now. Do you know > > what version are we hoping to have this put into as I won't perform an > > ovirt/vdsm update until its part of the upstream RPM's > > The fix has been proposed to ovirt-3.6.4. I'll make sure it's accepted. > > > > > Do you need IPv6 connectivity? If so, you'll need to use a vdsm hook or > > another interface that is not controlled by oVirt. > > -- Ideally I'd prefer not to have it, but the way our network has been > > configured some hosts are IPv6 only, so at a min the guests need it.. > > the hypervisors not so much. > > May I tap to what your IPv6 experience? (only if you feel confortable sharing > this publically). What does these IPv6-only servers do? What does the guest do > with them? > > > > > -- I've now hit an issue with it not starting up the master storage > > gluster domain - as it’s a separate issue I'll review the mailing > > lists & create a new item if its related.. I've attached the > > supervdsm.log incase you can save me some time and point me in the > > right direction! > > All I see is this > > MainProcess|jsonrpc.Executor/4::ERROR::2016-03-03 > 11:15:04,699::supervdsmServer::118::SuperVdsm.ServerCallback::(wrapper) Error > in wrapper > Traceback (most recent call last): > File "/usr/share/vdsm/supervdsmServer", line 116, in wrapper > res = func(*args, **kwargs) > File "/usr/share/vdsm/supervdsmServer", line 531, in wrapper > return func(*args, **kwargs) > File "/usr/share/vdsm/gluster/cli.py", line 496, in volumeInfo > xmltree = _execGlusterXml(command) > File "/usr/share/vdsm/gluster/cli.py", line 108, in _execGlusterXml > raise ge.GlusterCmdExecFailedException(rc, out, err) > GlusterCmdExecFailedException: Command execution failed > return code: 2 We have this logs before the exception: MainProcess|jsonrpc.Executor/3::DEBUG::2016-03-03 11:02:42,945::utils::669::root::(execCmd) /usr/bin/taskset --cpu-list 0-39 /usr/sbin/gluster --mode=script volume info --re mote-host=ovirtmount.test.lab data --xml (cwd None) The command looks correct MainProcess|jsonrpc.Executor/3::DEBUG::2016-03-03 11:02:43,024::utils::687::root::(execCmd) FAILED: = '\n'; = 2 gluster command line failed in an unhelpful way. (Adding Sahina) David, can you try to run this command manually on this host? maybe there is some --verbose flag revealing more info? You may also try a simpler command: gluster volume info --remote-host=ovirtmount.test.lab data Another issue you should check - gluster version on the hosts and on the gluster nodes *must* match - otherwise you should expect failures accessing gluster server. We have this patch for handling such errors gracefully - can you test it? https://gerrit.ovirt.org/53785 (Adding Ala) Nir This email and any attachments may contain confidential and proprietary information of Blackboard that is for the sole use of the intended recipient. If you are not the intended recipient, disclosure, copying, re-distribution or other use of any of this information is strictly prohibited. Please immediately notify the sender and delete this transmission if you received this email in error. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Configuring the SRIOV virsh device
Hey All, Still trying to work through this VMFEX stuff, and I know what I want the file to look like at the end.. but not sure how to achieve it from the doco written here http://www.ovirt.org/develop/developer-guide/vdsm/hook/vmfex/ and http://www.ovirt.org/develop/release-management/features/network/ucs-integration/ Currently my device looks like this # virsh -r net-dumpxml vdsm-SRIOV vdsm-SRIOV I want it looking like this, then the networking will be as it should be! A port group would be a vNIC Profile from the looks of things... vdsm-SRIOV <-- defined as a passthrough device, not a bridge < .. list of interfaces available to it which would need to be manually inputted as a hook> Cheers David This email and any attachments may contain confidential and proprietary information of Blackboard that is for the sole use of the intended recipient. If you are not the intended recipient, disclosure, copying, re-distribution or other use of any of this information is strictly prohibited. Please immediately notify the sender and delete this transmission if you received this email in error. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Losing IP config on host
Hi Rein, Not sure if you are using IPv6, but I ran into this issue it wouldn't configure things correctly. If I fixed it manually after a reboot it would fail again. There is a patch that is being released in ovirt 3.6.4 which resolves the issue I was having. Your issue might be related - http://lists.ovirt.org/pipermail/users/2016-March/038201.html which is fixed in https://gerrit.ovirt.org/#/c/54237 The RH guys will generally ask for your vdsm logs and maybe supervdsm (see the above post for more information on where they are located). Looking in these logs might guide you as well. Regards David -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Rein van Weerden Sent: Thursday, March 24, 2016 07:16 To: users@ovirt.org Subject: [ovirt-users] Losing IP config on host Hi All, When creating a new host i lose the ip configuration on the host while creating the interfaces. Please advice. Using: oVirt engine 3.6.3.4-1 on CentOS 7 oVirt engine SDK python 3.6.3.0 ->Rein. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users This email and any attachments may contain confidential and proprietary information of Blackboard that is for the sole use of the intended recipient. If you are not the intended recipient, disclosure, copying, re-distribution or other use of any of this information is strictly prohibited. Please immediately notify the sender and delete this transmission if you received this email in error. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] oVirt 3.6.4 / PXE guest boot issues
Hey All, Summary: ipxe fails to get DHCP address, but it works when I don't use ipxe eg from iso installer. I'm running into the same issue which is noted in this thread, but the workaround they used didn't seem to work for me. I only change the rom images on the 1 ovirt host, nothing else - but have since changed them back. There's a few differences to the environment I setup as well and am looking for any pointers. http://lists.ovirt.org/pipermail/users/2015-March/031690.html This is the config & a fresh build as of last week - so I'm using ovirt 3.6.4 1. All 3 physical hosts were built from a vanilla foreman server which does everything (TFTP, DNS, DHCP, Puppet, and Puppet CA) - this is the same server I'm trying to use for the guests, so I know it works for bare metal hosts. 2. Ovirt engine was installed using the rpm bundle/image (Cent OS7) 3. 3 Node ovirt setup very close to this guide - http://blogs-ramesh.blogspot.com.au/2016/01/ovirt-and-gluster-hyperconvergence.html 4. There is a VMFEX/SRIOV network setup in the oVirt config and this is what is being used to provision the guest VM's When I try and boot a host via PXE (have tried e1000 etc, but leaving as VirtIO driver) it fails to get the DHCP address, I can see the broadcast traffic hitting the foreman server, and the foreman server replying with an IP - but it isn't getting to the guest, or the packets are getting corrupted. The UCS is correctly identifying and seeing the MAC address, so that looks good as well from the VMFEX side of things. Tested the dhcp only component, so I grabbed an ISO and booted from a CD. The installer correctly got its DHCP address and proceed to install. Once the host was on-line it correctly got its IP via DHCP - So by this I've proven that a vm guest can correctly receive DHCP packets when using the VMFEX network. Open to any further suggestions - as when using this and a foreman server/katello satellite pxe booting is kinda important! Screenshot of iPXE boot version [cid:image001.png@01D18E9F.FE7AA5D0] Cheers David This email and any attachments may contain confidential and proprietary information of Blackboard that is for the sole use of the intended recipient. If you are not the intended recipient, disclosure, copying, re-distribution or other use of any of this information is strictly prohibited. Please immediately notify the sender and delete this transmission if you received this email in error. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
