OVM Server Ownership in OVM Manager

Hi,
I am new to OVM so go easy on me ;)
Am having a play around with OVM 3 for the first time. I managed to get into a state in OVM Manager where my OVM Server was kind of half discovered, although I was able to "Take Ownership" in the Manager. When I tried to delete it it failed saying it didn't exist. When I tried to re-discover it said it already existed. So in the end I gave up and just uninstalled and re-installed OVM Manager.
So now I can successfully discover my OVM server, great, I thought, but now when I try and "Take Ownership" of this newly discovered VM server it says it's already owned by another manager:
OVMRU_000009E Server <my OVM server> is already owned by an Oracle VM Manager.
Anybody any ideas how I can resolve this?
Thanks
Jim

bmace wrote:
I'm not sure how it ended up being implemented exactly but I believe there should also be a way to specify the manager UUID at manager install time.Just run the installer with the -u option to pass the UUID in:
# ./runInstaller.sh -u <uuid> You can find the UUID of your Manager installation by checking the .config file at */u01/app/oracle/ovm-manager-3/.config*

Similar Messages

  • Lost connection between ovm-manager and ovm-server (ovm 3.1)

    Hi,
    I have a manager as a VM on my laptop and a physical server as an ovm-server. Everything is fine when i boot the server but after some time, the manager stop to show the information from the server. in the ovs-agent log file the following messages are repeated regulary
    [2013-08-29 13:06:19 6160] DEBUG (notification:289) Trying to connect to manager.
    [2013-08-29 13:06:20 6160] DEBUG (notification:291) Connected to manager.
    [2013-08-29 13:06:20 6160] ERROR (notification:316) No manager Core API server object for 10:60:4b:88:bc:24:10:60:4b:88:bc:25:fe:ff:ff:ff.
    [2013-08-29 13:06:34 6171] ERROR (notification:64) Unable to send notification: (111, 'Connection refused')
    I did not reboot neither the server nor the manager. No IP change. Rebooting the manager has no effect.
    The only way to restore communication is to restart the ovs-agent on the server, but this restart disable the network card. I must be physical on the server to restart the network.
    any help will be very helpful
    best regards
    Jean-Marc

    Hi,
    The are many steps to verify:
    Verify with your firewall on the Oracle VM Manager system (service iptables stop).
    Verify with a ping between OVM Manager and OVM Server using the IP Address and using the hostname for each one (from OVM Manager : ping ovm-server ; and from OVM Server: ping ovm-manager).
    I hope this can help you
    Best Regards

  • How to start virtual OVM Manager and restore server pool which hosts it?

    It had to happen... the day I migrate our OVM Manager from an ESX host into an Oracle VM, we have a massive NetApp outage, and everything fails to come back. As a result of having lock errors when trying to start any VMs I noted on the forum various solutions and ended up following the steps concerning stopping ovs-agent and removal of /etc/ovs-agent/db/* on all the servers. Next I re-added the repo to all the servers using repos.py, but of course now none of the servers are in a pool so the --list command shows them as [R] rather than [*], and the /OVS directory is not yet mapped. So the next stage, according to the instructions which I am following, describes using the 'Restore' option in the OVM Manager GUI. Given that /OVS is not mounted and all of the servers are now config-less, I can't see how I can start the OVM Manager VM to get to the aforementioned "restore" option...
    Thank Jeebus I kept the ESX copy of OVM manager on (but powered down), as I was able to fire it up and do the restore, and now everything is hunky dory. However, this is our Dev platform and I was going to build the Prod platform and deploy OVM Manager straight into the OVM architecture via the template, rather than having it on ESX, but this issue on the Dev install has made me think twice about the mobius nature of managing the VM architecture from within the VM architecture...
    I am assuming I am missing some sort of commandline knowledge, so... given:
    - empty db directory
    - root repos [R] on all servers
    - as yet unmapped /OVS
    ...how to get the server pool up and get something back into /OVS, and then start my OVM Manager VM so I can 'restore'? Is it even possible? because if it isn't, I'll be blowed if the Prod OVM manager is going to get deployed like this...
    And no, there's no money in the budget for extra tin just to sit there running the OVM Manager and nothing else.
    TIA
    Kev

    user12474530 wrote:
    Still nobody seems to know of how to create a server pool on the CLI (outside of OVM Manager) though...There is no way to create a server pool on the CLI without Oracle VM Manager. You either need to use the Web UI of the Manager, or use the ovmcli command-line tool. Both of those require Oracle VM Manager to be running.
    However, once the Pool is created, you do not need the Manager to be running to perform simple tasks like starting/stopping guests. That can be done with the xm command-line tool.
    I agree with you about running VM Manager as a guest of the Oracle VM Server: I actually don't recommend this in production, unless you have at least two Server Pools. Then you can have the Manager of Pool A hosted by Pool B and vice-versa. Most often however, I recommend a completely independent Manager machine, either physical or hosted on a separate virtualization stack.

  • OVM Manager 2.2.2: server pool error with file system type

    I'm just getting started with OVM. I've installed OVM on one machine and the manager on another.
    I created a server pool, which seemed to work OK but shows "Error" in the table under the "Server Pools" tab in the manager interface
    When I edit it I see
    Error: OVM-1011 OVM Manager communication with NNN.NNN.NN.NNN for operation Pre-check cluster root for Server Pool failed: <Exception: SR '/dev/sda3' not supported: type 'ocfs2.local' not in ['nfs', 'ocfs2.cluster']>
    Can anyone explain this? Does this mean I can't use a local file system in OVM 2.2.2? I understood this was the case with OVM 3, which is why I went with 2.2.2.
    Thanks.

    Roger Ford wrote:
    Error: OVM-1011 OVM Manager communication with NNN.NNN.NN.NNN for operation Pre-check cluster root for Server Pool failed: <Exception: SR '/dev/sda3' not supported: type 'ocfs2.local' not in ['nfs', 'ocfs2.cluster']>
    Can anyone explain this? Does this mean I can't use a local file system in OVM 2.2.2? I understood this was the case with OVM 3, which is why I went with 2.2.2.You can't created a clustered pool with a local filesystem. You need to format the filesystem with ocfs2 in clustered mode.

  • OVM Manager 2.2 - not starting after server move

    I have installed and configured OVS 2.2 and OVM Manager 2.2 and had all working and had everything running fine (I am having to use these versions to be compliant with the templates I wish to install)
    I then shut down everything and moved the server to its new location in the rack, plugged it all in and restarted and now I can no longer browse to the OVM Manager.
    I know very little about linux and oracle vm but assumed as I can no longer ping the Manager vm that it wasnt started, when I look in the /var/log/xen/qemu-dm-pid.log I see the following
    Warning: vlan 0 is not connected to host network
    as the first line.
    The only network change that I am aware of is the host machine now has multiple network cards connected where it only had one connected on initial setup.
    Any pointers on where to start are welcome...

    Create symbolic link to the "vm.cfg" in "/etc/xen/auto" e.g.
    ln -s /OVS/vm-name/vm.cfg /etc/xen/auto/vm-name
    [root@ovm222 ~]# cat /etc/ovs-release
    Oracle VM server release 2.2.2
    [root@ovm222 ~]# chkconfig --list xendomains
    xendomains 0:off 1:off 2:off 3:on 4:on 5:on 6:off
    [root@ovm222 ~]# grep ^XENDOMAINS_AUTO= /etc/sysconfig/xendomains
    XENDOMAINS_AUTO=/etc/xen/auto
    FYI XENDOMAINS_SAVE should be undefined unless you want to save on shutdown e.g.
    [root@denovm22 ~]# grep ^#XENDOMAINS_SAVE /etc/sysconfig/xendomains
    #XENDOMAINS_SAVE=/var/lib/xen/save

  • OVM Manager w 2nd NIC = A port conflict was detected in the server config

    Greetings,
    ENV: Oracle VM 3.1.1.544.
    Issue: We had to add/setup a second interface/NIC on a second subnet on Oracle VM Manager. Now, when ovmm is started, we get: <A port conflict was detected in the server configuration. The server is configured to listen on two ports that have the same port number and IP address. Channel "https" address "https://fe80:0:0:0:26b6:fdff:fec8:f4b1:7002" conflicts with channel "https" address "https://fe80:0:0:0:26b6:fdff:fec8:f4b1:7002".>
    BEA Docs (http://docs.oracle.com/cd/E13222_01/wls/docs92/messages/Server.html)
    BEA-002633: Emergency: A port conflict was detected in the server configuration. The server is configured to listen on two ports that have the same port number and IP address. Channel "channel1" address "url" conflicts with channel "channel2" address "url".
    Action: Please ensure that the address identities [ListenAddress and ListenPort combinations] are distinct and unique.
    Would you happen to know which file, (i.e. config.xml), and which lines (i.e. <listen-address>) we need to edit, with the correct syntax to add a second IP address/subnet to our WebLogic server?
    Thank you in advance for your support!
    Regards,
    Roddy

    Thank you for your support!
    1. What version of Linux? OL 62 x64
    2. Have you set a separate DNS name for the second interface IP? No, although we are using/setup dnsmasq on the second interface/eth3 to dish up DNS on the private network. DNS name resolutions works like a charm on the private vlan.
    3. Do you still have a single default route or are you trying to use more than one? The second interface is in a private unroutable network. the front end network/NIC eth0 is routable and on a public network.
    Public/Private Network Setup:
    * Public network with oracle vm manager on eth0/10.4.x.x. This is how we access the ovm manager GUI, and ssh to manager, and via manager ssh to the dom0s. The dom0s are on private nonroutable networks available via the manager host's eth3.
    * Private networks accessible via the oracle vm manager host eth3/802.1q/VLAN xxx. this is the server management network channel, this vlan is not routable. We have two other vlans, i.e. heartbeat and live migration, both also not routable.
    Thoughts?

  • OVM Manager 3.0.1. Setup: Create a Server Pool

    I am new to OVM, sorry.
    I would like to do the initial setup of OVM Manager to be able to create virtual machines. I followed the OVM user's guide in chapter 4.5 to create a server pool, but didn't succeed.
    I set up my OVM Server having a shared NFS directory, later planned to be on a separate RAID volume, but OVM Manager does not detect the NFS directory.
    On the OVM Manager host I can mount the NFS directory via "mount -t nfs ovm-srv:/share /test".
    Who can help?
    Edited by: user8163152 on 27.08.2011 06:35

    user8163152 wrote:
    I set up my OVM Server having a shared NFS directory, later planned to be on a separate RAID volume, but OVM Manager does not detect the NFS directory.Have you setup the File Server in Oracle VM Manager first? You need all the NFS mount points to be visible inside the UI before they can be used to create a server pool. Keep in mind that you will need a dedicated mount for the cluster/heartbeat. It cannot also be used for repository storage like in 2.2. So, you can make that mount pretty small (10GB should be fine).

  • Adding an OVM server back into OVM Manager after a reload

    We have created a sandbox environment to test Oracle virtualization and had 2 physical servers setup. One running Oracle OVM and the other Oracle Linux. The Oracle Linux box had OVM Manager installed and was using local storage for the repository.
    After about a month of running the Oracle Linux box was reloaded without saving any of the OVM Manager configuration information. After reloading the Oracle Linux box and installing OVM Manager my first issue was adding the OVM server back into a pool. We were getting the error that it was already being managed by another host. After a quick search of the Oracle forum I found a post suggesting that we stop the ovs-agent on the OVM box and remove a file.
    These were the commands:
    # service ovs-agent stop
    # rm /etc/ovs-agent/db/server
    # service ovs-agent start
    After doing this I was able to discover and add the server into a pool. The next issue was when I went to look at the virtual machines hosted on the OVM machine. All 6 of the virtual machines that were created now show as "orphan_004fb0000060000...". In digging around I noticed that the repository for the local storage was not setup so when I go to try add the local disk back as a repository and I select "create a data repository: select physical disk" it comes back as blank.
    If I click the storage tab and look under local file systems I see the disk and it has location repository specified and server listed under presented servers.
    I am thinking the mapping is somehow messed up after adding the host back to a new OVM Manager and I need to relink the storage to the repository but am a little lost as to how to accomplish this.
    I am trying to avoid reloading the entire OVM server so I don't lose the work already done with the existing virtual machines.

    To answer your second question first, It is an unclustered server pool.
    When I run the refresh I get an error. Below are the details:
    Job Construction Phase
    begin()
    Appended operation 'FileSystem refresh' to object '0004fb0000050000f6e5bfcdec6df114'.
    commit()
    Completed Step: COMMIT
    Objects and Operations
    Object (IN_USE): [Server] 44:45:4c:4c:31:00:10:51:80:50:b1:c0:4f:4e:4d:31 (fnt1gvs001.syncreon.local)
    Object (IN_USE): [LocalFileServer] 0004fb00000900008975e0e107a39557 (Local FS fnt1gvs001.syncreon.local)
    Object (IN_USE): [LocalFileSystem] 0004fb0000050000f6e5bfcdec6df114
    Operation: FileSystem refresh
    Job Running Phase at 15:03 on Wed, Dec 19, 2012
    Job Participants: [44:45:4c:4c:31:00:10:51:80:50:b1:c0:4f:4e:4d:31 (fnt1gvs001.syncreon.local)]
    Actioner
    Starting operation 'FileSystem refresh' on object '0004fb0000050000f6e5bfcdec6df114'
    Job Internal Error (Indeterminate)com.oracle.ovm.mgr.api.exception.RuleException: OVMRU_002017E Cannot perform operation. This repository: 36842b2b01874c700182161460904cc01, is not owned by this manager
    Wed Dec 19 15:03:54 EST 2012
    at com.oracle.ovm.mgr.rules.modules.api.virtual.RepositoryRules.throwErrorIfNotOwnedByThisManager(RepositoryRules.java:378)
    at com.oracle.ovm.mgr.rules.modules.api.virtual.RepositoryRules.setSimpleNamePre(RepositoryRules.java:197)
    at com.oracle.ovm.mgr.api.job.JobEngine.invokeMethod(JobEngine.java:662)
    at com.oracle.ovm.mgr.api.job.JobEngine.invokeMethod(JobEngine.java:631)
    at com.oracle.ovm.mgr.rules.RulesEngine.runRules(RulesEngine.java:190)
    at com.oracle.ovm.mgr.rules.RulesEngine.preProcess(RulesEngine.java:142)
    at com.oracle.ovm.mgr.model.ModelEngine.preValidate(ModelEngine.java:547)
    at com.oracle.ovm.mgr.model.ModelEngine.access$200(ModelEngine.java:65)
    at com.oracle.ovm.mgr.model.ModelEngine$3.notify(ModelEngine.java:352)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:326)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
    at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
    at com.oracle.ovm.mgr.api.virtual.RepositoryProxy.setSimpleName(Unknown Source)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.processRepoMetadata(FileSystemRefresh.java:338)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.discoverOcfs2FileSystem(FileSystemRefresh.java:188)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.action(FileSystemRefresh.java:84)
    at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1009)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
    at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
    at com.oracle.ovm.mgr.api.physical.storage.LocalFileSystemProxy.executeCurrentJobOperationAction(Unknown Source)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:218)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:309)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1140)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:773)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    FailedOperationCleanup
    Starting failed operation 'FileSystem refresh' cleanup on object '0004fb0000050000f6e5bfcdec6df114'
    Complete rollback operation 'FileSystem refresh' completed with direction=0004fb0000050000f6e5bfcdec6df114
    Rollbacker
    Executing rollback operation 'FileSystem refresh' on object '0004fb0000050000f6e5bfcdec6df114'
    Complete rollback operation 'FileSystem refresh' completed with direction=DONE
    Objects To Be Rolled Back
    Object (IN_USE): [Server] 44:45:4c:4c:31:00:10:51:80:50:b1:c0:4f:4e:4d:31 (fnt1gvs001.syncreon.local)
    Object (IN_USE): [Repository] 0004fb0000030000eac6a78cc3aa8b91 (36842b2b01874c700182161460904cc01)
    Object (IN_USE): [LocalFileServer] 0004fb00000900008975e0e107a39557 (Local FS fnt1gvs001.syncreon.local)
    Object (IN_USE): [LocalFileSystem] 0004fb0000050000f6e5bfcdec6df114
    Write Methods Invoked
    Class=InternalJobDbImpl vessel_id=1569 method=addTransactionIdentifier accessLevel=6
    Class=LocalFileSystemDbImpl vessel_id=930 method=refresh accessLevel=6
    Class=ServerDbImpl vessel_id=544 method=lock accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=897 method=lock accessLevel=6
    Class=InternalJobDbImpl vessel_id=1569 method=setCompletedStep accessLevel=6
    Class=InternalJobDbImpl vessel_id=1569 method=setAssociatedHandles accessLevel=6
    Class=RepositoryDbImpl vessel_id=1111 method=setSimpleName accessLevel=6
    Class=LocalFileSystemDbImpl vessel_id=930 method=nextJobOperation accessLevel=6
    Class=InternalJobDbImpl vessel_id=1569 method=setFailedOperation accessLevel=6
    Class=ServerDbImpl vessel_id=544 method=nextJobOperation accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=897 method=nextJobOperation accessLevel=6
    Class=LocalFileSystemDbImpl vessel_id=930 method=nextJobOperation accessLevel=6
    Class=LocalFileSystemDbImpl vessel_id=930 method=nextJobOperation accessLevel=6
    Completed Step: ROLLBACK
    Job failed commit (internal) due to com.oracle.ovm.mgr.api.exception.RuleException: OVMRU_002017E Cannot perform operation. This repository: 36842b2b01874c700182161460904cc01, is not owned by this manager
    Wed Dec 19 15:03:54 EST 2012
    at com.oracle.ovm.mgr.rules.modules.api.virtual.RepositoryRules.throwErrorIfNotOwnedByThisManager(RepositoryRules.java:378)
    at com.oracle.ovm.mgr.rules.modules.api.virtual.RepositoryRules.setSimpleNamePre(RepositoryRules.java:197)
    at com.oracle.ovm.mgr.api.job.JobEngine.invokeMethod(JobEngine.java:662)
    at com.oracle.ovm.mgr.api.job.JobEngine.invokeMethod(JobEngine.java:631)
    at com.oracle.ovm.mgr.rules.RulesEngine.runRules(RulesEngine.java:190)
    at com.oracle.ovm.mgr.rules.RulesEngine.preProcess(RulesEngine.java:142)
    at com.oracle.ovm.mgr.model.ModelEngine.preValidate(ModelEngine.java:547)
    at com.oracle.ovm.mgr.model.ModelEngine.access$200(ModelEngine.java:65)
    at com.oracle.ovm.mgr.model.ModelEngine$3.notify(ModelEngine.java:352)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:326)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
    at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
    at com.oracle.ovm.mgr.api.virtual.RepositoryProxy.setSimpleName(Unknown Source)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.processRepoMetadata(FileSystemRefresh.java:338)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.discoverOcfs2FileSystem(FileSystemRefresh.java:188)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.action(FileSystemRefresh.java:84)
    at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1009)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
    at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
    at com.oracle.ovm.mgr.api.physical.storage.LocalFileSystemProxy.executeCurrentJobOperationAction(Unknown Source)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:218)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:309)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1140)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:773)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Wed Dec 19 15:03:54 EST 2012
    com.oracle.ovm.mgr.api.exception.FailedOperationException: com.oracle.ovm.mgr.api.exception.RuleException: OVMRU_002017E Cannot perform operation. This repository: 36842b2b01874c700182161460904cc01, is not owned by this manager
    Wed Dec 19 15:03:54 EST 2012
    at com.oracle.ovm.mgr.rules.modules.api.virtual.RepositoryRules.throwErrorIfNotOwnedByThisManager(RepositoryRules.java:378)
    at com.oracle.ovm.mgr.rules.modules.api.virtual.RepositoryRules.setSimpleNamePre(RepositoryRules.java:197)
    at com.oracle.ovm.mgr.api.job.JobEngine.invokeMethod(JobEngine.java:662)
    at com.oracle.ovm.mgr.api.job.JobEngine.invokeMethod(JobEngine.java:631)
    at com.oracle.ovm.mgr.rules.RulesEngine.runRules(RulesEngine.java:190)
    at com.oracle.ovm.mgr.rules.RulesEngine.preProcess(RulesEngine.java:142)
    at com.oracle.ovm.mgr.model.ModelEngine.preValidate(ModelEngine.java:547)
    at com.oracle.ovm.mgr.model.ModelEngine.access$200(ModelEngine.java:65)
    at com.oracle.ovm.mgr.model.ModelEngine$3.notify(ModelEngine.java:352)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:326)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
    at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
    at com.oracle.ovm.mgr.api.virtual.RepositoryProxy.setSimpleName(Unknown Source)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.processRepoMetadata(FileSystemRefresh.java:338)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.discoverOcfs2FileSystem(FileSystemRefresh.java:188)
    at com.oracle.ovm.mgr.op.physical.storage.FileSystemRefresh.action(FileSystemRefresh.java:84)
    at com.oracle.ovm.mgr.api.collectable.ManagedObjectDbImpl.executeCurrentJobOperationAction(ManagedObjectDbImpl.java:1009)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:822)
    at com.oracle.odof.core.Exchange.invokeMethod(Exchange.java:245)
    at com.oracle.ovm.mgr.api.physical.storage.LocalFileSystemProxy.executeCurrentJobOperationAction(Unknown Source)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:218)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:309)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1140)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:773)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Wed Dec 19 15:03:54 EST 2012
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1201)
    at sun.reflect.GeneratedMethodAccessor1396.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:330)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:290)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:773)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    End of Job
    ----------

  • How many time to install/configure OVM Manager and OVM Server ?

    Hello,
    I wish to have your experience feedback on the mean time needed to install both OVM Server and OVM Manager in a production environement, with e.g : 2 CPUs, 4 G of RAM, or for 4 CPUs and 8 G of RAM.
    Regards,
    Lionel

    Not enough information. XE is not supported in a production environment so you will need to install a SE or EE version of Oracle Database. I would personally use EE because the Virtual Manager comes with a single use license that covers running the VM Manager on either edition. No extra cost to run EE over SE.
    You can use kicstart to rapidly deploy any VM Server. If you get your scripting right... it takes less than 10 minutes.

  • Repository after reinstall server and ovm manager

    I have problem
    I have one server connected FC to SAN storage. I have repo with vm on storage luns. After power crash i must to reinstall ovm on server and also reinstall ovm manager.
    Now can i connect old reository to new/reinstall server witouth loosing any data?

    Server with manager had hardware failure. Idont have backup so i have to install ovm manager on new machine.
    Vm server have problem with file system, dont seen the luns also xend dont start. So i reinstall also this server.
    I know that new ovm manager dont recognize old repository disk, so i create new lun on storage and create new repository on it. Now from CLI i map old ocfs repository and copy virtual disk and vm.cfg to new repository, but ovm manager dosn see any of them.

  • OVM Manager install for running OVM server for SPARC plateform

    Guys,
    I have to install and deploy OVM Manager for managing an existing OVM server for SPARC.
    When try to run ovs-agent-setup command, it fails telling that ovm server has not good configuration and exits!!
    ovs-agent ** ERROR: The vds service is not configured on the primary domain 
    Trying to fix by resetting factory default configuration, then poweroff domain and poweron aain but nothing!! I got same error and ovs-agent service is in maintenance.
    Now we have create ldoms and servers are in production!! We cannot reset configuration now.
    Is-it possible to deploy OVM manager, fix ovs-agent issue without impacting actual vm??? How to do this? I assume that vm created with ldm commande can not be provision with ovm manager.
    Please help!!

    Hi,
    Windows Server 2008 R2 supports two mutually exclusive methods for setting quotas on the amount of file system resources a user can use—disk quotas or directory quotas. Disk quotas are applied to specific users and limit the amount of disk space that user can
    use on a particular volume. Directory quotas are applied to all users and limit the amount of disk space that users can use in a particular folder and its subfolders.
    I do a test on my pc and find there is no priority between the two quotas, it depends on which quota is smaller. So user A can only save 1 GB files in the folder.
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Death of OVM manager. How to recover?

    I found myself in a situation where my OVM-manager server got hosed and I had to rebuild it (disks died, and since it's a test environment, no backup of the host exists).
    Unfortunately I had previously set up an OVM pool and repository.
    I re-mounted a repository NFS share that was in use on the now dead OVM-manager installation. That worked, and it inserted itself into the Storage->Fileservers list
    I attempted to reload this share as a repository on my new OVM-manager installation, it told me I couldn't because it belonged elsewhere.
    Now that I try to delete it from the list of File Servers, it tells me I can't because
    "OVMRU_002005E repo01 - Cannot delete NAS or fileSystem with a repository on it."
    This was despite the fact that it is not even recognised a repository on my new OVM manager box.
    So I went a deleted the share on the NFS device, but the error persists.
    Attempted to rediscover the share, and since it can no longer find it, that doesn't help the new OVM manager decide that is an "ex-NFS mount"
    Attempted to re-try deleting the file server mount, but it refuses to go away and out of the list, even though it is not even recognised as a repository on my new OVM manager install.
    Seems like OVM has some big issues regarding handling ownership.
    On a separate issue, I tried taking ownership of some OVM boxes tied to the old and dead OVM-manager, and I was rebuffed there too.
    I went and reinstalled the OVM servers as well.
    it seems like the death of an OVM-management server means the death of the entire architecture, including the repository and all files, and forces a complete rebuild.
    Any idea how to fix this?

    I'm no expert, but I know that the OVM Manager install has an option to force a specific UUID, so the manager will look "exactly like" the original one, and everything works again. I'm not sure that this scenario is applicable to you, since I'm fairly new to all this. But perhaps you can determine what the old UUID was (you may have written it down, or it's stored in your cluster data somewhere, and re-install with that UUID. I think this is mentioned in the docs, and there are postings here about it.

  • OVM 3.0.3 import VirtualBox OVM Manager 3.0.3 OVA template

    VirtualBox Template for Oracle VM Manager 3.0.3,
    http://www.oracle.com/technetwork/server-storage/vm/template-1482544.html
    The OVM 3.0.3 host should be configured with enough space to accommodate import of OVA template. In
    this case 36G was allocated for "sda",
    [root@ovm303 ~]# fdisk -l /dev/sda
    Disk /dev/sda: 38.6 GB, 38654705664 bytes
    255 heads, 63 sectors/track, 4699 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 4189 33648111 83 Linux
    /dev/sda2 4190 4699 4096575 82 Linux swap / Solaris
    Post OVA import disk usage,
    [root@ovm303 ~]# df -T -t ext3
    Filesystem Type 1K-blocks Used Available Use% Mounted on
    /dev/sda1 ext3 32594216 24105604 6806208 78% /.
    [root@ovm303 ~]# cat /etc/motd
    Warning: making manual modifications in the management domain
    might cause inconsistencies between Oracle VM Manager and the server.
    [root@ovm303 ~]# head -4 /etc/ovs-info
    OVS summary
    release: 3.0.3
    date: 201111300901
    build: 123
    The contents of "ovs-info" also include package information.
    The "vbox-img" package is something new in OVM 3.0.3,
    [root@ovm303 ~]# grep vbox-img /etc/ovs-info
    vbox-img-1.0-2
    [root@ovm303 ~]# rpm -ql vbox-img
    /usr/bin/vbox-img
    /usr/share/doc/vbox-img-1.0
    /usr/share/doc/vbox-img-1.0/COPYING
    [root@ovm303 ~]# vbox-img --help
    Oracle VM VirtualBox Disk Utility 4.1.3
    (C) 2005-2011 Oracle Corporation
    All rights reserved.
    Usage: vbox-img
    setuuid --filename <filename>
    [--format VDI|VMDK|VHD|...]
    [--uuid <uuid>]
    [--parentuuid <uuid>]
    [--zeroparentuuid]
    convert --srcfilename <filename>
    --dstfilename <filename>
    [--stdin]|[--stdout]
    [--srcformat VDI|VMDK|VHD|RAW|..]
    [--dstformat VDI|VMDK|VHD|RAW|..]
    [--variant Standard,Fixed,Split2G,Stream,ESX]
    info --filename <filename>
    compact --filename <filename>
    createcache --filename <filename>
    --size <cache size>
    Download "OracleVMManager3" OVA,
    [root@ovm303 xen]# mkdir /etc/xen/ovm303-m
    [root@ovm303 ~]# cd /etc/xen/ovm303-m
    [root@ovm303 xen]# wget http://download.oracle.com/otn-pub/otn_software/OracleVMManager3.ova
    --2012-03-14 17:06:01-- http://download.oracle.com/otn-pub/otn_software/OracleVMManager3.ova
    Length: 4234452992 (3.9G) [text/plain]
    Saving to: `OracleVMManager3.ova'
    100%[====================================>] 4,234,452,992 834K/s in 55m 36s
    2012-03-14 18:01:38 (1.21 MB/s) - `OracleVMManager3.ova' saved [4234452992/4234452992]
    [root@ovm303 xen]# md5sum OracleVMManager3.ova
    75fc334422eda6c3425a2f09fb88f9e0 OracleVMManager3.ova
    Unpack OVA,
    [root@ovm303 xen]# tar tvf OracleVMManager3.ova
    -rw------- someone/someone 59626 2012-01-12 17:42:49 OracleVMManager3.ovf
    -rw------- someone/someone 1987182592 2012-01-12 17:48:06 OracleVMManager3-disk1.vmdk
    -rw------- someone/someone 2247208960 2012-01-12 17:51:24 OracleVMManager3-disk2.vmdk
    [root@ovm303 ovm303-m]# tar xvf OracleVMManager3.ova
    OracleVMManager3.ovf
    OracleVMManager3-disk1.vmdk
    OracleVMManager3-disk2.vmdk
    Use "vbox-img" to show "OracleVMManager3-disk1.vmdk",
    [root@ovm303 ovm303-m]# vbox-img info --filename OracleVMManager3-disk1.vmdk
    --- Dumping VD Disk, Images=1
    Dumping VD image "OracleVMManager3-disk1.vmdk" (Backend=VMDK)
    Header: Geometry PCHS=16383/16/63 LCHS=1024/255/63 cbSector=52428800
    Header: uuidCreation={f3859e00-962c-440f-a63d-feb7b731d5da}
    Header: uuidModification={00000000-0000-0000-0000-000000000000}
    Header: uuidParent={00000000-0000-0000-0000-000000000000}
    Header: uuidParentModification={00000000-0000-0000-0000-000000000000}
    Convert "OracleVMManager3-disk1.vmdk" to RAW,
    [root@ovm303 ovm303-m]# vbox-img convert srcfilename OracleVMManager3-disk1.vmdk dstfilename OracleVMManager3-disk1.img srcformat VMDK dstformat RAW
    Converting image "OracleVMManager3-disk1.vmdk" with size 26843545600 bytes (25600MB)...
    [root@ovm303 ovm303-m]# file OracleVMManager3-disk1.img
    OracleVMManager3-disk1.img: x86 boot sector; partition 1: ID=0x83, active, starthead 1, startsector 63, 208782 sectors; partition 2: ID=0x8e, starthead 0, startsector 208845, 52211250 sectors, code offset 0x48
    [root@ovm303 ovm303-m]# fdisk -l OracleVMManager3-disk1.img
    last_lba(): I don't know how to handle files with mode 8180
    You must set cylinders.
    You can do this from the extra functions menu.
    Disk OracleVMManager3-disk1.img: 0 MB, 0 bytes
    255 heads, 63 sectors/track, 0 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    OracleVMManager3-disk1.img1 * 1 13 104391 83 Linux
    OracleVMManager3-disk1.img2 14 3263 26105625 8e Linux LVM
    Partition 2 has different physical/logical endings:
    phys=(1023, 254, 63) logical=(3262, 254, 63)
    Use "vbox-img" to show "OracleVMManager3-disk2.vmdk",
    [root@ovm303 ovm303-m]# vbox-img info --filename OracleVMManager3-disk2.vmdk
    --- Dumping VD Disk, Images=1
    Dumping VD image "OracleVMManager3-disk2.vmdk" (Backend=VMDK)
    Header: Geometry PCHS=16383/16/63 LCHS=1024/255/63 cbSector=20971520
    Header: uuidCreation={abc43be0-7a43-4ba2-a205-eaf37184a4d3}
    Header: uuidModification={00000000-0000-0000-0000-000000000000}
    Header: uuidParent={00000000-0000-0000-0000-000000000000}
    Header: uuidParentModification={00000000-0000-0000-0000-000000000000}
    Convert "OracleVMManager3-disk2.vmdk" to RAW,
    [root@ovm303 ovm303-m]# vbox-img convert srcfilename OracleVMManager3-disk2.vmdk dstfilename OracleVMManager3-disk2.img srcformat VMDK dstformat RAW
    Converting image "OracleVMManager3-disk2.vmdk" with size 10737418240 bytes (10240MB)...
    [root@ovm303 ovm303-m]# file OracleVMManager3-disk2.img
    OracleVMManager3-disk2.img: x86 boot sector; partition 1: ID=0x83, starthead 1, startsector 63, 20964762 sectors, extended partition table (last)\011
    [root@ovm303 ovm303-m]# fdisk -l OracleVMManager3-disk2.img
    last_lba(): I don't know how to handle files with mode 8180
    You must set cylinders.
    You can do this from the extra functions menu.
    Disk OracleVMManager3-disk2.img: 0 MB, 0 bytes
    255 heads, 63 sectors/track, 0 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    OracleVMManager3-disk2.img1 1 1305 10482381 83 Linux
    Partition 1 has different physical/logical endings:
    phys=(1023, 254, 63) logical=(1304, 254, 63)
    Update disk image "/boot" configuration using loopback mount,
    [root@ovm303 ovm303-m]# mkdir boot
    [root@ovm303 ovm303-m]# kpartx -l OracleVMManager3-disk1.img
    loop1p1 : 0 208782 /dev/loop1 63
    loop1p2 : 0 52211250 /dev/loop1 208845
    loop deleted : /dev/loop1
    [root@ovm303 ovm303-m]# kpartx -a OracleVMManager3-disk1.img
    [root@ovm303 ovm303-m]# mount /dev/mapper/loop1p1 boot
    Update "/boot/grub/device.map",
    [root@ovm303 ovm303-m]# cat boot/grub/device.map
    # this device map was generated by anaconda
    (hd0) /dev/hda
    Update "/boot/grub/grub.conf" to use non-UEK kernel to avoid issues with OL5u7 default UEK boot and HVM,
    [root@ovm303 ovm303-m]# grep default boot/grub/grub.conf
    default=1
    Mount "/" logical volume,
    [root@ovm303 ovm303-m]# vgscan
    Reading all physical volumes. This may take a while...
    Found volume group "VolGroup00" using metadata type lvm2
    [root@ovm303 ovm303-m]# vgchange -ay VolGroup00
    2 logical volume(s) in volume group "VolGroup00" now active
    [root@ovm303 ovm303-m]# lvs
    LV VG Attr LSize Origin Snap% Move Log Copy% Convert
    LogVol00 VolGroup00 -wi-a- 19.06G
    LogVol01 VolGroup00 -wi-a- 5.81G
    [root@ovm303 ovm303-m]# mkdir root
    [root@ovm303 ovm303-m]# ls /dev/VolGroup00/
    LogVol00 LogVol01
    [root@ovm303 ovm303-m]# mount /dev/VolGroup00/LogVol00 root
    Update "/etc/inittab" to boot single user,
    [root@ovm303 ovm303-m]# grep id root/etc/inittab
    id:1:initdefault:
    Update "/etc/fstab" to ignore "/u01" block device mount,
    [root@ovm303 ovm303-m]# grep sdb root/etc/fstab
    #/dev/sdb1 /u01 ext3 defaults 1 1
    Unmount "/boot" and "/",
    [root@ovm303 ovm303-m]# umount boot
    [root@ovm303 ovm303-m]# umount root
    [root@ovm303 ovm303-m]# vgchange -an VolGroup00
    0 logical volume(s) in volume group "VolGroup00" now active
    [root@ovm303 ovm303-m]# kpartx -d OracleVMManager3-disk1.img
    loop deleted : /dev/loop1
    The OVM 3.0.3 network bridge configuration uses "bond0" vs "xenbr0".
    Configure "vm.cfg",
    [root@ovm303 ovm303-m]# cat vm.cfg
    # (H)ardware (V)irtual (M)achine configuration
    # /etc/xen/xmexample.hvm
    kernel = 'hvmloader'
    builder = 'hvm'
    memory = '4096'
    # The number of cpus guest platform has, default=1
    #vcpus=1
    # PXE boot
    #bootloader = '/usr/bin/pypxeboot'
    #bootloader = '/usr/bin/pygrub'
    # Virtual block device configuration using file:
    # dd if=/dev/zero of=/$VM_PATH/$VM_NAME/System.img bs=1M count=$MB
    # disk = [ 'file:/$VM_PATH/$VM_NAME/System.img,ioemu:hda,w', ]
    # Configuration using physical disk logical volume:
    # lvcreate --size ${GB}G --name $VM_NAME $VG_NAME
    # disk = [ 'phy:/dev/$VG_NAME/$VM_NAME,xvda,w',]
    # CDROM configuration using file:
    # disk = [ 'file:/$BOOT_ISO_NAME,hdc:cdrom,r', ]
    disk = [ 'file:/etc/xen/ovm303-m/OracleVMManager3-disk1.img,ioemu:hda,w', 'file:/etc/xen/ovm303-m/OracleVMManager3-disk2.img,ioemu:hdb,w', ]
    # Domain name
    name = "ovm303-m"
    # Networking
    # Network bridge status:
    # /etc/xen/scripts/network-bridge status
    # 'bridge' should be proper interface e.g. xenbr0
    vif = ['type=ioemu, bridge=bond0']
    # boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d)
    # default: hard disk, cd-rom, floppy
    boot = "cdn"
    # Enable HV VNC console
    # Uses avaiablle next VNC port $OVM_SERVER_HOST:0 == 5900, :1 == 5901 etc
    # Use "xm list -l" to determince VNC port "location"
    vnc=1
    vncunused=1
    vnclisten="0.0.0.0"
    vncpasswd=''
    sdl=0
    # Set the real time clock to local time [default=0 i.e. set to utc]
    # Allows Win VM clock to work with UTC on OVM host system.
    #localtime=1
    Start VM,
    [root@ovm303 ovm303-m]# xm create vm.cfg
    Using config file "./vm.cfg".
    Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
    Current bridge,
    [root@ovm303 ~]# brctl show
    bridge name bridge id STP enabled interfaces
    Update "/etc/xen/xend-config.sxp" to enable "network-bridge",
    [root@ovm303 ovm303-m]# cp /etc/xen/xend-config.sxp /etc/xen/xend-config.sxp.orig
    [root@ovm303 ovm303-m]# diff /etc/xen/xend-config.sxp /etc/xen/xend-config.sxp.orig
    165,167d164
    < # Enable network-bridge, JAP 20120322
    < (network-script network-bridge)
    <
    [root@ovm303 ~]# service xend restart
    Restarting xend...
    xend daemon (pid 8848) is running...
    [root@ovm303 ~]# brctl show
    bridge name bridge id STP enabled interfaces
    bond0 8000.002128d5ce86 no pbond0
    Start VM,
    [root@ovm303 ovm303-m]# xm create vm.cfg
    Using config file "./vm.cfg".
    Started domain ovm303-m (id=1)
    Determine VNC console session,
    [root@ovm303 ovm303-m]# xm list -l ovm303-m | grep location
    (location 0.0.0.0:5900)
    (location 3)
    VNC console session. The "oraclevm-template" tools are not run in single user so hostname is "localhost",
    [root@localhost ~]# who -r
    run-level S 2012-03-23 09:09 last=1
    Update "/etc/fstab" for "/u01" mount to use label,
    [root@localhost ~]# grep /u01 /etc/fstab
    #/dev/sdb1 /u01 ext3 defaults 1 1
    [root@localhost ~]# blkid
    /dev/mapper/VolGroup00-LogVol01: TYPE="swap"
    /dev/mapper/VolGroup00-LogVol00: UUID="2751f1b2-836b-4786-ae71-8b402e0f8503" TYPE="ext3"
    /dev/VolGroup00/LogVol00: UUID="2751f1b2-836b-4786-ae71-8b402e0f8503" SEC_TYPE="ext2" TYPE="ext3"
    /dev/VolGroup00/LogVol01: TYPE="swap"
    /dev/hda1: LABEL="/boot" UUID="8701866e-5ed5-49f7-9597-bb9709d22359" TYPE="ext3"
    /dev/hdb1: UUID="5f9a7bef-3a6d-4a83-b288-638537424fa7" SEC_TYPE="ext2" TYPE="ext3"
    [root@localhost ~]# e2label /dev/hdb1 u01
    [root@localhost ~]# grep u01 /etc/fstab
    LABEL=u01 /u01 ext3 defaults 1 1
    [root@localhost ~]# mount /u01
    [root@localhost ~]# df /u01
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/hdb1 10317828 4250832 5542880 44% /u01
    As configured the default run level will be elevated to "5" by the "/etc/rc.local" script. This enables a
    console desktop for user "ovm". This is unneeded and will be implemented by VNC session for user
    "ovm".
    Update "/etc/inittab" to enable full multiuser mode run level 3,
    [root@localhost ~]# grep id /etc/inittab
    id:3:initdefault:
    Disable "/etc/rc.local" run level elevation,
    [root@localhost ~]# tail -2 /etc/rc.local
    # Disable local forced runlevel 5, JAP 20120404
    #telinit 5
    Disable firewall to allow VNC connections,
    [root@localhost ~]# chkconfig --list iptables
    iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off
    [root@localhost ~]# chkconfig iptables off
    [root@localhost ~]# chkconfig --list ip6tables
    ip6tables 0:off 1:off 2:on 3:on 4:on 5:on 6:off
    [root@localhost ~]# chkconfig ip6tables off
    Reboot,
    [root@localhost ~]# reboot
    Broadcast message from root (pts/0) (Mon Apr 2 09:22:17 2012):
    The system is going down for reboot NOW!
    Post "oraclevm-template" configuration e.g. defining FQDN and static IP addresss etc. OVM Manager 3.0.3 is up.
    Configure VNC for "ovm",
    [root@ovm303-m ~]# su - ovm
    [ovm@ovm303-m ~]$ vncserver
    You will require a password to access your desktops.
    Password: Welcome1
    Verify: Welcome1
    xauth: creating new authority file /home/ovm/.Xauthority
    New 'ovm303-m:1 (ovm)' desktop is ovm303-m:1
    Creating default startup script /home/ovm/.vnc/xstartup
    Starting applications specified in /home/ovm/.vnc/xstartup
    Log file is /home/ovm/.vnc/ovm303-m:1.log
    [ovm@ovm303-m ~]$ vncserver -kill :1
    Killing Xvnc process ID 12499
    Update "xstartup",
    [ovm@ovm303-m ~]$ cat /home/ovm/.vnc/xstartup
    #!/bin/sh
    # Uncomment the following two lines for normal desktop:
    unset SESSION_MANAGER
    exec /etc/X11/xinit/xinitrc
    #[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
    #[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
    #xsetroot -solid grey
    #vncconfig -iconic &
    #xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
    #twm &
    [ovm@ovm303-m ~]$ vncserver
    New 'ovm303-m:1 (ovm)' desktop is ovm303-m :1
    Starting applications specified in /home/ovm/.vnc/xstartup
    Log file is /home/ovm/.vnc/ovm303-m:1.log
    Configure "/etc/sysconfig/vncservers",
    [root@ovm303-m ~]# chkconfig --list vncserver
    vncserver 0:off 1:off 2:off 3:off 4:off 5:off 6:off
    [root@ovm303-m ~]# chkconfig vncserver on
    [root@ovm303-m ~]# chkconfig --list vncserver
    vncserver 0:off 1:off 2:on 3:on 4:on 5:on 6:off
    [root@ovm303-m ~]# tail -2 /etc/sysconfig/vncservers
    # Start VNC session for ovm, JAP 20120404
    VNCSERVERS="1:ovm"

    Thanks Jim - looks great!

  • OVM Manager 3.1.1 b399 won't start up

    My OVM Manager was working quite well.
    I shutdown and powered off the server for a few hours, but when I restarted it, I keep getting:-
    # service ovmm start
    Starting Oracle Vm ManagerTime Out...
    I have no idea why it's not wanting to start up at the moment.
    Any where I can look for logging information to try and diagnose the failure?
    I can't see why a restart on the box would cause this. I've restarted it before without issue.

    Problem with oracle-xe perhaps?
    [root@ovm-manager-dev-01 init.d]# service oracle-xe status
    LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 08-OCT-2012 15:09:00
    Copyright (c) 1991, 2011, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
    TNS-00511: No listener
    Linux Error: 2: No such file or directory
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ovm-manager-dev-01)(PORT=1521)))
    TNS-12545: Connect failed because target host or object does not exist
    TNS-12560: TNS:protocol adapter error
    TNS-00515: Connect failed because target host or object does not exist

  • Connection problem to the OVM Manager 3.0.3 Console

    My OVM Manager 3.0.3 installation was smooth on top of Oracle Linux 6.0, not even with a single error after taking care of some prerequisite warning stuff at the beginning.
    After the installation, it displayed some info on how to connect to the OVM Manager Console.
    http://ovmmanager:7001/ovm/console
    https://ovmmanager:7002/ovm/console
    But, not only neither address seems to work but also the server opens neither port.
    I have no problem remotely logging into the shell via ssh.
    Trying "telnet ovmmanager 7001" and "telnet ovmmanager 7002" isn't connecting.
    Also, Oracle is up and running.
    # ps -ef |grep XE |wc -l
    31
    # ps -ef |grep pmon
    oracle 1610 1 0 02:28 ? 00:00:02 xe_pmon_XE
    I rebooted it couple of times but the same thing.
    Could someone please let me know where I should start?
    Thanks.
    - Young

    Hi,
    The reason is the /etc/rc.d/init.d/ovmm shell script. It tries to start the weblogic with oracle user. The oracle user doesnt have permission and it fails with a timeout
    if [ $action = run ]; then
    logger "Starting the Oracle VM Manager application."
    echo -n "Starting Oracle VM Manager"
    nohup su - oracle  -c "$USER_MEM_ARGS DOMAIN_PRODUCTION_MODE=true JAVA_OPTIONS=\"-Djava.awt.headless=true -Xdebug -Xrunjdwp:transport=dt_socket,address=127.0.0.1:8453,server=y,suspend=n -da:org.apache.myfaces.trinidad\" /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/startWebLogic.sh &" > /dev/null
    RETVAL="$?"
    fi
    change it to
    if [ $action = run ]; then
    logger "Starting the Oracle VM Manager application."
    echo -n "Starting Oracle VM Manager"
    nohup su -  -c "$USER_MEM_ARGS DOMAIN_PRODUCTION_MODE=true JAVA_OPTIONS=\"-Djava.awt.headless=true -Xdebug -Xrunjdwp:transport=dt_socket,address=127.0.0.1:8453,server=y,suspend=n -da:org.apache.myfaces.trinidad\" /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/startWebLogic.sh &" > /dev/null
    RETVAL="$?"
    fi
    Thanks,
    With Regards,
    Sudhir Koneru
    Edited by: 926503 on Apr 17, 2012 12:38 PM

Maybe you are looking for