Hello,
I compiled a 2.6.23 kernel with domU support, but the following error
shows up when I try to boot it on a Xen-3.1.0:
Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no
loader found\n'')
xm log shows:
[2007-10-10 11:23:39 2395] ERROR (__init__:1094)
XendDomainInfo.initDomain: exception occurred
Traceback (most recent call last):
File
"/usr/src/xen-3.1.0-src/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py",
line 1517, in _initDomain
channel_details = self.image.createImage()
File
"/usr/src/xen-3.1.0-src/dist/install/usr/lib64/python/xen/xend/image.py",
line 112, in createImage
return self.createDomain()
File
"/usr/src/xen-3.1.0-src/dist/install/usr/lib64/python/xen/xend/image.py",
line 131, in createDomain
result = self.buildDomain()
File
"/usr/src/xen-3.1.0-src/dist/install/usr/lib64/python/xen/xend/image.py",
line 517, in buildDomain
return LinuxImageHandler.buildDomain(self)
File
"/usr/src/xen-3.1.0-src/dist/install/usr/lib64/python/xen/xend/image.py",
line 215, in buildDomain
features = self.vm.getFeatures())
Error: (2, \047Invalid kernel\047, \047xc_dom_find_loader: no loader
found\n\047)
Google did not give any useful infos. Am I missing some option in the
kernel config?
Regards,
Zoltan HERPAI
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hello Zoltan, I do have the exactly same problem as you can see here: http://lists.xensource.com/archives/html/xen-users/2007-10/msg00244.html If you solve the problem, please remember to post the solution here. Pherhaps, Mark Williamson could help us to solve the problem. Regards, NicoP. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Zoltan HERPAI wrote:> I compiled a 2.6.23 kernel with domU support, but the following error shows up when I try to boot it on a Xen-3.1.0: > > Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'')Yep, same here. Is there a fine manual somewhere on how to boot a 2.6.23 domU with Xen 3.1.x? -- Tomasz Chmielewski http://blog.wpkg.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > I compiled a 2.6.23 kernel with domU support, but the following error > > shows up when I try to boot it on a Xen-3.1.0: > > > > Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') > > Yep, same here. > > Is there a fine manual somewhere on how to boot a 2.6.23 domU with Xen > 3.1.x?Good to see that people are trying out the new Xen support in mainline! To boot under Xen you need to use a vmlinux / vmlinuz image. Were you guys perhaps trying to use the bzImage? That won''t work (yet). The vmlinux that''s in the root of your kernel build tree ought to work. I stripped and gziped mine to get a much, much smaller vmlinuz file and used it to boot a Xen domain for the first time last night - worked fine. Mainline should support virtual block, virtual network, virtual console, SMP, etc but not live migration, suspend-resume, framebuffer, or anything involving dom0 functionality or direct device access. Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson schrieb:>>> I compiled a 2.6.23 kernel with domU support, but the following error >>> shows up when I try to boot it on a Xen-3.1.0: >>> >>> Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') >> Yep, same here. >> >> Is there a fine manual somewhere on how to boot a 2.6.23 domU with Xen >> 3.1.x? > > Good to see that people are trying out the new Xen support in mainline! > > To boot under Xen you need to use a vmlinux / vmlinuz image. Were you guys > perhaps trying to use the bzImage? That won''t work (yet). > > The vmlinux that''s in the root of your kernel build tree ought to work. I > stripped and gziped mine to get a much, much smaller vmlinuz file and used it > to boot a Xen domain for the first time last night - worked fine.I tried vmlinux, but also, it didn''t work. It hanged at: # xm create -c somedomain Using config file "/etc/xen/somedomain". Started domain somedomain And it seems to wait there forever. Normally, I would expect: # xm create -c somedomain Using config file "/etc/xen/somedomain". Started domain somedomain Linux version 2.6.18-xen (root@.... -- Tomasz Chmielewski http://blog.wpkg.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson schrieb: (...)> Mainline should support virtual block, virtual network, virtual console, SMP, > etc but not live migration, suspend-resume, framebuffer, or anything > involving dom0 functionality or direct device access.Is it aimed for 2.6.24? Or some of these features perhaps (live migration)? -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > To boot under Xen you need to use a vmlinux / vmlinuz image. Were you > > guys perhaps trying to use the bzImage? That won''t work (yet). > > > > The vmlinux that''s in the root of your kernel build tree ought to work. > > I stripped and gziped mine to get a much, much smaller vmlinuz file and > > used it to boot a Xen domain for the first time last night - worked fine. > > I tried vmlinux, but also, it didn''t work. > > It hanged at: > > # xm create -c somedomain > Using config file "/etc/xen/somedomain". > Started domain somedomain > > > And it seems to wait there forever.It''s just not outputting to the console. In the domain config file add "console=/dev/hvc0" to the extra= line in order to append this to the kernel command line. Then you ought to see the usual boot output. Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tomasz Chmielewski schrieb:> Mark Williamson schrieb: >>>> I compiled a 2.6.23 kernel with domU support, but the following error >>>> shows up when I try to boot it on a Xen-3.1.0: >>>> >>>> Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') >>> Yep, same here. >>> >>> Is there a fine manual somewhere on how to boot a 2.6.23 domU with Xen >>> 3.1.x? >> >> Good to see that people are trying out the new Xen support in mainline! >> >> To boot under Xen you need to use a vmlinux / vmlinuz image. Were you >> guys perhaps trying to use the bzImage? That won''t work (yet). >> >> The vmlinux that''s in the root of your kernel build tree ought to >> work. I stripped and gziped mine to get a much, much smaller vmlinuz >> file and used it to boot a Xen domain for the first time last night - >> worked fine. > > I tried vmlinux, but also, it didn''t work. > > It hanged at: > > # xm create -c somedomain > Using config file "/etc/xen/somedomain". > Started domain somedomain > > > And it seems to wait there forever.Here are some logs - all that on a 3.1 dom0 running 2.6.18 kernel: # cat domain-builder-ng.log xc_dom_allocate: cmdline="root=/dev/sda5 ro 3", features="" xc_dom_kernel_file: filename="/boot/vmlinux" xc_dom_malloc_filemap : 3287 kB xc_dom_boot_xen_init: ver 3.1, caps xen-3.0-x86_32p xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... OK elf_parse_binary: phdr: paddr=0x100000 memsz=0x1e6064 elf_parse_binary: phdr: paddr=0x2e7000 memsz=0x78000 elf_parse_binary: memory: 0x100000 -> 0x35f000 elf_xen_parse_note: GUEST_OS = "linux" elf_xen_parse_note: GUEST_VERSION = "2.6" elf_xen_parse_note: XEN_VERSION = "xen-3.0" elf_xen_parse_note: VIRT_BASE = 0xc0000000 elf_xen_parse_note: ENTRY = 0xc030c268 elf_xen_parse_note: HYPERCALL_PAGE = 0xc033e000 elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb" elf_xen_parse_note: PAE_MODE = "yes" elf_xen_parse_note: LOADER = "generic" elf_xen_addr_calc_check: ELF_PADDR_OFFSET unset, using 0x0 elf_xen_addr_calc_check: addresses: virt_base = 0xc0000000 elf_paddr_offset = 0x0 virt_offset = 0xc0000000 virt_kstart = 0xc0100000 virt_kend = 0xc035f000 virt_entry = 0xc030c268 xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0xc0100000 -> 0xc035f000 xc_dom_mem_init: mem 192 MB, pages 0xc000 pages, 4k each xc_dom_mem_init: 0xc000 pages xc_dom_boot_mem_init: called x86_compat: guest xen-3.0-x86_32p, address size 32 xc_dom_malloc : 192 kB xc_dom_build_image: called xc_dom_alloc_segment: kernel : 0xc0100000 -> 0xc035f000 (pfn 0x100 + 0x25f pages) xc_dom_pfn_to_ptr: domU mapping: pfn 0x100+0x25f at 0xb1ce7000 elf_load_binary: phdr 0 at 0x0xb1ce7000 -> 0x0xb1ecd064 elf_load_binary: phdr 1 at 0x0xb1ece000 -> 0x0xb1f21086 xc_dom_alloc_segment: phys2mach : 0xc035f000 -> 0xc038f000 (pfn 0x35f + 0x30 pages) xc_dom_pfn_to_ptr: domU mapping: pfn 0x35f+0x30 at 0xb1cb7000 xc_dom_alloc_page : start info : 0xc038f000 (pfn 0x38f) xc_dom_alloc_page : xenstore : 0xc0390000 (pfn 0x390) xc_dom_alloc_page : console : 0xc0391000 (pfn 0x391) nr_page_tables: 0x00000000ffffffff/32: 0x0000000000000000 -> 0xffffffffffffffff, 1 table(s) nr_page_tables: 0x000000003fffffff/30: 0x00000000c0000000 -> 0x00000000ffffffff, 1 table(s) nr_page_tables: 0x00000000001fffff/21: 0x00000000c0000000 -> 0x00000000c07fffff, 4 table(s) xc_dom_alloc_segment: page tables : 0xc0392000 -> 0xc0398000 (pfn 0x392 + 0x6 pages) xc_dom_pfn_to_ptr: domU mapping: pfn 0x392+0x6 at 0xb1cb1000 xc_dom_alloc_page : boot stack : 0xc0398000 (pfn 0x398) xc_dom_build_image : virt_alloc_end : 0xc0399000 xc_dom_build_image : virt_pgtab_end : 0xc0800000 xc_dom_boot_image: called arch_setup_bootearly: doing nothing xc_dom_compat_check: supported guest type: xen-3.0-x86_32p <= matches xc_dom_update_guest_p2m: dst 32bit, pages 0xc000 clear_page: pfn 0x391, mfn 0x49de6 clear_page: pfn 0x390, mfn 0x49de7 xc_dom_pfn_to_ptr: domU mapping: pfn 0x38f+0x1 at 0xb1cb0000 start_info_x86_32: called setup_hypercall_page: vaddr=0xc033e000 pfn=0x33e domain builder memory footprint allocated malloc : 209 kB anon mmap : 0 bytes mapped file mmap : 3287 kB domU mmap : 2648 kB arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xbcc shared_info_x86_32: called vcpu_x86_32: called vcpu_x86_32: cr3: pfn 0x392 mfn 0x49de5 launch_vm: called, ctxt=0x82705d4 xc_dom_release: called # cat xend.log [2007-10-11 17:00:42 3682] DEBUG (XendDomainInfo:78) XendDomainInfo.create([''vm'', [''name'', ''imap1''], [''memory'', 192], [''vcpus'', 1], [''on_xend_start'', ''ignore''], [''on_xend_stop'', ''ignore''], [''image'', [''linux'', [''kernel'', ''/boot/vmlinux''], [''root'', ''/dev/sda5 ro''], [''args'', ''3'']]], [''device'', [''vbd'', [''uname'', ''phy:/dev/iscsi/iqn.2006-09.net.syneticon:san1.imap1/part''], [''dev'', ''sda5''], [''mode'', ''w'']]], [''device'', [''vif'', [''ip'', ''192.168.113.5''], [''mac'', ''00:16:3E:2D:49:51''], [''bridge'', ''xenbr113'']]], [''device'', [''vif'', [''ip'', ''87.79.32.169''], [''mac'', ''00:16:3E:23:50:74''], [''bridge'', ''xenbr511'']]]]) [2007-10-11 17:00:42 3682] DEBUG (XendDomainInfo:1414) XendDomainInfo.constructDomain [2007-10-11 17:00:42 3682] DEBUG (balloon:113) Balloon: 808380 KiB free; need 2048; done. [2007-10-11 17:00:42 3682] DEBUG (XendDomain:434) Adding Domain: 17 [2007-10-11 17:00:42 3682] DEBUG (XendDomainInfo:1468) XendDomainInfo.initDomain: 17 256 [2007-10-11 17:00:42 3682] DEBUG (XendDomainInfo:1500) _initDomain:shadow_memory=0x0, memory_static_max=0xc000000, memory_static_min=0x0. [2007-10-11 17:00:42 3682] DEBUG (balloon:113) Balloon: 808380 KiB free; need 196608; done. [2007-10-11 17:00:42 3682] INFO (image:129) buildDomain os=linux dom=17 vcpus=1 [2007-10-11 17:00:42 3682] DEBUG (image:198) domid = 17 [2007-10-11 17:00:43 3682] DEBUG (image:199) memsize = 192 [2007-10-11 17:00:43 3682] DEBUG (image:200) image = /boot/vmlinux [2007-10-11 17:00:43 3682] DEBUG (image:201) store_evtchn = 1 [2007-10-11 17:00:43 3682] DEBUG (image:202) console_evtchn = 2 [2007-10-11 17:00:43 3682] DEBUG (image:203) cmdline = root=/dev/sda5 ro 3 [2007-10-11 17:00:43 3682] DEBUG (image:204) ramdisk [2007-10-11 17:00:43 3682] DEBUG (image:205) vcpus = 1 [2007-10-11 17:00:43 3682] DEBUG (image:206) features [2007-10-11 17:00:43 3682] INFO (XendDomainInfo:1316) createDevice: vbd : {''uuid'': ''efe192d4-8ba2-95ed-de8b-3b2066def1c2'', ''bootable'': 1, ''driver'': ''paravirtualised'', ''dev'': ''sda5'', ''uname'': ''phy:/dev/iscsi/iqn.2006-09.net.syneticon:san1.imap1/part'', ''mode'': ''w''} [2007-10-11 17:00:43 3682] DEBUG (DevController:115) DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''2053'', ''device-type'': ''disk'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vbd/17/2053''} to /local/domain/17/device/vbd/2053. [2007-10-11 17:00:43 3682] DEBUG (DevController:117) DevController: writing {''domain'': ''imap1'', ''frontend'': ''/local/domain/17/device/vbd/2053'', ''uuid'': ''efe192d4-8ba2-95ed-de8b-3b2066def1c2'', ''dev'': ''sda5'', ''state'': ''1'', ''params'': ''/dev/iscsi/iqn.2006-09.net.syneticon:san1.imap1/part'', ''mode'': ''w'', ''online'': ''1'', ''frontend-id'': ''17'', ''type'': ''phy''} to /local/domain/0/backend/vbd/17/2053. [2007-10-11 17:00:43 3682] INFO (XendDomainInfo:1316) createDevice: vif : {''ip'': ''192.168.113.5'', ''mac'': ''00:16:3E:2D:49:51'', ''uuid'': ''f4777093-485e-ddf6-b454-e2ac7f8b4ce0'', ''bridge'': ''xenbr113''} [2007-10-11 17:00:43 3682] DEBUG (DevController:115) DevController: writing {''backend-id'': ''0'', ''mac'': ''00:16:3E:2D:49:51'', ''handle'': ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/17/0''} to /local/domain/17/device/vif/0. [2007-10-11 17:00:43 3682] DEBUG (DevController:117) DevController: writing {''bridge'': ''xenbr113'', ''domain'': ''imap1'', ''handle'': ''0'', ''uuid'': ''f4777093-485e-ddf6-b454-e2ac7f8b4ce0'', ''script'': ''/etc/xen/scripts/vif-bridge'', ''ip'': ''192.168.113.5'', ''state'': ''1'', ''frontend'': ''/local/domain/17/device/vif/0'', ''mac'': ''00:16:3E:2D:49:51'', ''online'': ''1'', ''frontend-id'': ''17'', ''type'': ''netfront''} to /local/domain/0/backend/vif/17/0. [2007-10-11 17:00:43 3682] INFO (XendDomainInfo:1316) createDevice: vif : {''ip'': ''87.79.32.169'', ''mac'': ''00:16:3E:23:50:74'', ''uuid'': ''78b1deb1-9e59-a2a7-a310-7c34d7937903'', ''bridge'': ''xenbr511''} [2007-10-11 17:00:43 3682] DEBUG (DevController:115) DevController: writing {''backend-id'': ''0'', ''mac'': ''00:16:3E:23:50:74'', ''handle'': ''1'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/17/1''} to /local/domain/17/device/vif/1. [2007-10-11 17:00:43 3682] DEBUG (DevController:117) DevController: writing {''bridge'': ''xenbr511'', ''domain'': ''imap1'', ''handle'': ''1'', ''uuid'': ''78b1deb1-9e59-a2a7-a310-7c34d7937903'', ''script'': ''/etc/xen/scripts/vif-bridge'', ''ip'': ''87.79.32.169'', ''state'': ''1'', ''frontend'': ''/local/domain/17/device/vif/1'', ''mac'': ''00:16:3E:23:50:74'', ''online'': ''1'', ''frontend-id'': ''17'', ''type'': ''netfront''} to /local/domain/0/backend/vif/17/1. [2007-10-11 17:00:43 3682] DEBUG (XendDomainInfo:1973) Storing VM details: {''on_xend_stop'': ''ignore'', ''shadow_memory'': ''0'', ''uuid'': ''6f8783d1-5e57-e2f6-a7db-807fb73c4a99'', ''on_reboot'': ''restart'', ''start_time'': ''1192114843.62'', ''on_poweroff'': ''destroy'', ''on_xend_start'': ''ignore'', ''on_crash'': ''restart'', ''xend/restart_count'': ''0'', ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''image'': "(linux (kernel /boot/vmlinux) (args ''root=/dev/sda5 ro 3'') (notes (FEATURES ''!writable_page_tables|pae_pgdir_above_4gb'') (VIRT_BASE 3221225472) (GUEST_VERSION 2.6) (GUEST_OS linux) (HYPERCALL_PAGE 3224625152) (LOADER generic) (PAE_MODE yes) (ENTRY 3224420968) (XEN_VERSION xen-3.0)))", ''name'': ''imap1''} [2007-10-11 17:00:43 3682] DEBUG (XendDomainInfo:824) Storing domain details: {''console/ring-ref'': ''302566'', ''image/entry'': ''3224420968'', ''image/pae-mode'': ''yes'', ''console/port'': ''2'', ''name'': ''imap1'', ''console/limit'': ''1048576'', ''image/loader'': ''generic'', ''image/virt-base'': ''3221225472'', ''image/guest-os'': ''linux'', ''vm'': ''/vm/6f8783d1-5e57-e2f6-a7db-807fb73c4a99'', ''domid'': ''17'', ''store/port'': ''1'', ''image/hypercall-page'': ''3224625152'', ''memory/target'': ''196608'', ''image/features/pae-pgdir-above-4gb'': ''1'', ''control/platform-feature-multiprocessor-suspend'': ''1'', ''image/features/writable-page-tables'': ''0'', ''store/ring-ref'': ''302567'', ''image/guest-version'': ''2.6'', ''cpu/0/availability'': ''online'', ''image/xen-version'': ''xen-3.0''} [2007-10-11 17:00:44 3682] DEBUG (DevController:115) DevController: writing {''state'': ''1'', ''backend-id'': ''0'', ''backend'': ''/local/domain/0/backend/console/17/0''} to /local/domain/17/device/console/0. [2007-10-11 17:00:44 3682] DEBUG (DevController:117) DevController: writing {''domain'': ''imap1'', ''protocol'': ''vt100'', ''uuid'': ''2b20f8f3-335a-e93c-2dd9-f41028ae22e1'', ''frontend'': ''/local/domain/17/device/console/0'', ''state'': ''1'', ''location'': ''2'', ''online'': ''1'', ''frontend-id'': ''17''} to /local/domain/0/backend/console/17/0. [2007-10-11 17:00:44 3682] DEBUG (XendDomainInfo:824) Storing domain details: {''console/ring-ref'': ''302566'', ''image/entry'': ''3224420968'', ''image/pae-mode'': ''yes'', ''console/port'': ''2'', ''name'': ''imap1'', ''console/limit'': ''1048576'', ''image/loader'': ''generic'', ''image/virt-base'': ''3221225472'', ''image/guest-os'': ''linux'', ''vm'': ''/vm/6f8783d1-5e57-e2f6-a7db-807fb73c4a99'', ''domid'': ''17'', ''store/port'': ''1'', ''image/hypercall-page'': ''3224625152'', ''memory/target'': ''196608'', ''image/features/pae-pgdir-above-4gb'': ''1'', ''control/platform-feature-multiprocessor-suspend'': ''1'', ''image/features/writable-page-tables'': ''0'', ''store/ring-ref'': ''302567'', ''image/guest-version'': ''2.6'', ''cpu/0/availability'': ''online'', ''image/xen-version'': ''xen-3.0''} [2007-10-11 17:00:44 3682] DEBUG (XendDomainInfo:908) XendDomainInfo.handleShutdownWatch [2007-10-11 17:00:44 3682] DEBUG (DevController:148) Waiting for devices vif. [2007-10-11 17:00:44 3682] DEBUG (DevController:153) Waiting for 0. [2007-10-11 17:00:44 3682] DEBUG (DevController:539) hotplugStatusCallback /local/domain/0/backend/vif/17/0/hotplug-status. [2007-10-11 17:00:44 3682] DEBUG (DevController:553) hotplugStatusCallback 1. [2007-10-11 17:00:44 3682] DEBUG (DevController:153) Waiting for 1. [2007-10-11 17:00:44 3682] DEBUG (DevController:539) hotplugStatusCallback /local/domain/0/backend/vif/17/1/hotplug-status. [2007-10-11 17:00:44 3682] DEBUG (DevController:553) hotplugStatusCallback 1. [2007-10-11 17:00:44 3682] DEBUG (DevController:148) Waiting for devices usb. [2007-10-11 17:00:44 3682] DEBUG (DevController:148) Waiting for devices vbd. [2007-10-11 17:00:44 3682] DEBUG (DevController:153) Waiting for 2053. [2007-10-11 17:00:44 3682] DEBUG (DevController:539) hotplugStatusCallback /local/domain/0/backend/vbd/17/2053/hotplug-status. [2007-10-11 17:00:45 3682] DEBUG (DevController:553) hotplugStatusCallback 1. [2007-10-11 17:00:45 3682] DEBUG (DevController:148) Waiting for devices irq. [2007-10-11 17:00:45 3682] DEBUG (DevController:148) Waiting for devices vkbd. [2007-10-11 17:00:45 3682] DEBUG (DevController:148) Waiting for devices vfb. [2007-10-11 17:00:45 3682] DEBUG (DevController:148) Waiting for devices console. [2007-10-11 17:00:45 3682] DEBUG (DevController:153) Waiting for 0. [2007-10-11 17:00:45 3682] DEBUG (DevController:148) Waiting for devices pci. [2007-10-11 17:00:45 3682] DEBUG (DevController:148) Waiting for devices ioports. [2007-10-11 17:00:45 3682] DEBUG (DevController:148) Waiting for devices tap. [2007-10-11 17:00:45 3682] DEBUG (DevController:148) Waiting for devices vtpm. [2007-10-11 17:00:45 3682] INFO (XendDomain:1108) Domain imap1 (17) unpaused. -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Mainline should support virtual block, virtual network, virtual console, > > SMP, etc but not live migration, suspend-resume, framebuffer, or anything > > involving dom0 functionality or direct device access. > > Is it aimed for 2.6.24? Or some of these features perhaps (live migration)?I''ve not seen a plan for the 2.6.24 merge, so I don''t know if any features are being added or if work is going into other things (e.g. paravirt_ops for x64). From what Jeremy has told me before, live migration interacts badly with pre-emptible kernel (a fact which the mainline folks weren''t too keen on, which I presume is why it isn''t merged yet) but should be doable in the short term if migration depends on !CONFIG_PREEMPT. I think there are plans for how to support both together in future, if there''s sufficient motivation. Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson schrieb:>>> I compiled a 2.6.23 kernel with domU support, but the following error >>> shows up when I try to boot it on a Xen-3.1.0: >>> >>> Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') >> Yep, same here. >> >> Is there a fine manual somewhere on how to boot a 2.6.23 domU with Xen >> 3.1.x? > > Good to see that people are trying out the new Xen support in mainline! > > To boot under Xen you need to use a vmlinux / vmlinuz image. Were you guys > perhaps trying to use the bzImage? That won''t work (yet). > > The vmlinux that''s in the root of your kernel build tree ought to work. I > stripped and gziped mine to get a much, much smaller vmlinuz file and used it > to boot a Xen domain for the first time last night - worked fine.Could you attach your 2.6.23 domU .config file? -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson schrieb:>>> To boot under Xen you need to use a vmlinux / vmlinuz image. Were you >>> guys perhaps trying to use the bzImage? That won''t work (yet). >>> >>> The vmlinux that''s in the root of your kernel build tree ought to work. >>> I stripped and gziped mine to get a much, much smaller vmlinuz file and >>> used it to boot a Xen domain for the first time last night - worked fine. >> I tried vmlinux, but also, it didn''t work. >> >> It hanged at: >> >> # xm create -c somedomain >> Using config file "/etc/xen/somedomain". >> Started domain somedomain >> >> >> And it seems to wait there forever. > > It''s just not outputting to the console. > > In the domain config file add "console=/dev/hvc0" to the extra= line in order > to append this to the kernel command line. Then you ought to see the usual > boot output.I''m not sure. Even when I add this line, I don''t see anything in the console. Moreover - even if I wait a bit, I can''t ping that host. Also, with 2.6.18 domU kernel, without a valid initrd/ramdisk, the guest would just do a kernel panic, and the domain would be automatically destroyed. With 2.6.23 domU, I don''t see anything like this. -- Tomasz Chmielewski http://blog.wpkg.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I''m not sure. > Even when I add this line, I don''t see anything in the console. > > Moreover - even if I wait a bit, I can''t ping that host. > > Also, with 2.6.18 domU kernel, without a valid initrd/ramdisk, the guest > would just do a kernel panic, and the domain would be automatically > destroyed. > With 2.6.23 domU, I don''t see anything like this.OK, interesting... If you run xm li does it give you any insights? Is the CPU time used by the guest increasing? I''m just running some additional tests around 2.6.23 as part of another user''s bug reports. Hopefully this will provide some additional insights here... Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson schrieb:>> I''m not sure. >> Even when I add this line, I don''t see anything in the console. >> >> Moreover - even if I wait a bit, I can''t ping that host. >> >> Also, with 2.6.18 domU kernel, without a valid initrd/ramdisk, the guest >> would just do a kernel panic, and the domain would be automatically >> destroyed. >> With 2.6.23 domU, I don''t see anything like this. > > OK, interesting... > > If you run xm li does it give you any insights? Is the CPU time used by the > guest increasing? > > I''m just running some additional tests around 2.6.23 as part of another user''s > bug reports. Hopefully this will provide some additional insights here...The thing is alive, always in "r" state, never in "b" state. An alien in a dead body... :) # xm list | grep imap imap1 25 192 1 r----- 25.9 # xm list | grep imap imap1 25 192 1 r----- 28.0 # xm list | grep imap imap1 25 192 1 r----- 29.2 # xm list | grep imap imap1 25 192 1 r----- 31.2 # xm list | grep imap imap1 25 192 1 r----- 68.4 # xm list | grep imap imap1 25 192 1 r----- 130.4 -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > I''m just running some additional tests around 2.6.23 as part of another > > user''s bug reports. Hopefully this will provide some additional insights > > here... > > The thing is alive, always in "r" state, never in "b" state. An alien in > a dead body... :)Spooky... Best get the zombie survival kit ready just in case they awaken other domains you''ve destroyed to consume the kernels of the living :-O> # xm list | grep imap > imap1 25 192 1 r----- > 25.9 # xm list | grep imap > imap1 25 192 1 r----- > 28.0 # xm list | grep imap > imap1 25 192 1 r----- > 29.2 # xm list | grep imap > imap1 25 192 1 r----- > 31.2 # xm list | grep imap > imap1 25 192 1 r----- > 68.4 # xm list | grep imap > imap1 25 192 1 r----- > 130.4Out of interest, did you compile the guest kernel with SMP support? Another user was reporting that the boot process hung if he compiled without SMP... Worth noting, I guess, that if the domain had panicked not finding the root filesystem (but not succeeded in outputting to the console) then you''d see it eating CPU like this (mine does). Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson schrieb:>>> I''m just running some additional tests around 2.6.23 as part of another >>> user''s bug reports. Hopefully this will provide some additional insights >>> here... >> The thing is alive, always in "r" state, never in "b" state. An alien in >> a dead body... :) > > Spooky... Best get the zombie survival kit ready just in case they awaken > other domains you''ve destroyed to consume the kernels of the living :-O > >> # xm list | grep imap >> imap1 25 192 1 r----- >> 25.9 # xm list | grep imap >> imap1 25 192 1 r----- >> 28.0 # xm list | grep imap >> imap1 25 192 1 r----- >> 29.2 # xm list | grep imap >> imap1 25 192 1 r----- >> 31.2 # xm list | grep imap >> imap1 25 192 1 r----- >> 68.4 # xm list | grep imap >> imap1 25 192 1 r----- >> 130.4 > > Out of interest, did you compile the guest kernel with SMP support? Another > user was reporting that the boot process hung if he compiled without SMP...I built the first kernel with SMP support; the second one without SMP support - both behaved exactly the same. -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson wrote:> I''ve not seen a plan for the 2.6.24 merge, so I don''t know if any features are > being added or if work is going into other things (e.g. paravirt_ops for > x64). >There''s not a lot of new stuff for .24; I''m mostly interested in the arch/x86 stuff, and stability. Maybe balloon will appear.> From what Jeremy has told me before, live migration interacts badly with > pre-emptible kernel (a fact which the mainline folks weren''t too keen on, > which I presume is why it isn''t merged yet) but should be doable in the short > term if migration depends on !CONFIG_PREEMPT. I think there are plans for > how to support both together in future, if there''s sufficient motivation. >Yeah, I don''t think there''s any clean way to do direct pagetables, preempt and suspend-resume. I''ll probably add it as something depending on !PREEMPT. J _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi NicoP, Further to my previous mail, if you send me the image you''re trying to boot I can try it over here and see what happens. Cheers, Mark On Wednesday 10 October 2007, Nico Prenzel wrote:> Hello Zoltan, > > I do have the exactly same problem as you can see here: > http://lists.xensource.com/archives/html/xen-users/2007-10/msg00244.html > > If you solve the problem, please remember to post the solution here. > Pherhaps, Mark Williamson could help us to solve the problem. > > Regards, > > NicoP.-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tomasz Chmielewski schrieb:> I tried vmlinux, but also, it didn''t work. > > It hanged at: > > # xm create -c somedomain > Using config file "/etc/xen/somedomain". > Started domain somedomain > > > And it seems to wait there forever. > > > Normally, I would expect: > > # xm create -c somedomain > Using config file "/etc/xen/somedomain". > Started domain somedomain > Linux version 2.6.18-xen (root@....Same thing here, nothing happens. Usually you should at least hear the hard drive working even if there wouldn''t be any console output. 2.6.20-xen (from gentoo) is working just fine. Basic system configuration: - VIA C3-2 CPU (Nehemia) - Xen 3.1.0 - dom0 kernel: 2.6.20-xen (from gentoo) - domU kernel: I tried both 2.6.23 vanilla and 2.6.23-gentoo, with and without SMP support. - domU kernel .config: http://www.boppstrasse.de/config-2.6.23-gentoo `xm list` shows that the domU''s CPU time doesn''t increase if I compile it without local apic support, it''s stuck somewhere between 0.6 and 1.0 seconds. When I enable local apic, the CPU time does increase steadily. `xm dmesg` shows nothing when I boot the domU kernel. Can anybody send me a known to be working 2.6.23 kernel .config so I can try if it works on my system? Cheers, Michael _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael Heyse schrieb: This is a follow-up to a thread from October 2007.>> It hanged at: >> >> # xm create -c somedomain >> Using config file "/etc/xen/somedomain". >> Started domain somedomain >> >> >> And it seems to wait there forever. >> >> >> Normally, I would expect: >> >> # xm create -c somedomain >> Using config file "/etc/xen/somedomain". >> Started domain somedomain >> Linux version 2.6.18-xen (root@.... > > Same thing here, nothing happens. Usually you should at least hear the > hard drive working even if there wouldn''t be any console output. > 2.6.20-xen (from gentoo) is working just fine.I just tried to make an upstream 2.6.24.2 to work as a domU, but it fails the same way. As there are more people which have problem starting an upstream domU kernel with Xen, I begin to wonder if it''s actually possible to boot it? Could anyone post a *working* config for a 2.6.24.x domU kernel? More users asked for a .config from a kernel which boots, but one was never provided... -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, Sorry I''ve been slow in replying to this.> This is a follow-up to a thread from October 2007. > > >> It hanged at: > >> > >> # xm create -c somedomain > >> Using config file "/etc/xen/somedomain". > >> Started domain somedomain > >> > >> > >> And it seems to wait there forever.<snip>> > I just tried to make an upstream 2.6.24.2 to work as a domU, but it > fails the same way.Did you include "console=hvc0" in you extra= parameter? Otherwise you won''t get any boot output.> As there are more people which have problem starting an upstream domU > kernel with Xen, I begin to wonder if it''s actually possible to boot it? > > Could anyone post a *working* config for a 2.6.24.x domU kernel? More > users asked for a .config from a kernel which boots, but one was never > provided...I''ve just built and booted a 2.6.24 on Xen so I know it *can* be done. It does seem to be causing issues for people though. I''ve attached one but it''s not yet as stripped down as I''d like it to be. Once it''s as small as I can get it, I may post it online somewhere as an example. I''ve been writing a howto on Xen-enabled kernel.org here: http://wiki.xensource.com/xenwiki/Kernel.org_Linux_on_Xen Cheers, Mark -- Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users