- Users - oVirt List Archives

Multipath iSCSI with several IPs
by James Michels 04 Aug '16

04 Aug '16

Hello, I want to add an iSCSI based storage domain. For that I add a domain on the Storage tab with one of the IPs (say 10.10.10.1), but for failover purposes I'd like to use multipath to add a failover IP so if the first one fails, LUNs can be reached via the second (say 10.10.10.2). How can this be done in oVirt 4.0.1? I have not seen a way how to add the second IP for multipath purposes. Thank you James

5 10

iSCSI domain on 4kn drives
by Martijn Grendelman 04 Aug '16

04 Aug '16

Hi, Does oVirt support iSCSI storage domains on target LUNs using a block size of 4k? Best regards, Martijn Grendelman

2 1

Fwd: Multipath iSCSI with several IPs
by James Michels 04 Aug '16

04 Aug '16

Hi Dan, The way you describe it I should have 2 storage backends with 2 IPs for the same SAN backend, right? The problem I see is that when you create a disk for a VM, you assign it to only one storage domain... so if the first fails, how will oVirt know which one should use as failover? Thank you 2016-08-04 15:20 GMT+01:00 Dan Yasny <dyasny(a)gmail.com>: > Normally you > 1. enter the IP > 2. click discover > 3. login to whatever was found > 4. enter another IP instead of the first > 5. goto 2 > > On Thu, Aug 4, 2016 at 10:13 AM, James Michels < > karma.sometimes.hurts(a)gmail.com> wrote: > >> Hello, >> >> I want to add an iSCSI based storage domain. For that I add a domain on >> the Storage tab with one of the IPs (say 10.10.10.1), but for failover >> purposes I'd like to use multipath to add a failover IP so if the first one >> fails, LUNs can be reached via the second (say 10.10.10.2). >> >> How can this be done in oVirt 4.0.1? I have not seen a way how to add the >> second IP for multipath purposes. >> >> Thank you >> >> James >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> >

3 3

Migrate machines in unknown state?
by Nicolás 04 Aug '16

04 Aug '16

Hi, We're running oVirt 4.0.1 and today I found out that one of our hosts has all its VMs in an unknown state. I actually don't know how (and when) did this happen, but I'd like to restore service possibly without turning off these machines. The host is up, the VMs are up, 'qemu' process exists, no errors, it's just the VMs running on it that have a '?' where status is defined. Is it safe in this case to simply modify database and set those VM's status to 'up'? I remember having to do this a time ago when we faced storage issues, it didn't break anything back then. If not, is there a "safe" way to migrate those VMs to a different host and restart the host that marked them as unknown? Thanks. Nicolás

3 4

IP Address Stealing
by Bill Bill 03 Aug '16

03 Aug '16

--_000_CO2PR0801MB074357235FE75D8258FE4A0DA6070CO2PR0801MB0743_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGVsbG8sDQoNCkl0IGlzIHBvc3NpYmxlIHRvIHByZXZlbnQgYSBWTSBmcm9tIGFkZGluZyBhbiBJ UD8gRm9yIGV4YW1wbGUsIGlmIHdlIHByb3Zpc2lvbiBhIFZNIHdpdGggb25lIElQLCBpZiB0aGUg dXNlciBoYXMgcm9vdCBhY2Nlc3MgdGhleSBjYW4gc2ltcGx5IGFkZCByYW5kb20gSVDigJlzIGZy b20gd2l0aGluIHRoZSBzYW1lIHJhbmdlIGFzIHN1YiBpbnRlcmZhY2VzOiBldGgwOjAgZXRoMDox IGV0aDA6MiBzbyBvbiBhbmQgc28gZm9ydGguDQoNClN1Ym5ldHRpbmcgaXMgbm90IGlkZWFsIGlu IHRoaXMgc2l0dWF0aW9uIGJlY2F1c2UgaXTigJlzIGEgaHVnZSB3YXN0ZSBvZiBJUCBzcGFjZS4N Cg0K --_000_CO2PR0801MB074357235FE75D8258FE4A0DA6070CO2PR0801MB0743_ Content-Type: text/html; charset="utf-8" Content-ID: <C00F14679A68B0459E8C965B9187F1A9(a)sct-15-1-485-2-msonline-outlook-1173a.templateTenant> Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4 bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2 IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5 Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQouTXNv Q2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTt9DQpAcGFnZSBXb3JkU2Vj dGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEu MGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHls ZT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0iIzk1NEY3 MiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGVs bG8sPC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj bGFzcz0iTXNvTm9ybWFsIj5JdCBpcyBwb3NzaWJsZSB0byBwcmV2ZW50IGEgVk0gZnJvbSBhZGRp bmcgYW4gSVA/IEZvciBleGFtcGxlLCBpZiB3ZSBwcm92aXNpb24gYSBWTSB3aXRoIG9uZSBJUCwg aWYgdGhlIHVzZXIgaGFzIHJvb3QgYWNjZXNzIHRoZXkgY2FuIHNpbXBseSBhZGQgcmFuZG9tIElQ 4oCZcyBmcm9tIHdpdGhpbiB0aGUgc2FtZSByYW5nZSBhcyBzdWIgaW50ZXJmYWNlczogZXRoMDow IGV0aDA6MSBldGgwOjIgc28gb24gYW5kIHNvDQogZm9ydGguPC9wPg0KPHAgY2xhc3M9Ik1zb05v cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5TdWJuZXR0 aW5nIGlzIG5vdCBpZGVhbCBpbiB0aGlzIHNpdHVhdGlvbiBiZWNhdXNlIGl04oCZcyBhIGh1Z2Ug d2FzdGUgb2YgSVAgc3BhY2UuPC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9 ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7 LHNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwv aHRtbD4NCg== --_000_CO2PR0801MB074357235FE75D8258FE4A0DA6070CO2PR0801MB0743_--

1 0

Upgrade from 3.6 to 4.0
by ovirt＠timmi.org 03 Aug '16

03 Aug '16

Hi List, is there a special upgrade procedure to get from 3.6 to 4.0 of oVirt? Or it is just a normal upgrade procedure? I'm currently running oVirt 3.6.7 on CentOS 7. Best regards and thank you for the answer. Christoph

6 15

[ANN] oVirt 4.0.2 Third Release Candidate is now available
by Sandro Bonazzola 03 Aug '16

03 Aug '16

The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 4.0.2 for testing, as of August 3rd, 2016. This release is available now for: * Fedora 23 (tech preview) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 23 (tech preview) * oVirt Next Generation Node 4.0 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is the third release candidate of the second in a series of stabilization updates to the 4.0 series. 4.0.2 brings 21 enhancements and nearly 200 bugfixes, including 91 high or urgent severity fixes, on top of oVirt 4.0 series See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is available. [4] * A new oVirt Next Generation Node will be available soon [4]. * A new oVirt Engine Appliance is already available. * Mirrors[5] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 4.0.2 release highlights: http://www.ovirt.org/release/4.0.2/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.0.2/ [4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/ [5] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Unusable log in engine.log
by Fabrice Bacchella 03 Aug '16

03 Aug '16

In the engine.log, there are many line like that : grep '2016-08-03 13:00:46,371 INFO .org.ovirt.engine.core.vdsbroker.HostDevListByCapsVDSCommand. .org.ovirt.thread.pool-8-thread-16. .28054a0c. ' /var/log/ovirt-engine/engine.log | wc 1 8574 179635 1 line 8574 words 179635 characters. And at the INFO level. It's almost impossible to check logs with line like that. They should be : 1/at trace level 2/send to a dedicated file 3/don't be logged at all.

1 0

Upgrade to 4.0.1 failed with NPE on org.postgresql.jdbc.TypeInfoCache.getSQLType
by Fabrice Bacchella 03 Aug '16

03 Aug '16

I'm running on Centos 7, just upgraded to ovirt 4.01 using the procedure given in the release notes. But now I'm getting that in /var/log/ovirt-engine/engine.log: 2016-08-03 12:04:39,751 ERROR [org.ovirt.engine.core.bll.Backend] (ServerService Thread Pool -- 54) [] Error during initialization: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.ovirt.engine.core.vds broker.ResourceManager.init() on org.ovirt.engine.core.vdsbroker.ResourceManager@28b87a8e at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) [weld-core-impl-2.3.2.Final.jar:2.3.2.Final] at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) [weld-core-impl-2.3.2.Final.jar:2.3.2.Final] at org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) [weld-core-impl-2.3.2.Final.jar:2.3.2.Final] at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) [weld-core-impl-2.3.2.Final.jar:2.3.2.Final] at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) [weld-core-impl-2.3.2.Final.jar:2.3.2.Final] at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) [weld-core-impl-2.3.2.Final.jar:2.3.2.Final] at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141) [weld-core-impl-2.3.2.Final.jar:2.3.2.Final] at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) [weld-core-impl-2.3.2.Final.jar:2.3.2.Final] at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) [weld-core-impl-2.3.2.Final.jar:2.3.2.Final] ... Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_92] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_92] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_92] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92] at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:98) [weld-core-impl-2.3.2.Final.jar:2.3.2.Final] ... 82 more Caused by: java.lang.NullPointerException at org.postgresql.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:182) at org.postgresql.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:178) at org.postgresql.jdbc.PgDatabaseMetaData.getProcedureColumns(PgDatabaseMetaData.java:1259) at org.postgresql.jdbc.PgDatabaseMetaData.getProcedureColumns(PgDatabaseMetaData.java:1040) at org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.processProcedureColumns(GenericCallMetaDataProvider.java:353) [spring-jdbc.jar:4.2.4.RELEASE] at org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.initializeWithProcedureColumnMetaData(GenericCallMetaDataProvider.java:112) [spring-jdbc.jar:4.2.4.RELEASE] at org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory$1.processMetaData(CallMetaDataProviderFactory.java:133) [spring-jdbc.jar:4.2.4.RELEASE] at org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:299) [spring-jdbc.jar:4.2.4.RELEASE] at org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory.createMetaDataProvider(CallMetaDataProviderFactory.java:73) [spring-jdbc.jar:4.2.4.RELEASE] at org.springframework.jdbc.core.metadata.CallMetaDataContext.initializeMetaData(CallMetaDataContext.java:286) [spring-jdbc.jar:4.2.4.RELEASE] at org.springframework.jdbc.core.simple.AbstractJdbcCall.compileInternal(AbstractJdbcCall.java:303) [spring-jdbc.jar:4.2.4.RELEASE] at org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall.compileInternal(PostgresDbEngineDialect.java:108) [dal.jar:] at org.springframework.jdbc.core.simple.AbstractJdbcCall.compile(AbstractJdbcCall.java:288) [spring-jdbc.jar:4.2.4.RELEASE] at org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.getCall(SimpleJdbcCallsHandler.java:169) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeImpl(SimpleJdbcCallsHandler.java:146) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeReadList(SimpleJdbcCallsHandler.java:109) [dal.jar:] at org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeRead(SimpleJdbcCallsHandler.java:101) [dal.jar:] at org.ovirt.engine.core.dao.VdsDynamicDaoImpl.get(VdsDynamicDaoImpl.java:129) [dal.jar:] at org.ovirt.engine.core.dao.VdsDynamicDaoImpl.updateIfNeeded(VdsDynamicDaoImpl.java:296) [dal.jar:] at org.ovirt.engine.core.dao.VdsDynamicDaoImpl.updateIfNeeded(VdsDynamicDaoImpl.java:34) [dal.jar:] at org.ovirt.engine.core.vdsbroker.VdsManager.updateDynamicData(VdsManager.java:421) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.addVds(ResourceManager.java:237) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.init(ResourceManager.java:134) [vdsbroker.jar:] ... 87 more And in server.log: 2016-08-03 12:04:39,758 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 54) MSC000001: Failed to start service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [wildfly-ee-10.0.0.Final.jar:10.0.0.Final] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_92] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_92] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_92] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92] at org.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) [wildfly-ee-10.0.0.Final.jar:10.0.0.Final] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) [wildfly-ee-10.0.0.Final.jar:10.0.0.Final] at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) [wildfly-ee-10.0.0.Final.jar:10.0.0.Final] at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124) at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138) at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [wildfly-ee-10.0.0.Final.jar:10.0.0.Final] ... 6 more Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.ovirt.engine.core.vdsbroker.ResourceManager.init() on org.ovirt.engine.core.vdsbroker.ResourceManager@28b87a8e at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInNoTx(CMTTxInterceptor.java:213) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:265) at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:374) at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-10.0.0.Final.jar:10.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [wildfly-ee-10.0.0.Final.jar:10.0.0.Final] ... 11 more Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.ovirt.engine.core.vdsbroker.ResourceManager.init() on org.ovirt.engine.core.vdsbroker.ResourceManager@28b87a8e ... 2016-08-03 12:04:40,311 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.ovirt.engine.core.vdsbroker.ResourceManager.init() on org.ovirt.engine.core.vdsbroker.ResourceManager@28b87a8e Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.ovirt.engine.core.vdsbroker.ResourceManager.init() on org.ovirt.engine.core.vdsbroker.ResourceManager@28b87a8e Caused by: java.lang.reflect.InvocationTargetException Caused by: java.lang.NullPointerException"}} ... 2016-08-03 12:04:40,916 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started (with errors) in 29114ms - Started 1320 of 1633 services (5 services failed or missing dependencies, 438 services are lazy, passive or on-demand) 2016-08-03 12:04:41,011 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 14) WFLYUT0022: Unregistered web context: /ovirt-engine/services 2016-08-03 12:04:41,012 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 15) WFLYUT0022: Unregistered web context: /ovirt-engine/webadmin 2016-08-03 12:04:41,015 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0022: Unregistered web context: /ovirt-engine/api 2016-08-03 12:04:41,022 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 13) WFLYUT0022: Unregistered web context: /ovirt-engine/docs 2016-08-03 12:04:41,022 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 11) WFLYUT0022: Unregistered web context: /ovirt-engine/sso 2016-08-03 12:04:41,022 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 18) WFLYUT0022: Unregistered web context: /ovirt-engine/userportal 2016-08-03 12:04:41,019 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 20) WFLYUT0022: Unregistered web context: /ovirt-engine 2016-08-03 12:04:41,013 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: / I see no other error message. Any hint about that ?

2 3

Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version 4.0.2? Thank you
by lifuqiong 02 Aug '16

02 Aug '16

This is a multipart message in MIME format. ------=_NextPart_000_00C5_01D1ECB7.2CD482F0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I create a cluster which already enabled ovs network as you mentioned , = but when I create vm in this cluster, I can only using = ovirtmgmt/ovirtmgmt vNIC profile, which is still a Linux bridge. I found no way to add a OVS vNIC profile, I have to chose = ovirtmgmt/ovirtmgmt vNIC to setup a VM. After VM is started, the vm is = still using Linux bridge to communicate with outside, not the ovs. =20 Need I to create a ovs bridge or vport and bind it to physical NIC in = vdsm manually? =20 Hope your reply as soon as possible. Thank you Mark =20 =E5=8F=91=E4=BB=B6=E4=BA=BA: users-bounces(a)ovirt.org = [mailto:users-bounces@ovirt.org] =E4=BB=A3=E8=A1=A8 Meni Yakove =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2016=E5=B9=B48=E6=9C=881=E6=97=A5 = 16:42 =E6=94=B6=E4=BB=B6=E4=BA=BA: Dan Kenigsberg =E4=B8=BB=E9=A2=98: Re: [ovirt-users] [ovirt-devel] How to add ovs-based = VM in version 4.0.2? Thank you =20 On Mon, Aug 1, 2016 at 11:07 AM, Dan Kenigsberg <danken(a)redhat.com> = wrote: On Mon, Aug 01, 2016 at 02:02:52PM +0800, lifuqiong wrote: > Hi, I upgrade my ovirt to version 4.0.2.2, how to using ovs in this = version? > Is there any instruction? Thank you Please note and note well: OVS is not production-grade yet. It is only a preliminary tech preview, under active development. However, we'd be very happy to get your help in testing it (and possibly fixing it, too). When defining a new cluster, you should see a check box, letting you select OVS for that cluster.=20 =20 To be precise, this is not a check box. In the Edit Cluster dialog, look = at the "switch=20 type" option, and change "LEGACY" to "OVS". =20 =20 =20 After being checked, each VM network that is defined in your cluster would be implemented with OVS instead of Linux bridge. As aluded before, there are plenty of known definciencies (e.g., no persistence of ip config on VM network, no live migration, not all bond modes, etc etc). But do not hesitate to raise other issues with the devel mailing list. Happy testing! Dan. _______________________________________________ Devel mailing list Devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/devel =20 ------=_NextPart_000_00C5_01D1ECB7.2CD482F0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta = name=3DGenerator content=3D"Microsoft Word 14 (filtered = medium)"><style></style></head><body lang=3DZH-CN link=3Dblue = vlink=3Dpurple><div class=3DWordSection1>I create a cluster which already enabled ovs network as you mentioned = , but when I create vm in this cluster, =C2=A0I can only using = ovirtmgmt/ovirtmgmt vNIC profile, which is still a Linux = bridge.<o:p></o:p>I found no way to add a OVS vNIC profile,=C2=A0 I have to chose = ovirtmgmt/ovirtmgmt vNIC to setup a VM. After VM is started, the vm is = still using Linux bridge to communicate with outside, not the = ovs.<o:p></o:p><o:p> </o:p>Need I to create a ovs bridge or vport and bind it to physical NIC in = vdsm manually?<o:p></o:p><o:p> </o:p>Hope your reply as soon as possible.<o:p></o:p>Thank you<o:p></o:p>Mark<o:p></o:p><a = name=3D"_MailEndCompose"><o:p> </o:p></a>=E5=8F=91=E4=BB=B6=E4=BA=BA: users-bounces(a)ovirt.org = [mailto:users-bounces@ovirt.org] =E4=BB=A3=E8=A1=A8 Meni Yakove =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2016=E5=B9=B48=E6=9C=881=E6=97=A5 16:42 =E6=94=B6=E4=BB=B6=E4=BA=BA: Dan = Kenigsberg =E4=B8=BB=E9=A2=98: Re: [ovirt-users] = [ovirt-devel] How to add ovs-based VM in version 4.0.2? Thank = you<o:p></o:p><o:p> </o:p><div><div><div>On Mon, Aug 1, 2016 at 11:07 AM, = Dan Kenigsberg <<a href=3D"mailto:danken@redhat.com" = target=3D"_blank">danken(a)redhat.com</a>> = wrote:<o:p></o:p>On = Mon, Aug 01, 2016 at 02:02:52PM +0800, lifuqiong wrote: > Hi, I = upgrade my ovirt to version 4.0.2.2, how to using ovs in this = version? > Is there any instruction? Thank you Please note = and note well: OVS is not production-grade yet. It is only = a preliminary tech preview, under active development. However, = we'd be very happy to get your help in testing it (and = possibly fixing it, too). When defining a new cluster, you = should see a check box, letting you select OVS for that cluster. = <o:p></o:p><div><o:p> </o:p></div><div>To be precise, this is not a check = box. In the Edit Cluster dialog, look at the = "switch <o:p></o:p></div><div>type" option, and change = "LEGACY" to = "OVS".<o:p></o:p></div><div><o:p> </o:p></div><div><o:p> </o:p></div><div> <o:p></o:p></div><blockquote = style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm = 6.0pt;margin-left:4.8pt;margin-right:0cm'>After being checked, each VM network that is defined in = your cluster would be implemented with OVS instead of Linux = bridge. As aluded before, there are plenty of known definciencies = (e.g., no persistence of ip config on VM network, no live migration, = not all bond modes, etc etc). But do not hesitate to raise other = issues with the devel mailing list. Happy = testing! Dan. _______________________________________________<b= r>Devel mailing list <a = href=3D"mailto:Devel@ovirt.org">Devel(a)ovirt.org</a> <a = href=3D"http://lists.ovirt.org/mailman/listinfo/devel" = target=3D"_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><o:p><= /o:p></blockquote></div><o:p> </o:p></div></div></div></body></html> ------=_NextPart_000_00C5_01D1ECB7.2CD482F0--

4 3