- Original Message -
> From: "Gianluca Cecchi"
> To: "Martin Sivak"
> Cc: "Dan Kenigsberg" , "users" ,
> mpriv...@redhat.com, "Gilad Chaplik"
>
> Sent: Friday, September 26, 2014 12:11:09 PM
> Subject: Re: [ovirt-u
On Fri, Sep 26, 2014 at 10:56 AM, Martin Sivak wrote:
> Hi,
>
> I think the default was changed to INTERLEAVE, because that is the value I
> see everywhere as preselected in the current 3.5 code.
>
> This is the logic that governs if the select boxes are enabled:
>
> if (getModel().getMigrationMo
Hi,
I think the default was changed to INTERLEAVE, because that is the value I see
everywhere as preselected in the current 3.5 code.
This is the logic that governs if the select boxes are enabled:
if (getModel().getMigrationMode().getSelectedItem() !=
MigrationSupport.PINNED_TO_HOST ||
On Thu, Sep 25, 2014 at 10:52 PM, Gianluca Cecchi wrote:
> On Thu, Sep 25, 2014 at 8:38 PM, Martin Sivak wrote:
>
>> Hi Gianluca,
>>
>> I see the numa mode select box in the Host sub-tab of the VM edit dialog.
>>
>> It was committed three days ago to the 3.5 branch so it should be
>> available i
On Thu, Sep 25, 2014 at 8:38 PM, Martin Sivak wrote:
> Hi Gianluca,
>
> I see the numa mode select box in the Host sub-tab of the VM edit dialog.
>
> It was committed three days ago to the 3.5 branch so it should be
> available in the 3.5 GA release I think. I am not exactly sure if it made
> the
Hi Gianluca,
I see the numa mode select box in the Host sub-tab of the VM edit dialog.
It was committed three days ago to the 3.5 branch so it should be available in
the 3.5 GA release I think. I am not exactly sure if it made the RC3 build
though.
http://gerrit.ovirt.org/#/q/I05b83028b722088e
Hello,
my suspect was correct.
I found some reference here about possible values:
http://www.ovirt.org/Features/Detailed_NUMA_and_Virtual_NUMA
so I made this
[root@ovirtmgr ~]# cat numa_tune.xml
interleave
[root@ovirtmgr ~]# curl --insecure -u "admin@internal:my_password" -H
"Content-type: appli
On Thu, Sep 25, 2014 at 1:38 PM, Gianluca Cecchi
wrote:
> On Thu, Sep 25, 2014 at 1:01 PM, Dan Kenigsberg wrote:
>
>>
>>
>> Clearly, there's a libvirt bug here. Maybe Michal and Martin (CC) can
>> help with it. I suspect that your `virsh capabilities` and the domxml
>> you're trying to start, w
On Thu, Sep 25, 2014 at 1:01 PM, Dan Kenigsberg wrote:
>
>
> Clearly, there's a libvirt bug here. Maybe Michal and Martin (CC) can
> help with it. I suspect that your `virsh capabilities` and the domxml
> you're trying to start, would assist him.
>
at this moment I have no access through the gu
On Thu, Sep 25, 2014 at 10:29:08AM +0200, Gianluca Cecchi wrote:
> In /var/log/libvirt/qemu/vm_name.log I find the information below
>
> BTW: how to eliminate 2hr offset in timestamp of libvrt logs?
> Time was 01:58 but in this file I see 23:58...
You can move to a country that uses UTC as its l
In /var/log/libvirt/qemu/vm_name.log I find the information below
BTW: how to eliminate 2hr offset in timestamp of libvrt logs?
Time was 01:58 but in this file I see 23:58...
2014-09-24 23:58:20.162+: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU
On Thu, Sep 25, 2014 at 1:58 AM, Gianluca Cecchi
wrote:
> Hello,
> after upgrading engine and hypervisor to rc3 I get this message when
> trying to start VM:
>
> VM vm_name is down with error. Exit message: internal error internal error
> NUMA memory tuning in 'preferred' mode only supports singl
Hello,
after upgrading engine and hypervisor to rc3 I get this message when trying
to start VM:
VM vm_name is down with error. Exit message: internal error internal error
NUMA memory tuning in 'preferred' mode only supports single node.
hypervisor is Intel blade MFS5520VI with
processor: 15
13 matches
Mail list logo
