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

[Xen-users] Antw: Xen-users Digest, Vol 104, Issue 18


  • To: xen-users@xxxxxxxxxxxxx
  • From: "M SIEVERS" <marcsievers@xxxxxxx>
  • Date: Tue, 15 Oct 2013 22:14:54 +0200
  • Delivery-date: Tue, 15 Oct 2013 20:17:01 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>
  • Priority: normal



Op 10/12/13, xen-users-request@xxxxxxxxxxxxx schreef:
Send Xen-users mailing list submissions to
xen-users@xxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-users
or, via email, send a message with subject or body 'help' to
xen-users-request@xxxxxxxxxxxxx

You can reach the person managing the list at
xen-users-owner@xxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xen-users digest..."


Today's Topics:

   1. Re: FreeBSD PVHVM call for testing (Eggert, Lars)
   2. Re: FreeBSD PVHVM call for testing (Roger Pau Monn?)
   3. Subscribe today to the Xen Project Newletter (Russ Pavlicek)
   4. Re: Subscribe today to the Xen Project Newletter (Shane Johnson)
   5. Re: Subscribe today to the Xen Project Newletter (Russ Pavlicek)
   6. Re: Subscribe today to the Xen Project Newletter (Shane Johnson)
   7. Re: Problem in building vTPM manager (Emma Allison)
   8. Possible locking issue with network-bridge (Andrew Davidoff)


----------------------------------------------------------------------

Message: 1
Date: Fri, 11 Oct 2013 09:42:11 +0000
From: "Eggert, Lars" <lars@xxxxxxxxxx>
To: Roger Pau Monn? <roger.pau@xxxxxxxxxx>
Cc: "freebsd-xen@xxxxxxxxxxx" <freebsd-xen@xxxxxxxxxxx>, xen-devel
<xen-devel@xxxxxxxxxxxxx>, "freebsd-virtualization@xxxxxxxxxxx"
<freebsd-virtualization@xxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxx"
<xen-users@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] FreeBSD PVHVM call for testing
Message-ID: <7BE1E0BE-C4E8-4706-8751-23A30D733A94@xxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi,

On May 13, 2013, at 20:32, Roger Pau Monn? <roger.pau@xxxxxxxxxx> wrote:
> Right now the code is in a state where it can be tested by users, so we
> would like to encourage FreeBSD and Xen users to test it and provide
> feedback.

any idea if/when this code will be merged into -CURRENT?

Thanks,
Lars
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 273 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.xen.org/archives/html/xen-users/attachments/20131011/f8786bef/attachment.pgp>

------------------------------

Message: 2
Date: Fri, 11 Oct 2013 15:56:22 +0200
From: Roger Pau Monn? <roger.pau@xxxxxxxxxx>
To: "Eggert, Lars" <lars@xxxxxxxxxx>
Cc: "freebsd-xen@xxxxxxxxxxx" <freebsd-xen@xxxxxxxxxxx>, xen-devel
<xen-devel@xxxxxxxxxxxxx>, "freebsd-virtualization@xxxxxxxxxxx"
<freebsd-virtualization@xxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxx"
<xen-users@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] FreeBSD PVHVM call for testing
Message-ID: <52580386.1020802@xxxxxxxxxx>
Content-Type: text/plain; charset="ISO-8859-1"

On 11/10/13 11:42, Eggert, Lars wrote:
> Hi,
>
> On May 13, 2013, at 20:32, Roger Pau Monn? <roger.pau@xxxxxxxxxx> wrote:
>> Right now the code is in a state where it can be tested by users, so we
>> would like to encourage FreeBSD and Xen users to test it and provide
>> feedback.
>
> any idea if/when this code will be merged into -CURRENT?

It's already in HEAD, and will hopefully be part of the 10 release.

Roger.




------------------------------

Message: 3
Date: Fri, 11 Oct 2013 14:42:13 -0400
From: Russ Pavlicek <russell.pavlicek@xxxxxxxxxxxxxx>
To: xen-users@xxxxxxxxxxxxx, xen-api@xxxxxxxxxxxxx
Subject: [Xen-users] Subscribe today to the Xen Project Newletter
Message-ID:
<CAHehzX1Sr0_A9kh2W5Bd5YPn4i+sFNPANEAh0xsvfkkvNx1feA@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

The monthly Xen Project newsletter is coming out in a couple days.

Subscribe now so you don't miss out.

http://xenproject.org/subscribe.html

Russell Pavlicek
Xen Project Evangelist



------------------------------

Message: 4
Date: Fri, 11 Oct 2013 12:50:21 -0600
From: Shane Johnson <sdj@xxxxxxxxxxxxxxxxxxxxxx>
To: Russ Pavlicek <russell.pavlicek@xxxxxxxxxxxxxx>
Cc: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>,
xen-api@xxxxxxxxxxxxx
Subject: Re: [Xen-users] Subscribe today to the Xen Project Newletter
Message-ID:
<CAPLO1L7cH=uC7YJ_Fw6Qfmj_1p5gv9y2i9bRa7GsRgQOmxK5Fw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

Most people are already overloaded on information in their inboxes.
Anywhere we can get a better idea of the intended content in the
newsletter so we can determine it's value?

Thanks
Shane

On Fri, Oct 11, 2013 at 12:42 PM, Russ Pavlicek
<russell.pavlicek@xxxxxxxxxxxxxx> wrote:
> The monthly Xen Project newsletter is coming out in a couple days.
>
> Subscribe now so you don't miss out.
>
> http://xenproject.org/subscribe.html
>
> Russell Pavlicek
> Xen Project Evangelist
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users



--
Shane D. Johnson
IT Administrator
Rasmussen Equipment



------------------------------

Message: 5
Date: Fri, 11 Oct 2013 15:09:47 -0400
From: Russ Pavlicek <russell.pavlicek@xxxxxxxxxxxxxx>
To: Shane Johnson <sdj@xxxxxxxxxxxxxxxxxxxxxx>
Cc: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>, Russ Pavlicek
<russell.pavlicek@xxxxxxxxxxxxxx>, xen-api@xxxxxxxxxxxxx
Subject: Re: [Xen-users] Subscribe today to the Xen Project Newletter
Message-ID:
<CAHehzX3k98rjWKXhw-orbYP2zgMOs2nR5zbSLSHZkf_9E+HkVg@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

>Anywhere we can get a better idea of the intended content in the
> newsletter so we can determine it's value?

Certainly.

Currently, the Xen Project Newsletter lists the critical highlights of
the month for folks who don't have time to check the Xen blog and
events calendar on a regular basic.  It has links to some of the most
notable Xen Project blogs, a listing of Xen-related events in the next
few weeks, and (starting in this issue), links to external articles
which have value for Xen users and developers.

Rather than featuring new content, it is a quick rundown of the
important things in the Xen world for the past month and for the month
ahead.  It is meant to be a quick read with links to more information,
so you can investigate those things which matter to you without wading
through tons of information which may not meet your needs.  Our
intention is to keep it monthly so that we don't burden your inbox any
more than necessary.

If you read it and decide that it could be improved by including or
excluding items, please let me know so we can make this a more
valuable experience for everyone.  And we always include a link to
unsubscribe if you decide you don't want to receive further issues.

Does that help?

Russ Pavlicek
Xen Project Evangelist (and newsletter editor ;)

On Fri, Oct 11, 2013 at 2:50 PM, Shane Johnson
<sdj@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> Most people are already overloaded on information in their inboxes.
> Anywhere we can get a better idea of the intended content in the
> newsletter so we can determine it's value?
>
> Thanks
> Shane
>
> On Fri, Oct 11, 2013 at 12:42 PM, Russ Pavlicek
> <russell.pavlicek@xxxxxxxxxxxxxx> wrote:
>> The monthly Xen Project newsletter is coming out in a couple days.
>>
>> Subscribe now so you don't miss out.
>>
>> http://xenproject.org/subscribe.html
>>
>> Russell Pavlicek
>> Xen Project Evangelist
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-users
>
>
>
> --
> Shane D. Johnson
> IT Administrator
> Rasmussen Equipment



------------------------------

Message: 6
Date: Fri, 11 Oct 2013 13:33:55 -0600
From: Shane Johnson <sdj@xxxxxxxxxxxxxxxxxxxxxx>
To: Russ Pavlicek <russell.pavlicek@xxxxxxxxxxxxxx>
Cc: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>,
xen-api@xxxxxxxxxxxxx
Subject: Re: [Xen-users] Subscribe today to the Xen Project Newletter
Message-ID:
<CAPLO1L52=oPjOxierFN1g2bZesN7kLUHm5VELK7oqWC9H+dgOA@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

Yes, Greatly.

Thank you

Shane

On Fri, Oct 11, 2013 at 1:09 PM, Russ Pavlicek
<russell.pavlicek@xxxxxxxxxxxxxx> wrote:
>>Anywhere we can get a better idea of the intended content in the
>> newsletter so we can determine it's value?
>
> Certainly.
>
> Currently, the Xen Project Newsletter lists the critical highlights of
> the month for folks who don't have time to check the Xen blog and
> events calendar on a regular basic.  It has links to some of the most
> notable Xen Project blogs, a listing of Xen-related events in the next
> few weeks, and (starting in this issue), links to external articles
> which have value for Xen users and developers.
>
> Rather than featuring new content, it is a quick rundown of the
> important things in the Xen world for the past month and for the month
> ahead.  It is meant to be a quick read with links to more information,
> so you can investigate those things which matter to you without wading
> through tons of information which may not meet your needs.  Our
> intention is to keep it monthly so that we don't burden your inbox any
> more than necessary.
>
> If you read it and decide that it could be improved by including or
> excluding items, please let me know so we can make this a more
> valuable experience for everyone.  And we always include a link to
> unsubscribe if you decide you don't want to receive further issues.
>
> Does that help?
>
> Russ Pavlicek
> Xen Project Evangelist (and newsletter editor ;)
>
> On Fri, Oct 11, 2013 at 2:50 PM, Shane Johnson
> <sdj@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>> Most people are already overloaded on information in their inboxes.
>> Anywhere we can get a better idea of the intended content in the
>> newsletter so we can determine it's value?
>>
>> Thanks
>> Shane
>>
>> On Fri, Oct 11, 2013 at 12:42 PM, Russ Pavlicek
>> <russell.pavlicek@xxxxxxxxxxxxxx> wrote:
>>> The monthly Xen Project newsletter is coming out in a couple days.
>>>
>>> Subscribe now so you don't miss out.
>>>
>>> http://xenproject.org/subscribe.html
>>>
>>> Russell Pavlicek
>>> Xen Project Evangelist
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxx
>>> http://lists.xen.org/xen-users
>>
>>
>>
>> --
>> Shane D. Johnson
>> IT Administrator
>> Rasmussen Equipment



--
Shane D. Johnson
IT Administrator
Rasmussen Equipment



------------------------------

Message: 7
Date: Fri, 11 Oct 2013 19:09:09 -0400
From: Emma Allison <em.allison.88@xxxxxxxxx>
To: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] Problem in building vTPM manager
Message-ID:
<CAH5i-_Lvxb7Ub0G4WsauJsYoPppSk5Kp0Vp9mo5KCXjcMiy5oQ@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Thanks Daniel,

When I run

sudo xl create -c vtpmmgr-stubdom.cfg

I receive the following error:

Parsing config from vtpmmgr-stubdom.cfg
Daemon running with PID 29361
Xen Minimal OS!
  start_info: 0xa2000(VA)
    nr_pages: 0x1000
  shared_inf: 0x83ad7000(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 0x2302d8
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/22/768
Failed to read /local/domain/0/backend/qdisk/22/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

How I can solve this problem?
Note: I had tcsd running on dom0, which I killed before I run the command.


On Fri, Sep 27, 2013 at 2:39 PM, Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>wrote:

> On 09/27/2013 02:17 PM, Emma Allison wrote:
>
>> Hi,
>>
>> I use Xen 4.3.0. When I build the source using "make world", the file
>> vtpmmgr-stubdom.gz is not created. Based on the documentation, manager
>> config file requires the path to this file to be specified.
>>
>> Is there any flag that I have to set, or any trick for building vTPM
>> manager?
>>
>> Thanks.
>>
>
> You likely need to install cmake and then rerun ./configure. You can also
> run "./configure --enable-vtpmmgr-stubdom" to make missing dependencies
> fatal.
>
> --
> Daniel De Graaf
> National Security Agency
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xen.org/archives/html/xen-users/attachments/20131011/47c96308/attachment.html>

------------------------------

Message: 8
Date: Sat, 12 Oct 2013 03:30:09 -0400
From: Andrew Davidoff <davidoff@xxxxxxxxx>
To: xen-users@xxxxxxxxxxxxx
Subject: [Xen-users] Possible locking issue with network-bridge
Message-ID:
<CAJLXCZTuibnO8r=ymDLnuCq-EGn2RRTPsbf1=QUqhnufihF5+A@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I'm running into a problem that I think has uncovered an issue with
how network-bridge is doing its locking. There's possibly a root cause
to my problem that's lower-level than the potential locking issue, but
it seems to me like I may have uncovered a locking issue either way.

I just installed Xen 4.2.3-23.el6 on a Scientific Linux 6.4 server.
Xen was installed from the CentOS xen4 repo installed by
centos-release-xen. The server has two ethernet ports configured in an
LACP bond. I have Xen configured to use network bridging.

During boot, when xend was setting up bridging, the network link was
going down and coming back up as bond0 was renamed pbond0, etc, but
then it was dropping for good and the xend bridging setup was ending
with this error:

RTNETLINK answers: File exists

I narrowed this down to the fact that network-bridge was running
multiple times, and the instances were stomping on each other. It's
possible that the fact that it is running multiple times is the root
cause of my issues here, but even if it should only be getting called
once, it seems that there's an issue with the call to claim_lock.

claim_lock happens after the checks that would make network-bridge exit earlly:

    if [ "${bridge}" = "null" ] ; then
        return
    fi

    if [ `brctl show | wc -l` != 1 ]; then
        return
    fi

    if link_exists "$pdev"; then
        # The device is already up.
        return
    fi

It seems that this is problematic in that if an instance of
network-bridge starts as another is running and has already claimed
the lock, but before the lock holder has created any bridges or turned
up $pdev, the late-comer will wait for the first script to complete,
get the lock for itself, then proceed to break networking.

I moved the call to claim_lock to the beginning of op_start and
dropped in calls to release_lock before the possible early-exit
returns, and this seems to have solved the problem. Does this seem
like the right thing to do? And either way, if network-bridge
shouldn't be running more than once, what do you think might be
causing that? At a glance I think it should just be getting called
once, when XendPIF.py is first loaded, but maybe I'm overlooking
something.

Thanks.
Andy



------------------------------

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


End of Xen-users Digest, Vol 104, Issue 18
******************************************

Attachment: marcsievers.vcf
Description: Card for "M SIEVERS" <marcsievers@home.nl>

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

 


Rackspace

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