Ya virt-manager and virt-install both and it accepts 128MB RAM easily no problem. I guess there need to be done something in cobbler or koan code that helps it accept and boot with 128MB RAM too. I have tried installing virtual machine via virt-install and virt-manager (with 128MB RAM given to them) and it all works fine.
Regards
SysAdmin
On 4/3/07, Michael DeHaan <mdehaan@xxxxxxxxxx> wrote:
niyaz chistee wrote:
> Ya thanks for telling this. But what if I want to give my Xen virtual
> machine 128MB RAM only. Isn't it possible?
Anaconda really likes to have 256.
> Because if I give 128MB koan always fails during balloning. While if I
> don't use koan + cobbler I can install xen virtual machine with 128 MB
> RAM support only.
Using virt-manager? Perhaps that is granting it more RAM during
install and using a different value after the fact? Hmm...
>
> Hope you got my point.
>
> Regards
> SysAdmin
>
> On 4/2/07, *Michael DeHaan* <mdehaan@xxxxxxxxxx
> <mailto: mdehaan@xxxxxxxxxx>> wrote:
>
> niyaz chistee wrote:
> > Hello,
> >
> > Finally I got rid of the dhcp problem.
>
> I'm glad you got your problems figured out. As you can guess, the
> balloon message was about you not having enough RAM. Xen isn't
> completely obvious about what goes wrong when, this is true :)
>
> > But I had to stop my dummy0 virtual network interface in dom0
> host and
> > have to bridge my xenbr1 to eth1 (physical wireless device on dom0
> > host). The installation started without asking me anything (that
> was
> > real great un-attended installation).
> > The only thing it asked was when it was about to create the
> > partitions. It asked me whether it should format the whole disk or
> > not. When I pressed Yes it continued. If I want it to not ask this
> > thing what should I do. And one more thing after installation it
> stop
> > and asked me to press reboot button.
> There are some sample kickstarts in /etc/cobbler that you could use,
> particularly one that is tailored to creating really small Xen
> guests.
>
> > If I want it to automatically reboot then what should I do. I guess
> > something %post directive.
>
> reboot goes in the main section of the kickstart, not post. For an
> example, see /etc/cobbler/kickstart_fc6_domU.ks
>
>
>
> > Please help. And one more thing, I had to made huge modifications in
> > my kickstart file. So I am posting it once more. Hope it help
> you guys
> > in getting me:
> >
> > install
> > nfs --server= 192.168.1.5 <http://192.168.1.5>
> <http://192.168.1.5> --dir=/rhel5/Dump
> > key <HIDDEN>
> > lang en_US.UTF-8
> > network --bootproto=bootp --device=eth0 -->> > rootpw --iscrypted $1$VwD9nalr$06K0bUawzanX72gNk0es91
> > firewall --disabled
> > authconfig --enableshadow --enablemd5
> > selinux --disabled
> > timezone --utc Asia/Calcutta
> > bootloader --location=mbr --driveorder=xvda --append="console=xvc0"
> > # The following is the partition information you requested
> > # Note that any partitions you deleted are not expressed
> > # here so unless you clear all partitions first, this is
> > # not guaranteed to work
> > clearpart --all --drives=xvda
> > part /boot --fstype ext3 --size=100 -->> > part pv.2 --size=0 --grow -->> > volgroup VolGroup00 --pesize=32768 pv.2
> > logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00
> --size=1024
> > --grow
> > logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00
> > --size=144 --grow --maxsize=288
> >
> > %packages
> > @admin-tools
> > @base
> > @core
> >
> >
> > On 3/31/07, *niyaz chistee* < prime.provogue@xxxxxxxxx
> <mailto:prime.provogue@xxxxxxxxx>
> > <mailto:prime.provogue@xxxxxxxxx
> <mailto: prime.provogue@xxxxxxxxx>> > wrote:
> >
> > Hello guys,
> >
> > I somehow overcome the balloon problem. What I did was I delete
> > the system and profile by
> > cobbler system remove --name=<system_mac>
> > cobbler profile remove --name=<profile_name>
> >
> > And I added again the profile but this time I gave
> > --virt-ram-size=256 (as this was where koan reported warning
> > earlier) and then I created system as I did previously.
> > Then I ran koan once again (as I did earlier) but now a new
> > problem. It starts the virtual machine and ask me to connect
> to it
> > via xm console. I did so but it hangs during acquiring ip
> address
> > from dhcp. After sometime it ask me to give ip address
> manually I
> > do so ( 10.1.1.45/255.255.255.0
> <http://10.1.1.45/255.255.255.0> < http://10.1.1.45/255.255.255.0>
> > gateway 10.1.1.1 <http://10.1.1.1> < http://10.1.1.1>) but
> then it reports error in
> > getting nfs:/10.1.1.1/rhel5/Dump/ks.cfg. I have figured out the
> > problem. But don't know how to resolve it.
> > It is the same as I mentioned earlier. I have two network
> > interfaces. One is eth1 (wireless device) and other is dummy0
> > (virtual network interface). All the communication of xen vm's
> > with the xen dom0 is done via a bridge xenbr1 which is mapped to
> > dummy0. And in the dhcpd.conf there is nothing for the subnet
> > 10.1.1.0 <http://10.1.1.0> <http://10.1.1.0> and if I do
> manually (as of now cobbler
> > is managing my dhcpd.con) it reports error and doesn't start
> dhcpd
> > service. The error is logged into /var/log/messages and it is
> > shown below:
> >
> > Mar 31 10:05:01 server dhcpd: Internet Systems Consortium DHCP
> > Server V3.0.5-RedHat
> > Mar 31 10:05:01 server dhcpd: Copyright 2004-2006 Internet
> Systems
> > Consortium.
> > Mar 31 10:05:01 server dhcpd: All rights reserved.
> > Mar 31 10:05:01 server dhcpd: For info, please visit
> > http://www.isc.org/sw/dhcp/ <http://www.isc.org/sw/dhcp/ >
> > Mar 31 10:05:01 server dhcpd: Wrote 0 deleted host decls to
> leases
> > file.
> > Mar 31 10:05:01 server dhcpd: Wrote 0 new dynamic host decls to
> > leases file.
> > Mar 31 10:05:01 server dhcpd: Wrote 0 leases to leases file.
> > Mar 31 10:05:01 server dhcpd:
> > Mar 31 10:05:01 server dhcpd: No subnet declaration for eth1 (
> > 192.168.1.5 <http://192.168.1.5> <http://192.168.1.5
> < http://192.168.1.5>>).
> > Mar 31 10:05:01 server dhcpd: ** Ignoring requests on eth1. If
> > this is not what
> > Mar 31 10:05:01 server dhcpd: you want, please write a subnet
> > declaration
> > Mar 31 10:05:01 server dhcpd: in your dhcpd.conf file for the
> > network segment
> > Mar 31 10:05:01 server dhcpd: to which interface eth1 is
> > attached. **
> > Mar 31 10:05:01 server dhcpd:
> > Mar 31 10:05:01 server dhcpd:
> > Mar 31 10:05:01 server dhcpd: Not configured to listen on any
> > interfaces!
> > Mar 31 10:05:01 server dhcpd:
> > Mar 31 10:05:01 server dhcpd: If you did not get this software
> > from ftp.isc.org <http://ftp.isc.org> <http://ftp.isc.org>,
> please
> > Mar 31 10:05:01 server dhcpd: get the latest from
> ftp.isc.org <http://ftp.isc.org>
> > <http://ftp.isc.org> and install that before
> > Mar 31 10:05:01 server dhcpd: requesting help.
> > Mar 31 10:05:01 server dhcpd:
> > Mar 31 10:05:01 server dhcpd: If you did get this software from
> > ftp.isc.org < http://ftp.isc.org> <http://ftp.isc.org> and
> have not
> > Mar 31 10:05:01 server dhcpd: yet read the README, please
> read it
> > before requesting help.
> > Mar 31 10:05:01 server dhcpd: If you intend to request help from
> > the dhcp-server@xxxxxxx <mailto: dhcp-server@xxxxxxx>
> <mailto:dhcp-server@xxxxxxx <mailto:dhcp-server@xxxxxxx>>
> > Mar 31 10:05:01 server dhcpd: mailing list, please read the
> > section on the README about
> > Mar 31 10:05:01 server dhcpd: submitting bug reports and
> requests
> > for help.
> > Mar 31 10:05:01 server dhcpd:
> > Mar 31 10:05:01 server dhcpd: Please do not under any
> > circumstances send requests for
> > Mar 31 10:05:01 server dhcpd: help directly to the authors
> of this
> > software - please
> > Mar 31 10:05:01 server dhcpd: send them to the appropriate
> mailing
> > list as described in
> > Mar 31 10:05:01 server dhcpd: the README file.
> > Mar 31 10:05:01 server dhcpd:
> > Mar 31 10:05:01 server dhcpd: exiting.
> > Mar 31 10:05:01 server dhcpd: dhcpd startup failed
> >
> > If you want me to give some more information please feel
> free to ask.
> > Thanks in advance
> >
> > Regards
> > SysAdmin
> >
> >
> > On 3/31/07, *niyaz chistee* < prime.provogue@xxxxxxxxx
> <mailto:prime.provogue@xxxxxxxxx>
> > <mailto: prime.provogue@xxxxxxxxx
> <mailto:prime.provogue@xxxxxxxxx>>> wrote:
> >
> > Well I thought that I should go the other way. So I did
> this:
> > Note: I have my RHEL5 Dump in /rhel5/Dump
> >
> > cobbler distro add --name=rhel5
> > --kernel=/rhel5/Dump/images/xen/vmlinuz
> > --initrd=/rhel5/Dump/images/initrd.img
> >
> > This ran good. Then I did the following:
> >
> > cobbler profile add --name=redhat5x --distro=rhel5
> > --kickstart=/rhel5/Dump/ks.cfg --virt-file-size=2
> --virt-ram=128
> > cobbler system add --name=00:16:3E:5F:93:6A
> --profile="">> >
> > Okay Now I exported my /rhel5/Dump via NFS. Here's cat
> > /etc/exports
> > /rhel5/Dump
> 10.1.1.0/255.255.255.0(rw,sync,no_root_squash)
> <http://10.1.1.0/255.255.255.0%28rw,sync,no_root_squash%29>
> > < http://10.1.1.0/255.255.255.0%28rw,sync,no_root_squash%29>
> >
> > For the sake of convience I am also posting my
> > /rhel5/Dump/ks.cfg and /etc/dhcpd.conf
> > cat /etc/dhcpd.conf
> > #
> >
> ******************************************************************
> > # Cobbler managed dhcpd.conf file
> > # generated from cobbler dhcp.conf template (Sat Mar 31
> > 02:31:13 2007)
> > #
> >
> ******************************************************************
> > ddns-update-style interim;
> > allow booting;
> > allow bootp;
> > ignore client-updates;
> > set vendorclass = option vendor-class-identifier;
> > subnet 192.168.1.0 <http://192.168.1.0>
> < http://192.168.1.0 <http://192.168.1.0>> netmask 255.255.255.0
> <http://255.255.255.0 >
> > <http://255.255.255.0> {
> > option routers 192.168.1.5
> < http://192.168.1.5> <http://192.168.1.5>;
> > option subnet-mask 255.255.255.0
> < http://255.255.255.0> <http://255.255.255.0 <http://255.255.255.0>>;
> > range dynamic-bootp 192.168.1.100
> <http://192.168.1.100>
> > <http://192.168.1.100> 192.168.1.254
> <http://192.168.1.254> <http://192.168.1.254>;
> > filename "/pxelinux.0";
> > default-lease-time 21600;
> > max-lease-time 43200;
> > next-server 10.1.1.1 < http://10.1.1.1>
> <http://10.1.1.1>;
> > }
> > host label1 {
> > hardware ethernet 00:16:3E:5F:93:6A;
> > next-server 10.1.1.1 <http://10.1.1.1>
> <http://10.1.1.1>;
> > }
> >
> > cat /rhel5/Dump/ks.cfg
> > install
> > url --url nfs: 10.1.1.1:/rhel5/Dump
> > key <I_AM_NOT_WRITING_IT>
> > lang en_US.UTF-8
> > network --device eth0 --bootproto dhcp
> > rootpw --iscrypted $1$VwD9nalr$06K0bUawzanX72gNk0es91
> > firewall --disabled
> > authconfig --enableshadow --enablemd5
> > selinux --disabled
> > timezone --utc Asia/Calcutta
> > bootloader --location=mbr --driveorder=xvda
> > --append="console=xvc0"
> > # The following is the partition information you requested
> > # Note that any partitions you deleted are not expressed
> > # here so unless you clear all partitions first, this is
> > # not guaranteed to work
> > clearpart --all --drives=xvda
> > part /boot --fstype ext3 --size=100 -->> > part pv.2 --size=0 --grow --
> > volgroup VolGroup00 --pesize=32768 pv.2
> > logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00
> > --size=1024 --grow
> > logvol swap --fstype swap --name=LogVol01
> --vgname=VolGroup00
> > --size=144 --grow --maxsize=288
> > %packages
> > @admin-tools
> > @base
> > @core
> > @dialup
> > @java
> > @system-tools
> > @text-internet
> >
> > Now I started my portmap,tftp,nfs,httpd services and
> finally I
> > started koan.
> >
> > koan --virt --server=192.168.1.5 <http://192.168.1.5 >
> <http://192.168.1.5>
> > --profile="">> > It gave me this:
> > - processing profile: redhat5x
> > - fetching configuration for profile: redhat5x
> > - url= "" href="http://192.168.1.5/cobbler/profiles/redhat5x">http://192.168.1.5/cobbler/profiles/redhat5x
> < http://192.168.1.5/cobbler/profiles/redhat5x>
> > - {'kickstart': 'nfs://10.1.1.1/rhel5/Dump/ks.cfg', 'name':
> > 'redhat5x', 'virt_ram': 128, 'repos': '', 'kernel_options':
> > 'ksdevice=eth0 lang= syslog= 10.1.1.1:25150
> <http://10.1.1.1:25150>
> > < http://10.1.1.1:25150> text ', 'virt_file_size': 2,
> 'distro':
> > 'rhel5-xen', 'virt_paravirt': 'True', 'ks_meta': ''}
> > - fetching configuration for distro: rhel5-xen
> > - url= "" href="http://192.168.1.5/cobbler/distros/rhel5-xen">http://192.168.1.5/cobbler/distros/rhel5-xen
> > - {'kernel': '/rhel5/Dump/images/xen/vmlinuz',
> 'ks_meta': '',
> > 'breed': 'redhat', 'kernel_options': 'ksdevice=eth0 lang=
> > syslog= 10.1.1.1:25150 <http://10.1.1.1:25150>
> <http://10.1.1.1:25150> text ',
> > 'initrd': '/rhel5/Dump/images/xen/initrd.img', 'arch':
> 'x86',
> > 'name': 'rhel5-xen'}
> > - downloading initrd initrd.img to /tmp/initrd.img
> > -
> url="" href="http://192.168.1.5/cobbler/images/rhel5-xen/initrd.img"> http://192.168.1.5/cobbler/images/rhel5-xen/initrd.img
> <http://192.168.1.5/cobbler/images/rhel5-xen/initrd.img>
> > - downloading kernel vmlinuz to /tmp/vmlinuz
> > - url= "" href="http://192.168.1.5/cobbler/images/rhel5-xen/vmlinuz">http://192.168.1.5/cobbler/images/rhel5-xen/vmlinuz
> > - kernel saved = /tmp/vmlinuz
> > - initrd saved = /tmp/initrd.img
> > - invalid RAM size specified, defaulting to 256 MB
> > libvir: Xen Daemon error : POST operation failed: ( xend.err
> > 'Error creating domain: The privileged domain did not
> balloon!')
> > Failed to create domain 00_16_3E_5C_D5_0C
> > Traceback (most recent call last):
> > File "/usr/lib/python2.4/site-packages/koan/app.py", line
> > 97, in main
> > k.run()
> > File "/usr/lib/python2.4/site-packages/koan/app.py", line
> > 152, in run
> > self.do_virt()
> > File "/usr/lib/python2.4/site-packages/koan/app.py", line
> > 297, in do_virt
> > return self.do_net_install("/tmp",after_download)
> > File "/usr/lib/python2.4/site-packages/koan/app.py", line
> > 253, in do_net_install
> > after_download(self, distro_data, profile_data)
> > File "/usr/lib/python2.4/site-packages/koan/app.py", line
> > 296, in after_download
> > self.do_virt_net_install (profile_data, distro_data)
> > File "/usr/lib/python2.4/site-packages/koan/app.py", line
> > 600, in do_virt_net_install
> > extra=kextra
> > File
> "/usr/lib/python2.4/site-packages/koan/virtcreate.py",
> > line 102, in start_paravirt_install
> > guest.start_install()
> > File
> >
> "/usr/lib/python2.4/site-packages/virtinst/ParaVirtGuest.py",
> > line 220, in start_install
> > return XenGuest.XenGuest.start_install (self, consolecb)
> > File
> > "/usr/lib/python2.4/site-packages/virtinst/XenGuest.py",
> line
> > 367, in start_install
> > self.domain = self.conn.createLinux(cxml, 0)
> > File "/usr/lib/python2.4/site-packages/libvirt.py", line
> > 249, in createLinux
> > if ret is None:raise
> libvirtError('virDomainCreateLinux()
> > failed')
> > libvirtError: virDomainCreateLinux() failed
> >
> > I don't know what happened during the ballon but it didn't
> > created the virtual machine I was expecting.
> > One more thing I would like to through light on is that
> I have
> > configured a virtual dummy0 network interface which is
> bridged
> > to xenbr1. Here's my ifconfig(not shown are the xen virtual
> > interfaces):
> > dummy0 Link encap:Ethernet HWaddr F6:42:E2:23:B6:57
> > inet addr:10.1.1.1 <http://10.1.1.1>
> <http://10.1.1.1 < http://10.1.1.1>> Bcast:
> > 10.1.1.255 <http://10.1.1.255>
> <http://10.1.1.255 > Mask:255.255.255.0 <http://255.255.255.0>
> > < http://255.255.255.0>
> > inet6 addr: fe80::f442:e2ff:fe23:b657/64
> Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:41 errors:0 dropped:0 overruns:0
> frame:0
> > TX packets:154 errors:0 dropped:0 overruns:0
> carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:7438 ( 7.2 KiB) TX bytes:11815 (11.5 KiB)
> > eth1 Link encap:Ethernet HWaddr 00:13:02:4B:70:05
> > inet addr: 192.168.1.5 < http://192.168.1.5>
> <http://192.168.1.5>
> > Bcast:192.168.1.255 <http://192.168.1.255 > <
> http://192.168.1.255> Mask:
> > 255.255.255.0 <http://255.255.255.0 > <http://255.255.255.0>
> > inet6 addr: fe80::213:2ff:fe4b:7005/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:318 errors:0 dropped:45 overruns:0
> frame:0
> > TX packets:336 errors:0 dropped:0 overruns:0
> carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:173630 (169.5 KiB) TX bytes:30388 (
> 29.6 KiB)
> > Interrupt:16 Base address:0xe000
> > Memory:b0200000-b0200fff
> >
> > All my xen related network stuff is handled by dummy0 and it
> > is then masqureaded to eth1. I think there is problem with
> > /etc/dhcpd.conf regarding eth1 and dummy0. I am not
> getting it.
> > Please through some light.
> >
> > Regards
> >
> >
> > On 3/31/07, *niyaz chistee* < prime.provogue@xxxxxxxxx
> <mailto:prime.provogue@xxxxxxxxx>
> > <mailto: prime.provogue@xxxxxxxxx
> <mailto:prime.provogue@xxxxxxxxx>>> wrote:
> >
> > Hi,
> >
> > I am trying to configure cobbler to configure my xen
> > virtual machines. I tried to import the installation
> tree
> > of rhel5 from cobbler using the command:
> >
> > cobbler import --mirror=/rhel5/Dump/
> --mirror-name=rhel5
> >
> > It ran for sometime mirroring my rpm's and in last it
> > ended up with this:
> > sent 2597509927 bytes received 50280 bytes 8644127.14
> > bytes/sec
> > total size is 2596994302 speedup is 1.00
> > - creating new distro: rhel5
> > - creating new profile: rhel5
> > - running repo update on
> /var/www/cobbler/ks_mirror/rhel5
> > - no comps file found:
> > /var/www/cobbler/ks_mirror/rhel5/repodata/comps.xml
> > - modifying existing distro: rhel5
> > - modifying existing profile: rhel5
> > - running repo update on
> /var/www/cobbler/ks_mirror/rhel5
> > - no comps file found:
> > /var/www/cobbler/ks_mirror/rhel5/repodata/comps.xml
> > - creating new distro: rhel5-xen
> > - creating new profile: rhel5-xen
> > - running repo update on
> /var/www/cobbler/ks_mirror/rhel5
> > - no comps file found:
> > /var/www/cobbler/ks_mirror/rhel5/repodata/comps.xml
> > Traceback (most recent call last):
> > File
> > "/usr/lib/python2.4/site-packages/cobbler/cobbler.py",
> > line 502, in main
> > BootCLI( sys.argv).run()
> > File
> > "/usr/lib/python2.4/site-packages/cobbler/cobbler.py",
> > line 102, in run
> > self.curry_args(self.args[1:],
> self.commands['toplevel'])
> > File
> > "/usr/lib/python2.4/site-packages/cobbler/cobbler.py",
> > line 418, in curry_args
> > commands[args[0]](args[1:])
> > File
> > "/usr/lib/python2.4/site-packages/cobbler/cobbler.py",
> > line 312, in import_tree
> > return self.apply_args(args,commands,on_ok)
> > File
> > "/usr/lib/python2.4/site-packages/cobbler/cobbler.py",
> > line 406, in apply_args
> > on_ok()
> > File
> > "/usr/lib/python2.4/site-packages/cobbler/cobbler.py",
> > line 311, in <lambda>
> > go_import()
> > File
> > "/usr/lib/python2.4/site-packages/cobbler/cobbler.py",
> > line 304, in go_import
> > self.temp_mirror_name)
> > File
> "/usr/lib/python2.4/site-packages/cobbler/api.py",
> > line 152, in import_tree
> > return importer.run()
> > File
> >
> "/usr/lib/python2.4/site-packages/cobbler/action_import.py",
> > line 82, in run
> > self.guess_kickstarts()
> > File
> >
> "/usr/lib/python2.4/site-packages/cobbler/action_import.py",
> > line 139, in guess_kickstarts
> > results = self.scan_rpm_filename(rpm)
> > File
> >
> "/usr/lib/python2.4/site-packages/cobbler/action_import.py",
> > line 186, in scan_rpm_filename
> > major = int(major)
> > ValueError: invalid literal for int(): 5Server
> >
> > I don't know what this is all about. But when I ran
> > cobbler report it showed me this:
> >
> > [ root@server cobbler]# cobbler report
> > distro : rhel5
> > kernel :
> > /var/www/cobbler/ks_mirror/rhel5/images/pxeboot/vmlinuz
> > initrd :
> >
> /var/www/cobbler/ks_mirror/rhel5/images/pxeboot/initrd.img
> > kernel options : {}
> > architecture : x86
> > ks metadata : {}
> > breed : redhat
> >
> > distro : rhel5-xen
> > kernel :
> > /var/www/cobbler/ks_mirror/rhel5/images/xen/vmlinuz
> > initrd :
> > /var/www/cobbler/ks_mirror/rhel5/images/xen/initrd.img
> > kernel options : {}
> > architecture : x86
> > ks metadata : {}
> > breed : redhat
> >
> > profile : rhel5
> > distro : rhel5
> > kickstart : /etc/cobbler/default.ks
> > kernel options : {}
> > ks metadata : {}
> > virt file size : 5
> > virt ram : 512
> > virt paravirt : True
> > repos :
> >
> > profile : rhel5-xen
> > distro : rhel5-xen
> > kickstart : /etc/cobbler/default.ks
> > kernel options : {}
> > ks metadata : {}
> > virt file size : 5
> > virt ram : 512
> > virt paravirt : True
> > repos :
> >
> > That means it has created the distro and profile
> part. Is
> > that perfect or something is missing.
> >
> > Please help.
> >
> > Regards
> > SysAdmin
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > et-mgmt-tools mailing list
> > et-mgmt-tools@xxxxxxxxxx <mailto:et-mgmt-tools@xxxxxxxxxx>
> > https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools@xxxxxxxxxx <mailto:et-mgmt-tools@xxxxxxxxxx>
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
