Kickstart undefined partition error

[wsani]

I have been bootstrapping linux for the last few years. Even now, I'm still a novice, and will probably remain one :-) That being said, I decided to get a CentOS6 repo going with a kickstart profile for Xen PVs.

My hardware consists of:

3 X CentOS 5.6 Xen servers (HVM) - For server resiliency and Xen motion, etc.
1 NFS mount serving as the mount point (/xenstore) - Why yes, this is a SPOF.

I run Convirture community for the Xen management, etc. It is a really nice tool to use considering the fact that it allows me to centralize the management.

Here is the profile for the Xen PVs:

auth --useshadow --enablemd5
bootloader --location=mbr
zerombr
text
firewall --disabled
firstboot --disable
keyboard us
lang en_US
logging --level=info
url --url=http://[URL]/centos/6.0/os/x86_64
network --bootproto=dhcp --device=eth0 --onboot=on
rootpw --iscrypted [HASH]
selinux --disabled
skipx
timezone --isUtc America/Los_Angeles
install
clearpart --all --drives=sda
volgroup VolGroup --pesize=4096 pv.lWzE3x-exBc-VT1O-29CQ-yHeC-e783-76hWwh
logvol / --fstype=ext4 --name=lv_root --vgname=VolGroup --grow --size=1024 --maxsize=51200
logvol swap --name=lv_swap --vgname=VolGroup --grow --size=2016 --maxsize=4032
part /boot --fstype=ext4 --size=500
part pv.lWzE3x-exBc-VT1O-29CQ-yHeC-e783-76hWwh --grow --size=1
%packages
@base
%end

The problem is that if I kickstart it, it will fail on line 20, which is:
volgroup VolGroup --pesize=4096 pv.lWzE3x-exBc-VT1O-29CQ-yHeC-e783-76hWwh

I can do a CD install without any issues but the kickstart seems to experience the issue. I thought to myself if I do a graphical install successfully, then I can use the anaconda-ks.cfg part commands and get it over with, apparently copying and pasting (see above) that in my profile didn't work too well.

So, here I am at the CentOS community, asking why is this not working? I've used LVM with CentOS 5.6 successfully on the same servers, why is CentOS6 giving me so much grief? Did I miss a TPS report?

Thanks for reading.

[wsani]

Sorry, forgot to attach screenshot.
Edit: well apparently I can't attach screenshot so, take my word for it.

[TrevorH]

I checked my examples and they use a much smaller pv id so maybe it doesn't like that or the - signs in it

[code]
part /boot --size=100 --ondisk=\$d1 --asprimary --fstype=ext3
part swap --size=8192 --ondisk=\$d1 --asprimary --fstype=swap
part pv.01 --size=16384 --grow --ondisk=\$d1 --asprimary
volgroup vg00 pv.01
logvol / --vgname=vg00 --size=16384 --name root --fstype=ext3
logvol /tmp --vgname=vg00 --size=2048 --name=tmp --fstype=ext3
[/code]

[wsani]

Well that works so, I agree with you, the UUID I have there is totally out of the acceptable range.

Thanks for the assist.