I try rombar=off on Ubuntu 18.04, out final choice of host os. The instance is paused after virsh create, and qemu log shows kvm error:
KVM internal error. Suberror: 1 emulation failure RAX=0000000000000001 RBX=ffffc40049027780 RCX=ffffc40049027780 RDX=fffff805276b1ad0 RSI=fffff8005c9ffbc0 RDI=fffff8005c9f9180 RBP=fffff8005ea39600 RSP=fffff8005ea48f10 R8 =ffffc40049027780 R9 =ffffc40049027760 R10=0000000000000002 R11=0000000000000000 R12=0000000000fa5680 R13=00000000ffffffff R14=ffffc400491b8180 R15=fffff8005cc83000 RIP=fffff805276b1af5 RFL=00010202 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 00000000 00409300 DPL=0 DS [-WA] DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] FS =0053 0000000000000000 00003c00 0040f300 DPL=3 DS [-WA] GS =002b fffff8005c9f9000 ffffffff 00c0f300 DPL=3 DS [-WA] LDT=0000 0000000000000000 ffffffff 00c00000 TR =0040 fffff8005ea2f000 00000067 00008b00 DPL=0 TSS64-busy GDT= fffff8005ea30fb0 00000057 IDT= fffff8005ea2e000 00000fff CR0=80050031 CR2=ffffad04eb0c5000 CR3=00000000001aa000 CR4=001506f8 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=f8 01 74 1c 8b 41 04 85 c0 74 0d 0f 1f 40 00 f3 90 8b 41 04 <85> c0 75 f7 33 c0 48 83 c4 20 5b c3 48 8b 41 08 48 8b 51 18 48 8b 49 10 ff 15 fd ab 02 00 No rom file defined in the xml, What VBIOS rom will be choosed by qemu when rombar is set to off? Acewind <[email protected]> 于2018年10月15日周一 下午3:30写道： > I add <rom bar=off/> in hostdev secion of the libvirt xml, and screen is > ok after virsh create, but I don't known why ... > > Acewind <[email protected]> 于2018年10月13日周六 下午10:46写道： > >> Thanks! I will try other VBIOS version available. >> >> Alex Williamson <[email protected]> 于2018年10月13日周六 上午7:59写道： >> >>> On Sat, 13 Oct 2018 07:24:14 +0800 >>> Acewind <[email protected]> wrote: >>> >>> > If I leave vnc graphic in libvirt xml, and set target address of IGD >>> > hostdev to another dbsf (not 0000:0:02.0)，win 10 guest can work. >>> > Then I connect into win10 guest with vnc viewer, Intel graphic device >>> can >>> > be seen ok and I can install driver for it. >>> >>> If the IGD is not at 0000:00:02.0 in the guest then it's not running in >>> legacy mode, which might be fine for you device, though Intel has kind >>> of abandoned the idea of Legacy vs UPT mode. UPT mode was originally >>> meant to run only as a secondary display to an emulated graphics, so >>> you probably wouldn't get boot graphics on a physical display, if >>> that's what you're after. Thanks, >>> >>> Alex >>> >>
_______________________________________________ vfio-users mailing list [email protected] https://www.redhat.com/mailman/listinfo/vfio-users
