similar to: iSCSI boot of Hypervisor(Dom0)

Hi all, some results from my configuration. I''ve this configuration (I''m not interested in raw top performances but in reliability.. so, I can accept slow MB/sec and prefer to rely on a RAID6, for example): 1 Infortrend iSCSI Array A16E-G2130-4 with: - 1GB DDR cache - RAID6 - 7 x 500GB sataII Seagate ST3500630NS with 16mb (no budget for SAS) - one of the logic volumes (about

Microsoft has their "boot" version of their iSCSI software initiator. Apparently this still requires that the network card be iSCSI Boot "enabled." Intel seems to be the only obvious company out there supporting it on their Server adapters - I was wondering if there are any thoughts/plans on implementing iSCSI Boot functionality in the HVM Boot ROM? Or maybe there''s

I just ordered quite a few servers, and, without verifying ahead of time, ordered without hard drives planning to boot over iSCSI using the built-in network cards (NOT an iSCSI HBA). I''m wondering if anyone has tried (and hopefully succeeded) installing XCP to an iSCSI volume using a network card with iSCSI boot support and the software iSCSI initiator in XCP. Obviously I can order HDs

Package: xen-hypervisor-3.0.3-1-i386 Version: 3.0.3-0-1 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, When you have a HVM domain running, if you try to boot a regular paravirtualized domain, dom0 (or maybe the hypervisor) crashes immediately (reboot). The opposite (trying to boot a HVM domain while a regular paravirtualized domain is running) crashes the system as well. I

Hi there, I have one server acting as a iscsi target running windows storage server r2 sp2 and the other server is running centos as an initiator. They are connected to a switch over a 1Gbit ethernet connection. the target is a Dell NF600 and the server running centos is a Poweredge R900. We want to move this configuration to a FC based installation using a Dell QLE2462 HBA (this is the hba we can

Hi there, during peak load on some running domU, I noticed random iSCSI "Reported LUNs data has changed" which forced me to shutdown the respective domU, re-login the target and do a fsck before starting domU again. This occurred on a 16 core machine, having only about 14 domUs running. Spare memory has been occupied by dom0 (about 40G). Each domU has it''s own iSCSI target.

Hi List, I don''t know if this is something that is a simple matter of opinion or if there are strong reasons to take one route or the other. I have dom0 nodes with dedicated bond interfaces that connect to a storage traffic-only VLAN. Currently I have a few domUs running that have large-ish volumes on the iSCSI SAN, and to present the volumes I''m connecting the dom0s to the

Hi Everyone I am looking at setting up a File Server that uses ISCSI storage. It is the first time I have done this, so I am wanting to get peoples thoughts on whether for CentOS systems you should use Hardware based ISCSI HBA's? If so do I need to be careful about what HBA I use ? Currently I am looking at purchasing a Dell System using Broadcom ethernet cards/ ISCSI HBA. From

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

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-2 Hi, Hvm domU does not starts up afer dom0 reboot. Bridge br0 is set up manually. Dom0: Debian Wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux DomU: Debian Squeeze 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux config: ===<======== kernel = '/usr/lib/xen-4.1/boot/hvmloader' builder = 'hvm'

I inherited a xen server that is setup to have all the VM images hosted on an iSCSI mounted NAS array. We been experiencing a random (about every 2-3 days) issue where xen would crash all the VMs, leaving nothing but the Domain0 running. What appears to be happening is something causes the iSCI mount to hiccup. Running "vgchange -a y" and restarting all the VMs brings everything up.

I installed xen on top of Cent OS 5.3 64bit OS with gitco rpm sources. Everything works fine except that I can''t run 64bit pv guest with virsh command. With xm commands I can load the same guest. 32bit pv guest, 32 bit and 64bit hvm works fine with both virsh and xm command. Has anyon have any idea? any help will be largely appreciated. **This is dumpxml for 64bit configuration* **

Dear all, I will setup soon an Infortrend iSCSI SAN device with a raid6 volume and a DELL PE1950 (8 VMs) with a Qlogic iSCSI HBA (server to be duplicated at later time for redundancy). My priorities are: 1) VMs on the iSCSI SAN in order to boot them also by another server if the first one fails 2) performances 3) live migration is a non mandatory option (i.e. I can suffer to shutdown

Hi list, I had setup my xen box with bond in active-backup mode. I had install open-iscsi as initiator to attach an external iscsi san to my box but open-iscsi didn''t work. When i run this command: #iscsiadm -m node -T iqn.2008-03.local.foo:iSCSI.test.disk1 -l I retrive, after some seconds, this error Logging in to [iface: iface0, target: iqn.2008-03.local.foo:iSCSI.test.disk1,

I''m experimenting with xen + iscsi, and I founded that under heavy stress domU''s can crash entire system, I''ve reproduced this many many times. My system is like this Software: - iSCSI Enterprise Target v0.4.13 - RedHat AS4 update 4 64bit + Xen 3.0.3-0 Kernel 2.6.16.29 + Open iSCSI v2.0.730 (Initiator) - Bonnie++ v1.03a VM: - Debian 3.1r3 + Open iSCSI v2.0.730

I am getting the following error on boot on a new install Centos 51: #/bin/sh ro no such file or directory then a kernel panic I have traced it to the call ''switchroot'' in the init script in the initrd. the exact same build without zen has no problems. the boot messages look like: Attaching to iSCSI storage iscsistart: transport class version 2.0-724. iscsid version 2.0-865

Hello, I have been using Xen now for several months and have been quite successful until attempting to utilize iscsi within my domU''s. My research has turned up many posts of people using iscsi with no problems, and I have found no others with the problem I seem to be experiencing. If this has been covered on this list in the past, please accept my humble apologies. Configuration:

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.2 Severity: important Tags: patch I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 / linux-image-2.6.26-2-xen-amd64 without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 / linux-image-2.6.32-5-xen-amd64 and now it does

Hello all, I got some severe iscsi connection loss on my dom0 (Gentoo 2.6.20-xen-r6, xen 3.1.1). Happening several times a day. open-iscsi version is 2.0.865.12. Target iscsi is the open-e DSS product. Here is a snip of my messages log file: May 5 16:52:50 ying connection226:0: iscsi: detected conn error (1011) May 5 16:52:51 ying iscsid: connect failed (111) May 5 16:52:51 ying iscsid:

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-6 Severity: normal Dear Maintainer, I'm trying to boot into xen/dom0 but so far all attempts have resulted in a crash followed by an automatic reboot. My hardware is Motherboard: Asus Sabertooth 990FX R2.0 CPU: AMD FX-8350 GPU: Sapphire Radeon R9 285 A trace of the kernel panic follows (full log captured over serial should