intel / XenGT-Preview-kernel

Other
33 stars 14 forks source link

Vm won't start with vgt=1 i3-4130 #1

Open slis opened 10 years ago

slis commented 10 years ago

hello... i am looking to get xengt running but i cant start it... got this in dmesg

[ 1.376813] vGT error:(vgt_set_device_type:432) Unknown chip 0x41e [ 1.376912] i915: xen_start_vgt done [ 1.400181] Wrong vgt_if magic number

ktian1 commented 10 years ago

which platform are you using? XenGT only supports HSW formally now.

From: slis [mailto:notifications@github.com] Sent: Tuesday, September 09, 2014 2:02 PM To: 01org/XenGT-Preview-kernel Subject: [XenGT-Preview-kernel] Vm won't start with vgt=1 i3-4130 (#1)

hello... i am looking to get xengt running but i cant start it... got this in dmesg

[ 1.376813] vGT error:(vgt_set_device_type:432) Unknown chip 0x41e [ 1.376912] i915: xen_start_vgt done [ 1.400181] Wrong vgt_if magic number

— Reply to this email directly or view it on GitHubhttps://github.com/01org/XenGT-Preview-kernel/issues/1.

slis commented 9 years ago

what do u mean by HSW? i am using h81 and i3 4130... haswell?

in pdf guide it says only 4th gen intel processor is requirment?

i changed source devtable.c or smth to include my chip number... now it almost works...

i tried in ubuntu 12.04 and when i enable VGT=1 this happens.... but i cant get screen on output, only brief windows green loading bar / or 0x0000003B BSOD on SDL or VNC,.... nothing on native screen.

thx

here is dmesg:

33.223610] xenbr0: port 1(eth0) entered forwarding state [ 282.619289] tun: Universal TUN/TAP device driver, 1.6 [ 282.655421] tun: (C) 1999-2004 Max Krasnyansky maxk@qualcomm.com [ 282.697475] vGT info:(create_vgt_instance:118) vm_id=1, low_gm_sz=64MB, high_gm_sz=384MB, fence_sz=4, vgt_primary=1 [ 282.721123] vGT info:(create_vgt_instance:170) Virtual GTT size: 0x200000 [ 282.743658] VM1 Ring0 context_save_area is allocated at gm(f952000) [ 282.778035] VM1 Ring1 context_save_area is allocated at gm(f992000) [ 282.800173] VM1 Ring2 context_save_area is allocated at gm(f9d2000) [ 282.822101] VM1 Ring3 context_save_area is allocated at gm(fa12000) [ 282.843937] vGT info:(create_vgt_instance:206) aperture: [0xe7800000, 0xeb7fffff] guest [0xe7800000, 0xeb7fffff] va(0xffffc9000c900000) [ 282.866923] vGT info:(create_vgt_instance:217) GM: [0x7800000, 0xb7fffff], [0x28000000, 0x3fffffff], guest[0x7800000, 0xb7fffff], [0x28000000, 0x3fffffff] [ 282.891514] vGT info:(create_vgt_instance:254) filling VGT_PVINFO_PAGE for dom1: [ 282.891514] visable_gm_base=0x7800000, size=0x4000000 [ 282.891514] hidden_gm_base=0x28000000, size=0x18000000 [ 282.891514] fence_base=4, num=4 [ 282.984929] vGT info:(vgt_hvm_io_req_handler:787) Received a IOREQ w/o vcpu target [ 282.985197] vGT info:(vgt_emulation_thread:522) start kthread for VM1 [ 282.985260] vGT(1): create debugfs node: virtual_mmio_space [ 282.985308] vGT(1): create debugfs node: shadow_mmio_space [ 282.985360] vGT(1): create debugfs node: frame_buffer_format [ 282.985411] vGT(1): create debugfs node: frame_buffer_format [ 283.128871] vGT info:(vgt_hvm_io_req_handler:788) Possible a false request from event binding [ 283.192520] update_pipe_mapping: Enable. pport = 4, vport = 4 [ 283.236745] update_pipe_mapping: Enable. pport = 4, vport = 0 [ 283.260186] update_pipe_mapping: Enable. pport = 4, vport = 0 [ 283.283277] update_pipe_mapping: Enable. pport = 3, vport = 4 [ 283.305910] update_pipe_mapping: Enable. pport = 3, vport = 0 [ 283.328080] update_pipe_mapping: Enable. pport = 3, vport = 0 [ 283.943716] device vif1.0 entered promiscuous mode [ 284.230353] device vif1.0-emu entered promiscuous mode [ 284.260849] xenbr0: port 3(vif1.0-emu) entered forwarding state [ 284.283174] xenbr0: port 3(vif1.0-emu) entered forwarding state [ 284.329826] Programming bar 0x10 with 0xffffffff [ 284.356986] Programming bar 0x10 with 0xf0000004 [ 284.379187] Programming bar 0x18 with 0xffffffff [ 284.401130] Programming bar 0x18 with 0xe000000c [ 284.423020] Programming bar 0x20 with 0xffffffff [ 284.444673] Programming bar 0x20 with 0xf001 [ 284.478128] Programming bar 0x18 with 0xc000000c [ 284.499809] add_map: domid=1 gfn_s=0xc7800 mfn_s=0xe7800 nr_mfns=0x4000 [ 284.524832] Programming bar 0x10 with 0xd1000004 [ 284.549107] Programming bar 0x20 with 0xc201

thx

slis commented 9 years ago

last part [ 1727.559839] vGT: write to MSI capa(92) with val (0) [ 1728.734173] xenbr0: port 3(vif24.0-emu) entered forwarding state [ 2414.822403] xenbr0: port 3(vif24.0-emu) entered disabled state [ 2414.854661] device vif24.0-emu left promiscuous mode [ 2414.873658] xenbr0: port 3(vif24.0-emu) entered disabled state [ 2414.894069] xenbr0: port 2(vif24.0) entered disabled state [ 2414.912783] device vif24.0 left promiscuous mode [ 2414.931507] xenbr0: port 2(vif24.0) entered disabled state [ 2416.857062] prepare to destroy vgt (1) [ 2416.875703] check render ownership... [ 2416.894296] vgt instance has been removed from run queue [ 2416.913283] check display ownership... [ 2416.931620] release display/render ownership... done [ 2416.970585] vGT: vgt_release_instance done

here is first part http://www.heypasteit.com/clip/1J7R

ktian1 commented 9 years ago

yes, it’s Haswell the 4th processor.

Looks your box is not included in current device list, so adding your device ID is right way to go, but it also means not validated so some trouble may be caused by hardware difference. Better to find a platform with device ID in existing list.

I didn’t see below log in your full log in another mail, so not sure whether it has all the information there. By default a new VM is in the background after it’s created. So it may already boot but you didn’t note it. One way is to add a boot option “hvm_boot_foreground”, or use sysfs control interface to switch foreground/background VM. You can check setup guide for detail.

From: slis [mailto:notifications@github.com] Sent: Tuesday, September 09, 2014 11:13 PM To: 01org/XenGT-Preview-kernel Cc: Tian, Kevin Subject: Re: [XenGT-Preview-kernel] Vm won't start with vgt=1 i3-4130 (#1)

what do u mean by HSW? i am using h81 and i3 4130... haswell?

in pdf guide it says only 4th gen intel processor is requirment?

i changed source devicemap.c or smth to include my chip number... now it almost works...

i tried in ubuntu 12.04 and when i enable VGT=1 this happens.... but i cant get screen on output, only brief windows green loading bar on SDL or VNC,....

thx

here is dmesg:

33.223610] xenbr0: port 1(eth0) entered forwarding state [ 282.619289] tun: Universal TUN/TAP device driver, 1.6 [ 282.655421] tun: (C) 1999-2004 Max Krasnyansky maxk@qualcomm.commailto:maxk@qualcomm.com [ 282.697475] vGT info:(create_vgt_instance:118) vm_id=1, low_gm_sz=64MB, high_gm_sz=384MB, fence_sz=4, vgt_primary=1 [ 282.721123] vGT info:(create_vgt_instance:170) Virtual GTT size: 0x200000 [ 282.743658] VM1 Ring0 context_save_area is allocated at gm(f952000) [ 282.778035] VM1 Ring1 context_save_area is allocated at gm(f992000) [ 282.800173] VM1 Ring2 context_save_area is allocated at gm(f9d2000) [ 282.822101] VM1 Ring3 context_save_area is allocated at gm(fa12000) [ 282.843937] vGT info:(create_vgt_instance:206) aperture: [0xe7800000, 0xeb7fffff] guest [0xe7800000, 0xeb7fffff] va(0xffffc9000c900000) [ 282.866923] vGT info:(create_vgt_instance:217) GM: [0x7800000, 0xb7fffff], [0x28000000, 0x3fffffff], guest[0x7800000, 0xb7fffff], [0x28000000, 0x3fffffff] [ 282.891514] vGT info:(create_vgt_instance:254) filling VGT_PVINFO_PAGE for dom1: [ 282.891514] visable_gm_base=0x7800000, size=0x4000000 [ 282.891514] hidden_gm_base=0x28000000, size=0x18000000 [ 282.891514] fence_base=4, num=4 [ 282.984929] vGT info:(vgt_hvm_io_req_handler:787) Received a IOREQ w/o vcpu target [ 282.985197] vGT info:(vgt_emulation_thread:522) start kthread for VM1 [ 282.985260] vGT(1): create debugfs node: virtual_mmio_space [ 282.985308] vGT(1): create debugfs node: shadow_mmio_space [ 282.985360] vGT(1): create debugfs node: frame_buffer_format [ 282.985411] vGT(1): create debugfs node: frame_buffer_format [ 283.128871] vGT info:(vgt_hvm_io_req_handler:788) Possible a false request from event binding [ 283.192520] update_pipe_mapping: Enable. pport = 4, vport = 4 [ 283.236745] update_pipe_mapping: Enable. pport = 4, vport = 0 [ 283.260186] update_pipe_mapping: Enable. pport = 4, vport = 0 [ 283.283277] update_pipe_mapping: Enable. pport = 3, vport = 4 [ 283.305910] update_pipe_mapping: Enable. pport = 3, vport = 0 [ 283.328080] update_pipe_mapping: Enable. pport = 3, vport = 0 [ 283.943716] device vif1.0 entered promiscuous mode [ 284.230353] device vif1.0-emu entered promiscuous mode [ 284.260849] xenbr0: port 3(vif1.0-emu) entered forwarding state [ 284.283174] xenbr0: port 3(vif1.0-emu) entered forwarding state [ 284.329826] Programming bar 0x10 with 0xffffffff [ 284.356986] Programming bar 0x10 with 0xf0000004 [ 284.379187] Programming bar 0x18 with 0xffffffff [ 284.401130] Programming bar 0x18 with 0xe000000c [ 284.423020] Programming bar 0x20 with 0xffffffff [ 284.444673] Programming bar 0x20 with 0xf001 [ 284.478128] Programming bar 0x18 with 0xc000000c [ 284.499809] add_map: domid=1 gfn_s=0xc7800 mfn_s=0xe7800 nr_mfns=0x4000 [ 284.524832] Programming bar 0x10 with 0xd1000004 [ 284.549107] Programming bar 0x20 with 0xc201

thx

— Reply to this email directly or view it on GitHubhttps://github.com/01org/XenGT-Preview-kernel/issues/1#issuecomment-55075121.

slis commented 9 years ago

thx for response... i have been struggling for 2 days...yeah... i tried with “hvm_boot_foreground”... or sysfs .... it says display not ready. and in xl list it says that vm is blocked. same on 12.04 and 14.04

here is full dmesg... http://paste.ubuntu.com/8315157/ (starting vm is at the end of the log, its spammed with bridge goin up down)

to me this looks strange:

[ 3.230753] vGT warning:(vgt_emulate_read:351) vGT: untracked MMIO read: vm_id(0), offset=0x651b4,len=4, val=0x0!!! and [ 1552.475228] vGT: write to MSI capa(92) with val (0)

so it only depends on processor/gpu? not mbo? still can't belive that my i3 is not on the list lol

what processor do u suggest that works? i am looking for cheap desktop one... thx again.

slis commented 9 years ago

i just got 4770k and i got same problem... so it's me... or smth is missing in pdf

sorry to bother you

l1viathan commented 9 years ago

Hi Slis, did you copy vgt_mgr to your /usr/bin, as well as copy vgt.rules to /etc/udev/rules.d/ ?

Thanks, Jike

On 09/11/2014 06:07 PM, slis wrote:

i just got 4770k and i got same problem... so it's me... or smth is missing in pdf

sorry to bother you

— Reply to this email directly or view it on GitHub https://github.com/01org/XenGT-Preview-kernel/issues/1#issuecomment-55244306.

slis commented 9 years ago

Hi, i think i did... i installed it twice (12.04 and 14.04), now i go 3rd time with graphic stack on 12.04. i'll report back later when it's done. thx

btw there is error in pdf at building kernel last line "cp vgt_mgt /usr/bin" it should be "cp vgt_mgr /usr/bin"

and program "bc" is missing form kernel build deps

slis commented 9 years ago

WORKING now :) i think keymap was problem.. now i go do some tests :P

thank you

one more question... if i want use 2 vm's with 2 monitors, i should use indirect mode? and write monitor.conf for each vm with specific output port? is that even possible? using 2 vms at same time on 2 monitors?

slis commented 9 years ago

I can confirm it works only with i7 4770k, but NOT with i3 4130 (0x041e id added to devtable.h)...

With i3 there is no sdl bios screen, only green "safe mode" windows loading, then black screen with only windows arrow on vnc or bsod 0x00000003B.

Here is full dmesg from i3 http://paste.ubuntu.com/8320970/

but if i can't use 2 separate vm's on 2 monitors at same time, my setup is doomed anyway :)

l1viathan commented 9 years ago

Hi Slis:

"cp vgt_mgt /usr/bin" it should be "cp vgt_mgr /usr/bin"

Thanks for reporting this! I fixed that doc and update the repo :)