Hi kaitlin.
I tested on three machines.
===Machine A===
[root@dhcp-66-70-159 ~]# ls -laut /boot/ | grep vmlinuz
-rw-r--r-- 1 root root 2045656 Jan 14 08:40 vmlinuz-2.6.18-183.el5xen
-rw-r--r-- 1 root root 158 Jan 14 06:15 .vmlinuz-2.6.18-183.el5.hmac
-rw-r--r-- 1 root root 1953468 Jan 8 14:28 vmlinuz-2.6.18-183.el5
-rw-r--r-- 1 root root 161 Dec 21 18:51 .vmlinuz-2.6.18-183.el5xen.hmac
[root@dhcp-66-70-159 ~]# find /boot/ | grep vmlinuz | egrep -v 'xen' |
tail -n1
/boot/.vmlinuz-2.6.18-183.el5.hmac
==Machine B====
[root@dhcp-66-70-128 tmp]# ls -laut /boot/ | grep vmlinuz
lrwxrwxrwx 1 root root 22 Jan 15 10:52 vmlinuz ->
vmlinuz-2.6.18-160.el5
-rw-r--r-- 1 root root 1931964 Dec 23 13:44 vmlinuz-2.6.18-160.el5
-rw-r--r-- 1 root root 1931580 Aug 1 05:02 vmlinuz-2.6.18-158.el5
-rw-r--r-- 1 root root 2029233 Aug 1 05:02 vmlinuz-2.6.18-158.el5xen
-rw-r--r-- 1 root root 158 Jul 28 05:41 .vmlinuz-2.6.18-160.el5.hmac
-rw-r--r-- 1 root root 161 Jul 14 2009 .vmlinuz-2.6.18-158.el5xen.hmac
-rw-r--r-- 1 root root 158 Jul 14 2009 .vmlinuz-2.6.18-158.el5.hmac
[root@dhcp-66-70-128 tmp]# find /boot/ | grep vmlinuz | egrep -v 'xen' |
tail -n1
/boot/.vmlinuz-2.6.18-160.el5.hmac
======Machine C===============
[root@amd-4450b-4-1 ~]# ls -laut /boot/ | grep vmlinuz
-rw-r--r-- 1 root root 1953468 Jan 12 21:29 vmlinuz-2.6.18-183.el5
-rw-r--r-- 1 root root 2045656 Jan 12 21:29 vmlinuz-2.6.18-183.el5xen
-rw-r--r-- 1 root root 161 Dec 22 07:51 .vmlinuz-2.6.18-183.el5xen.hmac
-rw-r--r-- 1 root root 158 Dec 22 07:43 .vmlinuz-2.6.18-183.el5.hmac
[root@amd-4450b-4-1 ~]# find /boot/ | grep vmlinuz | grep -v 'xen' |
tail -n1
/boot/vmlinuz-2.6.18-183.el5
so, the result depends on the access time of ".vmlinuz-*.hmac".
that means the patch is not useless. :)
Thanks and Regards
osier
Kaitlin Rupert wrote:
Hi Osier,
On my system, I have the following kernels:
# ls -la /boot/ | grep vmlinuz
-rw-r--r-- 1 root root 1931580 Jul 13 2009 vmlinuz-2.6.18-158.el5
-rw-r--r-- 1 root root 158 Jul 13 2009 .vmlinuz-2.6.18-158.el5.hmac
-rw-r--r-- 1 root root 2029233 Jul 13 2009 vmlinuz-2.6.18-158.el5xen
-rw-r--r-- 1 root root 161 Jul 13 2009
.vmlinuz-2.6.18-158.el5xen.hmac
When I run find "/boot | grep vmlinuz | egrep -v 'xen' | tail -n1", I
get:
# find /boot | grep vmlinuz | egrep -v 'xen' | tail -n1
/boot/vmlinuz-2.6.18-158.el5
Do you see different results? Even though I can't reproduce the
issue, I'm fine with this change. But can you resubmit the patch
following the guidelines in cimtest/doc/SubmittingPatches? Each patch
needs to have a DCO.
Thanks!
Osier Yang wrote:
> Hi all
>
> the patch is trying to solve the problem:
> when there is .vmlinuz-*.hmac under /boot,
> cimtest/suites/libvirt-cim/images/xmt-makefv.sh won't work.
>
> [root@dhcp-66-70-159 ~]# ls -a /boot/ | grep vmlinuz
> vmlinuz-2.6.18-183.el5
> .vmlinuz-2.6.18-183.el5.hmac
> vmlinuz-2.6.18-183.el5xen
> .vmlinuz-2.6.18-183.el5xen.hmac
>
> [root@dhcp-66-70-159 images]# make
> mkdir -p xm-test
> (cd xm-test && wget
>
http://xm-test.xensource.com/ramdisks/initrd-1.1-i386.img)
> --2010-01-14 08:33:15--
>
http://xm-test.xensource.com/ramdisks/initrd-1.1-i386.img
> Resolving xm-test.xensource.com... 70.42.241.107
> Connecting to xm-test.xensource.com|70.42.241.107|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 3645440 (3.5M) [text/plain]
> Saving to: `initrd-1.1-i386.img'
>
> 100%[=====================================>] 3,645,440 7.76K/s in
> 7m 22s
> 2010-01-14 08:40:39 (8.05 KB/s) - `initrd-1.1-i386.img' saved
> [3645440/3645440]
>
> chmod +x xmt-convert.sh
> (cd xm-test && sh ../xmt-convert.sh `basename
> xm-test/initrd-1.1-i386.img`)
> 1856 blocks
> if uname -r | grep -q xen; then \
> cp /boot/vmlinuz-`uname -r`
> /var/lib/libvirt/images/default-xen-kernel; \
> fi
> chmod +x xmt-makefv.sh
> ./xmt-makefv.sh xm-test/xm-test.gz xm-test/xmt_disk.img
> FAILED:
> make: *** [xm-test/xmt_disk.img] Error 1
>
> hope it helps. :-)
>
> Thanks and Regards
> osier
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Libvirt-cim mailing list
> Libvirt-cim(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/libvirt-cim