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

RE: [Xen-users] (no subject)

  • To: "Scott A. Wozny" <sawozny@xxxxxxxxxxx>
  • From: Mark Pryor <tlviewer@xxxxxxxxx>
  • Date: Sun, 16 Jan 2011 10:13:29 -0800 (PST)
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 16 Jan 2011 10:14:50 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=FgPRR9iCI0B9HZWZpKAwFvLC/GUf9jTtOgdjiLematV+dQUWxi3vV2c/vfIWJJ2PpbD1ZxBu6//eQzRIEAf0tBuwt+HdmPTod3H1jTT0t1WoW03D+7xy35izC0aAjwPu/Z0zbUep3zZ6P1Qn90tSbLZZSLGKmIRkhiR/7AWpynU=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

--- On Sun, 1/16/11, Scott A. Wozny <sawozny@xxxxxxxxxxx> wrote:

From: Scott A. Wozny <sawozny@xxxxxxxxxxx>
Subject: RE: [Xen-users] (no subject)
To: mark@xxxxxxxxxxxxxxxxxx
Cc: vchampion@xxxxxxxxx, "Xen Users" <xen-users@xxxxxxxxxxxxxxxxxxx>
Date: Sunday, January 16, 2011, 9:17 AM

Hi Mark,


First of all, thanks for the suggestion of giving Squeeze a try with the 
install package.  WAY easier and not only did it install, it actually boots 
into a Xen kernel!  :)  Might not sound like much of an accomplishment to 
others, but it's light years ahead of where I've been stuck.  I did an install 
of Squeeze RC1 with the base system only and then used apt-get to install ssh 
and then xen-linux-system-2.6.32-5-xen-amd64 (I didn't install xen-qemu-dm-4.0 
because my processor doesn't support hardware virtualization; part of why I 
chose Xen over KVM).  It all worked like a charm.  No errors on install and the 
reboot brought me into a Xen kernel with no errors.


Now, I'm hoping you or someone on the list can help me with a new difficulty.  
I can't get xend to start.  I've researched several of what looked like key 
phrases in the error output, but most of the similar errors are either several 
years old and relate to Xen 3 and, for one reason or another, don't look 
applicable to my circumstances OR are rooted in not having a Xen kernel started 
up which I have confirmed I have.  Does anyone have any suggestions on how to 
troubleshoot based upon the output below?  I have looked through dmesg, 
messages and kern.log (the /var/log/xen directory is empty as is 
/var/log/pycentral.log) and I can't seem to find anything that stands out.

To verify your xen package set:

#dpkg -l | grep -i xen

ii  libxenstore3.0                          4.0.1-1                     
Xenstore communications library for Xen
ii  linux-image-2.6.32-5-xen-amd64          2.6.32-29                   Linux 
2.6.32 for 64-bit PCs, Xen dom0 support
ii  linux-image-xen-amd64                   2.6.32+28                   Linux 
for 64-bit PCs (meta-package), Xen dom0 support, Xen dom0 support
ii  xen-hypervisor-4.0-amd64                4.0.1-1                     The Xen 
Hypervisor on AMD64
ii  xen-linux-system-2.6.32-5-xen-amd64     2.6.32-29                   Xen 
system with Linux 2.6.32 on 64-bit PCs (meta-package)
ii  xen-qemu-dm-4.0                         4.0.1-2                     Xen 
Qemu Device Model virtual machine hardware emulator
ii  xen-utils-4.0                           4.0.1-1                     XEN 
administrative tools
ii  xen-utils-common                        4.0.0-1                     XEN 
administrative tools - common files
ii  xenstore-utils                          4.0.1-1                     
Xenstore utilities for Xen

Check your mounts, and see if /proc/xen is mounted, if not execute the line 

#echo 'none /proc/xen xenfs defaults 0 0' >> /etc/fstab

to setup your xen init scripts

#dpkg-reconfigure xen-utils-common

While xend is in your path, you want to start xend via init scripts

#/etc/init.d/xend restart


Xen-users mailing list



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