No Console Defined in Xen Guest inittab
by Nicholas Schuetz
Hello,
I am using cobbler and koan to boot some RHEL 5.3 Xen pv guests on a
RHEL 5.3 host. The koan command I use to do so is:
koan --nogfx --server=<cobbler-server> --virt --system=<guest hostname>
The problem i'm seeing is ultimately the virtual guest ends up booting
w/o a console. The reason why is the guest inittab does not get
updated with:
co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav
I would think the --nogfx switch would tell virt-install or the like
that this is a no graphics installation and it needs a console.
Does anyone else have this issue. Is this a bug or am I doing
something wrong here?
As a workaround I've added a line in the kickstart %post section to
add this to the inittab:
echo "co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav" >> /etc/inittab
I'm using the following packages:
koan-1.4.1-1.el5
python-virtinst-0.300.2-12.el5
libvirt-python-0.3.3-14.el5
virt-manager-0.5.3-10.el5
libvirt-0.3.3-14.el5
xen-libs-3.0.3-80.el5
xen-3.0.3-80.el5
kernel-xen-2.6.18-128.1.1.el5
cobbler-1.4.1-1.el5
Regards,
Nick
15 years, 2 months
1.4.3 / 1.5.X status
by Michael DeHaan
Hi folks,
Just a quick update on release plans.
I'll be releasing 1.4.3 as soon as we get a EPEL-testing and Fedora 9/10
build for libyaml/PyYAML, which is expected this week (probably
Wednesday/Thursday). I'll also include any bug fixes I get before this
time, as well as any I fix myself before then.
Afterwards, barring unforseen events, the focus will be on getting 1.5
ready to go (release version will be 1.6). I am inclined to try to
release this in a couple of weeks following, and then push any more
feature enhancements towards a 1.6, rather than delaying things. The
reason for this is the devel branch already includes some rather nice
features, especially WRT cobblerd/web-app performance and s390 support.
I expect to get a few new minor fixes in before then. As I said
earlier, I want to try to get our release cycle for new major releases
closer to every two months if we can.
I've starred some of the big items that you might want to pay attention
to.
Here is 1.4.3's changelog thus far:
- (BUGF) fix OMAPI support's (note: deprecated) usage of subprocess
- (BUGF) don't traceback on invalid cmd ("cobbler distro list --name=foo")
- (BUGF) fix import usage with --kickstart option (no more traceback)
- (BUGF) fix removal of images with child system objects
- (BUGF) make --rpmlist on repo use same parsing routes as the rest of
cobbler
- (BUGF) default value for server override should be <<inherit>> not
<inherit> ***
- (BUGF) ensure if virt bridge is set to "" it will apply the value from
settings
- (BUGF) cobbler check should say path to config file is /etc/cobbler,
not /var/lib
- (FEAT) enable cobblerweb username/pass logins when authing with
spacewalk ***
- (BUGF) allow --kopts to take parameters that are shell quoted. ****
- (BUGF) allow kernel options to start with '-'
- (BUGF) prevent potential traceback when --template-file data isn't a hash
- (BUGF) set primary hostname manually in case Anaconda doesn't honor it
- (BUGF) anaconda doesn't honor nameserver always, set manually
- (BUGF) various post install network snippet fixes ***
- (SPEC) fix build for rawhide now that yaboot is included
- (BUGF) allow src and noarch arches for repo objects
- (BUGF) move to PyYAML for YAML implementation since it is better
maintained ***
- (BUGF) fixed web-interface editing of ownership
- (BUGF) fixed web-interface editing of management classes ***
Here is 1.5's changelog so far (on top of 1.4.3 changes):
- (FEAT) Improved anaconda monitoring code ***
- (FEAT) preliminary linux-ris support for windows installs (WIP)
- (FEAT) download comps.xml always
- (FEAT) performance upgrades for cobblerd service to avoid reloads ***
- (FEAT) more code for s390 imports
- (BUGF) import works better with rawhide
- (FEAT) snippet to preserve SSH host keys across reinstalls
- (FEAT) email trigger to notify when builds finish ***
- (FEAT) triggers now are written in Python, old system still exists.
- (FEAT) s390x zpxe support ***
- (BUGF) retry power 5 times before giving up
- (BUGF) fix for RHEL3 ppc imports
- (FEAT) use nameserver variable in network config in Anaconda when set
- (BUGF) sleep 5 seconds between power cycling systems
--Michael
15 years, 2 months
anamon misses modules on RHEL4 installation
by Vreman, Peter
To get anamon working on a RHEL4.6 installation I have to wget also the following files:
operator.so { this .so is python version dependent }
shlex.py
xmllib.py
xmlrpclib.py
How to solve this? Shall I also make the files available through http?
On which distro's is the anamon code developped?
Regards,
Peter
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
15 years, 2 months
help getting variables into power template
by Corey Osman
Hi
The following is an example power_vmware.template
I am trying to supply the powervmbymac.pl with a few extra variables:
/etc/cobbler/power/powervmbymac.pl
--server $power_address
--username $power_user
--password $power_pass
--operation $power_mode
--mac $interface['eth0'].get('mac_address')
--portgroup $portgroupname
The first three variables are easy to get but the last two I am not
sure.
How do I get the mac address of eth0? Or how do I get the mac address
from the system object?
I would like to add a section to /etc/cobbler/settings and have the
user set the default portgroup. But how would I retrieve this
variable set in settings?
Can I use python code in the template? What is the execution
environment for the template?
thanks,
Corey
15 years, 2 months
Re: RHN registration snippet
by James Cammarata
On Fri, 27 Feb 2009 21:00:23 +0000 (GMT), Rob Lazzurs <lazzurs(a)lazzurs.net>
wrote:
> On Fri, 27 Feb 2009, James Cammarata wrote:
>
>> I noticed the redhat_register snippet accesses a couple of variables
>> (also
>> shown in dumpvars), however the only one it seems you can edit is the
key
>> variable. Are the edit commands missing some options, or can someone
>> point me to some documentation on how to actually use this?
>>
>> # cobbler system dumpvars --name ks-test | grep redhat
>> 'breed': 'redhat',
>> 'redhat_management_key': '',
>> 'redhat_management_server': 'xmlrpc.rhn.redhat.com',
>> 'redhat_management_type': 'off',
>>
>> Hopefully it's not expected of people to hand-edit the config files to
>> use
>> this :)
>
> Hello James,
>
> If you wish to edit the management server then yes you will have to edit
> the configuration file in /etc/cobbler/settings. This file will also
have
> some other settings you have to change, the file is well documented and
> running 'cobbler check' on the command line should help you with any
> further settings you need to change.
>
> Take care.
>
> --
> Rob Lazzurs
Thanks guys, I didn't think to look in settings...
Might be a corner case, but if anyone had two different RHN servers they
might register to (I've actually seen this, last company had a completely
different satellite server for their lab/testing that was isolated from
production), this would be a limitation.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
15 years, 2 months