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] [XCP] Booting dom0 from iSCSI + bringing up VMs?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] [XCP] Booting dom0 from iSCSI + bringing up VMs?
From: Derrik Pates <dpates@xxxxxxxxx>
Date: Mon, 05 Jul 2010 17:21:04 -0600
Delivery-date: Tue, 06 Jul 2010 02:08:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100528 Thunderbird/3.0.5
All,

We are attempting to boot XCP on machines with no local storage, and use
iSCSI-based network storage by PXE booting the machines (not using an
iSCSI HBA, just plain gigabit/10gigE networking). We are finding that
the dom0 can boot, but if we attempt to set up a domU and boot it, the
whole machine seems to give out, like the dom0 just lost its IP address
(ssh session croaks, can't ping dom0, start getting "task hung too long"
warnings via console). This also persisted upon rebooting, requiring
manual editing of /var/xapi/state.db to get it back into working condition.

Has anyone else tried this? Is the network configuration toolset doing
something to dom0's eth0 interface that might cause it to temporarily
lose its IP, in a way that wouldn't matter with local storage? I'm not
sure if it's something specifically related to Open VSwitch, or if it's
the xe tools that are misbehaving or what. Any thoughts would be
appreciated.

(Sorry if this is a duplicate.)

Regards,

-- 
Derrik Pates
Voxel dot Net, Inc.
dpates@xxxxxxxxx


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

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