Having trouble converting VMX to Virt-image.
CentOS 5.5, python-virtinst-0.400.3-9.el5
Running this command with all sorts of variations on path names
(absolute/relative) ...
virt-convert -i vmx -o virt-image -D qcow2 --hvm --os-type=linux Smoothwall
Smoothwall2
... Invariably produces an err
Is there any way to disable the possibility that the same guest is
inadvertently started on two separate hosts?
We are storing guest images on NFS to allow for live migration, so blocking
host access to NFS by IP or similar is probably not what we're looking for.
Thanks again
Michael Hall
IT C
> Are the hosts "compatible" ?
> eg. what hardware are they running - are there issue with compatibility
> between then CPUs -eg. does host A have a newer cpu (with newer features)
> than host b ?
The machines are only compatible to the extent that both their CPUs support
vtx. When we go into
> We use the same basic software here. The only difference being that we
> use iscsi targets for each VM, instead of one big iscsi pool, or NFS.
We've successfully tested iSCSI as storage as well, and may use it for data
storage.
Our understanding is that live migration of guests is better on NF
> As a thought, do you have SELinux enabled on the servers host servers,
> and are the host servers patched to the latest available patches?
SELinux is/was enabled
virt_use_nfs == on
No patches, bog standard install with available RPM updates
I tried disabling SELinux (setenforce 0), but same res
... Following up ...
Similar story with a CentOS 5 guest.
The migration appears to work fine, but guest reboots and loses IP connectivity.
Michael Hall
IT Communications Officer
Alice Springs Town Council
mh...@astc.nt.gov.au
(08) 8950 0561
___
virt-to
We have the following test environment:
2 x CentOS 5.5 KVM virtual hosts
2 x CentOS 5.5 network storage boxes with NFS shares on LVs on DRBD
(primary/secondary, no HA, just replication).
We have installed a Win7 guest which can be live migrated almost instantly
between hosts using Virt Manager
Sorry about pestering you guys, let me know if this is not the best list for
this type of question.
Anyway, an NFS storage issue ...
-
SAN/NAS BOX (NFS Server):
-
/ filesystem on VolGroup00/LogVol00 = 7.6GB
A 20GB filesystem on vg_vm/lv_vm1 is moun
Does that help?
Yes, that helps a lot! So we'll go ahead testing live migration using VM file
images stored on NFS and see how that goes.
Thanks
___
virt-tools-list mailing list
virt-tools-list@redhat.com
https://www.redhat.com/mailman/listinfo/virt-
So a file based storage pool is one where VMs are stored as image files in a
partition (our current situation), rather than on separate block devices such
as partitions or LVs?
Thanks again
On 09/02/2010 01:59 AM, Mike Hall wrote:
> We've been working on the assumption that
We've been working on the assumption that KVM live migration would require the
use of a clustered filesystem such as GFS2.
However this page from the Virtualization Guide appears to suggest that either
iSCSI or NFS storage would also work:
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Lin
I successfully added an iSCSI target in VirtManager using '/dev/disk/by-path'
as the Target Path, and can now see the LUN on that target in the Volumes
listing.
However, I do not appear able to use this LUN as a location to store a file
image when setting up a new VM.
If I use the path '/dev/d
Hall
Cc: 'virt-tools-list@redhat.com'
Subject: Re: [virt-tools-list] VirtManager iSCSI Volume
On 08/24/2010 12:05 PM, Mike Hall wrote:
> Is is currently possible to set up iSCSI storage volumes for a KVM
> host using VirtManager?
> Alternatively, is there a manual way to do
Is is currently possible to set up iSCSI storage volumes for a KVM host using
VirtManager?
We're testing a CentOS 5.5 KVM host which will be converted to RHEL once we're
satisfied it works.
We can setup an iSCSI target in VirtManager OK, but when attempting to create
volumes on that target we g
14 matches
Mail list logo
