jiecho@sina.com
2008-Mar-19 02:06 UTC
Re: [Xen-users] conversion between Full-virtualization andPara-virtual
in a full-virtualization,this is my config file : name = "rhel51x64f" uuid = "8d33b93f-03e1-b2c2-c18f-82003c6e5b6f" maxmem = 2048 memory = 2048 vcpus = 2 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "cd" pae = 1 acpi = 1 apic = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib64/xen/bin/qemu-dm" sdl = 0 vnc = 1 vncunused = 1 keymap = "en-us" disk = [ "phy:/dev/xenvg/rhel51x64f,hda,w","file:/root/RHEL5.1-Server-20071017.0-x86_64-DVD.iso,hdc:cdrom,r" ] vif = [ "mac=00:16:3e:75:e8:4b,bridge=xenbr0" ] serial = "pty" I change to: name = "test" uuid = "1edde468-800e-3065-0336-cf4703c22cde" maxmem = 1024 memory = 2048 vcpus = 2 bootloader = "/usr/bin/pygrub" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1,keymap=en-us" ] disk = [ "phy:/dev/xenvg/rhel51x64f,xvda,w" ] vif = [ "mac=00:12:3e:13:12:c0,bridge=xenbr0" ] when I boot the guest with the error: [root@CDL-XEN xen]# xm create -c test Using config file "./test". Error: (2, 'Invalid kernel', 'xc_dom_parse_elf_kernel: ELF image has no shstrtab\n') and the error log file: [2008-03-19 05:51:29 xend 4506] DEBUG (balloon:127) Balloon: 2125808 KiB free; need 2097152; done. [2008-03-19 05:51:29 xend 4506] INFO (image:136) buildDomain os=linux dom=27 vcpus=2 [2008-03-19 05:51:29 xend 4506] DEBUG (image:201) domid = 27 [2008-03-19 05:51:29 xend 4506] DEBUG (image:202) memsize = 2048 [2008-03-19 05:51:29 xend 4506] DEBUG (image:203) image = /var/lib/xen/boot_kernel.ebKIa8 [2008-03-19 05:51:29 xend 4506] DEBUG (image:204) store_evtchn = 1 [2008-03-19 05:51:29 xend 4506] DEBUG (image:205) console_evtchn = 2 [2008-03-19 05:51:29 xend 4506] DEBUG (image:206) cmdline = ro root=LABEL=/ noapic rhgb quiet [2008-03-19 05:51:29 xend 4506] DEBUG (image:207) ramdisk = /var/lib/xen/boot_ramdisk.WXO_En [2008-03-19 05:51:29 xend 4506] DEBUG (image:208) vcpus = 2 [2008-03-19 05:51:29 xend 4506] DEBUG (image:209) features [2008-03-19 05:51:29 xend.XendDomainInfo 4506] ERROR (XendDomainInfo:212) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 205, in create vm.initDomain() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1471, in initDomain raise VmError(str(exn)) VmError: (2, \047Invalid kernel\047, \047xc_dom_parse_elf_kernel: ELF image has no shstrtab\n\047) [2008-03-19 05:51:29 xend.XendDomainInfo 4506] DEBUG (XendDomainInfo:1557) XendDomainInfo.destroy: domid=27 [2008-03-19 05:51:29 xend.XendDomainInfo 4506] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(27) There are several things you need to check. First, I'm going to assume you're running Linux as your guest O/S. If this is not the case, please respond with the O/S and version you're using. If you are using Linux, check the following: 1) In your guest config file on dom0, you need to switch your disk devices from IDE to xvd*. So, if you have a line that specifies a local volume as hda in your config file, change this to xvda. hdb -> xvdb, etc. 2) You need to specify the correct root device in your config file for the domU. This is done with root= in the file. If your previous root device was hda1, your root line would say root="/dev/xvda1 ro" or something similar. 3) You need to make sure that the kernel either has the Xen virtual block device module built in or that you create an initrd for your guest with this module. You also need to transfer the kernel and initrd into your dom0 so that you can put the kernel= and ramdisk= lines in your config file. 4) Finally, you need to change /etc/fstab to point to your new root device, e.g. /dev/xvda1. It would also be really helpful if you'd post the error you're getting. Just telling us that, "it fails to boot" isn't very descriptive. -Nick>>> On 2008/03/18 at 10:39, "HA"<jiecho@sina.com> wrote: Hi,All, I installed a guest os with full-virtualization and a local volume as the disk, now becuase of poor performance, I want to change the full-virtualization guest to para-virtualization, so I just changed the config file to boot the guest os with para-virtualization, but it fails to boot. but how can I convert the full-virtualization guest to para-virtualization without reinstall the os,on other hands,can I convert a para-virtualization to full-virtualization in xen? are there any suggestion?many thanks! This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. ------------------------------------------------------------------- 惠普春季促销送大礼，直降五千优惠连连( http://d1.sina.com.cn/sina/limeng3/mail_zhuiyu/2008/mail_zhuiyu_20080317.html ) ------------------------------------------------------------------- 注册新浪2G免费邮箱（http://mail.sina.com.cn/） _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
jim burns
2008-Mar-19 02:36 UTC
Re: [Xen-users] conversion between Full-virtualization andPara-virtual
On Tuesday 18 March 2008 10:06:11 pm jiecho@sina.com wrote:> when I boot the guest with the error: > [root@CDL-XEN xen]# xm create -c test > Using config file "./test". > Error: (2, ''Invalid kernel'', ''xc_dom_parse_elf_kernel: ELF image has no > shstrtab\n'')It looks like you didn''t install a kernel-xen in your domu. You are probably trying to boot the guest on the bare-metal kernel that would work on hvm. And make sure your grub.conf''s default= points to the kernel-xen stanza. Post your grub.conf if you need more help. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users