Re: [Xen-users] Can not init netfront

[Nodir Kodirov <nodir.qodirov@xxxxxxxxx>]

After hearing about positive experience with Xen MiniOS on Debian (not
CentOS), I switched into Debian Jessie x86_64 with kernel 3.14.7.
Everything else remained the same. Bridge xenbr0 is up.

As Joost suggested I've added a disk to the configuration file. Now it
looks like following:
# cat minios.cfg
kernel = "mini-os.gz"
memory = 32
name = "Mini-OS"
builder = 'pvm'
vcpus = 1
vif = [ 'bridge=xenbr0' ]
root = '/dev/xvda1 ro'
disk = [ 'file:/home/domains/second_dom/disk.img,xvda1,w' ]
on_poweroff = 'destroy'
on_reboot   = 'destroy'
on_crash = 'destroy'
device_model_version = "qemu-xen"
device_model_override = "/usr/bin/qemu-system-x86_64"
bios = "seabios"

The last 3 lines were added after facing problem with qemu-dm
executable, which is described and solved at
http://forums.debian.net/viewtopic.php?f=17&t=108672

Then I created VM instance with "xl -vv create minios.cfg" which
generated following output:

Parsing config from minios.cfg
libxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement
candidate with 1 nodes, 4 cpus and 3463 KB free selected
domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 ro ",
features="(null)"
domainbuilder: detail: xc_dom_kernel_file: filename="mini-os.gz"
domainbuilder: detail: xc_dom_malloc_filemap    : 205 kB
domainbuilder: detail: xc_dom_malloc            : 2615 kB
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x335ec -> 0x28dea1
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.3, 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 multiboot-binary loader ...
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ...
domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ...
domainbuilder: detail: loader probe OK
xc: detail: elf_parse_binary: phdr: paddr=0x0 memsz=0x8e200
xc: detail: elf_parse_binary: memory: 0x0 -> 0x8e200
xc: detail: elf_xen_parse: __xen_guest:
"GUEST_OS=Mini-OS,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPERCALL_PAGE=0x2,LOADER=generic"
xc: detail: elf_xen_parse_guest_info: GUEST_OS="Mini-OS"
xc: detail: elf_xen_parse_guest_info: XEN_VER="xen-3.0"
xc: detail: elf_xen_parse_guest_info: VIRT_BASE="0x0"
xc: detail: elf_xen_parse_guest_info: ELF_PADDR_OFFSET="0x0"
xc: detail: elf_xen_parse_guest_info: HYPERCALL_PAGE="0x2"
xc: detail: elf_xen_parse_guest_info: LOADER="generic"
xc: detail: elf_xen_addr_calc_check: addresses:
xc: detail:     virt_base        = 0x0
xc: detail:     elf_paddr_offset = 0x0
xc: detail:     virt_offset      = 0x0
xc: detail:     virt_kstart      = 0x0
xc: detail:     virt_kend        = 0x8e200
xc: detail:     virt_entry       = 0x0
xc: detail:     p2m_base         = 0xffffffffffffffff
domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0x0 -> 0x8e200
domainbuilder: detail: xc_dom_mem_init: mem 32 MB, pages 0x2000 pages, 4k each
domainbuilder: detail: xc_dom_mem_init: 0x2000 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_build_image: called
domainbuilder: detail: xc_dom_alloc_segment:   kernel       : 0x0 ->
0x8f000  (pfn 0x0 + 0x8f pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x0+0x8f at 0x7f540b685000
xc: detail: elf_load_binary: phdr 0 at 0x7f540b685000 -> 0x7f540b6bc5a0
domainbuilder: detail: xc_dom_alloc_segment:   phys2mach    : 0x8f000
-> 0x9f000  (pfn 0x8f + 0x10 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x8f+0x10 at 0x7f540b675000
domainbuilder: detail: xc_dom_alloc_page   :   start info   : 0x9f000 (pfn 0x9f)
domainbuilder: detail: xc_dom_alloc_page   :   xenstore     : 0xa0000 (pfn 0xa0)
domainbuilder: detail: xc_dom_alloc_page   :   console      : 0xa1000 (pfn 0xa1)
domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48:
0x0000000000000000 -> 0x0000ffffffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39:
0x0000000000000000 -> 0x0000007fffffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30:
0x0000000000000000 -> 0x000000003fffffff, 1 table(s)
domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21:
0x0000000000000000 -> 0x00000000003fffff, 2 table(s)
domainbuilder: detail: xc_dom_alloc_segment:   page tables  : 0xa2000
-> 0xa7000  (pfn 0xa2 + 0x5 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0xa2+0x5 at 0x7f540b75a000
domainbuilder: detail: xc_dom_alloc_page   :   boot stack   : 0xa7000 (pfn 0xa7)
domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 0xa8000
domainbuilder: detail: xc_dom_build_image  : virt_pgtab_end : 0x400000
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 0x2000
domainbuilder: detail: clear_page: pfn 0xa1, mfn 0x111e55
domainbuilder: detail: clear_page: pfn 0xa0, mfn 0x111e56
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn
0x9f+0x1 at 0x7f540b761000
domainbuilder: detail: start_info_x86_64: called
domainbuilder: detail: setup_hypercall_page: vaddr=0x2000 pfn=0x2
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail:    allocated
domainbuilder: detail:       malloc             : 2686 kB
domainbuilder: detail:       anon mmap          : 0 bytes
domainbuilder: detail:    mapped
domainbuilder: detail:       file mmap          : 205 kB
domainbuilder: detail:       domU mmap          : 660 kB
domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xce720
domainbuilder: detail: shared_info_x86_64: called
domainbuilder: detail: vcpu_x86_64: called
domainbuilder: detail: vcpu_x86_64: cr3: pfn 0xa2 mfn 0x111e54
domainbuilder: detail: launch_vm: called, ctxt=0x7fff4ce78740
domainbuilder: detail: xc_dom_release: called
Daemon running with PID 8001

domU is reported as created, but "xl list" shows only dom0. There are
3 log files newly created at /var/log/xen as follows:

cat /var/log/xen/xl-Mini-OS.log
Waiting for domain Mini-OS (domid 11) to die [pid 8002]
Domain 11 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 11 needs to be cleaned up: destroying the domain
Done. Exiting now

cat /var/log/xen/qemu-dm-Mini-OS.log
qemu: terminating on signal 1 from pid 8002

cat /var/log/xen/xen-hotplug.log
-empty-

Now I don't know what is going wrong at all.

Any help is appreciated.

Nodir.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users