WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Fully-Virtualized XEN domU not Booting over iSCSI

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Fully-Virtualized XEN domU not Booting over iSCSI
From: "Phillip Nkubito" <phil@xxxxxxxxxxxxxxxx>
Date: Thu, 3 Nov 2011 16:54:34 +0200 (SAST)
Delivery-date: Thu, 03 Nov 2011 07:42:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.9a
Hello,

I am currently trying to move my VMs from running on local host storage to
a shared storage (trying out iSCSI) but I am
facing a bit of a booting dilemma.

The domUs are a mix of paravirtualized and fully-virtualized VMs. They all
boot and run like clockwork when on local
storage.

The paravirtualized domUs appear not to have a problem when I relocate and
boot them from the shared storage
though the fully-virtualized ones give me an error on bootup.

************************************************************
Boot from Hard Disk failed: could not read the hard disk
FATAL: No bootable device
************************************************************

The iSCSI is offering the domUs as file images (.img) to the initiator i.e
.Type=fileio.

My host's processor (as you may have deduced) supports Intel-VTx. Does my
shared storage need to have this capability to be able to
boot my fully-virtualized domU?

Any pointers/suggestions would be appreciated.

Phillip

BASIC SYSTEM INFO:
------------------------------------------------------------
== BEGIN uname -rmi ==
2.6.18-238.19.1.el5xen i686 i386
== END   uname -rmi ==

== BEGIN rpm -qa \*-release\* ==
centos-release-5-6.el5.centos.1
rpmforge-release-0.5.2-2.el5.rf
centos-release-notes-5.6-0
== END   rpm -qa \*-release\* ==

== BEGIN cat /etc/redhat-release ==
CentOS release 5.6 (Final)
== END   cat /etc/redhat-release ==

== BEGIN getenforce ==
Disabled
== END   getenforce ==

== BEGIN free -m ==
             total       used       free     shared    buffers     cached
Mem:          1102       1072         29          0        208        356
-/+ buffers/cache:        507        594
Swap:         4031          0       4031
== END   free -m ==

_----------------------------------------------------------------



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users