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

[Xen-devel] changeset 1.1403 breaks previous xm behaviour

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Kip Macy <kip.macy@xxxxxxxxx>
  • Date: Sun, 15 May 2005 14:43:16 -0700
  • Delivery-date: Sun, 15 May 2005 21:42:47 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=hmQQPC/FESXdohnU1VqhjCLe8jJ6OX12JrQIhuA4taPMOwvX3zS0fsbiBT/WAIou1K9M0L7oPGWTYi0YspLSvOpAQ1K+r519Wd8b9I5wTXdl5ibLvFSBCpiGjfQ+B4rjzrXXi6sApufTGZqjuvJPnEorYb8FQrxqvnZqT35kgmA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

With the move to unix sockets from http, xm no longer works if you're
not running it as root. This is perfectly reasonable, but I just
wasted 45 minutes trying to figure out why it didn't work. I kept on
assuming it was a versioning with my libraries.

Did I miss an announcement on the list?


Xen-devel mailing list



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