similar to: iSCSI-based Storage Pool and virsh attach-device problems/questions

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, How do I make storage pool auto start? I have: virsh # pool-list Name State Autostart - ----------------------------------------- default active yes virtimages active no I don't see anything in pool's xml that could suit this purpose: virsh # pool-dumpxml virtimages

On 12/22/2013 10:09 AM, Marco wrote: > On 2013–12–21 John Ferlan wrote: > >> On 12/17/2013 07:13 PM, Marco wrote: >>> Hi! >>> >>> I'm new to libvirt and face problems connecting to an iSCSI target. >>> What I intend to do is to connect libvirt (I tried virt-manager and >>> virsh) to an iSCSI target and then boot from the LUNs which

On 2013–12–23 John Ferlan wrote: > On 12/22/2013 10:09 AM, Marco wrote: > > On 2013–12–21 John Ferlan wrote: > > > >> On 12/17/2013 07:13 PM, Marco wrote: > >>> Hi! > >>> > >>> I'm new to libvirt and face problems connecting to an iSCSI target. > >>> What I intend to do is to connect libvirt (I tried virt-manager and

hi,all I want to delete the storage pool,but libvirt tell me say: > error: Failed to delete pool virtimages > > error: Requested operation is not valid: storage pool is still active > > > the question is how to make the pool's status to be inactive? thanks liuzhijun -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 2013–12–21 John Ferlan wrote: > On 12/17/2013 07:13 PM, Marco wrote: > > Hi! > > > > I'm new to libvirt and face problems connecting to an iSCSI target. > > What I intend to do is to connect libvirt (I tried virt-manager and > > virsh) to an iSCSI target and then boot from the LUNs which contain > > the VMs. > > > > I followed the

I keep on getting the following entries in the xend.log file and it''s drowning out the important messages: [2007-07-23 14:58:28 2931] ERROR (XendConfig:909) dumping sxp from device controllers Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/xend/XendConfig.py", line 895, in to_sxp configs = controller.configurations(txn) File

Hi everybody, I am trying to take snapshot of a particular iscsi disk mounted inside the guest operating system. I have created my own snapshot feature for that. Could someone please suggest the better choice for stopping read/write operations on disk out of the two to take snapshots, or if you have any better solution, 1) freeze filesystems ( using domfsfreeze ) and then take the snapshot or,

Hi, When I add a new LUN on an iscsi target and then issue a pool-refresh command on the respective storage pool in libvirt, libvirt will not find the new lun (or notice if luns have been removed). I'm using a Dell PowerVault MD3200i iSCSI Array to hold the volumes for virtual servers in libvirt. In libvirt, I have defined the storage pool as this: <pool type='iscsi'>

Hello I''m trying to convert a HVM to PV dom0. The domU is a 10SP2 SLED ( Kernel 2.6.16.60-0.21 i386) and is a SLES11SP2 dom0 (Kernel 3.0.13-0.27-xen 64bit). The truth is that every tutorial I see it differently and I do not know where this error. When I start the domU, pvgrub shows the options but when I select the kenel-xen, returns the error "Boot loader did not return any

Hi, Can anyone identify whether this is a known issue (perhaps 6667208) and if the fix is going to be pushed out to Solaris 10 anytime soon? I''m getting badly beaten up over this weekly, essentially anytime we drop a packet between our twenty-odd iscsi-backed zones and the filer. Chris was kind enough to provide his synopsis here (thanks Chris):

Hi friends, i have a problem. I have a file server which initiates large volumes with iscsi initiator. Problem is, zfs side it shows non aviable space, but i am %100 sure there is at least, 5 TB space. Problem is, because zfs pool shows as 0 aviable all iscsi connection got lost and all sharing setup is gone and need restart to fix. all time till today i keep delete snapshots and make it alive

Hi, I want to start using iscsi storage but ran into a problem. I defined a storage pool and this contains my first LUN which is mounted on a hypervisor. When I now add a second LUN on a target and do a tgt-admin --update --force to reload the target the i/o to the first LUN seems to freeze for a few seconds. Now I'm wondering if I'm doing anything wrong? It's not really tolerable

On 10.01.2015 11:42, Mathieu Bouillaguet wrote: > Hi, > > I try to define an iscsi pool with virsh but I always get the following > error : > > error :internal error: missing backend for pool type 5 (iscsi) > > And yet libvirt was compiled with iscsi support : > configure: Storage Drivers > configure: > configure: Dir: yes > configure: FS: yes >

Hello everyone, I have recently installed libvirt 1.0.0 and am having a problem with my iSCSI storage pool's autostarting. They are just going to an inactive state right after a reboot of the host. However once the startup is complete I can manually start the pool without problem. I am getting the following errors in the libvirtd.log file but they don't really give me much as to what

Hi! I'm new to libvirt and face problems connecting to an iSCSI target. What I intend to do is to connect libvirt (I tried virt-manager and virsh) to an iSCSI target and then boot from the LUNs which contain the VMs. I followed the documentation¹ but got stuck at section 12.1.5.4.3. 1) virsh pool-define-as \ --name foo \ --type iscsi

Hi All, I've been trying to figure out the best way of using an iSCSI SAN with KVM and thanks to a helpful post by Tom Georgoulias that I found on this list (https://www.redhat.com/archives/libvirt-users/2010-May/msg00008.html), it appears I have a solution. What I'm wondering is the following: 1) If I use an iSCSI LUN as the storage pool (instead of creating an LVM VG from this iSCSI

Hi, I try to define an iscsi pool with virsh but I always get the following error : error :internal error: missing backend for pool type 5 (iscsi) And yet libvirt was compiled with iscsi support : configure: Storage Drivers configure: configure: Dir: yes configure: FS: yes configure: NetFS: yes configure: LVM: yes configure: iSCSI: yes configure: SCSI: yes configure:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Former user of Xen and newbie in kvm/qemu/libvirt stuff, I give it a try on my network ;-) I need to run a VM with iSCSI target attached. I did it this way : 1) Creation of iscsi pool (equa.xml) : <pool type="iscsi"> <name>equalog</name> <source> <host name="10.10.0.1"/> <device

Today I upgraded one of our KVM physical host servers to Centos 5.6. The other server remains on Centos 5.5. I've configured a storage pool in libvirt to use LUNs from an iscsi storage system as the volumes for each VM. After the upgrade, I decommisioned one of the VMs and removed the LUN from the storage system. Normally after this kind of operation, I simply need to run this command

Hello, I've spent a few days googling and reading documentation, but I'm looking for clarification and advise on setting up KVM/libvirt with shared storage. I have 2 (for now) Ubuntu Karmic systems with KVM/virsh/virt-manager set up and running. I have a storage server that can do NFS/iSCSI/samba/ etc. I am trying to figure out the best way to set things up so that I can run