This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-ia64-devel] RE: Multiple domains up on a bit old Rev

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Subject: [Xen-ia64-devel] RE: Multiple domains up on a bit old Rev
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Thu, 22 Sep 2005 06:49:12 -0700
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 22 Sep 2005 13:49:19 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-topic: Multiple domains up on a bit old Rev
Still no success for me.  I also did not reinstall everything
from scratch, so apparently there is something in my environment
that is different and is causing a problem.

I had forgotten yesterday to clean up xenstored so I was
hoping that was the problem, but it didn't help.

When I do "xm create -c", I get:

Error: Error creating domain: 'NoneType' object has no attribute 'port1'

I don't have your .img file but I don't think that is the problem.
(I am using the ski sda image and am able to mount it as loopback
and view the files in it.)

If you recognize this error and know a fix, please let me know.
since someone else on the team was able to reproduce your success,
I am willing to move on to the next step.  Do you feel comfortable
with reproducing and testing your changes/patches on a newer tree?
I am thinking that the next step is to try to build multiple domains
from -sparse and that will first require a re-synch with xen-unstable.
I haven't seen any significant changes in xen-unstable that would
break your multi-domain work, but unfortunately there have been
many "whitespace" patches that will make it almost impossible to
diff for recent changes.


> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx] 
> Sent: Thursday, September 22, 2005 4:25 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: Multiple domains up on a bit old Rev
> Hi, Dan,
>       Attached is the short receipt, and Anthony succeeded to 
> reproduce the multiple domain environment on RHEL3 distro. 
> Though not a fresh install from scratch for EL3, he never 
> tried multiple domains on that box before. BTW, our build 
> machine is separate as the test machine, so there's no need 
> to add mercurial on the test machine for us.
>       Before trying the receipt, I'd like you to confirm 
> following issues first which may be the suspect from my guess:
> - Currently xenlinux-ia64 doesn't remove 
> include/asm-xen/linux-public, instead it should be a symbolic 
> link created by Makefile now. So the privcmd.h under that 
> directory may be stale. In Anthony's first try, xen0 failed 
> to create /proc/xen/privcmd, and so xend start failed. After 
> remove that directory, xend can work.
> - Please confirm bad lines in xen-backend.agent removed, 
> since I didn't see it on latest xen-ia64-unstable.hg.
> - I'm always do "rm -rf /var/lib/xenstored/*" to ensure no 
> stale domain info from last run affecting next. Maybe 
> conservative, but I just want a clean environment.
>       OK, now let's go to the receipt section. Just a warn 
> that some steps may be temporary upon current repo, and 
> unnecessary soon. 
> ========================================================
> [On Build Machine]
> Download Xen-ia64-dev.hg and xenlinux-ia64.
> #Cd xen-ia64-dev.hg
> #make dist XEN_NO_IOEMU=y
> #tar -czf dist.tar.gz dist/
> #cd Xenlinux-ia64:
> #make clean (For current hg, you need to remove 
> include/asm-xen/linux-public directory manually)
> #cp arch/ia64/configs/xen_tiger_defconfig .config
> #make oldconfig
> #make menuconfig)
> ========NOTE============
> Currently the default Kconfig disables the CONFIG_VT, which 
> is wanted for xenU. However for xen0, this option off 
> requires user logon to xen0 by network. In my case, I chose 
> to compile xen0 and xenU separately with only difference on 
> CONFIG_VT (you can edit driver/char/Kconfig)
> =========================
> (Enable CONFIG_VT for xen0)
> #make -j4 XEN_PATH={full path of xen repo}
> #cp vmlinux xeno-vmlinux
> (Disable CONFIG_VT for xenU)
> #make -j4
> #cp vmlinux xenU-vmlinux
> [On Test Machine]
> #copy xen.gz/xeno-vmlinux to /boot/efi/efi/redhat (Set 
> elilo.conf as previous Dan's receipt)
> #copy xenU-vmlinux to /boot/
> #copy dist.tar.gz to /tmp/
> #cd /tmp/
> #tar -xzf dist.tar.gz
> #rm -rf /usr/lib/python/xen
> #cd dist
> #./install.sh
> #cp /etc/xen/example1 /etc/xen/xmdefconfig
> #Change following items per your setting:
> kernel = "/boot/xenU-vmlinux"
> memory = 256
> disk = [ 'phy:loop0,hda1,w' ] // We use a image file for domU
> #rm -rf /var/lib/xenstored/*  //Promise a clean environment
> #lomount -t ext2 -diskimage /root/xenia64.img -partition 2 /mnt
> xend start    // bind and mount the image file 
> #xend start
> #xm create -c
> Then you can wait to see xenU up to shell. Actually multiple 
> domains actually work stable on my box for almost one day, 
> until I actively stop it for other test. Also due to some 
> environment difference, some steps above may not adapt to 
> your case. Just a reference here. ;-)
> Thanks,
> Kevin

Xen-ia64-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>