[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xen 4.6 & dom0pvh

  • To: xen-users@xxxxxxxxxxxxx
  • From: ÃliÃs TamÃs <et@xxxxxxx>
  • Date: Tue, 15 Dec 2015 10:56:22 +0100
  • Delivery-date: Tue, 15 Dec 2015 09:58:12 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>


2015-12-14 18:08 keltezÃssel, Roger Pau Monnà Ãrta:
> Hello,
> Please don't top post, it completely screws the conversation log.
> El 14/12/15 a les 17.08, ÃliÃs TamÃs ha escrit:
>> Hi.
>> Ok, I recompiled with xen-staging (4.7-unstable), and made several
>> outputs for you.
>> I attach them all - standard text files in a tar.xz archive: The server
>> is an ASUS P8P67 motherboard with an I5-3550 CPU. I also attach the
>> cpuinfo and the lspci -v output, hwinfo and acpidump in a tar.xz file to
>> ease bug hunting.
>> Xen debug files:
>> minicom-normalboot.cap: this is how the system normally boots to prompt
>> without the dom0pvh=1 parameter. This is more-or-less a fresh debian 8.2
>> system.
> You seem to be getting IOMMU errors while booting, which is certainly
> not expected:
> [...]
> (XEN) [VT-D]DMAR:[DMA Write] Request device [0000:09:00.1] fault addr
> 21e91b000, iommu reg = ffff82c000201000
> [...]
> And AFAICT 0x21e91b000 is inside a usable memory region according to the
> memory map. Anyway, it doesn't seem to stop Xen/Linux from working, so
> let's leave it apart.
>> minicom-debugenabled.cap: as above, but with the pvh kernel parameter.
>> minicom-wotmem.cap: as above, but the boot parameters of transactional
>> memory had been removed (I read somewhere that it can cause problems).
>> Interestingly, in this case I receive no crash dump, but a silent
>> complete reboot without a notice.
>> minicom-woextrabootparams.cap: as above, but I removed ALL extra boot
>> parameters that can influence startup (of course except the dom0pvh=1).
>> This startup has gone further then the Åprevious one, but seemes to me
>> rebooting due to the same issue (ACPI MEMORY RESET REG).
> Can you pick this one and add "iommu=debug sync_console" to the Xen
> command line? The reboot without any kind of message from Xen is
> certainly weird.

Debug log attached.

> Roger.
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users


ÃliÃs TamÃs
Thomas Elias

ETIT[nwpro] KFT, ÃgyvezetÅ-HÃlÃzatbiztonsÃgi specialista
ETIT[nwpro] Ltd, General Manager-Network security specialist

Tel. HU: +36/30-497-1626
Tel. DE: +49/160-651-8723
OpenPGP pubkey: http://etit.hu/doc/et-pub.asc

Okleveles mÃrnÃk-informatikus (MSC)
Master of Science in Information Technology (MSC)

Kapcsolat: http://etit.hu/index.php/hu/kapcsolat
Jogi nyilatkozat: http://etit.hu/disclaimer-email-hu.txt
Contact: http://etit.hu/index.php/en/contact
Disclaimer: http://etit.hu/disclaimer-email-en.txt

Attachment: minicom.cap
Description: application/vnd.tcpdump.pcap

Attachment: signature.asc
Description: OpenPGP digital signature

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.