[et-mgmt-tools] Re: Koan problem

Martin Pearson martin.pearson at japannext.co.jp
Mon May 26 01:31:16 UTC 2008


Michael DeHaan wrote:
> Martin Pearson wrote:
>> Martin Pearson wrote:
>>> Hi All,
>>> Wonder if you can help me when I run Koan with the following inputs:-
>>>
>>> koan --virt --server=puppet --profile=RHEL4-ES-xen-x86_64 
>>> --virt-name=tkdvir1
>>>
>>> I get the following error:-
>>>
>>> libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID
>>>
>
> I don't think I have seen this particular error before.
>
> Can you share the koan, libvirt/Xen, and OS versions you are using, 
> and the full traceback (error message/output) if available?
>
> Koan also saves some additional logs in ~/.koan when creating VMs that 
> may also be useful.
> --Michael
>
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
Hi Michael,
Thanks very much for your reply. Please see below info requested:-

[root at xxxxxx ~]# rpm -qa | grep -i libvirt
libvirt-0.3.3-7.el5
libvirt-python-0.3.3-7.el5
[root at xxxxxx ~]# rpm -qa | grep -i xen
xen-libs-3.0.3-64.el5_2.1
kernel-xen-devel-2.6.18-92.el5
kernel-xen-2.6.18-92.el5
xen-devel-3.0.3-64.el5_2.1
xen-3.0.3-64.el5_2.1
[root at xxxxxx ~]# uname -a
Linux xxxxxxxx 2.6.18-92.el5xen #1 SMP Tue Apr 29 13:31:30 EDT 2008 
x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 5 (Tikanga)

Python info, just in case that helps.

python-urlgrabber-3.1.0-2
python-numeric-23.7-2.2.2
gtk-vnc-python-0.3.2-3.el5
python-setuptools-0.6c7-1.el5
libxml2-python-2.6.26-2.1.2.1
python-virtinst-0.300.2-8.el5
python-elementtree-1.2.6-5
python-sqlite-1.1.7-1.2.1
dbus-python-0.70-7.el5
libvirt-python-0.3.3-7.el5
python-2.4.3-21.el5
python-devel-2.4.3-21.el5
libselinux-python-1.33.4-5.el5
audit-libs-python-1.6.5-9.el5
rpm-python-4.4.2-48.el5
python-devel-2.4.3-21.el5

Version of cobbler on the server:-

cobbler-0.8.2-2

Output from koan command:-

[root at xxxxxxxx .koan]# koan --virt --server=puppet 
--profile=RHEL4-ES-xen-x86_64 --virt-name=tkdvir1
- reading URL: 
http://10.145.100.35/cblr/kickstarts/RHEL4-ES-xen-x86_64/ks.cfg
install_tree: http://10.145.100.35/cblr/links/RHEL4-ES-xen-x86_64
- no virt-type specified, auto-selecting xenpv
libvirtd (pid 16816) is running...
downloading initrd initrd.img to /var/lib/xen/initrd.img
url=http://puppet/cobbler/images/RHEL4-ES-xen-x86_64/initrd.img
- reading URL: http://puppet/cobbler/images/RHEL4-ES-xen-x86_64/initrd.img
downloading kernel vmlinuz to /var/lib/xen/vmlinuz
url=http://puppet/cobbler/images/RHEL4-ES-xen-x86_64/vmlinuz
- reading URL: http://puppet/cobbler/images/RHEL4-ES-xen-x86_64/vmlinuz
_*libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID
libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName*_
Kernel arguments: 
ks=http://10.145.100.35/cblr/kickstarts/RHEL4-ES-xen-x86_64/ks.cfg 
ksdevice=eth0 lang=  kssendmac syslog=10.145.100.35:25150 text
use virt-manager or reconnect with virsh console tkdvir1

Sorry was not precise enough with my previous email. Does not seem to be 
Koan that is crashing it just appears to be having a problem creating 
the virtual machine, i.e. if I go into virsh I have a machine there I 
can connect to via console <machine name>. Although the machine is stuck 
on boot see below:-

RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device installed.
Console: switching to colour frame buffer device 100x37
mice: PS/2 mouse device common for all mice
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 131072 (order: 9, 2097152 bytes)
TCP: Hash tables configured (established 131072 bind 131072)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 8192KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem). _*<Stuck at this point>

*_Also the tail end of the /var/log/messages log just in case this is 
useful:-

May 26 10:10:19 xxxxxxxx kernel: device vif28.0 entered promiscuous mode
May 26 10:10:19 xxxxxxxx kernel: audit(1211764219.787:43): dev=vif28.0 
prom=256 old_prom=0 auid=4294967295 ses=4294967295
May 26 10:10:19 xxxxxxxx kernel: ADDRCONF(NETDEV_UP): vif28.0: link is 
not ready
May 26 10:10:20 xxxxxxxx kernel: ADDRCONF(NETDEV_CHANGE): vif28.0: link 
becomes ready
May 26 10:10:20 xxxxxxxx kernel: xenbr0: port 3(vif28.0) entering 
learning state
May 26 10:10:20 xxxxxxxx kernel: blkback: ring-ref 522, event-channel 9, 
protocol 1 (x86_64-abi)
May 26 10:10:20 xxxxxxxx kernel: xenbr0: topology change detected, 
propagating
May 26 10:10:20 xxxxxxxx kernel: xenbr0: port 3(vif28.0) entering 
forwarding state
May 26 10:22:39 xxxxxxxx kernel: xenbr0: port 3(vif28.0) entering 
disabled state
May 26 10:22:39 xxxxxxxx kernel: device vif28.0 left promiscuous mode
May 26 10:22:39 xxxxxxxx kernel: audit(1211764959.982:44): dev=vif28.0 
prom=0 old_prom=256 auid=4294967295 ses=4294967295
May 26 10:22:39 xxxxxxxx kernel: xenbr0: port 3(vif28.0) entering 
disabled state
_*
*_Interesting thing is I can create a VM fine manually with virt-install?

Would be great if you could help out with this.


Many thanks,


Martin Pearson.





-------------- next part --------------
A non-text attachment was scrubbed...
Name: koan.log
Type: text/x-log
Size: 1875 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/et-mgmt-tools/attachments/20080526/4b14184c/attachment.bin>


More information about the et-mgmt-tools mailing list