On Tue, Dec 8, 2015 at 2:27 AM, Shahar Havivi <[email protected]> wrote:
> Adding Adam and Martin, > Can you please look why mom fails? > > Shahar. > > On 07.12.15 14:10, CLSA Mcmaster wrote: > > On Mon, Dec 7, 2015 at 1:37 PM, Shahar Havivi <[email protected]> > wrote: > > > > > On 07.12.15 13:34, CLSA Mcmaster wrote: > > > > On Mon, Dec 7, 2015 at 1:26 PM, Shahar Havivi <[email protected]> > > > wrote: > > > > > > > > > On 07.12.15 13:15, CLSA Mcmaster wrote: > > > > > > On Mon, Dec 7, 2015 at 1:03 PM, Shahar Havivi < > [email protected]> > > > > > wrote: > > > > > > > > > > > > > On 07.12.15 11:19, CLSA Mcmaster wrote: > > > > > > > > Greetings > > > > > > > > > > > > > > > > I am new to both CentOS and oVirt. I have been hoping to > migrate > > > some > > > > > > > > virtual machines from VMware to oVirt and I have hit a wall. > > > > > > > > > > > > > > > > CentOS 7.1 does not include the tool virt-v2v with the > > > > > libguestfs-tools > > > > > > > > package. I have enabled the CR repository and upgraded but no > > > luck. I > > > > > > > have > > > > > > > > attempted to compile but the dependency whack-a-mole process > > > wore me > > > > > down > > > > > > > > and I eventually hot another wall with supermin not being > "new > > > > > enough". I > > > > > > > > tried to compile that and ran into more dependency issues. > > > > > > > Hi Sean, > > > > > > > For virt-v2v compilation issue you can ask at > > > [email protected] > > > > > > > mailing > > > > > > > list. > > > > > > > > > > > > > > > > Frankly, I am at the point of throwing in the towel but I'm > > > hoping > > > > > > > someone > > > > > > > > can offer advise or insight on obtaining the tool through > other > > > > > means. I > > > > > > > > would also be open to importing guests through another > method. > > > For > > > > > > > example, > > > > > > > > the oVirt interface has a utility to import OVA files. Is > that > > > VMware > > > > > > > > created OVA files? The dialogue has host and path. Is the > path > > > to be > > > > > on > > > > > > > the > > > > > > > > host or the engine? Can it be any path? > > > > > > > Upstream ovirt git://gerrit.ovirt.org/ovirt-engine have > support > > > for > > > > > > > importing > > > > > > > OVA files that was exported from vShpere 5.5 and 6.0 as well as > > > > > connecting > > > > > > > to > > > > > > > a running esxi listing and importing the VMs that are in down > > > state. > > > > > > > > > > > > > > The OVA file must be accessed by the importing host with > > > permissions > > > > > > > 36:36(NFS > > > > > > > mount will work as well). > > > > > > > > > > > > > > To access the import VMs feature simply go to the VMs tab and > > > click on > > > > > the > > > > > > > import button there you will be able to select the import > source > > > > > > > (VMware/OVA > > > > > > > etc). > > > > > > > > > > > > > > More information about virt-v2v integration with oVirt can be > > > found in > > > > > its > > > > > > > feature page: > http://www.ovirt.org/Features/virt-v2v_Integration > > > > > > > > > > > > > > Shahar. > > > > > > > > > > > > > > > > Thank you in advance for any support offered. > > > > > > > > > > > > > > > > Sean. > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Users mailing list > > > > > > > > [email protected] > > > > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > > > > Thank you. Shahar. > > > > > > > > > > > > I did get an OVA imported. Unfortunately, immediately upon doing > so > > > I got > > > > > > this error: "Unit mom-vdsm.service has failed". > > > > > Can you add the vdsm log, its in /var/log/vdsm/vdsm.log > > > > > > > > > > > > Sean. > > > > > > > > > > > _______________________________________________ > > > > > > Users mailing list > > > > > > [email protected] > > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > I shut down the host. I will restart it. But on the engine side in > > > > engine.log I see: > > > Ok, > > > try to see if you can update the mom* packages on the host and also > what > > > version of vdsm and mom are you using? > > > vdsm log can be helpful. > > > > > > Shahar. > > > > > > > > Caused by: org.postgresql.util.PSQLException: ERROR: integer out of > range > > > > Where: PL/pgSQL function > fn_get_disk_commited_value_by_storage(uuid) > > > line > > > > 20 at assignment > > > > PL/pgSQL function > getstorage_domains_by_storagepoolid(uuid,uuid,boolean) > > > > line 3 at RETURN QUERY > > > > at > > > > > > > > org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2103) > > > > at > > > > > > > > org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1836) > > > > at > > > > > > > > org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257) > > > > at > > > > > > > > org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:512) > > > > at > > > > > > > > org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:388) > > > > at > > > > > > > > org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:273) > > > > at > > > > > > > > org.jboss.jca.adapters.jdbc.CachedPreparedStatement.executeQuery(CachedPreparedStatement.java:111) > > > > at > > > > > > > > org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462) > > > > at > > > > > > > > org.springframework.jdbc.core.JdbcTemplate$1.doInPreparedStatement(JdbcTemplate.java:644) > > > > [spring-jdbc.jar:3.1.1.RELEASE] > > > > at > > > > > org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:587) > > > > [spring-jdbc.jar:3.1.1.RELEASE] > > > > ... 153 more > > > > > > > _______________________________________________ > > > > Users mailing list > > > > [email protected] > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > On the host. > > > > mom.log > > > > mom - INFO - MOM starting > > 2015-12-07 18:59:15,242 - mom.HostMonitor - INFO - Host Monitor starting > > 2015-12-07 18:59:15,242 - mom - INFO - hypervisor interface vdsmxmlrpc > > 2015-12-07 18:59:16,965 - mom.vdsmInterface - ERROR - Cannot connect to > > VDSM! [Errno 111] Connection refused > > 2015-12-07 18:59:16,966 - mom.GuestManager - INFO - Guest Manager > starting: > > multi-thread > > 2015-12-07 18:59:16,970 - mom.vdsmInterface - ERROR - Cannot connect to > > VDSM! [Errno 111] Connection refused > > 2015-12-07 18:59:16,976 - mom.Policy - INFO - Loaded policy '00-defines' > > 2015-12-07 18:59:17,018 - mom.Policy - INFO - Loaded policy '02-balloon' > > 2015-12-07 18:59:17,079 - mom.Policy - INFO - Loaded policy '03-ksm' > > 2015-12-07 18:59:17,079 - mom.HostMonitor - INFO - HostMonitor is ready > > 2015-12-07 18:59:17,155 - mom.Policy - INFO - Loaded policy '04-cputune' > > 2015-12-07 18:59:17,156 - mom.PolicyEngine - INFO - Policy Engine > starting > > 2015-12-07 18:59:17,157 - mom.RPCServer - INFO - Using unix socket > > /var/run/vdsm/mom-vdsm.sock > > 2015-12-07 18:59:17,161 - mom.RPCServer - INFO - RPC Server starting > > 2015-12-07 18:59:32,232 - mom.Controllers.KSM - INFO - Updating KSM > > configuration: pages_to_scan:0 merge_across_nodes:1 run:0 > sleep_millisecs: > > > > vdsm.log > > > > BindingXMLRPC::INFO::2015-12-07 > > 19:01:47,298::xmlrpc::73::vds.XMLRPCServer::(handle_request) Starting > > request handler for 127.0.0.1:44559 > > Thread-23::INFO::2015-12-07 > > 19:01:47,298::xmlrpc::84::vds.XMLRPCServer::(_process_requests) Request > > handler for 127.0.0.1:44559 started > > Thread-23::INFO::2015-12-07 > > 19:01:47,300::xmlrpc::92::vds.XMLRPCServer::(_process_requests) Request > > handler for 127.0.0.1:44559 stopped > > Reactor thread::INFO::2015-12-07 > > > 19:02:02,317::protocoldetector::72::ProtocolDetector.AcceptorImpl::(handle_accept) > > Accepting connection from 127.0.0.1:44560 > > Reactor thread::DEBUG::2015-12-07 > > 19:02:02,329::protocoldetector::82::ProtocolDetector.Detector::(__init__) > > Using required_size=11 > > Reactor thread::INFO::2015-12-07 > > > 19:02:02,330::protocoldetector::118::ProtocolDetector.Detector::(handle_read) > > Detected protocol xml from 127.0.0.1:44560 > > Reactor thread::DEBUG::2015-12-07 > > 19:02:02,330::bindingxmlrpc::1297::XmlDetector::(handle_socket) xml over > > http detected from ('127.0.0.1', 44560) > > BindingXMLRPC::INFO::2015-12-07 > > 19:02:02,330::xmlrpc::73::vds.XMLRPCServer::(handle_request) Starting > > request handler for 127.0.0.1:44560 > > Thread-24::INFO::2015-12-07 > > 19:02:02,331::xmlrpc::84::vds.XMLRPCServer::(_process_requests) Request > > handler for 127.0.0.1:44560 started > > Thread-24::INFO::2015-12-07 > > 19:02:02,333::xmlrpc::92::vds.XMLRPCServer::(_process_requests) Request > > handler for 127.0.0.1:44560 stopped > > > > > > mom is 0.5.1 on both engine and node. > > vdsm 4.17.11 on node and 4.17.10 on engine. > > > > Thank you for your help. > > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.ovirt.org/mailman/listinfo/users > > As a note this occurred only after importing an OVA. Thanks.
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
