Re: [Users] Managing Remote Access to Physical Workstations
Hi, Randall! What you need is a "broker", and a terminal server is working as a "broker". There are several solutions that will work, but first I would want to know why you need physical machines? Are there demanding graphical applications you're going to run, or...? Rgrds Johan -users-boun...@ovirt.org skrev: - Till: Itamar Heim Från: Randall Wood Sänt av: users-boun...@ovirt.org Datum: 2012.07.20 22:37 Kopia: "users@ovirt.org" Ärende: Re: [Users] Managing Remote Access to Physical Workstations On Jul 20, 2012, at 16:30, Itamar Heim wrote: > On 07/20/2012 11:13 PM, Randall Wood wrote: >> >>> No. oVirt's focus is virtual machines so the user portal only lets you open >>> up consoles on VMs managed by oVirt engine. >> >> I thought so. >> >>> When you say physical machines - would they be Linux or could they be >>> Windows? >>> I might have an idea .. >> >> The physical machines would all be RHEL, CentOS, or Fedora. > > which protocol would you expect users to use to gain access to this physical > machines? I would prefer SPICE, but could use SPICE, VNC, or RDP. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Managing Remote Access to Physical Workstations
Potentially a combination of gnome boxes and xspice could do that. - Original Message - > From: "Randall Wood" > To: "Andrew Cathrow" > Cc: users@ovirt.org > Sent: Friday, July 20, 2012 4:13:45 PM > Subject: Re: [Users] Managing Remote Access to Physical Workstations > > > > No. oVirt's focus is virtual machines so the user portal only lets > > you open up consoles on VMs managed by oVirt engine. > > I thought so. > > > When you say physical machines - would they be Linux or could they > > be Windows? > > I might have an idea .. > > The physical machines would all be RHEL, CentOS, or Fedora. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Managing Remote Access to Physical Workstations
On Jul 20, 2012, at 16:30, Itamar Heim wrote: > On 07/20/2012 11:13 PM, Randall Wood wrote: >> >>> No. oVirt's focus is virtual machines so the user portal only lets you open >>> up consoles on VMs managed by oVirt engine. >> >> I thought so. >> >>> When you say physical machines - would they be Linux or could they be >>> Windows? >>> I might have an idea .. >> >> The physical machines would all be RHEL, CentOS, or Fedora. > > which protocol would you expect users to use to gain access to this physical > machines? I would prefer SPICE, but could use SPICE, VNC, or RDP. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Managing Remote Access to Physical Workstations
On 07/20/2012 11:13 PM, Randall Wood wrote: No. oVirt's focus is virtual machines so the user portal only lets you open up consoles on VMs managed by oVirt engine. I thought so. When you say physical machines - would they be Linux or could they be Windows? I might have an idea .. The physical machines would all be RHEL, CentOS, or Fedora. which protocol would you expect users to use to gain access to this physical machines? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Managing Remote Access to Physical Workstations
> No. oVirt's focus is virtual machines so the user portal only lets you open > up consoles on VMs managed by oVirt engine. I thought so. > When you say physical machines - would they be Linux or could they be Windows? > I might have an idea .. The physical machines would all be RHEL, CentOS, or Fedora. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Managing Remote Access to Physical Workstations
- Original Message - > From: "Randall Wood" > To: users@ovirt.org > Sent: Friday, July 20, 2012 3:34:16 PM > Subject: [Users] Managing Remote Access to Physical Workstations > > I have an environment where I would like to be able to provide users > with a single web interface from which they would be able to open a > console on either a virtual machine or on a physical machine. Playing > with a clean install of oVirt 3.1 suggests that oVirt is not capable > of doing this. No. oVirt's focus is virtual machines so the user portal only lets you open up consoles on VMs managed by oVirt engine. When you say physical machines - would they be Linux or could they be Windows? I might have an idea .. > > Has anyone successfully configured oVirt to provide this capability, > or know of a system that could integrate with oVirt to meet that > requirement? > -- > Randall Wood > Alexandria Software > http://www.alexandriasoftware.com > randall.h.w...@alexandriasoftware.com > 202.683.8604 > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Managing Remote Access to Physical Workstations
I have an environment where I would like to be able to provide users with a single web interface from which they would be able to open a console on either a virtual machine or on a physical machine. Playing with a clean install of oVirt 3.1 suggests that oVirt is not capable of doing this. Has anyone successfully configured oVirt to provide this capability, or know of a system that could integrate with oVirt to meet that requirement? -- Randall Wood Alexandria Software http://www.alexandriasoftware.com randall.h.w...@alexandriasoftware.com 202.683.8604 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Migrating from KVM to oVirt 3.1 fails - corrupt OVF
On Fri, Jul 20, 2012 at 11:32 AM, Itamar Heim wrote: > On 07/20/2012 07:21 PM, Trey Dockendorf wrote: >> >> On Fri, Jul 20, 2012 at 3:52 AM, Itamar Heim wrote: >>> >>> On 07/20/2012 02:08 AM, Trey Dockendorf wrote: On Thu, Jul 19, 2012 at 4:00 AM, Matthew Booth wrote: > > > On 18/07/12 23:52, Itamar Heim wrote: >> >> >> >> On 07/18/2012 06:00 PM, Trey Dockendorf wrote: >>> >>> >>> >>> I'm attempting to fine-tune the process of getting my KVM/Libvirt >>> managed VMs over into my new oVirt infrastructure, and the virt-v2v >>> import is failing in the WUI with "Failed to read VM 'dh-imager01' >>> OVF, it may be corrupted". I've attached both engine and vdsm logs >>> that are a snapshot from when I ran the virt-v2v command until I saw >>> the failure under Events. >> >> >> >> >> matt - any thoughts? > > > > > Nothing springs to mind immediately, but it sounds like v2v is > producing > an > invalid OVF. If somebody can diagnose what the problem with the OVF is > I > can > fix v2v. > > Matt > > >> >>> >>> virt-v2v command used... >>> >>> # virt-v2v -i libvirtxml -o rhev -os >>> dc-vmarchitect.tamu.edu:/exportdomain dh-imager01.xml >>> dh-imager01_sys.qcow2: 100% >>> >>> >>> >>> [===]D >>> >>> 0h00m37s >>> virt-v2v: dh-imager01 configured with virtio drivers. >>> >>> The xml has been modified numerous times based on past mailing list >>> comments to have VNC and Network information removed, but still the >>> same failure. I've attached the latest XML that was used in the >>> log's >>> failure as dh-imager01.xml. I've also tried passing hte bridge >>> device >>> (ovirtmgmt) in the above command with same failure results. >>> >>> Node and Engine are both CentOS 6.2, with vdsm-4.10.0-4 and >>> ovirt-engine-3.1 respectively. >>> >>> Please let me know what other configuration information could be >>> helpful to debug / troubleshoot this. >>> >>> Are there any other methods besides a virt-v2v migration that can >>> allow me to use my previous KVM VMs within oVirt? >>> >>> >>> Thanks >>> - Trey >>> >>> >>> >>> ___ >>> Users mailing list >>> Users@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >> >> > > > -- > Matthew Booth, RHCA, RHCSS > Red Hat Engineering, Virtualisation Team > > GPG ID: D33C3490 > GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 > > Attached is the virt-v2v generated ovf that's in my NFS export domain Any other means to get KVM/libvirt/virt-manager based VMs into oVirt? Possibly something as crude as provisioning new VMs with oVirt then replacing the virtual hard drives? >>> >>> this would work - just create the VM on an NFS storage domain with a disk >>> the same size as origin, and copy over the disk you had. >>> a bit trickier for iscsi, so i'd do this with nfs. >>> Thanks - Trey >>> >>> >> >> Why is it trickier with iSCSI? Currently the only Data Center I have >> functioning in oVirt only has iSCSI storage available. >> > > with iscsi, you will have to create the disks as pre-allocated, and use DD > to overwrite them. > NFS doesn't have to be pre-allocated. > and since you are using pre-allocated, you need to use the RAW format iirc > > Currently most of my KVM VMs are qcow2, so converting them to raw would not be a problem. However, why is DD necessary? Why can't I overwrite the .img with my *.img file ? Since I've used mostly qcow2 in my time with KVM/libvirt I may lack some understanding of how to correctly handle raw images. Would a qcow2 image with preallocation=metadata be possible on an iSCSI data store? Thanks - Trey ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Migrating from KVM to oVirt 3.1 fails - corrupt OVF
On 07/20/2012 07:21 PM, Trey Dockendorf wrote: On Fri, Jul 20, 2012 at 3:52 AM, Itamar Heim wrote: On 07/20/2012 02:08 AM, Trey Dockendorf wrote: On Thu, Jul 19, 2012 at 4:00 AM, Matthew Booth wrote: On 18/07/12 23:52, Itamar Heim wrote: On 07/18/2012 06:00 PM, Trey Dockendorf wrote: I'm attempting to fine-tune the process of getting my KVM/Libvirt managed VMs over into my new oVirt infrastructure, and the virt-v2v import is failing in the WUI with "Failed to read VM 'dh-imager01' OVF, it may be corrupted". I've attached both engine and vdsm logs that are a snapshot from when I ran the virt-v2v command until I saw the failure under Events. matt - any thoughts? Nothing springs to mind immediately, but it sounds like v2v is producing an invalid OVF. If somebody can diagnose what the problem with the OVF is I can fix v2v. Matt virt-v2v command used... # virt-v2v -i libvirtxml -o rhev -os dc-vmarchitect.tamu.edu:/exportdomain dh-imager01.xml dh-imager01_sys.qcow2: 100% [===]D 0h00m37s virt-v2v: dh-imager01 configured with virtio drivers. The xml has been modified numerous times based on past mailing list comments to have VNC and Network information removed, but still the same failure. I've attached the latest XML that was used in the log's failure as dh-imager01.xml. I've also tried passing hte bridge device (ovirtmgmt) in the above command with same failure results. Node and Engine are both CentOS 6.2, with vdsm-4.10.0-4 and ovirt-engine-3.1 respectively. Please let me know what other configuration information could be helpful to debug / troubleshoot this. Are there any other methods besides a virt-v2v migration that can allow me to use my previous KVM VMs within oVirt? Thanks - Trey ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 Attached is the virt-v2v generated ovf that's in my NFS export domain Any other means to get KVM/libvirt/virt-manager based VMs into oVirt? Possibly something as crude as provisioning new VMs with oVirt then replacing the virtual hard drives? this would work - just create the VM on an NFS storage domain with a disk the same size as origin, and copy over the disk you had. a bit trickier for iscsi, so i'd do this with nfs. Thanks - Trey Why is it trickier with iSCSI? Currently the only Data Center I have functioning in oVirt only has iSCSI storage available. with iscsi, you will have to create the disks as pre-allocated, and use DD to overwrite them. NFS doesn't have to be pre-allocated. and since you are using pre-allocated, you need to use the RAW format iirc ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Migrating from KVM to oVirt 3.1 fails - corrupt OVF
On Fri, Jul 20, 2012 at 3:52 AM, Itamar Heim wrote: > On 07/20/2012 02:08 AM, Trey Dockendorf wrote: >> >> On Thu, Jul 19, 2012 at 4:00 AM, Matthew Booth wrote: >>> >>> On 18/07/12 23:52, Itamar Heim wrote: On 07/18/2012 06:00 PM, Trey Dockendorf wrote: > > > I'm attempting to fine-tune the process of getting my KVM/Libvirt > managed VMs over into my new oVirt infrastructure, and the virt-v2v > import is failing in the WUI with "Failed to read VM 'dh-imager01' > OVF, it may be corrupted". I've attached both engine and vdsm logs > that are a snapshot from when I ran the virt-v2v command until I saw > the failure under Events. matt - any thoughts? >>> >>> >>> >>> Nothing springs to mind immediately, but it sounds like v2v is producing >>> an >>> invalid OVF. If somebody can diagnose what the problem with the OVF is I >>> can >>> fix v2v. >>> >>> Matt >>> >>> > > virt-v2v command used... > > # virt-v2v -i libvirtxml -o rhev -os > dc-vmarchitect.tamu.edu:/exportdomain dh-imager01.xml > dh-imager01_sys.qcow2: 100% > > > [===]D > > 0h00m37s > virt-v2v: dh-imager01 configured with virtio drivers. > > The xml has been modified numerous times based on past mailing list > comments to have VNC and Network information removed, but still the > same failure. I've attached the latest XML that was used in the log's > failure as dh-imager01.xml. I've also tried passing hte bridge device > (ovirtmgmt) in the above command with same failure results. > > Node and Engine are both CentOS 6.2, with vdsm-4.10.0-4 and > ovirt-engine-3.1 respectively. > > Please let me know what other configuration information could be > helpful to debug / troubleshoot this. > > Are there any other methods besides a virt-v2v migration that can > allow me to use my previous KVM VMs within oVirt? > > > Thanks > - Trey > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > >>> >>> >>> -- >>> Matthew Booth, RHCA, RHCSS >>> Red Hat Engineering, Virtualisation Team >>> >>> GPG ID: D33C3490 >>> GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 >>> >>> >> >> Attached is the virt-v2v generated ovf that's in my NFS export domain >> >> Any other means to get KVM/libvirt/virt-manager based VMs into oVirt? >> Possibly something as crude as provisioning new VMs with oVirt then >> replacing the virtual hard drives? >> > > this would work - just create the VM on an NFS storage domain with a disk > the same size as origin, and copy over the disk you had. > a bit trickier for iscsi, so i'd do this with nfs. > >> Thanks >> - Trey >> > > Why is it trickier with iSCSI? Currently the only Data Center I have functioning in oVirt only has iSCSI storage available. Thanks - Trey ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Error: Cannot attach Storage. Storage Domain doesn't exist.
Hi again! Hmm, very strange, the size LVM reports on the LUN is actually 30 Gb...??? So why doesn't it allow me to create on it? PV VG Fmt Attr PSize PFree /dev/mapper/3600144f09aa180004fd87a31p4 HostVG lvm2 a-- 288.00m0 /dev/mapper/3600144f09aa18000500788c20002p1 HostVG lvm2 a-- 30.00g0 [root@node1 admin]# rgrds Johan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Error: Cannot attach Storage. Storage Domain doesn't exist.
Ohh, I see that I haven't sent to the list, so I do that now
Hi!
Ahaa, I can shed some light here...
This is a part of the log in engine:
2012-07-15 13:46:51,837 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(http--0.0.0.0-8080-3) Vds: node1.hemma.home
2012-07-15 13:46:51,837 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase]
(http--0.0.0.0-8080-3) Command CreateVGVDS execution failed. Exception:
VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand
to CreateVGVDS, error = Volume Group not big enough: ('VG size must be more
than 10240 MiB',)
2012-07-15 13:46:51,837 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVGVDSCommand]
(http--0.0.0.0-8080-3) FINISH, CreateVGVDSCommand, log id: da915ec
2012-07-15 13:46:51,838 ERROR
[org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand]
(http--0.0.0.0-8080-3) Command
org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand throw Vdc Bll
exception. With error message VdcBLLException:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
VDSGenericException: VDSErrorException: Failed in vdscommand to CreateVGVDS,
error = Volume Group not big enough: ('VG size must be more than 10240 MiB',)
2012-07-15 13:46:51,859 INFO
[org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand]
(http--0.0.0.0-8080-3) Command [id=db9901fd-9f2d-4298-88d9-70dd898fa4bd]:
Compensating NEW_ENTITY_ID of
org.ovirt.engine.core.common.businessentities.storage_domain_dynamic; snapshot:
ae76ccdb-e920-436c-b623-09d5e3db3acd.
2012-07-15 13:46:51,869 INFO
[org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand]
(http--0.0.0.0-8080-3) Command [id=db9901fd-9f2d-4298-88d9-70dd898fa4bd]:
Compensating NEW_ENTITY_ID of
org.ovirt.engine.core.common.businessentities.storage_domain_static; snapshot:
ae76ccdb-e920-436c-b623-09d5e3db3acd.
2012-07-15 13:46:51,890 ERROR
[org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand]
(http--0.0.0.0-8080-3) Transaction rolled-back for command:
org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand.
2012-07-15 13:46:52,049 WARN
[org.ovirt.engine.core.bll.storage.AttachStorageDomainToPoolCommand]
(http--0.0.0.0-8080-3) CanDoAction of action AttachStorageDomainToPool failed.
Reasons:VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ATTACH,ACTION_TYPE_FAILED_STORAGE_DOMAIN_NOT_EXIST
And the important part is that it say`s that "error = Volume Group not big
enough: ('VG size must be more than 10240 MiB',)"
The LUN I created is a qcow2-LUN of 50 Gb size, which of coarse doesn't have
the size of 50 Gb, because it is a thin provisioned LUN.
So question is then: Doesn't oVirt support thin provisioned LUN's? If not, it
is not very good, because most SAN's provide thin provisioned LUN's nowaday's...
This is perhaps a limitation of LVM2? It would be a real setback to not be able
to use qcow2, though
Regards Johan
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt-engine upgrade 3.0 to 3.1 issue
Any thoughts here on this, should I file a bug?
Per: http://wiki.ovirt.org/wiki/Second_Release
Working upgrade is one of the release criteria.
I will help in any way possible to get a 3.0 to 3.1 upgrade path working.
- DHC
On Thu, Jul 19, 2012 at 3:40 PM, Dead Horse
wrote:
> If it helps here is the contents of "upgrade.sh.log":
>
> * QUERY **
> create or replace function __temp_fn_create_schema_version ()
> returns void
> AS $procedure$
> begin
> if not exists (select 1 from information_schema.tables where table_name =
> 'schema_version') then
> CREATE SEQUENCE schema_version_seq INCREMENT BY 1 START WITH 1;
> CREATE TABLE schema_version
> (
> id INTEGER DEFAULT NEXTVAL('schema_version_seq') NOT NULL,
> "version" varchar(10) NOT NULL,
> script varchar(255) NOT NULL,
> checksum varchar(128),
> installed_by varchar(30) NOT NULL,
> started_at timestamp DEFAULT now(),
> ended_at timestamp ,
> state character varying(15) NOT NULL,
> "current" boolean NOT NULL,
> CONSTRAINT schema_version_primary_key PRIMARY KEY (id)
> );
>
> insert into
> schema_version(version,script,checksum,installed_by,ended_at,state,current)
> values
> ('0300','upgrade/03_00__add_schema_version.sql','0','postgres',now(),'INSTALLED',true);
> end if;
>
> END; $procedure$
> LANGUAGE plpgsql;
> **
>
> CREATE FUNCTION
> * QUERY **
> select __temp_fn_create_schema_version();
> **
>
>
>
> * QUERY **
> DROP FUNCTION __temp_fn_create_schema_version();
> **
>
> DROP FUNCTION
> * QUERY **
> CREATE OR REPLACE FUNCTION __temp_Upgrade_add_job_table()
> RETURNS void
> AS $function$
> BEGIN
>IF NOT EXISTS (SELECT * FROM information_schema.tables WHERE table_name
> ILIKE 'job') THEN
>
>-- Add the job table.
>
>CREATE TABLE job
>(
> job_id UUID NOT NULL,
> action_type VARCHAR(50) NOT NULL,
> description TEXT NOT NULL,
> status VARCHAR(32) NOT NULL,
> owner_id UUID,
> visible BOOLEAN NOT NULL DEFAULT true,
> start_time TIMESTAMP WITH TIME ZONE NOT NULL,
> end_time TIMESTAMP WITH TIME ZONE default NULL,
> last_update_time TIMESTAMP WITH TIME ZONE default NULL,
> correlation_id VARCHAR(50) NOT NULL,
> CONSTRAINT pk_jobs PRIMARY KEY(job_id)
>)
>WITH OIDS;
>
>END IF;
> END; $function$
> LANGUAGE plpgsql;
> **
>
> CREATE FUNCTION
> * QUERY **
> SELECT * FROM __temp_Upgrade_add_job_table();
> **
>
>
>
> * QUERY **
> DROP FUNCTION __temp_Upgrade_add_job_table();
> **
>
> DROP FUNCTION
> * QUERY **
> insert into
> schema_version(version,script,checksum,installed_by,started_at,ended_at,state,current,comment)
> values
> (trim('03010260'),'upgrade/03_01_0260_add_job_table.sql','c74d309cfb8f9d802e54f2ff66d560b4','postgres',
> cast(trim(' 2012-07-19 15:30:52.500231-05') as
> timestamp),cast(trim(' 2012-07-19 15:30:52.565532-05') as
> timestamp),'INSTALLED',false,'');
> **
>
> * QUERY **
> create or replace function __temp_fn_create_schema_version ()
> returns void
> AS $procedure$
> begin
> if not exists (select 1 from information_schema.tables where table_name =
> 'schema_version') then
> CREATE SEQUENCE schema_version_seq INCREMENT BY 1 START WITH 1;
> CREATE TABLE schema_version
> (
> id INTEGER DEFAULT NEXTVAL('schema_version_seq') NOT NULL,
> "version" varchar(10) NOT NULL,
> script varchar(255) NOT NULL,
> checksum varchar(128),
> installed_by varchar(30) NOT NULL,
> started_at timestamp DEFAULT now(),
> ended_at timestamp ,
> state character varying(15) NOT NULL,
> "current" boolean NOT NULL,
> CONSTRAINT schema_version_primary_key PRIMARY KEY (id)
> );
>
> insert into
> schema_version(version,script,checksum,installed_by,ended_at,state,current)
> values
> ('0300','upgrade/03_00__add_schema_version.sql','0','postgres',now(),'INSTALLED',true);
> end if;
>
> END; $procedure$
> LANGUAGE plpgsql;
> **
>
> CREATE FUNCTION
> * QUERY **
> select __temp_fn_create_schema_version();
> **
>
>
>
> * QUERY **
> DROP FUNCTION __temp_fn_create_schema_version();
> **
>
> DROP FUNCTION
> * QUERY **
> CREATE OR REPLACE FUNCTION __temp_Upgrade_add_job_table()
> RETURNS void
> AS $function$
> BEGIN
>IF NOT EXISTS (SELECT * FROM information_schema.tables WHERE table_name
> ILIKE 'job') THEN
>
>-- Add the job table.
>
>CREATE TABLE job
>(
> job_id UUID NOT NULL,
> action_type VARCHAR(50) NOT NULL,
> de
Re: [Users] Migrating from KVM to oVirt 3.1 fails - corrupt OVF
On 07/20/2012 02:08 AM, Trey Dockendorf wrote: On Thu, Jul 19, 2012 at 4:00 AM, Matthew Booth wrote: On 18/07/12 23:52, Itamar Heim wrote: On 07/18/2012 06:00 PM, Trey Dockendorf wrote: I'm attempting to fine-tune the process of getting my KVM/Libvirt managed VMs over into my new oVirt infrastructure, and the virt-v2v import is failing in the WUI with "Failed to read VM 'dh-imager01' OVF, it may be corrupted". I've attached both engine and vdsm logs that are a snapshot from when I ran the virt-v2v command until I saw the failure under Events. matt - any thoughts? Nothing springs to mind immediately, but it sounds like v2v is producing an invalid OVF. If somebody can diagnose what the problem with the OVF is I can fix v2v. Matt virt-v2v command used... # virt-v2v -i libvirtxml -o rhev -os dc-vmarchitect.tamu.edu:/exportdomain dh-imager01.xml dh-imager01_sys.qcow2: 100% [===]D 0h00m37s virt-v2v: dh-imager01 configured with virtio drivers. The xml has been modified numerous times based on past mailing list comments to have VNC and Network information removed, but still the same failure. I've attached the latest XML that was used in the log's failure as dh-imager01.xml. I've also tried passing hte bridge device (ovirtmgmt) in the above command with same failure results. Node and Engine are both CentOS 6.2, with vdsm-4.10.0-4 and ovirt-engine-3.1 respectively. Please let me know what other configuration information could be helpful to debug / troubleshoot this. Are there any other methods besides a virt-v2v migration that can allow me to use my previous KVM VMs within oVirt? Thanks - Trey ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 Attached is the virt-v2v generated ovf that's in my NFS export domain Any other means to get KVM/libvirt/virt-manager based VMs into oVirt? Possibly something as crude as provisioning new VMs with oVirt then replacing the virtual hard drives? this would work - just create the VM on an NFS storage domain with a disk the same size as origin, and copy over the disk you had. a bit trickier for iscsi, so i'd do this with nfs. Thanks - Trey ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Install ovirt on EC2.
On 07/20/2012 05:22 AM, Steve Gordon wrote: - Original Message - From: "Itamar Heim" To: jdbjun...@gmail.com Cc: users@ovirt.org Sent: Wednesday, July 18, 2012 5:51:18 AM Subject: Re: [Users] Install ovirt on EC2. On 07/18/2012 08:22 AM, jdbjun...@gmail.com wrote: For those of you testing ovirt. Is it possible to configure all of it using amazon ec2? And if possible, is there any public AMI preconfigured at amazon nowadays that one could use to get up and running easily. I'm unsure about the need of having a physical machine to try ovirt out. (or use amazon ec2/linode) you could run the engine on EC2. but you can run guests on it (unless you use fake qemu, which will launch fake guests). there isn't currently an AMI I did actually build and provide an Engine AMI for one of our very early builds (even before the first formal release) which I blogged about [1] but I didn't end up doing a new one for the actual release. If there is interest I guess I could probably do it again, but without hosts somewhere to actually run VMs it's a very limited look at the engine. Especially with the new 'all in one' mode meaning with even just one host with virt extensions you can get some VMs up and running. Steve [1] http://rainhilltrials.blogspot.ca/2011/11/testing-ovirt-engine-on-amacon-ec2.html well, for someone to just play around to get an impression of capabilities, you could: 1. yum install vdsm vdsm-hook-faqemu ovirt-setup ovirt-engine ovirt-engine-setup-plugin-allinone 2. edit /etc/vdsm/vdsm.conf and set vars.fake_kvm_support=True 3. run ovirt-engine-setup this should get you an all-in-one node in a guest, which you can do everything with, including creating and running virtual machines (fake one, which won't really run). ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Unable to run VM with ”opening backend ‘pyt’ failed”
On 07/20/2012 10:20 AM, xuejie chen wrote: > 2012/7/17 Martin Kletzander : >> On 07/17/2012 02:41 AM, Mark Wu wrote: >>> On 07/16/2012 09:46 AM, xuejie chen wrote: >>> file="/rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259 >>> Please upgrade vdsm to 4.10.0 as Dan suggested above. If the problem >>> still exists, please: >>> >>> check the owner and permission of that image file: >>> >>> ls -l >>> /rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259/9c728c1d-762e-4670-9076-9ca5a37b6354 >>> >>> Run "setenforce 0" to disable selinux and see if it helps: >>> >> >> As Mark pointed out, checking the permissions should be enough, so >> "ls -lZ" will do. I don't know if "Local on host" means exactly what I >> think, but in case it's not managed using vdsm, that directory may need >> to me mounted from somewhere, libvirt itself doesn't do that (unless >> it's in network filesystem pool). > > I checked the owner of that image file is vdsm. > But I found the user of qemu-kvm is root. > So I modified the qemu.conf and set user to qemu. This modification shouldn't be necessary as the binary packages are compiled with this setting usually. However, in case you used some yourself-built package, that might have caused the config change (happens to me with compiled packages from repo. Martin ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Unable to run VM with ”opening backend ‘pyt’ failed”
2012/7/17 Martin Kletzander : > On 07/17/2012 02:41 AM, Mark Wu wrote: >> On 07/16/2012 09:46 AM, xuejie chen wrote: >>> >> file="/rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259 >> Please upgrade vdsm to 4.10.0 as Dan suggested above. If the problem >> still exists, please: >> >> check the owner and permission of that image file: >> >> ls -l >> /rhev/data-center/2d7df94d-738d-4d7d-97a4-dd5027a4bf25/d3267b58-cbbd-4e6e-8685-8acd152d49a1/images/7e1011e0-d0ac-4c1f-bd09-a19e450c3259/9c728c1d-762e-4670-9076-9ca5a37b6354 >> >> Run "setenforce 0" to disable selinux and see if it helps: >> > > As Mark pointed out, checking the permissions should be enough, so > "ls -lZ" will do. I don't know if "Local on host" means exactly what I > think, but in case it's not managed using vdsm, that directory may need > to me mounted from somewhere, libvirt itself doesn't do that (unless > it's in network filesystem pool). I checked the owner of that image file is vdsm. But I found the user of qemu-kvm is root. So I modified the qemu.conf and set user to qemu. The problem disappeared. Thanks a lot Xuejie Chen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] "Error: Cannot attach Storage. Storage Domain doesn't exist."
On 07/19/2012 07:35 PM, Johan Kragsterman wrote: Hi all! This is my first post to this list. I set up a fedora16 HV, and an oVirt engine on fedora 16, both booted and installed on fibre channel storage. Everything works fine, shows up in web gui on engine, host discovered and active, until that I try to attach storage. Then I get this message: "Error: Cannot attach Storage. Storage Domain doesn't exist." Same as in the post: "iSCSI discovery not showing all LUNs - oVirt 3.14", also this month. In that post discuss if LUN's are dirty or not. My LUN's are not dirty. I checked that by removing the data LUN, removing the LUN mapping creating a new LUN I didn't use(so the new LUN I will use didn't use something of the old one), and finally creating a new LUN of different size. Same result with that LUN when I try to use it as storage domain: "Error: Cannot attach Storage. Storage Domain doesn't exist." I was reading the enclosed vdsm-log of the message: "iSCSI discovery not showing all LUNs - oVirt 3.14" Hi Johan, could you please try to attach the vdsm log again? I don't have it attached in this mail. Thanks, Kuba The log was a lot about MPIO, if I understood right. Could it be that the MPIO driver isn't discover a dual path, only a single path? Right now I don't have an fc switch, so I am unable to test if that would solve the problem. Anyone have any suggestions? Regards Johan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
