Re: [ovirt-users] VM running on multiple hosts

[support]

This matches about with what we were thinking, thank you!

To answer your questions

We do not have power management configured due to it causing a cascading 
failure early in our deployment.  The host was not fenced and "confirm host 
rebooted" was never used.  The VMs were powered on via virsh (this shouldn't 
have happened)

The way they were powered on is most likely why they were corrupted is our 
thought


Logan

> On September 20, 2017 at 12:03 PM Michal Skrivanek 
>  wrote:
> 
> 
> 
> > > On 20 Sep 2017, at 18:06, Logan Kuhn 
>  wrote:
> > 
> > We had an incident where a VM hosts' disk filled up, the VMs all 
> > went unknown in the web console, but were fully functional if you were to 
> > login or use the services of one.
> > 
> > > 
> Hi,
> yes, that can happen since the VM’s storage is on NAS whereas the server 
> itself is non-functional as the management and all other local processes are 
> using local resources
> 
> 
> > >   We couldn't migrate them so we powered them down on 
> that host and powered them up and let ovirt choose the host for it, same as 
> always. 
> > 
> > > 
> that’s a mistake. The host should be fenced in that case, you likely do 
> not have a power management configured, do you? Even when you do not have a 
> fencing device available it should have been resolved manually by rebooting 
> it  manually(after fixing the disk problem), or in case of permanent damage 
> (e.g. server needs to be replaced, that takes a week, you need to run those 
> VMs in the meantime elsewhere) it should have been powered off and VM states 
> should be reset by “confirm host has been rebooted” manual action.
> 
> Normally you should now be able to run those VMs while the status of the 
> host is still Not Responding - was it not the case? How exactly you get to 
> the situation that you were able to power up the VMs?
> 
> 
> 
> > > However the disk image on a few of them were corrupted 
> because once we fixed the host with the full disk, it still thought it should 
> be running the VM.  Which promptly corrupted the disk, the error seems to be 
> this in the logs:
> > 
> > > 
> this can only happen for VMs flagged as HA, is it a case?
> 
> Thanks,
> michal
> 
> 
> > > 
> > 2017-09-19 21:59:11,058 INFO  
> > [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
> > (DefaultQuartzScheduler3) [36c806f6] VM 
> > '70cf75c7-0fc2-4bbe-958e-7d0095f70960'(testhub) is running in db and not 
> > running on VDS 'ef6dc2a3-af6e-4e00-aa4
> > 0-493b31263417'(vm-int7)
> > 
> > We upgraded to 4.1.6 from 4.0.6 earlier in the day, I don't really 
> > think it's anything more than coincidence, but it's worrying enough to send 
> > to the community.
> > 
> > Regards,
> > Logan
> > ___
> > Users mailing list
> > Users@ovirt.org mailto:Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> > > 
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4

[support]

Which makes sense seeing as that's what Red Hat officially supports.  It just 
made sense for our infrastructure to put it on our postgres cluster that is 
running 9.5.x.  Unfortunately things like this happen sometimes when running a 
slightly unsupported infrastructure.


Is this worth putting in an RFE?  Support for postgresql-jdbc 42+ and 
postgresql 9.5+


Logan

> On May 24, 2017 at 5:24 AM Martin Perina <mper...@redhat.com> wrote:
> 
> Yes, postgresql 9.2 JDBC drivers are the only working and supported JDBC 
> drivers. Also please be aware that we test and only PostgreSQL 9.2  for 
> oVirt, so there may be other issues with newer versions.
> 
> On Tue, May 23, 2017 at 11:15 PM, Yedidyah Bar David <d...@redhat.com 
> mailto:d...@redhat.com > wrote:
> 
> > > On Wed, May 24, 2017 at 12:06 AM,  <supp...@jac-properties.com 
> mailto:supp...@jac-properties.com > wrote:
> > > Wow, that looks almost exactly like what we're seeing.
> > >
> > > Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, 
> > restarting ovirt-engine and rerunning engine-setup produces the same error 
> > messages.
> > >
> > 
> > Please try 9.2. Thanks!
> > 
> > > Logan
> > >
> > >> On May 23, 2017 at 3:39 PM Yedidyah Bar David <d...@redhat.com 
> > mailto:d...@redhat.com > wrote:
> > >>
> > >>
> > >> On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn 
> > <supp...@jac-properties.com mailto:supp...@jac-properties.com > wrote:
> > >> > Hi
> > >> >
> > >> > We recently upgraded from postgres 9.5.4 to 9.5.6 and then to 
> > 9.5.7.  We
> > >> > restarted ovirt-engine between 9.5.4 and it worked as 
> > expected.  After we
> > >> > updated to 9.5.7 we have started to get postgres errors in 
> > engine.log and a
> > >> > 404 error in the browser when we try to start ovirt-engine.
> > >> >
> > >> > Updates were done on client and server to keep them in sync.
> > >> >
> > >> > The error is complaining about a missing function, but we can 
> > verify that
> > >> > the function exists in the database.  We've also restored 
> > engine and
> > >> > ovirt_engine_history from a backup at 8am this morning when it 
> > was working
> > >> > and before we upgraded to 9.5.7 with no apparent help and run 
> > engine-setup
> > >> > afterwards, still no luck.
> > >> >
> > >> > 2017-05-23 15:07:48,418 INFO  
> > [org.ovirt.engine.core.dal.dbbroker.DbFacade]
> > >> > (ServerService Thread Pool -- 51) [] Initializing the DbFacade
> > >> > 2017-05-23 15:07:48,480 INFO  
> > [org.ovirt.engine.core.bll.Backend]
> > >> > (ServerService Thread Pool -- 51) [] Start initializing Backend
> > >> > 2017-05-23 15:07:48,502 ERROR
> > >> > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] 
> > (ServerService
> > >> > Thread Pool -- 46) [] Error initializing: 
> > PreparedStatementCallback; bad SQL
> > >> > grammar [select * from  getallmacpoolrangesbymacpoolid()]; 
> > nested exception
> > >> > is org.postgresql.util.PSQL
> > >> > Exception: ERROR: function getallmacpoolrangesbymacpoolid() 
> > does not exist
> > >> >  Hint: No function matches the given name and argument types. 
> > You might need
> > >> > to add explicit type casts.
> > >> >  Position: 16
> > >> > 2017-05-23 15:07:48,517 ERROR 
> > [org.ovirt.engine.core.bll.Backend]
> > >> > (ServerService Thread Pool -- 51) [] Error during 
> > initialization:
> > >> > org.jboss.weld.exceptions.WeldException: WELD-49: Unable 
> > to invoke
> > >> > public void
> > >> > 
> > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre
> > >> > ate() on
> > >> > 
> > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461
> > >> >at
> > >> > 
> > org.jboss.weld.injection.producer.DefaultLifecycleCallbackI

Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4

[support]

Thanks, that's what we've put in place too


Logan

> 
> On May 24, 2017 at 2:20 AM Fabrice Bacchella 
>  wrote:
> 
> In /etc/yum.repos.d/pgdg-94-centos.repo, I added :
> 
> [pgdg94]
> ...
> exclude=postgresql-jdbc
> 
> > > 
> > Le 23 mai 2017 à 23:06, supp...@jac-properties.com a écrit :
> > 
> > Wow, that looks almost exactly like what we're seeing.
> > 
> > Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, 
> > restarting ovirt-engine and rerunning engine-setup produces the same error 
> > messages.
> > 
> > Logan
> > 
> > > > > 
> > > On May 23, 2017 at 3:39 PM Yedidyah Bar David 
> > >  wrote:
> > > 
> > > On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn 
> > >  wrote:
> > > 
> > > > > > > 
> > > > Hi
> > > > 
> > > > We recently upgraded from postgres 9.5.4 to 9.5.6 and 
> > > > then to 9.5.7. We
> > > > restarted ovirt-engine between 9.5.4 and it worked as 
> > > > expected. After we
> > > > updated to 9.5.7 we have started to get postgres errors 
> > > > in engine.log and a
> > > > 404 error in the browser when we try to start 
> > > > ovirt-engine.
> > > > 
> > > > Updates were done on client and server to keep them in 
> > > > sync.
> > > > 
> > > > The error is complaining about a missing function, but 
> > > > we can verify that
> > > > the function exists in the database. We've also 
> > > > restored engine and
> > > > ovirt_engine_history from a backup at 8am this morning 
> > > > when it was working
> > > > and before we upgraded to 9.5.7 with no apparent help 
> > > > and run engine-setup
> > > > afterwards, still no luck.
> > > > 
> > > > 2017-05-23 15:07:48,418 INFO 
> > > > [org.ovirt.engine.core.dal.dbbroker.DbFacade]
> > > > (ServerService Thread Pool -- 51) [] Initializing the 
> > > > DbFacade
> > > > 2017-05-23 15:07:48,480 INFO 
> > > > [org.ovirt.engine.core.bll.Backend]
> > > > (ServerService Thread Pool -- 51) [] Start initializing 
> > > > Backend
> > > > 2017-05-23 15:07:48,502 ERROR
> > > > 
> > > > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService
> > > > Thread Pool -- 46) [] Error initializing: 
> > > > PreparedStatementCallback; bad SQL
> > > > grammar [select * from 
> > > > getallmacpoolrangesbymacpoolid()]; nested exception
> > > > is org.postgresql.util.PSQL
> > > > Exception: ERROR: function 
> > > > getallmacpoolrangesbymacpoolid() does not exist
> > > > Hint: No function matches the given name and argument 
> > > > types. You might need
> > > > to add explicit type casts.
> > > > Position: 16
> > > > 2017-05-23 15:07:48,517 ERROR 
> > > > [org.ovirt.engine.core.bll.Backend]
> > > > (ServerService Thread Pool -- 51) [] Error during 
> > > > initialization:
> > > > org.jboss.weld.exceptions.WeldException: WELD-49: 
> > > > Unable to invoke
> > > > public void
> > > > 
> > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre
> > > > ate() on
> > > > 
> > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461
> > > > at
> > > > 
> > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at 
> > > > org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
> > > > 

Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4

[support]

I downgraded the jdbc to 9.2.1002 and it's working again.  Thank you for your 
help!

The full setup is as such in case it helps anyone in the future:

OS: CentOS 7.3.1611

Backend: Ceph via Cinder

oVirt: 4.0.6.3

Postgres is remote and 9.5.7 on client and server

Postgres jdbc: 9.2.1002

Logan

> 
> On May 23, 2017 at 4:15 PM Yedidyah Bar David  wrote:
> 
> On Wed, May 24, 2017 at 12:06 AM,  wrote:
> 
> > > 
> > Wow, that looks almost exactly like what we're seeing.
> > 
> > Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, 
> > restarting ovirt-engine and rerunning engine-setup produces the same error 
> > messages.
> > 
> > > 
> Please try 9.2. Thanks!
> 
> > > 
> > Logan
> > 
> > > > > 
> > > On May 23, 2017 at 3:39 PM Yedidyah Bar David 
> > >  wrote:
> > > 
> > > On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn 
> > >  wrote:
> > > 
> > > > > > > 
> > > > Hi
> > > > 
> > > > We recently upgraded from postgres 9.5.4 to 9.5.6 and 
> > > > then to 9.5.7. We
> > > > restarted ovirt-engine between 9.5.4 and it worked as 
> > > > expected. After we
> > > > updated to 9.5.7 we have started to get postgres errors 
> > > > in engine.log and a
> > > > 404 error in the browser when we try to start 
> > > > ovirt-engine.
> > > > 
> > > > Updates were done on client and server to keep them in 
> > > > sync.
> > > > 
> > > > The error is complaining about a missing function, but 
> > > > we can verify that
> > > > the function exists in the database. We've also 
> > > > restored engine and
> > > > ovirt_engine_history from a backup at 8am this morning 
> > > > when it was working
> > > > and before we upgraded to 9.5.7 with no apparent help 
> > > > and run engine-setup
> > > > afterwards, still no luck.
> > > > 
> > > > 2017-05-23 15:07:48,418 INFO 
> > > > [org.ovirt.engine.core.dal.dbbroker.DbFacade]
> > > > (ServerService Thread Pool -- 51) [] Initializing the 
> > > > DbFacade
> > > > 2017-05-23 15:07:48,480 INFO 
> > > > [org.ovirt.engine.core.bll.Backend]
> > > > (ServerService Thread Pool -- 51) [] Start initializing 
> > > > Backend
> > > > 2017-05-23 15:07:48,502 ERROR
> > > > 
> > > > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService
> > > > Thread Pool -- 46) [] Error initializing: 
> > > > PreparedStatementCallback; bad SQL
> > > > grammar [select * from 
> > > > getallmacpoolrangesbymacpoolid()]; nested exception
> > > > is org.postgresql.util.PSQL
> > > > Exception: ERROR: function 
> > > > getallmacpoolrangesbymacpoolid() does not exist
> > > > Hint: No function matches the given name and argument 
> > > > types. You might need
> > > > to add explicit type casts.
> > > > Position: 16
> > > > 2017-05-23 15:07:48,517 ERROR 
> > > > [org.ovirt.engine.core.bll.Backend]
> > > > (ServerService Thread Pool -- 51) [] Error during 
> > > > initialization:
> > > > org.jboss.weld.exceptions.WeldException: WELD-49: 
> > > > Unable to invoke
> > > > public void
> > > > 
> > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre
> > > > ate() on
> > > > 
> > > > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461
> > > > at
> > > > 
> > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at 
> > > > org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> > > > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> > > > at
> > > > 
> > > > 

Re: [ovirt-users] Postgres errors after updating to 9.5.7 from 9.5.4

[support]

Wow, that looks almost exactly like what we're seeing.

Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, restarting 
ovirt-engine and rerunning engine-setup produces the same error messages.

Logan

> On May 23, 2017 at 3:39 PM Yedidyah Bar David  wrote:
> 
> 
> On Tue, May 23, 2017 at 11:19 PM, Logan Kuhn  
> wrote:
> > Hi
> >
> > We recently upgraded from postgres 9.5.4 to 9.5.6 and then to 9.5.7.  We
> > restarted ovirt-engine between 9.5.4 and it worked as expected.  After we
> > updated to 9.5.7 we have started to get postgres errors in engine.log and a
> > 404 error in the browser when we try to start ovirt-engine.
> >
> > Updates were done on client and server to keep them in sync.
> >
> > The error is complaining about a missing function, but we can verify that
> > the function exists in the database.  We've also restored engine and
> > ovirt_engine_history from a backup at 8am this morning when it was working
> > and before we upgraded to 9.5.7 with no apparent help and run engine-setup
> > afterwards, still no luck.
> >
> > 2017-05-23 15:07:48,418 INFO  [org.ovirt.engine.core.dal.dbbroker.DbFacade]
> > (ServerService Thread Pool -- 51) [] Initializing the DbFacade
> > 2017-05-23 15:07:48,480 INFO  [org.ovirt.engine.core.bll.Backend]
> > (ServerService Thread Pool -- 51) [] Start initializing Backend
> > 2017-05-23 15:07:48,502 ERROR
> > [org.ovirt.engine.core.bll.network.macpool.MacPoolPerDc] (ServerService
> > Thread Pool -- 46) [] Error initializing: PreparedStatementCallback; bad SQL
> > grammar [select * from  getallmacpoolrangesbymacpoolid()]; nested exception
> > is org.postgresql.util.PSQL
> > Exception: ERROR: function getallmacpoolrangesbymacpoolid() does not exist
> >  Hint: No function matches the given name and argument types. You might need
> > to add explicit type casts.
> >  Position: 16
> > 2017-05-23 15:07:48,517 ERROR [org.ovirt.engine.core.bll.Backend]
> > (ServerService Thread Pool -- 51) [] Error during initialization:
> > org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke
> > public void
> > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost.cre
> > ate() on
> > org.ovirt.engine.core.bll.hostedengine.PreviousHostedEngineHost@3a35f461
> >at
> > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:189)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at
> > org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100)
> > [weld-core-impl-2.3.5.Final.jar:2.3.5.Final]
> >at org.ovirt.engine.core.bll.Backend.loadService(Backend.java:301)
> > [bll.jar:]
> >at org.ovirt.engine.core.bll.Backend.initialize(Backend.java:212)
> > [bll.jar:]
> >at org.ovirt.engine.core.bll.Backend.create(Backend.java:159)
> > [bll.jar:]
> >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > [rt.jar:1.8.0_131]
> >at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > [rt.jar:1.8.0_131]
> >at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > [rt.jar:1.8.0_131]
> >at java.lang.reflect.Method.invoke(Method.java:498)
> > [rt.jar:1.8.0_131]
> >at
> > org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96)
> >at
> > 

Re: [ovirt-users] shutdown and kernel panic

[Synt - Support Service]

2016-11-23 18:06 GMT+01:00 Pavel Gashev <p...@acronis.com>:

> It’s necessary to put a host into maintenance mode before shutdown.


I cant put host in maintenance mode before, because the host-egnie is a VM
inside the single host.
... unfortunately the shutdown problem persist ... :-(


-- 
<http://www.synt.net>

*Luigi** Fanton*
Tecnical Support
Office +39.0422.545487
supp...@synt.net

*Synt.net S.r.l.*
Viale IV Novembre, 85/3
31100 - Treviso - Italy
P.IVA 04586950265
Tel +39.0422.545487
Fax +39.0422.0247047

i...@synt.net
www.synt.net

*Soluzioni in movimento per le Imprese*
<http://www.opensource.org>
<http://www.asterisk.org>



* Le informazioni contenute in questo messaggio di posta elettronica e
negli eventuali allegati sono riservate e confidenziali e sono indirizzate
esclusivamente al destinatario. Si prega di non fare copia, inoltrare a
terzi o conservare tale messaggio se non si è il legittimo destinatario
dello stesso. Qualora questo messaggio sia stato ricevuto per errore, si
prega di rinviarlo al mittente e di cancellarlo permanentemente dal proprio
computer. Ogni prezzo indicato è puramente indicativo e soggetto a
verifica. The information contained in this message and in any attachment
is intended exclusively for the recipient. If you are not the intended
recipient you are hereby notified not to copy, save, disclose, or
distribute it to any third party. If you erroneously received this message
you are kindly requested to return it to the sender and eliminate it
permanently from your computer.*
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] LVM Volumes can be manage by oVirt?

[Periko Support]

Got it, I will check the manual, thanks!!!

On Tue, Jul 1, 2014 at 11:01 PM, Itamar Heim ih...@redhat.com wrote:
 On 07/01/2014 09:21 PM, Periko Support wrote:

 I'm working with oVirt, learning curve.

 I setup the system, but I didn't see if is possible to manage my KVM
 server Volumes inside oVirt.

 I have a KVM server, I add my LVM volume to a pool with virsh.

 After I setup oVirt didn't know if I can manage that pool/volume inside
 oVirt?

 I have there 2 vm's already running.

 Is possible?


 oVirt is managing its storage domains differently than how virsh does that.
 you'd need to import (or in 3.5, maybe register) the disks to ovirt.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] LVM Volumes can be manage by oVirt?

[Periko Support]

I'm working with oVirt, learning curve.

I setup the system, but I didn't see if is possible to manage my KVM
server Volumes inside oVirt.

I have a KVM server, I add my LVM volume to a pool with virsh.

After I setup oVirt didn't know if I can manage that pool/volume inside oVirt?

I have there 2 vm's already running.

Is possible?

Centos 6.5 x64, thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users