<div dir="ltr"><div dir="ltr">I try rombar=off on Ubuntu 18.04, out final choice of host os.</div><div dir="ltr">The instance is paused after virsh create, and qemu log shows kvm error:<br><div><br></div><div>KVM internal error. Suberror: 1</div><div>emulation failure</div><div>RAX=0000000000000001 RBX=ffffc40049027780 RCX=ffffc40049027780 RDX=fffff805276b1ad0</div><div>RSI=fffff8005c9ffbc0 RDI=fffff8005c9f9180 RBP=fffff8005ea39600 RSP=fffff8005ea48f10</div><div>R8 =ffffc40049027780 R9 =ffffc40049027760 R10=0000000000000002 R11=0000000000000000</div><div>R12=0000000000fa5680 R13=00000000ffffffff R14=ffffc400491b8180 R15=fffff8005cc83000</div><div>RIP=fffff805276b1af5 RFL=00010202 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0</div><div>ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA]</div><div>CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA]</div><div>SS =0018 0000000000000000 00000000 00409300 DPL=0 DS [-WA]</div><div>DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA]</div><div>FS =0053 0000000000000000 00003c00 0040f300 DPL=3 DS [-WA]</div><div>GS =002b fffff8005c9f9000 ffffffff 00c0f300 DPL=3 DS [-WA]</div><div>LDT=0000 0000000000000000 ffffffff 00c00000</div><div>TR =0040 fffff8005ea2f000 00000067 00008b00 DPL=0 TSS64-busy</div><div>GDT= fffff8005ea30fb0 00000057</div><div>IDT= fffff8005ea2e000 00000fff</div><div>CR0=80050031 CR2=ffffad04eb0c5000 CR3=00000000001aa000 CR4=001506f8</div><div>DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000</div><div>DR6=00000000ffff0ff0 DR7=0000000000000400</div><div>EFER=0000000000000d01</div><div>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 </div><div><br></div><div>No rom file defined in the xml, What VBIOS rom will be choosed by qemu when rombar is set to off? </div><div><br></div><div><br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr">Acewind <<a href="mailto:acewind@gmail.com">acewind@gmail.com</a>> 于2018年10月15日周一下午3:30写道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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 ...</div><br><div class="gmail_quote"><div dir="ltr">Acewind <<a href="mailto:acewind@gmail.com" target="_blank">acewind@gmail.com</a>> 于2018年10月13日周六下午10:46写道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks! I will try other VBIOS version available. </div><br><div class="gmail_quote"><div dir="ltr">Alex Williamson <<a href="mailto:alex.williamson@redhat.com" target="_blank">alex.williamson@redhat.com</a>> 于2018年10月13日周六上午7:59写道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sat, 13 Oct 2018 07:24:14 +0800<br> Acewind <<a href="mailto:acewind@gmail.com" target="_blank">acewind@gmail.com</a>> wrote:<br> <br> > If I leave vnc graphic in libvirt xml, and set target address of IGD<br> > hostdev to another dbsf (not 0000:0:02.0)，win 10 guest can work.<br> > Then I connect into win10 guest with vnc viewer, Intel graphic device can<br> > be seen ok and I can install driver for it.<br> <br> If the IGD is not at 0000:00:02.0 in the guest then it's not running in<br> legacy mode, which might be fine for you device, though Intel has kind<br> of abandoned the idea of Legacy vs UPT mode. UPT mode was originally<br> meant to run only as a secondary display to an emulated graphics, so<br> you probably wouldn't get boot graphics on a physical display, if<br> that's what you're after. Thanks,<br> <br> Alex<br> </blockquote></div> </blockquote></div> </blockquote></div>