Не стартует Xen DomU

Всем привет

# uname -a
Linux localhost 3.0.6-gentoo #4 SMP Sun Jan 1 04:25:00 Local time zone must be set--see zic m x86_64 Intel® Xeon® CPU E31270 @ 3.40GHz GenuineIntel GNU/Linux

собственно генту.

# xl list
Name ID Mem VCPUs State Time(s)
Domain-0 0 3045 8 r----- 1060.0

Как видно Xen работает.

DomU .config:
# cat /usr/src/linux/.config | grep XEN
# CONFIG_XEN is not set
# CONFIG_XEN_PRIVILEGED_GUEST is not set

В DomU выключен Dom0

# cat /xen/gentoo.vm
kernel = "/xen/gentoo-3.0.6"
memory = 1024
name = «gentoo»
disk = ['file:/xen/disks/gentoo-root.img,sda1,w']
root = "/dev/sda1 ro"
vcpus = 2

Типовой конфиг…

# xl create gentoo.vm
Parsing config file gentoo.vm
xc: error: elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images: Invalid kernel
libxl: error: libxl_dom.c:196:libxl__build_pv xc_dom_parse_image failed: Success
cannot (re-)build domain: -3

Собственно ошибка. Подскажите что ему не нравится в моем ядре?
  • Вопрос задан
  • 3439 просмотров
Пригласить эксперта
Ответы на вопрос 2
BuriK666
@BuriK666
Компьютерный псих
В ядре /xen/gentoo-3.0.6 включен CONFIG_XEN_PRIVILEGED_GUEST?
Ответ написан
@Breaker Автор вопроса
на текущий момент всё останавливается на:

# xl -v create /xen/gentoo.vm
Parsing config file /xen/gentoo.vm
domainbuilder: detail: xc_dom_allocate: cmdline=«root=/dev/xvda1 ro xencons=tty», features="(null)"
domainbuilder: detail: xc_dom_kernel_file: filename="/xen/gentoo-3.1.6"
domainbuilder: detail: xc_dom_malloc_filemap: 4636 kB
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.1, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
domainbuilder: detail: xc_dom_parse_image: called
domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader…
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader…
domainbuilder: detail: xc_dom_malloc: 17798 kB
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x47f057 -> 0x11618d8
domainbuilder: detail: loader probe OK
xc: detail: elf_parse_binary: phdr: paddr=0x1000000 memsz=0xa0d000
xc: detail: elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xae0e0
xc: detail: elf_parse_binary: phdr: paddr=0x1caf000 memsz=0x13380
xc: detail: elf_parse_binary: phdr: paddr=0x1cc3000 memsz=0x316000
xc: detail: elf_parse_binary: memory: 0x1000000 -> 0x1fd9000
xc: detail: elf_xen_parse_note: GUEST_OS = «linux»
xc: detail: elf_xen_parse_note: GUEST_VERSION = «2.6»
xc: detail: elf_xen_parse_note: XEN_VERSION = «xen-3.0»
xc: detail: elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
xc: detail: elf_xen_parse_note: ENTRY = 0xffffffff81cc3200
xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
xc: detail: elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
xc: detail: elf_xen_parse_note: PAE_MODE = «yes»
xc: detail: elf_xen_parse_note: LOADER = «generic»
xc: detail: elf_xen_parse_note: unknown xen elf note (0xd)
xc: detail: elf_xen_parse_note: SUSPEND_CANCEL = 0x1
xc: detail: elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0x0
xc: detail: elf_xen_addr_calc_check: addresses:
xc: detail: virt_base = 0xffffffff80000000
xc: detail: elf_paddr_offset = 0x0
xc: detail: virt_offset = 0xffffffff80000000
xc: detail: virt_kstart = 0xffffffff81000000
xc: detail: virt_kend = 0xffffffff81fd9000
xc: detail: virt_entry = 0xffffffff81cc3200
xc: detail: p2m_base = 0xffffffffffffffff
domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0xffffffff81000000 -> 0xffffffff81fd9000
domainbuilder: detail: xc_dom_mem_init: mem 1024 MB, pages 0x40000 pages, 4k each
domainbuilder: detail: xc_dom_mem_init: 0x40000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64
domainbuilder: detail: xc_dom_malloc: 2048 kB
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment: kernel: 0xffffffff81000000 -> 0xffffffff81fd9000 (pfn 0x1000 + 0xfd9 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1000+0xfd9 at 0x7f97d55e8000
xc: detail: elf_load_binary: phdr 0 at 0x0x7f97d55e8000 -> 0x0x7f97d5ff5000
xc: detail: elf_load_binary: phdr 1 at 0x0x7f97d61e8000 -> 0x0x7f97d62960e0
xc: detail: elf_load_binary: phdr 2 at 0x0x7f97d6297000 -> 0x0x7f97d62aa380
xc: detail: elf_load_binary: phdr 3 at 0x0x7f97d62ab000 -> 0x0x7f97d6349000
domainbuilder: detail: xc_dom_alloc_segment: phys2mach: 0xffffffff81fd9000 -> 0xffffffff821d9000 (pfn 0x1fd9 + 0x200 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1fd9+0x200 at 0x7f97d53e8000
domainbuilder: detail: xc_dom_alloc_page: start info: 0xffffffff821d9000 (pfn 0x21d9)
domainbuilder: detail: xc_dom_alloc_page: xenstore: 0xffffffff821da000 (pfn 0x21da)
domainbuilder: detail: xc_dom_alloc_page: console: 0xffffffff821db000 (pfn 0x21db)
domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 0xffff000000000000 -> 0xffffffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 0xffffff8000000000 -> 0xffffffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0xffffffff80000000 -> 0xffffffffbfffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0xffffffff80000000 -> 0xffffffff823fffff, 18 table(s)
domainbuilder: detail: xc_dom_alloc_segment: page tables: 0xffffffff821dc000 -> 0xffffffff821f1000 (pfn 0x21dc + 0x15 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x21dc+0x15 at 0x7f97d9e30000
domainbuilder: detail: xc_dom_alloc_page: boot stack: 0xffffffff821f1000 (pfn 0x21f1)
domainbuilder: detail: xc_dom_build_image: virt_alloc_end: 0xffffffff821f2000
domainbuilder: detail: xc_dom_build_image: virt_pgtab_end: 0xffffffff82400000
domainbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: arch_setup_bootearly: doing nothing
domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches
domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32
domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p
domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64
domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x40000
domainbuilder: detail: clear_page: pfn 0x21db, mfn 0x1ca405
domainbuilder: detail: clear_page: pfn 0x21da, mfn 0x1ca406
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x21d9+0x1 at 0x7f97d9e2f000
domainbuilder: detail: start_info_x86_64: called
domainbuilder: detail: setup_hypercall_page: vaddr=0xffffffff81001000 pfn=0x1001
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail: allocated
domainbuilder: detail: malloc: 19956 kB
domainbuilder: detail: anon mmap: 0 bytes
domainbuilder: detail: mapped
domainbuilder: detail: file mmap: 4636 kB
domainbuilder: detail: domU mmap: 18364 kB
domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xef475
domainbuilder: detail: shared_info_x86_64: called
domainbuilder: detail: vcpu_x86_64: called
domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x21dc mfn 0x1ca404
domainbuilder: detail: launch_vm: called, ctxt=0x7fff6598dbd0
domainbuilder: detail: xc_dom_release: called
Ответ написан
Комментировать
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы