Error in OVS!!

i am getting error which is mentioned below regarding OVS,particularly when the browser is running slow and i am clicking 2nd time for the value help.
If anyone know the answer,give me the solution.
I will reward point.
error is like ....
The following error text was processed in the system EC6 : Access via 'NULL' object reference not possible.
The error occurred on the application server HSDNT24S12_EC6_03 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: IF_WDR_OVS_LISTENER~MODIFY_RESULT_VIEW of program CL_WDR_VALUE_HELP_HANDLER=====CP
Method: WDDOMODIFYVIEW of program /1BCWDY/RZ2TAVAGXRRTKWWIR62K==CP
Method: IF_WDR_VIEW_DELEGATE~WD_DO_MODIFY_VIEW of program /1BCWDY/RZ2TAVAGXRRTKWWIR62K==CP
Method: DO_MODIFY_VIEW of program CL_WDR_DELEGATING_VIEW========CP
Method: MODIFY_VIEW of program CL_WDR_VIEW===================CP
Method: DO_MODIFY_VIEW of program CL_WDR_CLIENT_COMPONENT=======CP
Method: DO_MODIFY_VIEW of program CL_WDR_WINDOW_PHASE_MODEL=====CP
Method: PROCESS_REQUEST of program CL_WDR_WINDOW_PHASE_MODEL=====CP
Method: PROCESS_REQUEST of program CL_WDR_WINDOW=================CP
Method: EXECUTE of program CL_WDR_MAIN_TASK==============CP
thanks in advance,
Subhasis.

HI,
DID U WRITE THE FOLLOWING CODE IN A METHOD :
  types : begin of ist_fields,
           carrid type spfli-carrid,
           countryfr type spfli-countryfr,
           cityfrom type spfli-cityfrom,
         end of ist_fields.
  data:
        it_fields type ist_fields,
        it_conn   type table of spfli.
  field-symbols : <lfs_input> type ist_fields,
                  <lfs_select> type spfli.
  case ovs_callback_object->phase_indicator.
    when 0.
      call method ovs_callback_object->set_configuration
        exporting
          window_title       = 'search Flights'
          group_header       = 'enter flight details'
         LABEL_TEXTS        =
         TABLE_HEADER       =
         COLUMN_TEXTS       =
          col_count          = 1
         ROW_COUNT          =
         TABLE_MULTI_SELECT =
    when 1.
      call method ovs_callback_object->set_input_structure
        exporting
          input        = it_fields
           GROUP_HEADER =
           LABEL_TEXTS  =
           WINDOW_TITLE =
    when 2.
      assign ovs_callback_object->query_parameters->* to <lfs_input> casting.
       call method cl_wd_flight_model=>get_conns_by_carrid_cityfrom
         exporting
           i_carrid         = <lfs_input>-carrid
           i_countryfr      = <lfs_input>-countryfr
           i_cityfrom       = <lfs_input>-cityfrom
         importing
          et_spfli_sflight = it_conn
       call method ovs_callback_object->set_output_table
         exporting
           output       =  it_conn
          TABLE_HEADER =
          COLUMN_TEXTS =
     when 3.
         data:
           node_flight                         type ref to if_wd_context_node,
           elem_flight                         type ref to if_wd_context_element,
           stru_flight                         type if_inputview=>element_flight .
         assign ovs_callback_object->selection->* to <lfs_select> casting.
       navigate from <CONTEXT> to <FLIGHT> via lead selection
         node_flight = wd_context->get_child_node( name = if_inputview=>wdctx_flight ).
        node_flight->bind_structure(
          exporting
            new_item             = <lfs_select> ).
AND ALSO IN THE CONTEXT DID U SELECT OBJECT VALUE SELECTOR IN INPUT HELP MODE3 AND OVS COMPONENT USAGE.
MADHU

Similar Messages

  • Getting error in OVS!!

    Scenario:
    I am using Object Value Selector(OVS) in my application for an attribute of a node.
    Problem:
    when i am clicking for value help,
    Sometimes i am getting an error message like
    'error type:sapPopupMainId_X1'  in a popup.
    within that popup there is a OK button.
    after clicking the OK button if i again click for the value help,the application is giving dump like NULL object reference.
    How to overcome this??
    Please anyone give me a solution.
    Thanks in advance,
    Subhasis.

    Hi Subhasis,
    This is a known bug and has been fixed. Depending on your current SP-level you will either have to apply some notes or move to a higher SP-level.
    Best regards,
    Thomas

  • Wrapper Error in "OVS." Please help

    Hi!! I need your knowledge !!
    I build a OVS... and functioned well.
    But, i create a another RFC Model (for other functionality), and when I realice deployment, and execute the OVS in my WebDynpro , this error generated:
    <i>java.lang.NullPointerException
    at <b>com.sap.tc.webdynpro.progmodel.valuehelp.NodeCMIModelClassWrapper.<init>(NodeCMIModelClassWrapper.java:46)</i></b>
    what is this error in Wrapper? Has someone has occurred him?
    Help please!
    Thanks...

    Mauricio,
    Seems that node element passed to constructor is null. Looks like you are using
    WDValueServices.addOVSExtension
    String providerName,
    IWDAttributeInfo[] startupAttributes,
    IWDNode queryInputNode,
    IWDNode queryResultNode,
    IWDOVSContextNotificationListener queryListener
    and queryInputNode contains no element. try to add element to this node and test again.
    Valery Silaev
    EPAM Systems
    http://www.NetWeaverTeam.com

  • Errors in OVS code

    Hi all,
       Can someone help rectify errors in the below code. I can't able to run this code
    // This file has been generated partially by the Web Dynpro Code Generator.
    // MODIFY CODE ONLY IN SECTIONS ENCLOSED BY @@begin AND @@end.
    // ALL OTHER CHANGES WILL BE LOST IF THE FILE IS REGENERATED.
    package se.abb.com;
    // IMPORTANT NOTE:
    // ALL IMPORT STATEMENTS MUST BE PLACED IN THE FOLLOWING SECTION ENCLOSED
    // BY @@begin imports AND @@end. FURTHERMORE, THIS SECTION MUST ALWAYS CONTAIN
    // AT LEAST ONE IMPORT STATEMENT (E.G. THAT FOR IPrivateOVSCust).
    // OTHERWISE, USING THE ECLIPSE FUNCTION "Organize Imports" FOLLOWED BY
    // A WEB DYNPRO CODE GENERATION (E.G. PROJECT BUILD) WILL RESULT IN THE LOSS
    // OF IMPORT STATEMENTS.
    //@@begin imports
    import se.abb.com.wdp.IPrivateOVSCust;
    import se.abb.com.wdp.IPrivateView2;
    import se.abb.com.wdp.IPublicOVSCust;
    import se.abb.com01.Zexigo_Cats_Search_Input;
    import se.abb.com01.Zexigo_Cvr_Update_Input;
    import com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException;
    import com.sap.tc.webdynpro.progmodel.api.IWDMessageManager;
    import com.sap.tc.webdynpro.progmodel.api.IWDNode;
    import com.sap.tc.webdynpro.progmodel.api.IWDNodeElement;
    import com.sap.tc.webdynpro.progmodel.api.IWDOVSContextNotificationListener;
    //@@end
    //@@begin documentation
    //@@end
    public class OVSCust
    Logging location.
      private static final com.sap.tc.logging.Location logger =
        com.sap.tc.logging.Location.getLocation(OVSCust.class);
      static
        //@@begin id
        String id = "$Id$";
        //@@end
        com.sap.tc.logging.Location.getLocation("ID.com.sap.tc.webdynpro").infoT(id);
    Private access to the generated Web Dynpro counterpart
    for this controller class.  </p>
    Use <code>wdThis</code> to gain typed access to the context,
    to trigger navigation via outbound plugs, to get and enable/disable
    actions, fire declared events, and access used controllers and/or
    component usages.
    @see se.abb.com.wdp.IPrivateOVSCust for more details
      private final IPrivateOVSCust wdThis;
    Root node of this controller's context. </p>
    Provides typed access not only to the elements of the root node
    but also to all nodes in the context (methods node<i>XYZ</i>())
    and their currently selected element (methods current<i>XYZ</i>Element()).
    It also facilitates the creation of new elements for all nodes
    (methods create<i>XYZ</i>Element()). </p>
    @see se.abb.com.wdp.IPrivateOVSCust.IContextNode for more details.
      private final IPrivateOVSCust.IContextNode wdContext;
    A shortcut for <code>wdThis.wdGetAPI()</code>. </p>
    Represents the generic API of the generic Web Dynpro counterpart
    for this controller. </p>
      private final com.sap.tc.webdynpro.progmodel.api.IWDController wdControllerAPI;
    A shortcut for <code>wdThis.wdGetAPI().getComponent()</code>. </p>
    Represents the generic API of the Web Dynpro component this controller
    belongs to. Can be used to access the message manager, the window manager,
    to add/remove event handlers and so on. </p>
      private final com.sap.tc.webdynpro.progmodel.api.IWDComponent wdComponentAPI;
      public OVSCust(IPrivateOVSCust wdThis)
        this.wdThis = wdThis;
        this.wdContext = wdThis.wdGetContext();
        this.wdControllerAPI = wdThis.wdGetAPI();
        this.wdComponentAPI = wdThis.wdGetAPI().getComponent();
      //@@begin javadoc:wdDoInit()
      /** Hook method called to initialize controller. */
      //@@end
      public void wdDoInit()
        //@@begin wdDoInit()
        //$$begin Service Controller(-1119166442)
        wdContext.nodeZexigo_Cvr_Update_Input_OVS().bind(new Zexigo_Cvr_Update_Input());
        //$$end
         Zexigo_Cats_Search_Input searchInput = new Zexigo_Cats_Search_Input();
         wdContext.nodeZexigo_Cats_Search_Input().bind(searchInput);   
        //@@end
      //@@begin javadoc:wdDoExit()
      /** Hook method called to clean up controller. */
      //@@end
      public void wdDoExit()
        //@@begin wdDoExit()
        //@@end
      //@@begin javadoc:executeZexigo_Cvr_Update_Input_OVS()
      /** Declared method. */
      //@@end
      public void executeZexigo_Cvr_Update_Input_OVS( )
        //@@begin executeZexigo_Cvr_Update_Input_OVS()
        //$$begin Service Controller(-1263234559)
        IWDMessageManager manager = wdComponentAPI.getMessageManager();
        try
          wdContext.currentZexigo_Cvr_Update_Input_OVSElement().modelObject().execute();
          wdContext.nodeOutput_update().invalidate();
        catch(WDDynamicRFCExecuteException e)
          manager.reportException(e.getMessage(), false);
        //$$end
        //@@end
    The following code section can be used for any Java code that is
    not to be visible to other controllers/views or that contains constructs
    currently not supported directly by Web Dynpro (such as inner classes or
    member variables etc.). </p>
    Note: The content of this section is in no way managed/controlled
    by the Web Dynpro Designtime or the Web Dynpro Runtime.
      //@@begin others
      private class OVSDemoContextNotificationListener implements IWDOVSContextNotificationListener {
      /* @see com.sap.tc.webdynpro.progmodel.api
      .IWDOVSContextNotificationListener#onQuery(... */
      public void onQuery(IWDNodeElement queryInputNodeElement,IWDNode queryOutputNode) {
      IPublicOVSCust.IZexigo_Cats_Search_InputElement ovsInput = (IPublicOVSCust.IZexigo_Cats_Search_InputElement) queryInputNodeElement;
      IPublicOVSCust.IZexigo_Cats_Search_OutputNode ovsOutput = (IPublicOVSCust.IZexigo_Cats_Search_OutputNode) queryOutputNode;
      try {
      ovsInput.modelObject().execute();
    //      invalidate 'Output' model node via a top-down access
    //      approach
      ovsInput.node().getChildNode("Output",0).invalidate();
      } catch (Exception e) {
      IWDMessageManager msgMgr = wdComponentAPI.getMessageManager();
      msgMgr.reportException(e.getLocalizedMessage(), false);
      /* @see com.sap.tc.webdynpro.progmodel.api
    .IWDOVSContextNotificationListener#applyResult(...)*/
      public void applyResult(IWDNodeElement applicationNodeElement,
      IWDNodeElement queryOutputNodeElement) {
      IPrivateView2.IZexigo_Cats_Search_InputElement ovsCallerNodeElement = (IPrivateView2.IZexigo_Cats_Search_InputElement) applicationNodeElement;
      IPublicOVSCust.IZexigo_Cats_Search_OutputElement output = (IPublicOVSCust.IZexigo_Cats_Search_OutputElement) queryOutputNodeElement;
      ovsCallerNodeElement.setVariant(output.getAttributeValue());
      /* @see com.sap.tc.webdynpro.progmodel.api
    .IWOVSC
      DontextNotificationListener#applyInputValues(...) */
      public void applyInputValues(IWDNodeElement applicationNodeElement,IWDNodeElement queryInputNodeElement) {
      Object initialValue = applicationNodeElement.getAttributeValue("Variant");
      queryInputNodeElement.setAttributeValue("Variant", initialValue);
      private IWDOVSContextNotificationListener ovsListener = new OVSDemoContextNotificationListener();
      public com.sap.tc.webdynpro.progmodel.api.IWDOVSContextNotificationListener getOVSListener( ) {
      return ovsListener;
      public com.sap.tc.webdynpro.progmodel.api.IWDNode getOVSInputNode( ) {
    //     @@begin getOVSInputNode()
      return wdContext.nodeZexigo_Cats_Search_Input();
    //     @@end
      public com.sap.tc.webdynpro.progmodel.api.IWDNode getOVSOutputNode( ) {
    //     @@begin getOVSOutputNode()
    return wdContext.nodeQueryOutputNode();
    //     @@end
      //@@begin others
      //@@end

    Hi all,
       Can someone help rectify errors in the below code. I can't able to run this code
    // This file has been generated partially by the Web Dynpro Code Generator.
    // MODIFY CODE ONLY IN SECTIONS ENCLOSED BY @@begin AND @@end.
    // ALL OTHER CHANGES WILL BE LOST IF THE FILE IS REGENERATED.
    package se.abb.com;
    // IMPORTANT NOTE:
    // ALL IMPORT STATEMENTS MUST BE PLACED IN THE FOLLOWING SECTION ENCLOSED
    // BY @@begin imports AND @@end. FURTHERMORE, THIS SECTION MUST ALWAYS CONTAIN
    // AT LEAST ONE IMPORT STATEMENT (E.G. THAT FOR IPrivateOVSCust).
    // OTHERWISE, USING THE ECLIPSE FUNCTION "Organize Imports" FOLLOWED BY
    // A WEB DYNPRO CODE GENERATION (E.G. PROJECT BUILD) WILL RESULT IN THE LOSS
    // OF IMPORT STATEMENTS.
    //@@begin imports
    import se.abb.com.wdp.IPrivateOVSCust;
    import se.abb.com.wdp.IPrivateView2;
    import se.abb.com.wdp.IPublicOVSCust;
    import se.abb.com01.Zexigo_Cats_Search_Input;
    import se.abb.com01.Zexigo_Cvr_Update_Input;
    import com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException;
    import com.sap.tc.webdynpro.progmodel.api.IWDMessageManager;
    import com.sap.tc.webdynpro.progmodel.api.IWDNode;
    import com.sap.tc.webdynpro.progmodel.api.IWDNodeElement;
    import com.sap.tc.webdynpro.progmodel.api.IWDOVSContextNotificationListener;
    //@@end
    //@@begin documentation
    //@@end
    public class OVSCust
    Logging location.
      private static final com.sap.tc.logging.Location logger =
        com.sap.tc.logging.Location.getLocation(OVSCust.class);
      static
        //@@begin id
        String id = "$Id$";
        //@@end
        com.sap.tc.logging.Location.getLocation("ID.com.sap.tc.webdynpro").infoT(id);
    Private access to the generated Web Dynpro counterpart
    for this controller class.  </p>
    Use <code>wdThis</code> to gain typed access to the context,
    to trigger navigation via outbound plugs, to get and enable/disable
    actions, fire declared events, and access used controllers and/or
    component usages.
    @see se.abb.com.wdp.IPrivateOVSCust for more details
      private final IPrivateOVSCust wdThis;
    Root node of this controller's context. </p>
    Provides typed access not only to the elements of the root node
    but also to all nodes in the context (methods node<i>XYZ</i>())
    and their currently selected element (methods current<i>XYZ</i>Element()).
    It also facilitates the creation of new elements for all nodes
    (methods create<i>XYZ</i>Element()). </p>
    @see se.abb.com.wdp.IPrivateOVSCust.IContextNode for more details.
      private final IPrivateOVSCust.IContextNode wdContext;
    A shortcut for <code>wdThis.wdGetAPI()</code>. </p>
    Represents the generic API of the generic Web Dynpro counterpart
    for this controller. </p>
      private final com.sap.tc.webdynpro.progmodel.api.IWDController wdControllerAPI;
    A shortcut for <code>wdThis.wdGetAPI().getComponent()</code>. </p>
    Represents the generic API of the Web Dynpro component this controller
    belongs to. Can be used to access the message manager, the window manager,
    to add/remove event handlers and so on. </p>
      private final com.sap.tc.webdynpro.progmodel.api.IWDComponent wdComponentAPI;
      public OVSCust(IPrivateOVSCust wdThis)
        this.wdThis = wdThis;
        this.wdContext = wdThis.wdGetContext();
        this.wdControllerAPI = wdThis.wdGetAPI();
        this.wdComponentAPI = wdThis.wdGetAPI().getComponent();
      //@@begin javadoc:wdDoInit()
      /** Hook method called to initialize controller. */
      //@@end
      public void wdDoInit()
        //@@begin wdDoInit()
        //$$begin Service Controller(-1119166442)
        wdContext.nodeZexigo_Cvr_Update_Input_OVS().bind(new Zexigo_Cvr_Update_Input());
        //$$end
         Zexigo_Cats_Search_Input searchInput = new Zexigo_Cats_Search_Input();
         wdContext.nodeZexigo_Cats_Search_Input().bind(searchInput);   
        //@@end
      //@@begin javadoc:wdDoExit()
      /** Hook method called to clean up controller. */
      //@@end
      public void wdDoExit()
        //@@begin wdDoExit()
        //@@end
      //@@begin javadoc:executeZexigo_Cvr_Update_Input_OVS()
      /** Declared method. */
      //@@end
      public void executeZexigo_Cvr_Update_Input_OVS( )
        //@@begin executeZexigo_Cvr_Update_Input_OVS()
        //$$begin Service Controller(-1263234559)
        IWDMessageManager manager = wdComponentAPI.getMessageManager();
        try
          wdContext.currentZexigo_Cvr_Update_Input_OVSElement().modelObject().execute();
          wdContext.nodeOutput_update().invalidate();
        catch(WDDynamicRFCExecuteException e)
          manager.reportException(e.getMessage(), false);
        //$$end
        //@@end
    The following code section can be used for any Java code that is
    not to be visible to other controllers/views or that contains constructs
    currently not supported directly by Web Dynpro (such as inner classes or
    member variables etc.). </p>
    Note: The content of this section is in no way managed/controlled
    by the Web Dynpro Designtime or the Web Dynpro Runtime.
      //@@begin others
      private class OVSDemoContextNotificationListener implements IWDOVSContextNotificationListener {
      /* @see com.sap.tc.webdynpro.progmodel.api
      .IWDOVSContextNotificationListener#onQuery(... */
      public void onQuery(IWDNodeElement queryInputNodeElement,IWDNode queryOutputNode) {
      IPublicOVSCust.IZexigo_Cats_Search_InputElement ovsInput = (IPublicOVSCust.IZexigo_Cats_Search_InputElement) queryInputNodeElement;
      IPublicOVSCust.IZexigo_Cats_Search_OutputNode ovsOutput = (IPublicOVSCust.IZexigo_Cats_Search_OutputNode) queryOutputNode;
      try {
      ovsInput.modelObject().execute();
    //      invalidate 'Output' model node via a top-down access
    //      approach
      ovsInput.node().getChildNode("Output",0).invalidate();
      } catch (Exception e) {
      IWDMessageManager msgMgr = wdComponentAPI.getMessageManager();
      msgMgr.reportException(e.getLocalizedMessage(), false);
      /* @see com.sap.tc.webdynpro.progmodel.api
    .IWDOVSContextNotificationListener#applyResult(...)*/
      public void applyResult(IWDNodeElement applicationNodeElement,
      IWDNodeElement queryOutputNodeElement) {
      IPrivateView2.IZexigo_Cats_Search_InputElement ovsCallerNodeElement = (IPrivateView2.IZexigo_Cats_Search_InputElement) applicationNodeElement;
      IPublicOVSCust.IZexigo_Cats_Search_OutputElement output = (IPublicOVSCust.IZexigo_Cats_Search_OutputElement) queryOutputNodeElement;
      ovsCallerNodeElement.setVariant(output.getAttributeValue());
      /* @see com.sap.tc.webdynpro.progmodel.api
    .IWOVSC
      DontextNotificationListener#applyInputValues(...) */
      public void applyInputValues(IWDNodeElement applicationNodeElement,IWDNodeElement queryInputNodeElement) {
      Object initialValue = applicationNodeElement.getAttributeValue("Variant");
      queryInputNodeElement.setAttributeValue("Variant", initialValue);
      private IWDOVSContextNotificationListener ovsListener = new OVSDemoContextNotificationListener();
      public com.sap.tc.webdynpro.progmodel.api.IWDOVSContextNotificationListener getOVSListener( ) {
      return ovsListener;
      public com.sap.tc.webdynpro.progmodel.api.IWDNode getOVSInputNode( ) {
    //     @@begin getOVSInputNode()
      return wdContext.nodeZexigo_Cats_Search_Input();
    //     @@end
      public com.sap.tc.webdynpro.progmodel.api.IWDNode getOVSOutputNode( ) {
    //     @@begin getOVSOutputNode()
    return wdContext.nodeQueryOutputNode();
    //     @@end
      //@@begin others
      //@@end

  • PowerOn Failed Error: Domain Does Not Exist

    [Simon Thorpe's blog |http://blogs.oracle.com/simonthorpe/2009/07/migrating_a_vmware_server_2_wi.html] I'm new to OracleVM. The wizard through OVM Manager successfully converted a windows VMWare vm to ovm. I was able to start up the VM once and get the driver updates loaded. I was following Simon Thorpe's blog and other documents to complete this.
    Upon reboot, I get the following error:
    Start - /OVS/running_pool/ECM_Xmonth_2010_vm
    PowerOn Failed : Result - failed:<Exception: return=>failed:<Exception: ['xm', 'create', '/var/ovs/mount/69D37D3828A040A08A7E01E5DE43C1D8/running_pool/ECM_Xmonth_2010_vm/vm.cfg'] => Error: Domain 'ECM_Xmonth_2010_vm' does not exist.
    >
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSXXenVM.py", line 57, in xen_start_vm
    run_cmd(args=cmd)
    File "/opt/ovs-agent-2.3/OVSCommons.py", line 69, in run_cmd
    raise Exception('%s => %s' % (cmdlist, p.childerr.read()))
    >
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSSiteVM.py", line 113, in start_vm
    raise e
    Here's my vm.cfg
    acpi = 1
    apic = 1
    builder = 'hvm'
    device_model = '/usr/lib/xen/bin/qemu-dm'
    disk = ['file:/var/ovs/mount/69D37D3828A040A08A7E01E5DE43C1D8/running_pool/ECM_Xmonth_2010_vm/ECM_XMonth_2010_disk.img,hda,w',
    ',hdc:cdrom,r',
    kernel = '/usr/lib/xen/boot/hvmloader'
    maxmem = 2999
    memory = 2999
    name = 'ECM_Xmonth_2010_vm'
    on_crash = 'restart'
    on_reboot = 'restart'
    pae = 1
    sdl = 1
    serial = 'pty'
    timer_mode = '0'
    usbdevice = 'tablet'
    uuid = '4d3f3741-e29c-472a-bfaf-7416d31d21e8'
    vcpus = 1
    vif = ['bridge=xenbr0,mac=00:16:3E:4C:BF:71,type=ioemu']
    vif_other_config = []
    vncconsole = 1
    vnclisten = '0.0.0.0'
    vncpasswd = '****'
    Any advice?
    Edited by: dierardi on Jan 6, 2010 9:21 AM
    Edited by: dierardi on Jan 6, 2010 9:24 AM
    Edited by: dierardi on Jan 6, 2010 10:00 AM

    dierardi wrote:
    PowerOn Failed : Result - failed:<Exception: return=>failed:<Exception: ['xm', 'create', '/var/ovs/mount/69D37D3828A040A08A7E01E5DE43C1D8/running_pool/ECM_Xmonth_2010_vm/vm.cfg'] => Error: Domain 'ECM_Xmonth_2010_vm' does not exist.Check /var/log/xen/xend.log for errors during boot: Essentially, the domain is failing to be created properly on startup.
    If this is a linux guest, try running xm create -c vm.cfg from the ECM_Xmonth_2010_vm directory to start the guest with the console immediately attached. You may be able to see a boot/GRUB related error. If this is a Windows guest, you could start it paused with xm create -p vm.cfg and then attach a VNC console. Once you have a VNC session, you can resume the guest and it will begin booting.

  • /OVS empty after upgrading to VM 2.2

    I have noticed since upgrading to VM 2.2 my /OVS directory is now empty and I have a directory /OVS.<timestamp>.bak containing all the files/directories from my VM 2.1.2 installation.
    I was managing this via Grid Control 10.2.0.5.0 but as this does not currently support VM Server 2.2 - I have installed VM Manager 2.2 with a view to creating a new Server Pool to populate /OVS
    However on doing this I got the following error -
    OVM-1011 OVM Manager communication with jalfrezi for operation HA Setup for Oracle VM Agent 2.2 failed:<Exception: Cluster root not found.>
    (or something similar)
    So the suggestion (via a few doc bugs) is to run -
    repos.py -n and repos.py -r
    To setup the Storage Repository
    When I run repos.py -n <storage> on my system
    I get a message saying something like -
    Mount point: /tmp/ovsrepos_SBkc1q
    Error: ['mount','/OVS','/tmp/ovsrepos_SBkc1q'] => mount: /OVS is not a block device
    and the same for any directory I use
    e.g.
    repos.py -n /test
    When I created this VM Server originally I used 2X250GB SATA drives as a Logical Volume (which was supported)....could this be the reason I cannot now create a storage repository now ?
    Should I re-install and just create non logical devices ?
    Thanks

    My reply may be unrelated, But I had been through the exact same situation.
    I had 4 OVM servers running 2.1.5 and later I followed Oracle recommended way (http://download.oracle.com/docs/cd/E15458_01/doc.22/e16206/toc.htm#BEJHBIIC) to upgrade them to 2.2 and post upgrade, I find that the storage is mounted under +/var/ovs/mount/uuid+ ONLY on the master pool server and rest 3 server had an empty /OVS directory.
    I tried many troubleshooting steps and have confirmed that in this scenario, restarting the "ovs-agent" service on MASTER pool server would mount the storage under +/var/ovs/mount/uuid+ on all the NON-master servers.
    To confirm this solution, I have tried upgrade process multiple times, faced exact same issue and restarting "ovs-agent" service on MASTER pool server got me going.
    --Dheeraj.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Error: Could not find machine_name in any storage repository.

    Hi,
    we got 4 servers in the same Pool Group called PROD.
    vmserver10 = Virtual Machine Server     
    vmserver13 = Virtual Machine Server     
    vmserver14 = Server Pool Master,Utility Server,Virtual Machine Server     
    vmserver15 = Virtual Machine Server     
    This is shared with an iSCSI partition. All servers got the following configuration:
    */etc/hosts*
    +# Do not remove the following line, or various programs+
    +# that require network functionality will fail.+
    +127.0.0.1          localhost.localdomain localhost+
    +::1          localhost6.localdomain6 localhost6+
    +# Hypervisors+
    +193.109.174.110          vmserver10.pic.es vmserver10+
    +193.109.174.111          vmserver11.pic.es vmserver11+
    +193.109.174.112          vmserver12.pic.es vmserver12+
    +193.109.174.113          vmserver13.pic.es vmserver13+
    +193.109.174.114          vmserver14.pic.es vmserver14+
    +193.109.174.115          vmserver15.pic.es vmserver15+
    +193.109.174.116          vmserver16.pic.es vmserver16+
    +193.109.174.117          vmserver17.pic.es vmserver17+
    +193.109.174.118          vmserver18.pic.es vmserver18+
    +193.109.174.119          vmserver19.pic.es vmserver19+
    +# Other Hypervisors+
    +193.109.174.51          vminfra01.pic.es vminfra01+
    +193.109.174.58          vminfra02.pic.es vminfra02+
    +# iSCSI Server+
    +193.109.174.106          disk001.pic.es disk001+
    cat /etc/ocfs2/cluster.conf
    node:
    ip_port     = 7777
    ip_address  = 193.109.174.114
    number      = 0
    name        = vmserver14.pic.es
    cluster     = ocfs2
    node:
    ip_port     = 7777
    ip_address  = 193.109.174.113
    number      = 1
    name        = vmserver13.pic.es
    cluster     = ocfs2
    node:
    ip_port     = 7777
    ip_address  = 193.109.174.115
    number      = 2
    name        = vmserver15.pic.es
    cluster     = ocfs2
    node:
    ip_port     = 7777
    ip_address  = 193.109.174.110
    number      = 3
    name        = vmserver10.pic.es
    cluster     = ocfs2
    cluster:
    node_count  = 4
    name        = ocfs2
    We have working this since few weeks ago. We created a new machine from the Oracle VM Manager but when starting up this machine we get the following error:
    Start - /OVS/running_pool/310_wmsmonitor
    PowerOn Failed : Result - failed:<Exception: Could not find 'running_pool/310_wmsmonitor' in any storage repository.>
    ++
    StackTrace:
    + File "/opt/ovs-agent-2.3/OVSSiteVM.py", line 113, in start_vm+
    + raise e+
    But when creating it, not all servers can see this machine in the shared storage...
    +[root@vmserver15 running_pool]# ls /OVS/running_pool/ | grep wmsmonitor+
    +312_wmsmonitor+
    +[root@vmserver14 running_pool]# ls /OVS/running_pool/ | grep wmsmonitor+
    +[root@vmserver13 running_pool]# ls /OVS/running_pool/ | grep wmsmonitor+
    +312_wmsmonitor+
    +[root@vmserver10 running_pool]# ls /OVS/running_pool/ | grep wmsmonitor+
    After few seconds, nobody sees this machine...
    +[root@vmserver15 running_pool]# ls /OVS/running_pool/ | grep wmsmonitor+
    +[root@vmserver14 running_pool]# ls /OVS/running_pool/ | grep wmsmonitor+
    +[root@vmserver13 running_pool]# ls /OVS/running_pool/ | grep wmsmonitor+
    +[root@vmserver10 running_pool]# ls /OVS/running_pool/ | grep wmsmonitor+
    ... but this machine can be found it in the manager... and of course when I start it I get the above error.
    Anybody knows what is happening to my system?
    Thanks in advance,
    Marc Caubet

    Marc Caubet wrote:
    Anybody knows what is happening to my system?No, but something is very wrong with your storage. I'd log an SR for this.

  • Exiting from OVS

    Hi All,
    Is there any way to exit from an OVS ?
    I've tried giving exit.
    But it throws an error message:  OVS: Methode SET_OUTPUT_TABLE Cannot Be Called .
    Any ideas?
    Thanks,
    Fathima

    Hi Fathima,
    Check the below code.How to raise the error message.
    when if_wd_ovs=>co_phase_2.
      If phase 1 is implemented, use the field input for the
      selection of the table.
      If phase 1 is omitted, use values from your own context.
          if ovs_callback_object->query_parameters is not bound.
        TODO exception handling
          endif.
          assign ovs_callback_object->query_parameters->*
                                  to <query_params>.
          if not <query_params> is assigned.
    TODO exception handling
          endif.
          l_selopt-low = <query_params>-early.
          l_selopt-high = <query_params>-late.
          l_selopt-option = 'BT'.
          l_selopt-sign = 'I'.
          insert l_selopt into table l_selopt_tab.
          call function 'BAPI_FLIGHT_GETLIST'
            tables
              date_range  = l_selopt_tab
              flight_list = l_flight_list
              return      = l_bapi_return.
          l_api = wd_this->wd_get_api( ).
          l_msg_manager = l_api->get_message_manager( ).
          loop at l_bapi_return into wa_bapi_return where type = 'E' or type = 'A'.
            l_msg_text = wa_bapi_return-message.
            l_msg_manager->report_error_message( message_text = l_msg_text ).
          endloop.
          loop at l_flight_list into wa_flight_list.
            wa_select_list-carrid = wa_flight_list-airlineid.
            wa_select_list-connid = wa_flight_list-connectid.
            wa_select_list-fldate = wa_flight_list-flightdate.
            insert wa_select_list into table l_select_list.
          endloop.
          ovs_callback_object->set_output_table( output = l_select_list ).

  • Oracle VM 3.1.1 Manager - OVM Servers in "Starting" status

    Hi,
    today I've downloaded Oracle VM Manager 3.1.1(Upgrade only) from e-delivery, and upgraded my previous version of OVMM 3.0.3 without any problems. My servers are still running on OVM Server 3.0.3 version.
    Usually, my practice for upgrading was:
    - first upgrade OVMM
    - login into OVMM
    - migrate some VMs to free-up one OVM server
    - then I upgrade that server to newer version of OVM Server
    - bring back VMs to updated server to free-up another one and so on.
    After login into new OVMM 3.1.1, I see all my servers, storage and VMs running on these servers as they was set before. But, my servers are in Starting state. I cannot manage any of my VMs, nothing! Later on, I've manually restarted one server(S1) and tried to upgrade it to OVM 3.1.1 version but I had some problems with mounting ISO, so I've only restated it. After that, that server(S1) showed as Running and OK. Then I tried to do that with another server(S2), migrated VMs to S1 server, restarted S2 but it remained Starting.
    So now my situation is:
    - have one server(S1) in Running state with several VMs
    - other servers are in Starting state also with some VMs
    I cannot shutdown servers, as theirs status is not Running, cannot migrate or manage VMs at all.
    Please, how can I set right status for my servers without shutting VMs?
    Thanks in advance.

    Hi,
    now I've got very serious situation. I've reinstalled OVMM 3.1.1 with -uuid option, and tried to rediscover servers. Only one server shows up, S1, no other servers, they cannot be added. Error from ovs-agent log on these servers show this message when I try to rediscover it:
    ERROR  (OVSCommons:143)  catch_error: rpmdb open failed
    Luckly, my VMs are working fine, but now I'm not sure till when they will.
    Is there any possible solution to resolve this?
    Best regards,
    I resolved ERROR  (OVSCommons:143)  catch_error: rpmdb open failed by executing two commands on each server that I couldn't add:
    rm -rf /var/lib/rpm/__db*
    rpm --rebuilddb
    after this my servers automatically were added in OVMM. Then, I rediscovered repository and my VMs showed up as well. So, could it be possible that corrupted rpm database caused all this?
    Thanks.
    Edited by: DBagy on May 15, 2012 10:34 AM

  • Running out of memory when trying to run two VMs

    Hi all,
    I have created a VM (RHEL 5 with Oracle 11g) and cloned it in the same server pool. When i tried to start up the clone, I received the following error:
    Start - /OVS/running_pool/13_OVM_10g_1
    PowerOn Failed : Result - failed:errcode=20000, errmsg=No enough memory to run vm(/OVS/running_pool/13_OVM_10g_1), required memory=2048.
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSSiteVM.py", line 124, in start_vm
    Is there a way to configure more memory for additional VMs?
    Thanks.

    I thought is was not enough physical memory. The server has 4GB of RAM and the BIOS can see it.
    However, the OS only sees 574 MB:
    [root@patchy ~]# free -m
                 total       used       free     shared    buffers     cached
    Mem:           574        228        345          0         16         63
    -/+ buffers/cache:        148        425
    Swap:         1027          0       1027xm info shows 4095MB:
    [root@patchy ~]# xm info
    host                   : patchy
    release                : 2.6.18-128.2.1.4.25.el5xen
    version                : #1 SMP Tue Mar 23 12:43:27 EDT 2010
    machine                : i686
    nr_cpus                : 4
    nr_nodes               : 1
    cores_per_socket       : 1
    threads_per_core       : 2
    cpu_mhz                : 2992
    hw_caps                : bfebfbff:20100800:00000000:00000180:0000641d:00000000:00000000:00000000
    virt_caps              :
    total_memory           : 4095
    free_memory            : 1418
    node_to_cpu            : node0:0-3
    node_to_memory         : node0:1418
    xen_major              : 3
    xen_minor              : 4
    xen_extra              : .0
    xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p
    xen_scheduler          : credit
    xen_pagesize           : 4096
    platform_params        : virt_start=0xff800000
    xen_changeset          : unavailable
    cc_compiler            : gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)
    cc_compile_by          : mockbuild
    cc_compile_domain      : (none)
    cc_compile_date        : Wed Mar 24 16:00:43 EDT 2010
    xend_config_format     : 4xm dmesg shows (only showing partial output to preserve space):
    [root@patchy ~]# xm dmesg
    \ \/ /___ _ __   |___ /| || |  / _ \
      \  // _ \ \047_ \    |_ \| || |_| | | |
      /  \  __/ | | |  ___) |__   _| |_| |
    /_/\_\___|_| |_| |____(_) |_|(_)___/
    (XEN) Xen version 3.4.0 (mockbuild@(none)) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) Wed Mar 24 16:00:43 EDT 2010
    (XEN) Latest ChangeSet: unavailable
    (XEN) Command line: dom0_mem=574M
    (XEN) Xen-e820 RAM map:
    (XEN)  0000000000000000 - 00000000000a0000 (usable)
    (XEN)  0000000000100000 - 00000000dffc0000 (usable)
    (XEN)  00000000dffc0000 - 00000000dffcfc00 (ACPI data)
    (XEN)  00000000dffcfc00 - 00000000dffff000 (reserved)
    (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
    (XEN)  00000000fec00000 - 00000000fec90000 (reserved)
    (XEN)  00000000fed00000 - 00000000fed00400 (reserved)
    (XEN)  00000000fee00000 - 00000000fee10000 (reserved)
    (XEN)  00000000ffb00000 - 0000000100000000 (reserved)
    (XEN)  0000000100000000 - 0000000120000000 (usable)
    (XEN) System RAM: 4095MB (4193664kB)
    (XEN) Detected 2992.646 MHz processor.
    (XEN) CPU0: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
    (XEN) Booting processor 1/6 eip 8c000
    (XEN) CPU1: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
    (XEN) Booting processor 2/1 eip 8c000
    (XEN) CPU2: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
    (XEN) Booting processor 3/7 eip 8c000
    (XEN) CPU3: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
    (XEN) Total of 4 processors activated.
    (XEN) mm.c:804:d1 Error getting mfn 17e9b (pfn 5555555555555555) from L1 entry 0000000017e9b025 for dom1
    (XEN) mm.c:4224:d1 ptwr_emulate: fixing up invalid PAE PTE 0000000017e9b025I am able to start up one VM, and xm list shows that it has 2GB of memory:
    [root@patchy ~]# xm list
    Name                                        ID   Mem VCPUs      State   Time(s)
    13_OVM_10g_1                                 1  2048     2     -b----     33.6
    Domain-0                                     0   574     4     r-----    100.9When I try to start a clone of the first VM from the VM Manager, it errors out with the following error message:
    Start - /OVS/running_pool/19_10g_clone_1
    PowerOn Failed : Result - failed:errcode=20000, errmsg=No enough memory to run vm(/OVS/running_pool/19_10g_clone_1), required memory=2048.
    StackTrace:
      File "/opt/ovs-agent-2.3/OVSSiteVM.py", line 124, in start_vm
        raise eI'm not sure how Xen handles memory, but I would imagine that dom0 should see all 4GB of RAM.
    How can I make sure that all 4GB of RAM are available?
    Thanks.
    Edited by: Christoph on Jan 5, 2011 8:39 AM

  • Oracle VM 3.1.1 - Failed to start PVM machine

    Hi,
    We're using Oracle VM 3.1.1 on HP ProLiant BL460c G7 servers. We have a 2-node cluster running. We've just recently installed them, and succesfuly created PVM vms but when trying to start them we're receiving the following error on OVM Manager:
    Starting operation 'Bridge Configure Operation' on object '0004fb0000200000bff878c5197d0da1 (network.EthernetPort (2) in ovm01)'
    Bridge [0004fb0010df7d1] already exists (and should exist) on interface [eth1] on server [ovm01]; skipping bridge creation
    Completed operation 'Bridge Configure Operation' completed with direction ==> DONE
    Starting operation 'Virtual Machine Start' on object '0004fb000006000073354ef14166aee6 (fblvm01)'
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: dispatch to server: ovm01 failed. OVMAPI_4004E Server Failed Command: dispatch https://?uname?:[email protected]:8899/api/2 start_vm 0004fb0000030000af269b04471b29e5 0004fb000006000073354ef14166aee6, Status: org.apache.xmlrpc.XmlRpcException: exceptions.RuntimeError:Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg'] failed (1): stderr: Error: (22, 'Invalid argument')
    stdout: Using config file "/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg".
    This is the vm.cfg filed created by ovmm:
    vif = ['mac=00:21:f6:00:00:27,bridge=0004fb0010df7d1']
    OVM_simple_name = 'fblvm01'
    guest_os_type = 'linux'
    disk = ['file:/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualDisks/0004fb00001200004acb9a7d32512731.img,xvda,w']
    bootargs = 'nfs:ovmm:/data/ol58'
    uuid = '0004fb00-0006-0000-7335-4ef14166aee6'
    on_reboot = 'restart'
    boot = 'n'
    cpu_weight = 27500
    memory = 4096
    cpu_cap = 0
    maxvcpus = 2
    OVM_high_availability = True
    OVM_description = 'fblvm01'
    on_poweroff = 'destroy'
    on_crash = 'restart'
    bootloader = '/usr/bin/xenpvboot'
    maxmem = 4096
    name = '0004fb000006000073354ef14166aee6'
    vfb = ['type=vnc,vncunused=1,vnclisten=127.0.0.1,keymap=es']
    vcpus = 1
    OVM_os_type = 'Oracle Linux 5'
    OVM_cpu_compat_group = ''
    OVM_domain_type = 'xen_pvm'
    This is the complete error on ovs-agent.log:
    [2011-06-04 05:13:12 9908] DEBUG (common:46) dispatch function discover_network to server https://oracle:******@172.16.7.3:8899/api/2
    [2011-06-04 05:13:12 9909] DEBUG (service:77) discover_network: ()
    [2011-06-04 05:13:12 9909] DEBUG (service:85) discover_network: call completed.
    [2011-06-04 05:13:12 9910] DEBUG (common:46) dispatch function start_vm to server https://oracle:******@172.16.7.3:8899/api/2
    [2011-06-04 05:13:12 9911] DEBUG (service:77) start_vm: ('0004fb0000030000af269b04471b29e5', '0004fb000006000073354ef14166aee6')
    [2011-06-04 05:13:13 9911] ERROR (service:96) catch_error: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg'] failed (1): stderr: Error: (22, 'Invalid argument')
    stdout: Using config file "/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg".
    Traceback (most recent call last):
    File "/usr/lib64/python2.4/site-packages/agent/service.py", line 94, in wrapper
    return func(*args)
    File "/usr/lib64/python2.4/site-packages/agent/hypervisor/xenxm.py", line 719, in start_vm
    run_cmd(['xm', 'create', path])
    File "/usr/lib64/python2.4/site-packages/agent/common.py", line 66, in run_cmd
    raise RuntimeError('Command: %s failed (%s): stderr: %s stdout: %s'
    RuntimeError: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg'] failed (1): stderr: Error: (22, 'Invalid argument')
    stdout: Using config file "/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg".
    [2011-06-04 05:13:13 9910] ERROR (common:50) dispatch error: start_vm: <Fault 1: 'exceptions.RuntimeError:Command: [\'xm\', \'create\', \'/OVS/Repositories/0004
    fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg\'] failed (1): stderr: Error: (22, \'Invalid argument\')\n stdout: Using config file "/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg".\n'>
    [2011-06-04 05:13:13 9910] ERROR (service:96) catch_error: <Fault 1: 'exceptions.RuntimeError:Command: [\'xm\', \'create\', \'/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg\'] failed (1): stderr: Error: (22, \'Invalid argument\')\n stdout: Using config file "/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg".\n'>
    Traceback (most recent call last):
    File "/usr/lib64/python2.4/site-packages/agent/service.py", line 94, in wrapper
    return func(*args)
    File "/usr/lib64/python2.4/site-packages/agent/common.py", line 48, in dispatch
    return getattr(sp, func)(*args)
    File "/usr/lib64/python2.4/site-packages/agent/utils/xmlrpclib.py", line 1099, in __call__
    return self.__send(self.__name, args)
    File "/usr/lib64/python2.4/site-packages/agent/utils/xmlrpclib.py", line 1386, in __request
    verbose=self.__verbose
    File "/usr/lib64/python2.4/site-packages/agent/utils/xmlrpclib.py", line 1150, in request
    return self._parse_response(h.getfile(), sock)
    File "/usr/lib64/python2.4/site-packages/agent/utils/xmlrpclib.py", line 1289, in parseresponse
    return u.close()
    File "/usr/lib64/python2.4/site-packages/agent/utils/xmlrpclib.py", line 746, in close
    raise Fault(**self._stack[0])
    Fault: <Fault 1: 'exceptions.RuntimeError:Command: [\'xm\', \'create\', \'/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg\'] failed (1): stderr: Error: (22, \'Invalid argument\')\n stdout: Using config file "/OVS/Repositories/0004fb0000030000af269b04471b29e5/VirtualMachines/0004fb000006000073354ef14166aee6/vm.cfg".\n'>
    Has anyone seen this problem before?
    Thanks, Franco.

    Well, in the end we had a problem we the NFS share, it was possible to mount it on other servers but all read operation failed, we moved the iso to a different nfs server and it worked just fine. Closing the thread.

  • Updating Oracle VM Manager from 3.1.1 to 3.2.1 where server is yum repo

    I have a server running Oracle Enterprise Linux 6.3. Upon which is running Oracle VM Manager 3.1.1 ("BUILDID=3.1.1.305" from /u01/app/oracle/ovm-manager-3/.config).
    This server is also my Oracle Enterprise Linux yum repo. This means its subscribed channels are (on ULN):
    - Latest Unbreakable Enterprise Linux Kernel for Oracle Linux (x86_64)
    - Oracle Linux 6 Add ons (x86_64)
    - Oracle Linus 6 Latest (x86_64)
    - Oracle VM 3 latest
    - Oracle VM 3.2.1 Server Patches
    Note that the last one was "Oracle VM 3.1.1 Server Patches" until this attempt to update. The "Yum Server" button is also ticked on ULN and I've followed the instructions on http://www.oracle.com/technetwork/articles/servers-storage-admin/yum-repo-setup-1659167.html.
    Now, when I attempt a "yum update" on this server I get the following:
    --> Finished Dependency Resolution
    Error: Package: kernel-uek-2.6.39-300.28.1.el5uek.x86_64 (ovm3_3.2.1_x86_64_patch)
    Requires: mkinitrd >= 5.1.19.6-71.0.10
    Available: mkinitrd-5.1.19.6-61.100.1.el5_5.5.x86_64 (ovm3_x86_64_latest)
    mkinitrd = 5.1.19.6-61.100.1.el5_5.5
    Available: mkinitrd-5.1.19.6-61.100.1.el5_5.8.x86_64 (ovm3_x86_64_latest)
    mkinitrd = 5.1.19.6-61.100.1.el5_5.8
    Available: mkinitrd-5.1.19.6-61.100.1.el5_5.11.x86_64 (ovm3_x86_64_latest)
    mkinitrd = 5.1.19.6-61.100.1.el5_5.11
    Available: mkinitrd-5.1.19.6-71.100.1.el5_7.3.x86_64 (ovm3_x86_64_latest)
    mkinitrd = 5.1.19.6-71.100.1.el5_7.3
    Available: mkinitrd-5.1.19.6-71.100.1.el5_7.3.1.x86_64 (ovm3_x86_64_latest)
    mkinitrd = 5.1.19.6-71.100.1.el5_7.3.1
    Available: mkinitrd-5.1.19.6-71.100.1.el5_7.5.x86_64 (ovm3_x86_64_latest)
    mkinitrd = 5.1.19.6-71.100.1.el5_7.5
    Error: Package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64 (ol6_x86_64_latest)
    Requires: libgnutls.so.26()(64bit)
    Removing: gnutls-2.8.5-4.el6_2.2.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
    libgnutls.so.26()(64bit)
    Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
    Not found
    Available: gnutls-2.8.5-4.el6.x86_64 (ol6_x86_64_latest)
    libgnutls.so.26()(64bit)
    Available: gnutls-1.4.1-3.el5_3.5.x86_64 (ovm3_x86_64_latest)
    Not found
    Error: Package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
    Requires: dbus-python
    Removing: dbus-python-0.83.0-6.1.el6.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
    dbus-python = 0.83.0-6.1.el6
    Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
    Not found
    Available: dbus-python-0.70-9.el5_4.x86_64 (ovm3_x86_64_latest)
    dbus-python = 0.70-9.el5_4
    Error: Package: python-urlgrabber-3.9.1-9.100.3.el5.noarch (ovm3_x86_64_latest)
    Requires: python(abi) = 2.4
    Installed: python-2.6.6-29.el6_3.3.x86_64 (@ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.4.3-27.100.1.el5_5.6.x86_64 (ovm3_x86_64_latest)
    python(abi) = 2.4
    Available: python-2.6.5-3.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.5-3.el6_0.2.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-20.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-29.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-29.el6_2.2.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Error: Package: ovs-agent-3.2.1-183.x86_64 (ovm3_x86_64_latest)
    Requires: python(abi) = 2.4
    Installed: python-2.6.6-29.el6_3.3.x86_64 (@ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.4.3-27.100.1.el5_5.6.x86_64 (ovm3_x86_64_latest)
    python(abi) = 2.4
    Available: python-2.6.5-3.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.5-3.el6_0.2.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-20.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-29.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-29.el6_2.2.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Error: Package: neon-0.29.3-2.el6.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
    Requires: libgnutls.so.26()(64bit)
    Removing: gnutls-2.8.5-4.el6_2.2.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
    libgnutls.so.26()(64bit)
    Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
    Not found
    Available: gnutls-2.8.5-4.el6.x86_64 (ol6_x86_64_latest)
    libgnutls.so.26()(64bit)
    Available: gnutls-1.4.1-3.el5_3.5.x86_64 (ovm3_x86_64_latest)
    Not found
    Error: Package: rhn-client-tools-1.0.0-87.0.6.el6.noarch (ol6_x86_64_latest)
    Requires: dbus-python
    Removing: dbus-python-0.83.0-6.1.el6.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
    dbus-python = 0.83.0-6.1.el6
    Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
    Not found
    Available: dbus-python-0.70-9.el5_4.x86_64 (ovm3_x86_64_latest)
    dbus-python = 0.70-9.el5_4
    Error: Package: xen-tools-4.1.3-25.el5.3.x86_64 (ovm3_3.2.1_x86_64_patch)
    Requires: python(abi) = 2.4
    Installed: python-2.6.6-29.el6_3.3.x86_64 (@ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.4.3-27.100.1.el5_5.6.x86_64 (ovm3_x86_64_latest)
    python(abi) = 2.4
    Available: python-2.6.5-3.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.5-3.el6_0.2.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-20.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-29.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-29.el6_2.2.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Error: Package: multiprocessing-2.6.1.1-1.x86_64 (ovm3_x86_64_latest)
    Requires: python(abi) = 2.4
    Installed: python-2.6.6-29.el6_3.3.x86_64 (@ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.4.3-27.100.1.el5_5.6.x86_64 (ovm3_x86_64_latest)
    python(abi) = 2.4
    Available: python-2.6.5-3.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.5-3.el6_0.2.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-20.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-29.el6.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Available: python-2.6.6-29.el6_2.2.i686 (ol6_x86_64_latest)
    python(abi) = 2.6
    Error: Package: neon-0.29.3-2.el6.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
    Requires: libgnutls.so.26(GNUTLS_1_4)(64bit)
    Removing: gnutls-2.8.5-4.el6_2.2.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
    libgnutls.so.26(GNUTLS_1_4)(64bit)
    Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
    Not found
    Available: gnutls-2.8.5-4.el6.x86_64 (ol6_x86_64_latest)
    libgnutls.so.26(GNUTLS_1_4)(64bit)
    Available: gnutls-1.4.1-3.el5_3.5.x86_64 (ovm3_x86_64_latest)
    Not found
    Error: Package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64 (ol6_x86_64_latest)
    Requires: libgnutls.so.26(GNUTLS_1_4)(64bit)
    Removing: gnutls-2.8.5-4.el6_2.2.x86_64 (@anaconda-OracleLinuxServer-201206261930.x86_64/6.3)
    libgnutls.so.26(GNUTLS_1_4)(64bit)
    Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
    Not found
    Available: gnutls-2.8.5-4.el6.x86_64 (ol6_x86_64_latest)
    libgnutls.so.26(GNUTLS_1_4)(64bit)
    Available: gnutls-1.4.1-3.el5_3.5.x86_64 (ovm3_x86_64_latest)
    Not found
    Error: Package: avahi-0.6.25-11.el6.x86_64 (@ol6_latest)
    Requires: libdaemon.so.0()(64bit)
    Removing: libdaemon-0.14-1.el6.x86_64 (@ol6_latest)
    libdaemon.so.0()(64bit)
    Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
    Not found
    Available: libdaemon-0.10-5.el5.x86_64 (ovm3_x86_64_latest)
    libdaemon.so.0()(64bit)
    Error: Package: avahi-0.6.25-11.el6.x86_64 (@ol6_latest)
    Requires: libdaemon >= 0.11
    Removing: libdaemon-0.14-1.el6.x86_64 (@ol6_latest)
    libdaemon = 0.14-1.el6
    Obsoleted By: ovs-release-3.2-5.208.x86_64 (ovm3_x86_64_latest)
    Not found
    Available: libdaemon-0.10-5.el5.x86_64 (ovm3_x86_64_latest)
    libdaemon = 0.10-5.el5
    You could try using --skip-broken to work around the problem
    You could try running: rpm -Va nofiles nodigest
    Can someone please explain what mistakes I've made so I can get this box updated (both OS and Oracle VM Manager), please? Do I simply need to exclude some channels for the duration of the update of the local box, then add them back in for the repo mirroring to continue working?
    With thanks,
    Ben

    It appears that for the most part the package ovs-release is the problem. To judge from the first half of a failed yum update. Why isn't there an ovs-release package that references el6 packages? Really, did I make a mistake installing Oracle VM Manager on OL6 given that http://public-yum.oracle.com/repo/OracleVM/OVM3/latest/x86_64/ contains only "el5"-tagged packages?
    Resolving Dependencies
    --> Running transaction check
    ---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be obsoleted
    --> Processing Dependency: dbus-python for package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch
    --> Processing Dependency: dbus-python for package: rhn-client-tools-1.0.0-87.0.6.el6.noarch
    ---> Package gnutls.x86_64 0:2.8.5-4.el6_2.2 will be obsoleted
    --> Processing Dependency: libgnutls.so.26()(64bit) for package: neon-0.29.3-2.el6.x86_64
    --> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
    --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: neon-0.29.3-2.el6.x86_64
    --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
    ---> Package kexec-tools.x86_64 0:2.0.3-3.0.1.el6 will be updated
    ---> Package kexec-tools.x86_64 0:2.0.3-4.0.7.*el5* will be an update
    --> Processing Dependency: libxenctrl.so.4.0()(64bit) for package: kexec-tools-2.0.3-4.0.7.*el5*.x86_64
    ---> Package libdaemon.x86_64 0:0.14-1.el6 will be obsoleted
    --> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-11.el6.x86_64
    --> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-11.el6.x86_64
    Package libdaemon is obsoleted by ovs-release, but obsoleting package does not provide for requirements
    ---> Package ovs-release.x86_64 0:3.2-5.208 will be obsoleting
    --> Processing Dependency: openvswitch for package: ovs-release-3.2-5.208.x86_64
    --> Processing Dependency: kmod-openvswitch-uek for package: ovs-release-3.2-5.208.x86_64
    --> Processing Dependency: net-snmp-utils for package: ovs-release-3.2-5.208.x86_64
    --> Processing Dependency: lm_sensors for package: ovs-release-3.2-5.208.x86_64
    --> Processing Dependency: ovs-agent for package: ovs-release-3.2-5.208.x86_64
    ---> Package smartmontools.x86_64 1:5.42-2.el6 will be updated
    ---> Package smartmontools.x86_64 1:5.42-2.100.2.*el5* will be an update
    --> Running transaction check
    ---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be obsoleted
    --> Processing Dependency: dbus-python for package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch
    --> Processing Dependency: dbus-python for package: rhn-client-tools-1.0.0-87.0.6.el6.noarch
    ---> Package gnutls.x86_64 0:2.8.5-4.el6_2.2 will be obsoleted
    --> Processing Dependency: libgnutls.so.26()(64bit) for package: neon-0.29.3-2.el6.x86_64
    --> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
    --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: neon-0.29.3-2.el6.x86_64
    --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
    ---> Package kmod-openvswitch-uek.x86_64 0:1.6.90-2 will be installed
    --> Processing Dependency: kernel(memcpy) = 0x6067a146 for package: kmod-openvswitch-uek-1.6.90-2.x86_64
    Package kernel-ovs is obsoleted by ovs-release, but obsoleting package does not provide for requirements
    --> Processing Dependency: kernel(printk) = 0x985558a1 for package: kmod-openvswitch-uek-1.6.90-2.x86_64
    ---> Package libdaemon.x86_64 0:0.14-1.el6 will be obsoleted
    --> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-11.el6.x86_64
    --> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-11.el6.x86_64
    Package libdaemon is obsoleted by ovs-release, but obsoleting package does not provide for requirements
    ---> Package lm_sensors.x86_64 0:3.1.1-10.el6 will be installed
    --> Processing Dependency: libsensors.so.4()(64bit) for package: lm_sensors-3.1.1-10.el6.x86_64
    ---> Package net-snmp-utils.x86_64 1:5.5-41.el6_3.1 will be installed
    --> Processing Dependency: net-snmp-libs = 1:5.5-41.el6_3.1 for package: 1:net-snmp-utils-5.5-41.el6_3.1.x86_64
    --> Processing Dependency: libnetsnmp.so.20()(64bit) for package: 1:net-snmp-utils-5.5-41.el6_3.1.x86_64
    ---> Package openvswitch.x86_64 0:1.6.90-7 will be installed
    --> Processing Dependency: libcrypto.so.6()(64bit) for package: openvswitch-1.6.90-7.x86_64
    --> Processing Dependency: libssl.so.6()(64bit) for package: openvswitch-1.6.90-7.x86_64
    ---> Package ovs-agent.x86_64 0:3.2.1-183 will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: ovs-agent-3.2.1-183.x86_64
    --> Processing Dependency: multiprocessing >= 2.6.1.1 for package: ovs-agent-3.2.1-183.x86_64
    --> Processing Dependency: python-simplejson >= 2.0.7 for package: ovs-agent-3.2.1-183.x86_64
    ---> Package xen-tools.x86_64 0:4.1.3-25.*el5.3* will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: xen-tools-4.1.3-25.*el5.3*.x86_64
    --> Running transaction check
    ---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be obsoleted
    --> Processing Dependency: dbus-python for package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch
    --> Processing Dependency: dbus-python for package: rhn-client-tools-1.0.0-87.0.6.el6.noarch
    ---> Package gnutls.x86_64 0:2.8.5-4.el6_2.2 will be obsoleted
    --> Processing Dependency: libgnutls.so.26()(64bit) for package: neon-0.29.3-2.el6.x86_64
    --> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
    --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: neon-0.29.3-2.el6.x86_64
    --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
    ---> Package kernel-uek.x86_64 0:2.6.39-300.28.1.*el5uek* will be installed
    --> Processing Dependency: kernel-firmware = 2.6.39-300.28.1.*el5uek* for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
    --> Processing Dependency: device-mapper-multipath >= 0.4.9-23.0.1.*el5* for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
    --> Processing Dependency: mkinitrd >= 5.1.19.6-71.0.10 for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
    --> Processing Dependency: ql2xxx-firmware for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
    ---> Package kmod-openvswitch-uek.x86_64 0:1.6.90-2 will be installed
    ---> Package libdaemon.x86_64 0:0.14-1.el6 will be obsoleted
    --> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-11.el6.x86_64
    --> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-11.el6.x86_64
    Package libdaemon is obsoleted by ovs-release, but obsoleting package does not provide for requirements
    ---> Package lm_sensors-libs.x86_64 0:3.1.1-10.el6 will be installed
    ---> Package multiprocessing.x86_64 0:2.6.1.1-1 will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: multiprocessing-2.6.1.1-1.x86_64
    ---> Package net-snmp-libs.x86_64 1:5.5-41.el6_3.1 will be installed
    ---> Package openssl098e.x86_64 0:0.9.8e-17.0.1.el6_2.2 will be installed
    ---> Package ovs-agent.x86_64 0:3.2.1-183 will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: ovs-agent-3.2.1-183.x86_64
    ---> Package python-simplejson.x86_64 0:2.0.9-3.1.el6 will be installed
    ---> Package xen-tools.x86_64 0:4.1.3-25.*el5.3* will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: xen-tools-4.1.3-25.*el5.3*.x86_64
    --> Running transaction check
    ---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be obsoleted
    --> Processing Dependency: dbus-python for package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch
    --> Processing Dependency: dbus-python for package: rhn-client-tools-1.0.0-87.0.6.el6.noarch
    ---> Package device-mapper-multipath.x86_64 0:0.4.9-56.el6_3.1 will be installed
    --> Processing Dependency: device-mapper-multipath-libs = 0.4.9-56.el6_3.1 for package: device-mapper-multipath-0.4.9-56.el6_3.1.x86_64
    --> Processing Dependency: libmultipath.so()(64bit) for package: device-mapper-multipath-0.4.9-56.el6_3.1.x86_64
    ---> Package gnutls.x86_64 0:2.8.5-4.el6_2.2 will be obsoleted
    --> Processing Dependency: libgnutls.so.26()(64bit) for package: neon-0.29.3-2.el6.x86_64
    --> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
    --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: neon-0.29.3-2.el6.x86_64
    --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
    ---> Package kernel-uek.x86_64 0:2.6.39-300.28.1.*el5uek* will be installed
    --> Processing Dependency: mkinitrd >= 5.1.19.6-71.0.10 for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
    ---> Package kernel-uek-firmware.noarch 0:2.6.39-300.28.1.*el5uek* will be installed
    ---> Package libdaemon.x86_64 0:0.14-1.el6 will be obsoleted
    --> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-11.el6.x86_64
    --> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-11.el6.x86_64
    Package libdaemon is obsoleted by ovs-release, but obsoleting package does not provide for requirements
    ---> Package multiprocessing.x86_64 0:2.6.1.1-1 will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: multiprocessing-2.6.1.1-1.x86_64
    ---> Package ovs-agent.x86_64 0:3.2.1-183 will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: ovs-agent-3.2.1-183.x86_64
    ---> Package ql2xxx-firmware.noarch 0:1.01.01-0.1.*el5* will be installed
    ---> Package xen-tools.x86_64 0:4.1.3-25.*el5.3* will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: xen-tools-4.1.3-25.*el5.3*.x86_64
    --> Running transaction check
    ---> Package dbus-python.x86_64 0:0.83.0-6.1.el6 will be obsoleted
    --> Processing Dependency: dbus-python for package: system-config-network-tui-1.6.0.el6.2-1.0.3.el6.noarch
    --> Processing Dependency: dbus-python for package: rhn-client-tools-1.0.0-87.0.6.el6.noarch
    ---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-56.el6_3.1 will be installed
    ---> Package gnutls.x86_64 0:2.8.5-4.el6_2.2 will be obsoleted
    --> Processing Dependency: libgnutls.so.26()(64bit) for package: neon-0.29.3-2.el6.x86_64
    --> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
    --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: neon-0.29.3-2.el6.x86_64
    --> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: 1:cups-libs-1.4.2-48.el6_3.3.x86_64
    ---> Package kernel-uek.x86_64 0:2.6.39-300.28.1.*el5uek* will be installed
    --> Processing Dependency: mkinitrd >= 5.1.19.6-71.0.10 for package: kernel-uek-2.6.39-300.28.1.*el5uek*.x86_64
    ---> Package libdaemon.x86_64 0:0.14-1.el6 will be obsoleted
    --> Processing Dependency: libdaemon.so.0()(64bit) for package: avahi-0.6.25-11.el6.x86_64
    --> Processing Dependency: libdaemon >= 0.11 for package: avahi-0.6.25-11.el6.x86_64
    Package libdaemon is obsoleted by ovs-release, but obsoleting package does not provide for requirements
    ---> Package multiprocessing.x86_64 0:2.6.1.1-1 will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: multiprocessing-2.6.1.1-1.x86_64
    ---> Package ovs-agent.x86_64 0:3.2.1-183 will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: ovs-agent-3.2.1-183.x86_64
    ---> Package xen-tools.x86_64 0:4.1.3-25.*el5.3* will be installed
    --> Processing Dependency: python(abi) = 2.4 for package: xen-tools-4.1.3-25.*el5.3*.x86_64
    Edited by: user7586670 on 20-Feb-2013 06:20

  • OVM Servers trying to start non-existing VM??

    Hi,
    all of my OVM servers log(AdminServer.log) are continually reporting error message:
    [2011-10-24 16:33:25 15835] ERROR (OVSCommons:142) catch_error: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg'] failed (1): Error: Unable to open config file: /OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg
    Traceback (most recent call last):
    File "/opt/ovs-agent-3.0/OVSCommons.py", line 140, in wrapper
    return func(*args)
    File "/opt/ovs-agent-3.0/vm.py", line 558, in start_vm
    run_cmd(['xm', 'create', path])
    File "/opt/ovs-agent-3.0/OVSCommons.py", line 31, in run_cmd
    raise RuntimeError('Command: %s failed (%s): %s ' % (cmd,
    RuntimeError: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg'] failed (1): Error: Unable to open config file: /OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg
    In my repository there's no such location. Recently, I've reinstalled OVMM 3.0.2 and imported .dmp file, redisovered pool, servers and my VM's are running fine, but still there's this error in OVMM AdminServer.log.
    I truly hope that I'll get an answer this time :(
    Thanks.

    My advice is not to reimport the .dmp file -- rather, re-install your manager using the same UUID as before and then just discover your servers/repositories. It will rebuilt the DB from the on-disk data and thus should not have any phantom VM data left.Avi,
    I've done this, everything is working fine, AdminServer.log have no errors, but ovs-agent.log on every OVM server still have this message:
    [2011-10-25 10:20:22 24604] ERROR (OVSCommons:142) catch_error: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg'] failed (1): Error: Unable to open config file: /OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg
    Traceback (most recent call last):
    File "/opt/ovs-agent-3.0/OVSCommons.py", line 140, in wrapper
    return func(*args)
    File "/opt/ovs-agent-3.0/vm.py", line 558, in start_vm
    run_cmd(['xm', 'create', path])
    File "/opt/ovs-agent-3.0/OVSCommons.py", line 31, in run_cmd
    raise RuntimeError('Command: %s failed (%s): %s ' % (cmd,
    RuntimeError: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg'] failed (1): Error: Unable to open config file: /OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg
    Is it ok to ignore and wait for 3.0.3 patch release, or what?
    Thanks.

  • Paravirtualization installation : PowerOn Failed after reboot

    HI,
    Here the context :
    ORACLE VM 2.2.1
    ORACLE VManager 2.2.0
    I have created a virtual Machaine with the option : Create from installation media
    I have use a NFS directory directly on the Server.
    I have install sucessfull the Oracle Entreprise Linux 5 Release 5.
    But When the installation reboot at the end of the process I have this error :
    Start - /OVS/running_pool/27_Oracle11gR2
    PowerOn Failed : Result - failed:<Exception: return=>failed:<Exception: ['xm', 'create', '/var/ovs/mount/FA6D9F67C4E84333A18347EF4DF8296D/running_pool/27_Oracle11gR2/vm.cfg'] => Error: (2, 'Invalid kernel', 'xc_dom_parse_elf_kernel: ELF image has no shstrtab\n')
    >
    StackTrace:
      File "/opt/ovs-agent-2.3/OVSXXenVM.py", line 57, in xen_start_vm
        run_cmd(args=cmd)
      File "/opt/ovs-agent-2.3/OVSCommons.py", line 85, in run_cmd
        raise Exception('%s => %s' % (cmdlist, p.childerr.read()))
    >
    StackTrace:
      File "/opt/ovs-agent-2.3/OVSSiteVM.py", line 131, in start_vm
        raise eBest regards,
    Calà Salvatore

    I have redo the process. but this time I have not change the hosts name during the OEL5 installation and leave only 1 virtual disk. Before I have attach a shared virtual disk.
    Making a simple installation, it have working well.
    Best regards.

  • OEL 5.3 guest wouldn't boot after installing 11gR2 grid - fixed

    Ran into this twice so I thought I'd post it:
    - standard OEL 5.3 64bit template
    - Using the public Oracle yum repo and install the unixODBC pkgs and possibly a couple others that the installer is looking for.
    - Configure ASM via manually adding a storage volume, fdisk'ing it, udev'ing it and "service oracleasm configure" - ASM is happy, installer sees the ASM storage
    - runInstaller using the 11.2.0.1 11gR2-GridInfrastruture.zip downloaded from Oracle
    - Installer does it's thing, no errors. +ASM  is up and running just fine.
    - reboot - not so much - grub is pointing to a non-existant kernel. OVS blows this (confusing) error:
    >
    Start - /OVS/running_pool/66_cnvdb01
    PowerOn Failed : Result - failed:<Exception: return=>failed:<Exception: ['xm', 'create', '/var/ovs/mount/42B0519525064CA2B952462BEC0C206E/running_pool/66_cnvdb01/vm.cfg'] => Error: Boot loader didn't return any data!
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSXXenVM.py", line 57, in xen_start_vm
    run_cmd(args=cmd)
    File "/opt/ovs-agent-2.3/OVSCommons.py", line 85, in run_cmd
    raise Exception('%s => %s' % (cmdlist, p.childerr.read()))
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSSiteVM.py", line 131, in start_vm
    raise e
    >
    Fix for me is: Do this on the host -->
    mkdir /x
    mount -t ext3 -o loop,rw,offset=32256 /OVS/running_pool/<xx_broken_guest>/System.img /x
    cd /x/grub
    ls -la grub*
    mv grub.conf grub.conf-bad
    cp grub.conf.orabackup grub.conf
    cd /
    umount /x
    Then you can startup the guest. You can do it manually if you want to watch it by -->
    xm create -c /OVS/running_pool/66_cnvdb01/vm.cfg

    The lights/fans powering up for a split second and going back out every time you try to turn the PC on = PSU going in to protection mode due to a fault or short, most likely in the board.
    Given MSI's track record lately, I would bet you fried at least one of the MOSFETs...this is a common problem on the 890fx they're producing, not sure if it is happening with their other models.  Unplug the 4 or 8pin cpu power from the board and hit the power button.  System won't boot, but the lights/fans should come on.  If they do, the MOSFETs are junk and you'll need a new board.
    Another possibility is you are grounding out the board somewhere it shouldn't be grounded.  Remove the board, check the back of it and make sure it is not contacting the case anywhere.  Check all the board standoffs to make sure they are mounted securely to the case, check all the board mounting screws to make sure they are threading in to the standoffs correctly and that you didn't overtighten any and damage the board.
    The "flicker" is usually one of the above issues, but could also be a bad PSU, bad CPU, bad RAM, etc.  You could try booting with one stick of RAM at a time, without the video card, etc, try to use a process-of-elimination to figure out what the faulty part is.  If installing the new cooler caused this, the problem would have likely shown itself right away instead of waiting a day or two.

Maybe you are looking for