Fix built into xen-3.0.3-94.el5_4.1

Verify this on xen-3.0.3-94.el5_4.1, do follow steps:
1. Create a Fv/Pv domain
2. Reboot the domain by `xm reboot'
3. Wait for booting up the domain
4. Run `xm list'
5. Run 'virsh list --all'

Especially, I do above steps on Fv domain and Pv domain for 25 times.Each time I can see this domain in the xm list. So this bug can not be reproduced on xen-3.0.3-94.el5_4.1. Please see the follow info:

[root@dhcp-66-82-130 xen]# xm list
Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0     3998     2 r-----  71826.0
rhel5u4_ia64_xenfv                        31     1047     1 -b----     72.8


[root@dhcp-66-82-130 xen]# virsh list --all
 Id Name                 State
----------------------------------
  0 Domain-0             running
 31 rhel5u4_ia64_xenfv   idle
  - fv_rh                shut off
  - v7ia64               shut off
 
So change status to verified.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2009-1472.html