xen, revisor
by Arno Karner
ok I make a new dvd iso image with revisor, modify the isolinux.cfg so it boots, and installs with my kickstart file.
I look at the anaconda.ks.cfg and none of my rpm packaes, which were installed show up.
Now I'm trying to trouble shoot the post install section of a few of my packages, which didn't seem to be executed,
so is there some where to look. install log didn't show anything useful.
How do I get my rpm-keys installed, doing it from an rpm is not possible because rpm does not support nested transactions,
any Ideas here welcome also. the key files are in the root directory od the install image, but that is not good enough.
I looked at the spec file of the package in question and it had a Requires: <package> <package> but the packages were not installed,
or complained about. Hence other packages that were installed gave warning messages about user xxx, group yyyy not defined using root:root
not what I wanted........
I'm reducing the install ks.cfg file, to make trouble shooting this in xen faster, and including a second menu option for a full install of what I want.
Sorry for the cross post but this issue deals with revisor, xen, anaconda. I'll be looking into the anaconda emailing list next.
I am using bleeding edge rpms, git fc7.testing revisor:git pull, and I should expect this. So I thought I'd ask while I try and reduce my loop time from 4+ hours
build iso image, xen.new virt machine + play free civ, update scripts and ks.list(s)....repeat
Ideas, flames, constructive criticizing welcome.
Arno
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
16 years, 6 months
virt-manager "Cannot allocate memory" creating Win2K3 HVM
by Andy Burns
Configuration of dom0 is as follows
8GB memory
2 x dual core Xeon
kernel-xen.x86_64 2.6.20-2931.fc7
xen.x86_64 3.1.0-2.fc7
xen-libs.x86_64 3.1.0-2.fc7
libvirt.x86_64 0.3.2-1.fc7
virt-manager-0.4.0-2.fc7
I'm trying to install a win2K3 32bit HVM domU
using /cd.iso file local to dom0
LVM partition /dev/vgmirror/win2k3 as domU disk
bridged eth0 network
1024MB memory for domU (have tried with lower memory)
Fails with POST operation failed: (xend.err "Error creating domain:
(12, 'Cannot allocate memory')")
Rebooting the dom0 is to be avoided if possible due to other paravirt
domU guests running, any suggestions or extra info that might help?
I have managed to successfully create a win2K3 64bit HVM domU on an
identical dom0 server.
16 years, 6 months
Xen Virt-Manager odd reaction
by slbubba@charter.net
Folks;
I have a small problem here that perhaps someone knows the answer to.
I'm running the following:
kernel xen 2.6.18-8.1.14.el5
xen 3.0.3-25.0.4.el5
virt-manager-0.2.6-7.0.2.el5
When using virt-manager to add a new VM (in this case Fedora core 6) the
installation moves along smoothly and the VM is displayed in the main
virt-manager window under dom-0.
At the end of the VM installation the screen to remove all disks and
click the reboot button appears.
Clicking on "reboot" in the VM window starts the reboot process.
However, the VM entry in the virt-manager window disappears, the VM
console disappears, and the VM never comes back.
The VM flat file is there (in my case it's /opt/vm01a) and the correct
size but virt-manager does not see the VM, only dom-0.
I've gone through this multiple times and now have 3 VM's but no way to
access them.
Where is the data for the VM kept that virt-manager uses? Why is
virt-manager acting this way? Any patches, fixes, different revs?
Thanks
Warren
16 years, 6 months