On Mon, 2017-06-26 at 15:06 +0200, Andrew Jones wrote: > > Cool, I'll have a look as well and will document my complete > > environment, then hopefully we can diff with yours and see where this > > ISA thing shows up. > > It's likely a pci-serial vs. isa-serial device getting created. Something > like > > -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \ > -chardev stdio,logfile=logfile,id=chardev0,logappend=off \ > -device pci-serial,chardev=chardev0,bus=pci.3,addr=0x0 > > works for me, but only with upstream (not RHEL) qemu, and when adding > console=ttyS0 to the guest kernel command line. That's using QEMU directly though, right? Because the default for libvirt is to use isa-serial and you would have to tell it explicitly to use pci-serial instead, with <serial type='pty'> <target type='pci-serial' port='0'/> </serial> My point is that you or Christoffer having configured your QEMU binary differently shouldn't be enough to affect the command line generated by libvirt. -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
