From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xen.org
Subject: Re: pci passthrough kills qemu-xen
Date: Wed, 27 Jul 2016 21:07:29 -0400 [thread overview]
Message-ID: <20160728010729.GC2861@char.us.oracle.com> (raw)
In-Reply-To: <20160725095640.GA9832@aepfle.de>
On Mon, Jul 25, 2016 at 11:56:40AM +0200, Olaf Hering wrote:
> I'm trying to assing a PCIe network card to a HVM guest on an Dell
> Optiplex 980. This works with qemu-xen-traditional, but fails with
> qemu-xen. I tried staging-4.4 and staging-4.7, both with xenlinux based
> SLE12 dom0 kernel and with plain pvops 4.6.4 dom0 kernel.
>
> First I ran "xl pci-assignable-add 02:00.0", then xl create.
>
> Any idea whats wrong on this host?
..snip..
> name='fv-x64-tw-clean'
> uuid='37c8ce56-7ad3-41ea-bff1-a3df282bde0a'
> memory=1024
> vcpus=2
> disk=[
> 'file:/vm_images/xen_images/fv-x64-tw-clean/vdisk-fv-x64-tw-clean-disk0.raw,hda,w',
> ]
> vif=[ 'mac=00:08:15:41:00:00,bridge=br0', ]
> vfb=[ 'type=vnc,vncunused=1,keymap=de', ]
> keymap="de"
> serial="pty"
> builder="hvm"
> pci=[ '02:00.0', ]
> device_model_override="/vm_images/xen_images/bug989250/dm.sh"
Why that over-write? Does it call the right qemu-binary? Does that binary
construct an /var/log/xen/qemu.. something?
Why not just:
bios="seabios"
Anhyow I also see:
> Xen 4.7.20160704T103633.a492556-1.xen47
> (XEN) Xen version 4.7.20160704T103633.a492556-1.xen47 (abuild@) (gcc (SUSE Linux) 4.8.5) debug=n Mon Jul 4 12:36:33 UTC 2016
Could you recompile it with debug=y?
.. snip..
> (XEN) HVM1 save: CPU
> (XEN) HVM1 save: PIC
> (XEN) HVM1 save: IOAPIC
> (XEN) HVM1 save: LAPIC
> (XEN) HVM1 save: LAPIC_REGS
> (XEN) HVM1 save: PCI_IRQ
> (XEN) HVM1 save: ISA_IRQ
> (XEN) HVM1 save: PCI_LINK
> (XEN) HVM1 save: PIT
> (XEN) HVM1 save: RTC
> (XEN) HVM1 save: HPET
> (XEN) HVM1 save: PMTIMER
> (XEN) HVM1 save: MTRR
> (XEN) HVM1 save: VIRIDIAN_DOMAIN
> (XEN) HVM1 save: CPU_XSAVE
> (XEN) HVM1 save: VIRIDIAN_VCPU
> (XEN) HVM1 save: VMCE_VCPU
> (XEN) HVM1 save: TSC_ADJUST
> (XEN) HVM1 restore: CPU 0
> (XEN) HVM2 save: CPU
> (XEN) HVM2 save: PIC
> (XEN) HVM2 save: IOAPIC
> (XEN) HVM2 save: LAPIC
> (XEN) HVM2 save: LAPIC_REGS
> (XEN) HVM2 save: PCI_IRQ
> (XEN) HVM2 save: ISA_IRQ
> (XEN) HVM2 save: PCI_LINK
> (XEN) HVM2 save: PIT
> (XEN) HVM2 save: RTC
> (XEN) HVM2 save: HPET
> (XEN) HVM2 save: PMTIMER
> (XEN) HVM2 save: MTRR
> (XEN) HVM2 save: VIRIDIAN_DOMAIN
> (XEN) HVM2 save: CPU_XSAVE
> (XEN) HVM2 save: VIRIDIAN_VCPU
> (XEN) HVM2 save: VMCE_VCPU
> (XEN) HVM2 save: TSC_ADJUST
> (XEN) HVM2 restore: CPU 0
.. Huh? Where is hvmloader?
Is it even being loaded?
May have a bit more help if you compile it with debug=y and we can
see where hvmloader gets stuck.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-28 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 9:56 pci passthrough kills qemu-xen Olaf Hering
2016-07-28 1:07 ` Konrad Rzeszutek Wilk [this message]
2016-07-28 6:15 ` Olaf Hering
2016-08-08 14:33 ` Olaf Hering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160728010729.GC2861@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.