OVM « Różności …

Różności …

9 grudnia 2015

Solution: Oracle VM Server Reboots

Zaszufladkowany do: Informatyka - pozostałe — Tagi: — Jacek @ 10:59

http://mokumsolutions.com/solution-oracle-vm-server-reboots

13 sierpnia 2014

VirtualBox to VMware

Zaszufladkowany do: Oracle,VMware — Tagi: , — Jacek @ 13:37

In this tutorial I’ll show you how to convert a VirtualBox image to a VMware image.

I’m sure that there were many situation when you need to migrate a VirtualBox machine to a VMware one.

Tools used are VMware OVF Tool(ovftool.exe is a nice tool that will help you migrate from VirtualBox to VMware) and WMware vCenter Converter Standalone.

So, let’s convert ova image to vmx:

C:\PROGRA~1\VMware\VMware OVF Tool>ovftool.exe D:\IOU_VM.ova D:\IOU_VM.vmx
Opening OVA source: D:\IOU_VM.ova
Opening VMX target: D:\IOU_VM.vmx
Info:    License agreement for the virtual system
License: FREE and Only for PERSONAL use
Accept end-user license agreement?
Write ‘yes’ or ‘no’ (write ‘read’ to reread the EULA):
yes
Error: OVF Package is not supported by target:
- Line 39: Unsupported hardware family ‘virtualbox-2.2′.
Completed with errors


If you get Unsupported hardware family ‘virtualbox-2.2′ error you should try to use –lax argument.

This will transform the Unsupported hardware family ‘virtualbox-2.2′ error into a warning and convert ova file to vmx:

C:\PROGRA~1\VMware\VMware OVF Tool>ovftool.exe –lax D:\IOU_VM.ova D:\IOU_VM.vmx
Opening OVA source: D:\IOU_VM.ova
Opening VMX target: D:\IOU_VM.vmx
Info:    License agreement for the virtual system
License: FREE and Only for PERSONAL use
Accept end-user license agreement?
Write ‘yes’ or ‘no’ (write ‘read’ to reread the EULA):
yes
Warning:
- Line 39: Unsupported hardware family ‘virtualbox-2.2′.
- Line 80: OVF hardware element ‘ResourceType’ with instance ID ’5′: No support
for the virtual hardware device type ’20′.
Writing VMX file: D:\IOU_VM.vmx
Transfer Completed
Warning:
- No manifest entry found for: ‘IOU VM-disk1.vmdk’.
- No manifest file found.
Completed successfully
C:\PROGRA~1\VMware\VMware OVF Tool>


After that you use WMware vCenter Converter Standalone and get a working vmware machine.

From now you can deploy VirtualBox machines on VMware ESXi hosts.

Source

http://www.linuxexpert.ro/Virtualization-Tutorials/convert-virtualbox-image-to-vmware.html

17 lipca 2014

ovm cdrom boot problem

Zaszufladkowany do: Oracle — Tagi: , — Jacek @ 12:27

Its funny how things work in Oracle VM ..

I made some changes in configuration file and its working for me.. But I think this needs to be corrected.

xvdb is replaced with hdc..

Before

disk = ['file:/OVS/Repositories/0004fb0000030000aa8563ec6175dcfb/VirtualDisks/0004fb000012000095516dd08c3b253f.img,hda,w', 'file:/OVS/Repositories/0004fb0000030000aa8563ec6175dcfb/ISOs/slampp.iso,xvdb:cdrom,r']

After

disk = ['file:/OVS/Repositories/0004fb0000030000aa8563ec6175dcfb/VirtualDisks/0004fb000012000095516dd08c3b253f.img,hda,w', 'file:/OVS/Repositories/0004fb0000030000aa8563ec6175dcfb/ISOs/slampp.iso,hdc:cdrom,r']

I didn’t upload the iso using OVM managers import option ..Instead i have uploaded the iso file to ISO folder.refreshed repository from Manager..

ISO was reflected in Manager.

Hope this will be helpful for other guys facing similar issue.

———————————————————————————

So you broke lilo. Well done.

Insert your Slackware install DVD or CD1 and boot with defaults.
Once booted:

mkdir /foo
mount /dev/sda1 /foo
mount –bind /proc /foo/proc
mount –bind /sys /foo/sys
mount –bind /dev /foo/dev
chroot /foo
vi /etc/lilo.conf
lilo
exit
reboot

where /dev/sda1 is your installed / partition. Adjust as necessary.

lilo -F -r /mnt/sda2 -b /dev/sda -C /etc/lilo.conf

Strona startowa: www.jaceksen.pl