On 3/7/17 9:44 PM, Konrad Rzeszutek Wilk wrote: > On Tue, Mar 07, 2017 at 12:39:04AM +0100, Daniel Kiper wrote: >> On Wed, Feb 22, 2017 at 09:04:17AM -0800, Doug Goldstein wrote: >> >> [...] >> >>> I'm currently at ELC and then on vacation so I don't have access to any >>> of the machines currently myself. However the machine I most use to test >>> is a NUC5i5MYHE and a NUC5i3MYHE if you want to ask around if someone >>> has one internally. But that's why I gave QEMU as an example. >>> >>> I was using qemu master from a few weeks ago. I'll have to find the >>> revision for you. But the command line I use is: >>> >>> -enable-kvm -M pc-q35-2.8 -device intel-iommu -cpu host -m 2048 -smp 2 >>> -drive if=pflash,format=raw,file=/tmp/tmp.EiR6ixmYzV -global >>> isa-debugcon.iobase=0x402 -debugcon file:/tmp/tmp.nuvEXUWfnA -monitor >>> stdio -chardev socket,host=127.0.0.1,port=25914,id=S0,server,nowait >>> -device isa-serial,chardev=S0 -device piix3-usb-uhci -device usb-tablet >>> -netdev id=net0,type=tap -device >>> virtio-net-pci,netdev=net0,mac=52:54:00:12:34:56 -boot order=n -device >>> qxl-vga -gdb tcp::14952 >> >> Sadly, my colleagues and I are not able to reproduce the problem on any of >> machines available for us (available on the market and some development >> stuff in our labs). I did tests with QEMU (I am not able to run it with >> "-device intel-iommu" on my machine; I have to investigate this). Everything >> works. Joao did some tests on Intel NUC D34010WYK second generation. >> Everything works. So, Konrad ordered Intel NUC NUC5i3MYHE for me. I am >> waiting for delivery. Doug, could you tell me what distro, Xen, etc. you >> have installed on that NUC? I would like to test same config as yours on >> this machine. > > I had a chat with Doug on IRC and: > - I had tested earlier on AMD, while he has only Intel boxes, > - He was wondering if this was an IOMMU issue. > > So to double-check that, I installed Ubuntu 16.10 on my X11SAE > SuperMicro, which has an Haswell E3-1245 v5 and with IOMMU enabled. > > I tested the 'origin/staging' xen.gz build with the upstream grub2 > (I just used the 'master' branch) first and also just booting xen.efi. > > Both worked fine.
Well if this was really the IOMMU issue then there's already a patch in staging which noops out part of the memory allocator from the first part of the series that was causing problems. > > Then I used v16 of Daniel's patches (this thread). They are also > now on git://xenbits.xen.org/people/konradwilk/xen.git mb2.v16 > also the same way - as xen.efi and then using grub.efi and booting it > (see below) > > All worked fine. <snip> > > konrad-Super-Server login: [ 188.181526] reboot: Restarting system > (XEN) Hardware Dom0 shutdown: rebooting machine > (XEN) APIC error on CPU0: 40(00) > > ... reboot. So as I've mentioned you have to run 'xl info' and look at nr_cpus to see the issue. <snip> > Starting Notify bootloader > tha[^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G[0;32m OK [0m] Started > Notify bootloader that boot was successful. > > Ubuntu 16.10 konrad-Super-Server hvc0 > > konrad-Super-Server login: > Still missing 'xl info'. -- Doug Goldstein
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
