Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-users

[Xen-users] Problem in updating linux kernel in a remote xen virtual mac

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Problem in updating linux kernel in a remote xen virtual machine
From: hxsrmeng <hxsrmeng@xxxxxxxxx>
Date: Wed, 28 Nov 2007 10:00:43 -0500
Delivery-date: Wed, 28 Nov 2007 07:04:22 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to:content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=Kf2NYhw7m7IRfybRW0L2yfnBqwUqo2MLkCt1BmJiusU=; b=q8/HDCs1KsHV6KT0Vl2DpKtMfwBvmSZDO9Z3RsvtpGZ3v1dIv7W459w3/NCqJmIwFbnoo7whMEQq3QLhTcuPS1hrah0gvvTVruuK+8Wzn0K2hNLc1PwWmA8Drj2wbo0lg4ZFU/OWAOmjUYHNj20/2HpfgQFvpRIZGdRbhjNYAsU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:subject:from:reply-to:to:content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=XIV08KUREjeBYzOBsxhiQHhzVESYhA3HmKrSQNxpEhYDDRtE7yLt3RHrTaoKi3FuLvjnMWZdPvEI/Vke9K5xqcZAU/0MM0kzNCUG3tmhMv9wKxY3bNTOyJsDG6bdu1GnwkWcuaLnwRMSUeiDpLsTyUsRzzMtwo7u41OBWIXLMm4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: TT
Reply-to: hxsrmeng@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi friends,

I'd like to update a linux kernel in a remote xen virtual machine but
met a problem.

The currently working kernel in that xen VM is linux-2.6.16.46-0.12, the
local version is "-xen".

I added one module, several kernel hacking options, and change the local
version to "-mine". After recompiling, I set this "-mine" kernel as my
default one in /boot/grub/menu.lst.

But the remote xen VM always boots with the original "-xen" kernel,
ignoring the "default" setting in the menu.lst. (I have not yet the
graphic access to the VM and host). Also I can not "modprobe" the module
I added.

So, I don't know what's wrong. Is there any difference in updating
kernels in VM? Or is there any general setting to set which kernels a VM
can boot with?

Thank you so much.

BTW, when doing kernel recompiling, I did

#make menuconfig
#make clean
#make 
#make modules_install install

At this point,
System.map-2.6.16.46-0.12-mine
config-2.6.16.46-0.12-mine
vmlinux-syms-2.6.16.46-0.12-mine
vmlinuz-2.6.16.46-0.12-mine

were generated and copied to /boot automatically, but no
initrd-2.6.16.46-0.12-mine. I had to use "mkinitrd" to generate it.Also,
the "-mine" entry in the menu.lst need to be added manually. 

Thank you again.




 


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>