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/module
Hello.
I tried to rebuild xen and qemu-xen (again *using patches from
byt_experimental branch*) and seems that now is going to show bios messages
and tried to start ubuntu, but when it starts it is very lagging.
I will create separate thread for discussing problem of ui lagging.
Thanks for help.
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
> [ 4859.389889] vGT info:(create_vgt_instance:
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 informat
