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

[Xen-devel] Problem upgrading xen-unstable

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ge van Geldorp" <gvg@xxxxxxxxxxx>
  • Date: Sun, 22 May 2005 23:59:39 +0200
  • Delivery-date: Sun, 22 May 2005 21:59:04 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcVfGY0N92PQ5rYdQR2tEZY/H6CSMQ==

I've been working on a xen-unstable tree from mid-April. I wanted to upgrade
to the latest version, so here is what I did:

- Clone a fresh copy of xeno-unstable.bk (1.1507)
- "make world"
- Change the .config of linux-2.6.11-xen0 to include my ethernet card
- Add localversion files to linux-2.6.11-xen0 and linux-2.6.11-xenU
- rm -rf the existing dist directory
- "make kernels"
- "make dist"
- Tar the dist directory (plus subdirectories), transfer the tar file to the
destination dom0 and untar there
- On the destination dom0, cd into the dist directory and "./install.sh"
- Reboot

I'm now seeing a lot of problems which all seem to be related to xend. When
running "xm console mydomU" on dom0, output is garbled. Shutting down or
destroying a domain using xm frequently results in the domain still being
listed by "xm list", although with a 0 memory size. After recreating a
domain in that state, "xm list" will show two lines with the same domid (but
the domain won't get created).

My guess is I messed something up during the upgrade. I just can't figure
out what...

All help appreciated, Gé van Geldorp.

Xen-devel mailing list



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