- Original Message -
> From: "Md Akther Hossain Khan"
> To: users@ovirt.org
> Sent: Sunday, February 10, 2013 5:06:10 PM
> Subject: [Users] VM Console Issue.
> Dear All,
> I am new in this forum.
> I have installed Ovirt 3.1 successfully.
> As per I have done the following tasks:
> 1. A
On Feb 10, 2013, at 20:18 , Rocky wrote:
> Hi,
>
> Today after I reinstalled my hypvervisors I just got 15MB of RAM inside
> my guests. I hade this problem on one of my hypervisors before but if I
> started the VMs on the other hypervisors and then migrate the VM to the
> "faulty" hypervisor al
Hi Michael,
I think I have missunderstod something deeply.
After my reinstall of the hypervisors I got "The guest virtual machine
cannot be started: internal error guest CPU is not compatible with
host CPU" when trying to run a VM. So I found the Fake package and
after I have restarted vdsmd on t
Thanks Frankel,
We added ISO/NFS Domain & Storage Domain from Disk Tab.
Meanwhile we attached the CD which we uploaded by (engine-iso-uploader
upload -i cloud12 Centos_6.3_64bit.iso) this command.
But @ VNC console it shows nothing but a black window.
On Mon, Feb 11, 2013 at 2:17 PM, Omer Fre
I'm struggeling setting up my network in oVirt at the moment as I would
like to seperate specific VM's from other devices/clients in my network.
I have decent setup switching network using Vlans, this is also the fact
for ovirt and the storage nodes where teh ports are seperated between
storage an
On Feb 11, 2013, at 11:09 , Ricky wrote:
> Hi Michael,
>
> I think I have missunderstod something deeply.
>
> After my reinstall of the hypervisors I got "The guest virtual machine
> cannot be started: internal error guest CPU is not compatible with
> host CPU" when trying to run a VM. So I fo
- Original Message -
> From: "Md Akther Hossain Khan"
> To: "Omer Frenkel"
> Cc: users@ovirt.org
> Sent: Monday, February 11, 2013 12:32:24 PM
> Subject: Re: [Users] VM Console Issue.
> Thanks Frankel,
> We added ISO/NFS Domain & Storage Domain from Disk Tab.
> Meanwhile we attached th
Le 09/02/2013 11:26, Nicolas Ecarnot a écrit :
Le 08/02/2013 21:54, Richard W.M. Jones a écrit :
On Thu, Feb 07, 2013 at 04:48:13PM +0100, Nicolas Ecarnot wrote:
Hi,
After having successfully migrated Debian, XP, 2003, 2008 VMs, I'm
stuck with a migration I was expecting to be easy : RHAS3.
H
Thanks Frenkel.
I have attached the vm creation log of VDSM.
On Mon, Feb 11, 2013 at 4:47 PM, Omer Frenkel wrote:
>
>
> --
>
> *From: *"Md Akther Hossain Khan"
> *To: *"Omer Frenkel"
> *Cc: *users@ovirt.org
> *Sent: *Monday, February 11, 2013 12:32:24 PM
> *Subjec
On Sun, Feb 10, 2013 at 05:07:08PM +0100, Matt . wrote:
>
> 2013/2/10 Shahar Havivi
>
> > On 10.02.13 16:36, Matt . wrote:
> > > Hi,
> > >
> > > I'm thinking about the way how I did that with the dedicated NIC to the
> > VM.
> > > I was discussing this a couple of months ago on IRC but I can't r
> I found the issue, there is a little icon of a pencil that you need
> to click on in order to specify what IP you want the connection to
> use. Once I did that it worked perfectly.
>
> Also, I noticed that the interface for assigning virtual networks to
> physical interfaces does NOT work corre
Matt,
I attached a hook that will give you a kick start on the promisc mode,
it implemented only the mirror mode which is a part of vdsm now but you can
look at the comments and the README file that have the appropriate in-line mode
commands and implementation.
Shahar Havivi.
On 10.02.13 17:07, M
Le 11/02/2013 11:47, Nicolas Ecarnot a écrit :
This issue looks very similar to what is discussed here:
https://bugzilla.redhat.com/show_bug.cgi?id=816930
I'm so sorry to debug that issue in a so crappy manner, but I have to
keep going.
I just commented out "_configure_boot($kernel, $virtio
Hi Stephen,
Just to be clear: there is a moderation queue for wiki accounts, but we
hand those things out completely freely - it is purely an anti-spam measure.
Head on over to http://www.ovirt.org/Special:RequestAccount and I will
approve your request ASAP!
Thanks,
Dave.
On 02/08/2013 09:
On Fri, 2013-02-08 at 20:54 +, Richard W.M. Jones wrote:
> On Thu, Feb 07, 2013 at 04:48:13PM +0100, Nicolas Ecarnot wrote:
> > Hi,
> >
> > After having successfully migrated Debian, XP, 2003, 2008 VMs, I'm
> > stuck with a migration I was expecting to be easy : RHAS3.
> >
> > Here is the err
Hi,
I find it hard to find any information about the way I have to follow to
convert/import a vmdk/qcow/raw/etc... single disk into an oVirt disks list.
I know how to use virt-v2v to import complete VMs (disk AND config), but
don't know how to handle a single data disk.
Regards,
--
Nicolas
On Mon, Feb 11, 2013 at 3:07 PM, Matthew Booth wrote:
> I'd need to know exactly which version of virt-v2v you're running in
at the beginning of this same thread, after I asked the same thing, on
Feb 8th Nicolas wrote:
- Fedora 17 64 bits
- virt-v2v.x86_64version 0.8.8-1.fc17
- every ovirt c
On 02/08/2013 11:45 AM, Yair Zaslavsky wrote:
- Original Message -
From: "Jorick Astrego"
To: users@ovirt.org
Sent: Friday, February 8, 2013 6:07:50 PM
Subject: [Users] rhevm_admin_password = engine_admin_password ?
Hi,
Just a quick question. I have PXE boot setup correctly now and
On 02/11/2013 06:11 PM, Mike Burns wrote:
On 02/08/2013 11:45 AM, Yair Zaslavsky wrote:
- Original Message -
From: "Jorick Astrego"
To: users@ovirt.org
Sent: Friday, February 8, 2013 6:07:50 PM
Subject: [Users] rhevm_admin_password = engine_admin_password ?
Hi,
Just a quick questio
Hello,
connecting to ovirt 3.2 beta from F17 with firefox-18.0-1.fc17.x86_64 I receive
This Browser version isn't optimal for displaying the application
graphics (refer to Documentation for details)
How is the check made to show or not the warning?
What is the current status of supported browsers
On 02/12/2013 11:32 AM, Gianluca Cecchi wrote:
Hello,
connecting to ovirt 3.2 beta from F17 with firefox-18.0-1.fc17.x86_64 I receive
This Browser version isn't optimal for displaying the application
graphics (refer to Documentation for details)
How is the check made to show or not the warning?
21 matches
Mail list logo