|
From: | Tian, Kevin |
Subject: | Re: [Qemu-devel] [XenGT][IGVT-g] Device model creation failed |
Date: | Tue, 5 Jan 2016 05:55:54 +0000 |
For below error: [ 5023.070461] vGT error:(g2h_gm_range:1660) VM(21): invalid address range: g_addr(0x1000), size(0x1000) Likely you didn’t use a XenGT-aware i915 driver inside VM, which is required e.g. to handle address space ballooning. A simple way is to copy same
Dom0 kernel/initrd/modules into guest image. Thanks Kevin From: Oleksii Kurochko [mailto:address@hidden
Hello. I've tried byt_experimental branch and got some another result. With vgt=1 it failed with some time and got next log: [ 4859.380332] vGT info:(create_vgt_instance:118) vm_id=21, low_gm_sz=128MB, high_gm_sz=384MB, fence_sz=4, vgt_primary=1 Create in next way: sudo xl -vvv create ubuntu.hvm Is it known issue? With best regards, Oleksii On Thu, Dec 31, 2015 at 2:56 AM, Tian, Kevin <address@hidden> wrote: What does Qemu log tell you about below error? libxl: error: libxl_dm.c:1531:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3)
In the meantime, it’d be helpful if you can capture serial console output. If error
comes from XenGT driver, there should be some useful information. btw, looks this VTC-1010 is based Baytrail. Please be noted that XenGT formally supports
only Core based system. Atom SoC is not the target. We do have a BYT experimental porting (‘byt-experiment’ branch) on github, which is based on old code and not maintained anymore. You may want to try that branch instead. Thanks Kevin From: Oleksii
Kurochko [mailto:address@hidden]
Hello! We are going to use XenGT on Intel Atom based board(VTC-1010, with 4GB RAM). For this purpose we use next repos: dom0 (ubuntu linux, 1024MB or 2048MB ) -
https://github.com/01org/Igvtg-kernel domU (android-x86, rest memory excluding xen heap, xen, about 1.7GB RAM ) - same kernel, with some config changes Guest domain are going to be started in HVM mode. We follow iGVT-g setup guide (https://github.com/01org/Igvtg-kernel/blob/2015q3-3.18.0/iGVT-g_Setup_Guide.txt)
and successfully setup dom0 with iGVT. But, when we are going to start domU (with enabled vgt=1 switch) domain creation failed with follow log: address@hidden:~$ sudo xl -vvv create -c ./a.cfg
Parsing config from ./a.cfg
WARNING: specifying "tsc_mode" as an integer is deprecated. Please use the named parameter variant. e.g. tsc_mode="default"
WARNING: you seem to be using "kernel" directive to override HVM guest firmware. Ignore that. Use "firmware_override" instead if you really want a non-default firmware
libxl: debug: libxl_create.c:1501:do_domain_create: ao 0x14c3190: create: how=(nil) callback=(nil) poller=0x14c31f0
libxl: debug: libxl_create.c:907:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:323:libxl__bootloader_run: not a PV domain, skipping bootloader
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x14b97c0: deregister unregistered
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0xc9524
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x1c9524
xc: detail: VIRTUAL MEMORY ARRANGEMENT:
xc: detail: Loader: 0000000000100000->00000000001c9524
xc: detail: Modules: 0000000000000000->0000000000000000
xc: detail: TOTAL: 0000000000000000->000000003f800000
xc: detail: ENTRY: 0000000000100000
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail: 4KB PAGES: 0x0000000000000200
xc: detail: 2MB PAGES: 0x00000000000001fb
xc: detail: 1GB PAGES: 0x0000000000000000
xc: detail: elf_load_binary: phdr 0 at 0x7f1c9464c000 -> 0x7f1c9470c391
libxl: debug: libxl_dm.c:1462:libxl__spawn_local_dm: Spawning device-model /usr/lib/xen/bin/qemu-system-i386 with arguments:
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: /usr/lib/xen/bin/qemu-system-i386
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -xen-domid
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: 1
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -chardev
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-1,server,nowait
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -mon
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: chardev=libxl-cmd,mode=control
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -nodefaults
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -name
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: vgtHVMDomain
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -sdl
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -k
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: en-us
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -serial
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: pty
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -vga
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: xengt
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -vgt_low_gm_sz
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: 128
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -vgt_high_gm_sz
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: 384
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -vgt_fence_sz
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: 4
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -boot
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: order=cda
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -usb
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -usbdevice
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: tablet
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -net
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: none
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -machine
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: xenfv
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: -m
libxl: debug: libxl_dm.c:1464:libxl__spawn_local_dm: 1016
libxl: debug: libxl_event.c:577:libxl__ev_xswatch_register: watch w=0x14b9a20 wpath=/local/domain/0/device-model/1/state token=3/0: register slotnum=3
libxl: debug: libxl_create.c:1517:do_domain_create: ao 0x14c3190: inprogress: poller=0x14c31f0, flags=i
libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x14b9a20 wpath=/local/domain/0/device-model/1/state token=3/0: event epath=/local/domain/0/device-model/1/state
libxl: debug: libxl_event.c:615:libxl__ev_xswatch_deregister: watch w=0x14b9a20 wpath=/local/domain/0/device-model/1/state token=3/0: deregister slotnum=3
libxl: error: libxl_dm.c:1531:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1319:domcreate_devmodel_started: device model did not start: -3
libxl: error: libxl_dm.c:1635:kill_device_model: Device Model already exited
libxl: debug: libxl_event.c:629:libxl__ev_xswatch_deregister: watch w=0x14bd010: deregister unregistered
libxl: debug: libxl_event.c:1765:libxl__ao_complete: ao 0x14c3190: complete, rc=-3
libxl: debug: libxl_event.c:1737:libxl__ao__destroy: ao 0x14c3190: destroy
xc: debug: hypercall buffer: total allocations:949 total releases:949
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:936 misses:4 toobig:9
Without this flag - are all ok, domain created and running normally. Do you have any ideas about this issue? Thank you.
Oleksii Kurochko | Embedded Dev
Oleksii Kurochko | Embedded Dev |
[Prev in Thread] | Current Thread | [Next in Thread] |