Re: [Xen-users] Problems with vTPM manager

[Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>]

On 09/24/2013 09:51 AM, Eduardo Peixoto Macedo wrote:
> Hi,
>
> I am following http://xenbits.xen.org/docs/unstable/misc/vtpm.txt, but
> I'm having some problems when I try to start vtpmmgr-stubdom
> I'm using Xen 4.3 on Ubuntu 12.04 and I have a physical TPM.
>
> The config file for vTPM manager is:
>
> kernel="/usr/local/lib/xen/boot/vtpmmgr-stubdom.gz"
> memory=16
> disk=["file:/var/vtpmmgr-stubdom.img,hda,w"]
> name="vtpmmgr"
> iomem=["fed40,5"]
>
>
> And I get this output when I try xl create -c vtpmmgr-stubdom.cfg:
>
> Parsing config from /home/xen_images/vtpmmgr-stubdom.cfg
> Daemon running with PID 5048
> Xen Minimal OS!
>    start_info: 0xa2000(VA)
>      nr_pages: 0x1000
>    shared_inf: 0x44e09000(MA)
>       pt_base: 0xa5000(VA)
> nr_pt_frames: 0x5
>      mfn_list: 0x9a000(VA)
>     mod_start: 0x0(VA)
>       mod_len: 0
>         flags: 0x0
>      cmd_line:
>    stack:      0x597e0-0x797e0
> MM: Init
>        _text: 0x0(VA)
>       _etext: 0x39357(VA)
>     _erodata: 0x45000(VA)
>       _edata: 0x47c40(VA)
> stack start: 0x597e0(VA)
>         _end: 0x99e00(VA)
>    start_pfn: ad
>      max_pfn: 1000
> Mapping memory range 0x400000 - 0x1000000
> setting 0x0-0x45000 readonly
> skipped 0x1000
> MM: Initialise page allocator for b3000(b3000)-1000000(1000000)
> MM: done
> Demand map pfns at 1001000-2001001000.
> Heap resides at 2001002000-4001002000.
> Initialising timer interface
> Initialising console ... done.
> gnttab_table mapped at 0x1001000.
> Initialising scheduler
> Thread "Idle": pointer: 0x2001002050, stack: 0xd0000
> Thread "xenstore": pointer: 0x2001002800, stack: 0xe0000
> xenbus initialised on irq 1 mfn 0x5e26b
> Thread "shutdown": pointer: 0x2001002fb0, stack: 0xf0000
> Dummy main: start_info=0x798e0
> Thread "main": pointer: 0x2001003760, stack: 0x100000
> "main"
> Shutting down ()
> Shutdown requested: 3
> Thread "shutdown" exited.
> INFO[VTPM]: Starting vTPM manager domain
> INFO[VTPM]: Option: Using tpm_tis driver
> ******************* BLKFRONT for device/vbd/768 **********
>
>
> backend at /local/domain/0/backend/qdisk/4/768
> Failed to read /local/domain/0/backend/qdisk/4/768/feature-barrier.
> 32768 sectors of 512 bytes
> **************************
> blk_open(device/vbd/768) -> 3
> ============= Init TPM BACK ================
> Thread "tpmback-listener": pointer: 0x20010043f0, stack: 0xf0000
> ============= Init TPM TIS Driver ==============
> IOMEM Machine Base Address: FED40000
> Enabled Localities: 0
> Map 1 (fed40, ...) at 0x1006000 failed: -1.
> Do_exit called!
> base is 0x10fcb8 caller is 0x1f24d
> base is 0x10fcd8 caller is 0x27658
> base is 0x10fd88 caller is 0x2772b
> base is 0x10fde8 caller is 0x26bf6
> base is 0x10fe28 caller is 0x26c1e
> base is 0x10fe38 caller is 0x1ba94
> base is 0x10fe78 caller is 0x6f84
> base is 0x10ff38 caller is 0x353c
> base is 0x10ff68 caller is 0x1fa80
> base is 0x10ffe8 caller is 0x343b
>
>
> Please, could you help me with this?
This is an issue that has been reported before, but at the time I thought
it was due to lack of a physical TPM and did not investigate further. This
is actually a bug introduced by the XSM changes in 4.3 which broke DOMID_IO
mappings with XSM disabled (or when using the dummy module). I will be
sending a patch fixing this to xen-devel; could you test it and verify that
it fixes this issue?

--
Daniel De Graaf
National Security Agency

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