From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: Kouya Shimura <kouya@jp.fujitsu.com>
Cc: Keir Fraser <keir.fraser@eu.citrix.com>,
"Huang2, Wei" <Wei.Huang2@amd.com>,
takebe_akio@jp.fujitsu.com,
xen-devel <xen-devel@lists.xensource.com>,
Yoshisato YANAGISAWA <yanagisawa.yoshisato@lab.ntt.co.jp>
Subject: Re: Could not run HVM domain on the latest xen-unstable.hgand Barcelona.
Date: Wed, 11 Mar 2009 14:02:12 +0900 [thread overview]
Message-ID: <49B745D4.1090004@lab.ntt.co.jp> (raw)
In-Reply-To: <7ksklku3o2.fsf@pingu.sky.yk.fujitsu.co.jp>
Hi,
Thanks for handling this issue.
I tried your patch and got the following messages.
> If the guest dies with the following serial console message, 32bit
> gateway code is correct. otherwise, the guest hanging up means PMM is
> innocent.
> ==========================================================================
> (XEN) io.c:199:d1 MMIO emulation failed @ 0008:deadbeaf: db e6 1c 80 8c 82
> (XEN) hvm.c:810:d1 Triple fault on VCPU0 - invoking HVM system reset.
> ==========================================================================
(XEN) HVM1: ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) HVM1: IDE time out
(XEN) HVM1:
(XEN) io.c:199:d1 MMIO emulation failed @ 0008:deadbeaf: 00 00 00 00 84 be
(XEN) hvm.c:810:d1 Triple fault on VCPU0 - invoking HVM system reset.
> If you get the above message, please revert only 32bitgateway.c and
> try again. You can get debug messages of PMM.
I reverted 32bitgateway.c part, and got the following message on the console.
(XEN) HVM1: PMM Alloc length=20000 handle=ffffffff flags=6 ret=200000
Let me know if I was doing wrong.
Hope this help.
Thanks,
Yoshi
>
> Thanks,
> Kouya
>
> Huang2, Wei writes:
>> We saw this problem recently. I traced it down to PMM patch submitted by
>> Kouya and Akio (changeset 19077).
>>
>> To fix this problem temporarily, add mode=e1000 to your vif option.
>> vif = [ 'type=ioemu, bridge=xenbr0, model=e1000']
>>
>>
>> Regards,
>>
>> -Wei
>>
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xensource.com
>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Yoshisato
>> YANAGISAWA
>> Sent: Tuesday, March 10, 2009 3:17 AM
>> To: xen-devel
>> Subject: [Xen-devel] Could not run HVM domain on the latest
>> xen-unstable.hgand Barcelona.
>>
>>
>> Hi all,
>>
>> Does anybody have tested the latest xen-unstable.hg with an HVM domain
>> on AMD Barcelona Opteron?
>> I cloned xen-unstable.hg today (2009-03-10 JST), made config file for
>> booting an OS image from CD-ROM, and tried to run an HVM domain.
>> However, it stops running while booting.
>>
>> According to the vnc, the virtual machine displayed following message:
>> (snip)
>> | Bochs BIOS - build: 06/23/99
>> | $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
>> | Options: apmbios pcibios eltorito PMM
>> |
>> | ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
>> |
>> | gPXE (http://etherboot.org) - 00:04.0 C900 PCI2.10 INT19 PMM0020_
>>
>> According to the serial console, I also saw following message:
>> (XEN) HVM1: HVM Loader
>> (XEN) HVM1: Detected Xen v3.4-unstable
>> (XEN) HVM1: CPU speed is 2300 MHz
>> (XEN) irq.c:235: Dom1 PCI link 0 changed 0 -> 5
>> (XEN) HVM1: PCI-ISA link 0 routed to IRQ5
>> (XEN) irq.c:235: Dom1 PCI link 1 changed 0 -> 10
>> (XEN) HVM1: PCI-ISA link 1 routed to IRQ10
>> (XEN) irq.c:235: Dom1 PCI link 2 changed 0 -> 11
>> (XEN) HVM1: PCI-ISA link 2 routed to IRQ11
>> (XEN) irq.c:235: Dom1 PCI link 3 changed 0 -> 5
>> (XEN) HVM1: PCI-ISA link 3 routed to IRQ5
>> (XEN) HVM1: pci dev 01:3 INTA->IRQ10
>> (XEN) HVM1: pci dev 03:0 INTA->IRQ5
>> (XEN) HVM1: pci dev 04:0 INTA->IRQ5
>> (XEN) HVM1: pci dev 02:0 bar 10 size 02000000: f0000008
>> (XEN) HVM1: pci dev 03:0 bar 14 size 01000000: f2000008
>> (XEN) HVM1: pci dev 02:0 bar 14 size 00001000: f3000000
>> (XEN) HVM1: pci dev 03:0 bar 10 size 00000100: 0000c001
>> (XEN) HVM1: pci dev 04:0 bar 10 size 00000100: 0000c101
>> (XEN) HVM1: pci dev 04:0 bar 14 size 00000100: f3001000
>> (XEN) HVM1: pci dev 01:1 bar 20 size 00000010: 0000c201
>> (XEN) HVM1: Multiprocessor initialisation:
>> (XEN) HVM1: - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8]
>> ... don.
>> (XEN) HVM1: Testing HVM environment:
>> (XEN) HVM1: - REP INSB across page boundaries ... passed
>> (XEN) HVM1: Passed 1/1 tests
>> (XEN) HVM1: Writing SMBIOS tables ...
>> (XEN) HVM1: Loading ROMBIOS ...
>> (XEN) HVM1: 9628 bytes of ROMBIOS high-memory extensions:
>> (XEN) HVM1: Relocating to 0xfc000000-0xfc00259c ... done
>> (XEN) HVM1: Creating MP tables ...
>> (XEN) HVM1: Loading Cirrus VGABIOS ...
>> (XEN) HVM1: Loading PCI Option ROM ...
>> (XEN) HVM1: - Manufacturer: http://etherboot.org
>> (XEN) HVM1: - Product name: gPXE
>> (XEN) HVM1: Loading ACPI ...
>> (XEN) HVM1: - Lo data: 000ea020-000ea04f
>> (XEN) HVM1: - Hi data: fc002800-fc0042bf
>> (XEN) HVM1: vm86 TSS at fc004400
>> (XEN) HVM1: BIOS map:
>> (XEN) HVM1: c0000-c8fff: VGA BIOS
>> (XEN) HVM1: c9000-d57ff: Etherboot ROM
>> (XEN) HVM1: eb000-eb14c: SMBIOS tables
>> (XEN) HVM1: f0000-fffff: Main BIOS
>> (XEN) HVM1: Invoking ROMBIOS ...
>> (XEN) HVM1: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
>> (XEN) stdvga.c:147:d1 entering stdvga and caching modes
>> (XEN) HVM1: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert
>> Exp $
>> (XEN) HVM1: Bochs BIOS - build: 06/23/99
>> (XEN) HVM1: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $
>> (XEN) HVM1: Options: apmbios pcibios eltorito PMM
>> (XEN) HVM1:
>> (XEN) HVM1: ata1 master: QEMU DVD-ROM ATAPI-4 CD-Rom/DVD-Rom
>> (XEN) HVM1: IDE time out
>> (XEN) HVM1:
>>
>> No suspicious log is found in /var/log/xen/xend.log.
>>
>> I came across this problem with AMD Quad-Core Opteron(tm) 2356 on Dell
>> PowerEdge R805. However, this kind of problem did not happened on the
>> another machine I use (Intel Xeon 5130).
>>
>> Does anybody know how to fix this problem or how to analyze it?
>>
>> Thank you in advance,
>>
>> --
>> Yoshisato YANAGISAWA, Ph.D.
>> Open Source Software Computing Project
>> NTT Cyber Space Laboratories
>> NIPPON TELEGRAPH AND TELEPHONE CORPORATION
>> 1-1 Hikarinooka, Yokosuka-Shi,
>> Kanagawa 239-0847, Japan
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
--
TAMURA, Yoshiaki
NTT Cyber Space Labs
OSS Computing Project
Kernel Group
E-mail: tamura.yoshiaki@lab.ntt.co.jp
TEL: +81-46-859-2771
FAX: +81-46-855-1152
Address: 1-1 Hikarinooka, Yokosuka
Kanagawa 239-0847 JAPAN
next prev parent reply other threads:[~2009-03-11 5:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 8:16 Could not run HVM domain on the latest xen-unstable.hg and Barcelona Yoshisato YANAGISAWA
2009-03-10 23:18 ` Could not run HVM domain on the latest xen-unstable.hgand Barcelona Huang2, Wei
2009-03-11 1:40 ` Yoshisato YANAGISAWA
2009-03-11 3:41 ` Kouya Shimura
2009-03-11 4:51 ` Could not run HVM domain on the latestxen-unstable.hgand Barcelona Huang2, Wei
2009-03-11 8:29 ` Kouya Shimura
2009-03-11 5:02 ` Yoshiaki Tamura [this message]
2009-03-11 5:36 ` Could not run HVM domain on the latest xen-unstable.hgand Barcelona Kouya Shimura
2009-03-11 5:51 ` Yoshiaki Tamura
2009-03-11 6:14 ` Kouya Shimura
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=49B745D4.1090004@lab.ntt.co.jp \
--to=tamura.yoshiaki@lab.ntt.co.jp \
--cc=Wei.Huang2@amd.com \
--cc=keir.fraser@eu.citrix.com \
--cc=kouya@jp.fujitsu.com \
--cc=takebe_akio@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
--cc=yanagisawa.yoshisato@lab.ntt.co.jp \
/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.