I've created a virtual machine, but it won't start (blocked).
import os, re
arch = os.uname() 
kernel = "hvmloader"
memory = 10240
name = "OL-DB2-PRI"
cpus = "" # leave to Xen to pick
vcpus = 4
disk = [ 'file:/srv/OL-DB2-PRI/OL-DB2-PRI.img,xvda,w', 'file:/media/usb/extraISOs/OL6_64_1.iso,xvdc:cdrom,r' ]
vfb = [ 'vnc=1,vnclisten=0.0.0.0,vncdisplay=1,vncpasswd=Welkom_01' ]
root = "/dev/hda1 ro"
extra = "4"
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
xm list :
[root@OVS-PRI xen]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 832 8 r----- 547.4
OL-DB2-PRI 7 10240 4 -b---- 6.8
The log shows, xen is trying to watch files or directories that don't exsist:
xs_read(/local/domain/0/device-model/7/xen_extended_power_mgmt): read error
xs_read(/local/domain/7/log-throttling): read error
Am I using odd parameters in my config file?
The ISO file is downloaded straight from Oracle site. Which I also used to install OL6 directly.
Where else could I check?
I've created the directories manualy, but have no idea, what the files should contain.
I prefer not to use OVM Manager. To much dependancies.
xm create is not supposed to create any files. It is the command to start an already defined virtual machine. Your iso file would be presented as a block device, as would the blank, empty (I assume) boot disk, but you must create the networking, disks and cdroms beforehand. This is usually done with the OVM Manager.
I'm trying to get a Oracle Linux 6.3 Virtual machine.
Reason why I need a virtual machine is because of CPU capping to meet lincing demands.
On this OL6 I'll install Oracle RDBMS 11gR2 RAC.
So it would be my ISO, who expects these files?
Because the same messages are logged when trying to open a console.
The domain ID keeps changing, so the required dir, needs to created everytime too.. but which process would do this?
xm needs to do it's administration. Does this happen in allready existing files?
I've tried with a img file and with a raw device (last partition not mounted.
[root@OVS-PRI xen]# fdisk /dev/sda
The number of cylinders for this disk is set to 345652.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sda: 299.4 GB, 299439751168 bytes
47 heads, 36 sectors/track, 345652 cylinders
Units = cylinders of 1692 * 512 = 866304 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 121 102348 83 Linux
/dev/sda2 122 3839 3145428 83 Linux
/dev/sda3 3840 5078 1048194 82 Linux swap / Solaris
/dev/sda4 5079 345652 288125604 83 Linux