John.Sanabria@xxxxxxxxxxxx wrote:
Hi, i did a littler changes respect previous messages. Now, the cobbler server is 136.145.116.78 and the machine that will be use koan is 136.145.116.114. So, i execute the steps in order to create a distro and profiles in .78 machine, and execute "cobbler sync". When i run the command "cobbler report" i got it: [root@dhcp-crl-116-78 ~]# cobbler report distro : test1 kernel : /boot/vmlinuz-2.6.19-1.2895.fc6 initrd : /boot/initrd-2.6.19-1.2895.fc6.img kernel options : architecture : x86 ks metadata : profile : test1-profile distro : test1 kickstart : /root/anaconda-ks.cfg kernel options : ks metadata : virt name : cobblertest virt file size : 3 virt ram : 512 virt paravirt : True repos : commands executed, previously: cobbler distro add --name="test1" --kernel=/boot/vmlinuz-2.6.19-1.2895.fc6 --initrd=/boot/initrd-2.6.19-1.2895.fc6.img cobbler profile add --name="test1-profile" --distro="test1" --kickstart=/root/anaconda-ks.cfg --virt-name="cobblertest" --virt-file-size=3 cobbler sync then, when i try to run the next koan command: koan --virt --server=136.145.116.78 --profile="test1-profile" at host 136.145.116.114, i got it: - processing profile: test1-profile - fetching configuration for profile: test1-profile - url=http://136.145.116.78/cobbler/profiles/test1-profile - {'kickstart': 'http://136.145.116.78/cobbler_track/kickstarts/test1-profile/ks .cfg', 'name': 'test1-profile', 'virt_ram': 512, 'repos': '', 'kernel_options': 'lang ksdevice=eth0 text syslog=136.145.116.78:25150 devfs=nomount ramdisk_size =16438 syslog=136.145.116.78:25150', 'virt_name': 'cobblertest', 'virt_file_size ': 3, 'distro': 'test1', 'virt_paravirt': 'True', 'ks_meta': ''} - fetching configuration for distro: test1 - url=http://136.145.116.78/cobbler/distros/test1 - {'kernel': '/boot/vmlinuz-2.6.19-1.2895.fc6', 'ks_meta': '', 'kernel_options': 'lang ksdevice=eth0 text devfs=nomount ramdisk_size=16438 syslog=136.145.116.7 8:25150', 'initrd': '/boot/initrd-2.6.19-1.2895.fc6.img', 'arch': 'x86', 'name': 'test1'} - downloading initrd initrd-2.6.19-1.2895.fc6.img to /tmp/initrd-2.6.19-1.2895.f c6.img - url=http://136.145.116.78/cobbler/images/test1/initrd-2.6.19-1.2895.fc6.img - downloading kernel vmlinuz-2.6.19-1.2895.fc6 to /tmp/vmlinuz-2.6.19-1.2895.fc6 - url=http://136.145.116.78/cobbler/images/test1/vmlinuz-2.6.19-1.2895.fc6 - kernel saved = /tmp/vmlinuz-2.6.19-1.2895.fc6 - initrd saved = /tmp/initrd-2.6.19-1.2895.fc6.imglibvir: Xen Daemon error : POST operation failed: (xend.err "Error creating doma in: (22, 'Invalid argument')") Failed to create domain cobblertest_1 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 155, in run self.do_virt() File "/usr/lib/python2.4/site-packages/koan/app.py", line 296, in do_virt return self.do_net_install("/tmp",after_download) File "/usr/lib/python2.4/site-packages/koan/app.py", line 254, in do_net_insta ll after_download(self, distro_data, profile_data) File "/usr/lib/python2.4/site-packages/koan/app.py", line 295, in after_downlo ad self.do_virt_net_install(profile_data, distro_data) File "/usr/lib/python2.4/site-packages/koan/app.py", line 595, in do_virt_net_ install extra=kextra File "/usr/lib/python2.4/site-packages/koan/virtcreate.py", line 196, in start _paravirt_install dom = conn.createLinux(cfgxml, 0) File "/usr/lib/python2.4/site-packages/libvirt.py", line 329, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self ) libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err "Er ror creating domain: (22, 'Invalid argument')") Thanks a lot, for any suggestion. regards.
Good job, the koan issue is resolved. You now have a straight up Xen issue, which should be directly reproducible by using virt-install, so here are some initial thoughts:
Initial thoughts: - Make sure you're using a Xen kernel and initrd, rather than the normal one. This comes out of the "xen" directory on a CD, not the "pxeboot" one.
- Check the logfiles (/var/log/xen/*) for anything suspicious - If all else fails, ask fedora-xen@xxxxxxxxxx
