2:46 p.m.
Hi all,
I am running a 3 node ovirt 4.1 selft hosted setup.
I have consistently observed that windows 10 VMs with SPICE console fail to
live migrate. Other VMs (windows server 2016) do migrate normally.
VDSM log indicates:
internal error: unable to execute QEMU command 'migrate': qxl: guest bug:
command not in ram bar (migration:287)
2018-02-18 11:41:59,586+0000 ERROR (migsrc/2cf3a254) [virt.vm]
(vmId='2cf3a254-8450-44cf-b023-e0a49827dac0') Failed to migrate
(migration:429)
if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed',
dom=self)
libvirtError: internal error: unable to execute QEMU command 'migrate':
qxl: guest bug: command not in ram bar
Seems as a guest agent bug for Windows 10? Is there any fix?
Thanx,
Alex
2:53 p.m.
Seems that this is due to:
https://bugzilla.redhat.com/show_bug.cgi?id=1446147
I will check If i can find newer guest agents.
On Sun, Feb 18, 2018 at 1:46 PM, Alex K <rightkicktech(a)gmail.com> wrote:
Hi all,
I am running a 3 node ovirt 4.1 selft hosted setup.
I have consistently observed that windows 10 VMs with SPICE console fail
to live migrate. Other VMs (windows server 2016) do migrate normally.
VDSM log indicates:
internal error: unable to execute QEMU command 'migrate': qxl: guest bug:
command not in ram bar (migration:287)
2018-02-18 11:41:59,586+0000 ERROR (migsrc/2cf3a254) [virt.vm]
(vmId='2cf3a254-8450-44cf-b023-e0a49827dac0') Failed to migrate
(migration:429)
if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed',
dom=self)
libvirtError: internal error: unable to execute QEMU command 'migrate':
qxl: guest bug: command not in ram bar
Seems as a guest agent bug for Windows 10? Is there any fix?
Thanx,
Alex
3:09 p.m.
I see that the latest guest tools for 4.1 are dated 27-04-2017.
http://resources.ovirt.org/pub/ovirt-4.1/iso/oVirt-toolsSetup/
http://resources.ovirt.org/pub/ovirt-4.2/iso/oVirt-toolsSetup/4.2-1.el7.c...
Can I use the tools from 4.2 at and install them at Windows VMs running on
top 4.1?
Thanx,
Alex
On Sun, Feb 18, 2018 at 1:53 PM, Alex K <rightkicktech(a)gmail.com> wrote:
Seems that this is due to:
https://bugzilla.redhat.com/show_bug.cgi?id=1446147
I will check If i can find newer guest agents.
On Sun, Feb 18, 2018 at 1:46 PM, Alex K <rightkicktech(a)gmail.com> wrote:
> Hi all,
>
> I am running a 3 node ovirt 4.1 selft hosted setup.
> I have consistently observed that windows 10 VMs with SPICE console fail
> to live migrate. Other VMs (windows server 2016) do migrate normally.
>
> VDSM log indicates:
>
> internal error: unable to execute QEMU command 'migrate': qxl: guest bug:
> command not in ram bar (migration:287)
> 2018-02-18 11:41:59,586+0000 ERROR (migsrc/2cf3a254) [virt.vm]
> (vmId='2cf3a254-8450-44cf-b023-e0a49827dac0') Failed to migrate
> (migration:429)
> if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed',
> dom=self)
> libvirtError: internal error: unable to execute QEMU command 'migrate':
> qxl: guest bug: command not in ram bar
>
> Seems as a guest agent bug for Windows 10? Is there any fix?
>
> Thanx,
> Alex
>
5:25 p.m.
--Apple-Mail=_5717A820-FDA3-454E-8943-1F7473E17809
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
On 18 Feb 2018, at 13:09, Alex K <rightkicktech(a)gmail.com>
wrote:
=20
I see that the latest guest tools for 4.1 are dated 27-04-2017.=20
=20
http://resources.ovirt.org/pub/ovirt-4.1/iso/oVirt-toolsSetup/ =
<http://resources.ovirt.org/pub/ovirt-4.1/iso/oVirt-toolsSetup/>
=20
=
http://resources.ovirt.org/pub/ovirt-4.2/iso/oVirt-toolsSetup/4.2-1.el7.ce=
ntos/ =
<http://resources.ovirt.org/pub/ovirt-4.2/iso/oVirt-toolsSetup/4.2-1.el7.c=
entos/>
=20
Can I use the tools from 4.2 at and install them at Windows VMs =
running on top
4.1?=20
yes you can, tools are compatible and it almost always makes sense to =
run latest regardless what=E2=80=99s your ovirt cluster version
=20
Thanx,=20
Alex
=20
On Sun, Feb 18, 2018 at 1:53 PM, Alex K <rightkicktech(a)gmail.com =
<mailto:rightkicktech@gmail.com>> wrote:
Seems that this is due to:=20
=20
https://bugzilla.redhat.com/show_bug.cgi?id=3D1446147 =
<https://bugzilla.redhat.com/show_bug.cgi?id=3D1446147>
=20
I will check If i can find newer guest agents.=20
=20
On Sun, Feb 18, 2018 at 1:46 PM, Alex K <rightkicktech(a)gmail.com =
<mailto:rightkicktech@gmail.com>> wrote:
Hi all,=20
=20
I am running a 3 node ovirt 4.1 selft hosted setup.=20
I have consistently observed that windows 10 VMs with SPICE console =
fail to live
migrate. Other VMs (windows server 2016) do migrate =
normally.=20
=20
VDSM log indicates:=20
=20
internal error: unable to execute QEMU command 'migrate': qxl: guest =
bug:
command not in ram bar (migration:287)
2018-02-18 11:41:59,586+0000 ERROR (migsrc/2cf3a254) [virt.vm] =
(vmId=3D'2cf3a254-8450-44cf-b023-e0a49827dac0') Failed to migrate =
(migration:429)
if ret =3D=3D -1: raise libvirtError
('virDomainMigrateToURI3() =
failed', dom=3Dself)
libvirtError: internal error: unable to execute QEMU command =
'migrate': qxl: guest bug: command not in ram bar
=20
Seems as a guest agent bug for Windows 10? Is there any fix?
=20
Thanx,=20
Alex
=20
=20
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_5717A820-FDA3-454E-8943-1F7473E17809
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type"
content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"
class=3D""><br =
class=3D""><div><br class=3D""><blockquote
type=3D"cite" class=3D""><div =
class=3D"">On 18 Feb 2018, at 13:09, Alex K <<a =
href=3D"mailto:rightkicktech@gmail.com" =
class=3D"">rightkicktech(a)gmail.com</a>&gt; wrote:</div><br
=
class=3D"Apple-interchange-newline"><div class=3D""><div
dir=3D"ltr" =
class=3D""><div class=3D""><div
class=3D""><div class=3D"">I see that =
the latest guest tools for 4.1 are dated 27-04-2017. <br =
class=3D""></div><br class=3D""><a =
href=3D"http://resources.ovirt.org/pub/ovirt-4.1/iso/oVirt-toolsSetu... =
class=3D"">http://resources.ovirt.org/pub/ovirt-4.1/iso/oVir...
/a><br class=3D""><br class=3D""><a =
href=3D"http://resources.ovirt.org/pub/ovirt-4.2/iso/oVirt-toolsSetu...
1.el7.centos/" =
class=3D"">http://resources.ovirt.org/pub/ovirt-4.2/iso/oVir...
.2-1.el7.centos/</a><br class=3D""><br class=3D"">
Can I use the tools from 4.2 at and install them at Windows VMs running =
on top 4.1?
<br
class=3D""></div></div></div></div></blockquote><div><br
=
class=3D""></div>yes you can, tools are compatible and it almost always
=
makes sense to run latest regardless what=E2=80=99s your ovirt cluster =
version</div><div><br class=3D""><blockquote
type=3D"cite" class=3D""><div=
class=3D""><div dir=3D"ltr" class=3D""><div
class=3D""><div =
class=3D""><br class=3D""></div>Thanx, <br
class=3D""></div>Alex<br =
class=3D""></div><div class=3D"gmail_extra"><br
class=3D""><div =
class=3D"gmail_quote">On Sun, Feb 18, 2018 at 1:53 PM, Alex K <span =
dir=3D"ltr" class=3D""><<a
href=3D"mailto:rightkicktech@gmail.com" =
target=3D"_blank"
class=3D"">rightkicktech(a)gmail.com</a>&gt;</span> =
wrote:<br class=3D""><blockquote class=3D"gmail_quote"
style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div
dir=3D"ltr" =
class=3D""><div class=3D"">Seems that this is due to: <br
class=3D""><br =
class=3D""><a
href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D144614=
7" target=3D"_blank"
class=3D"">https://bugzilla.redhat.com/<wbr =
class=3D"">show_bug.cgi?id=3D1446147</a><br
class=3D""><br =
class=3D""></div>I will check If i can find newer guest agents. <br
=
class=3D""></div><div class=3D"HOEnZb"><div
class=3D"h5"><div =
class=3D"gmail_extra"><br class=3D""><div
class=3D"gmail_quote">On Sun, =
Feb 18, 2018 at 1:46 PM, Alex K <span dir=3D"ltr"
class=3D""><<a =
href=3D"mailto:rightkicktech@gmail.com" target=3D"_blank" =
class=3D"">rightkicktech(a)gmail.com</a>&gt;</span>
wrote:<br =
class=3D""><blockquote class=3D"gmail_quote"
style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr" =
class=3D""><div class=3D""><div
class=3D""><div class=3D""><div =
class=3D""><div class=3D"">Hi all, <br
class=3D""><br =
class=3D""></div><div class=3D"">I am running a 3 node
ovirt 4.1 selft =
hosted setup. <br class=3D""></div>I have consistently observed that
=
windows 10 VMs with SPICE console fail to live migrate. Other VMs =
(windows server 2016) do migrate normally. <br class=3D""><br =
class=3D""></div>VDSM log indicates: <br
class=3D""><br class=3D""><span =
style=3D"font-family:monospace,monospace" class=3D"">internal
error: =
unable to execute QEMU command 'migrate': qxl: guest bug: command not in =
ram bar (migration:287)<br class=3D"">2018-02-18 11:41:59,586+0000 ERROR
=
(migsrc/2cf3a254) [virt.vm] (vmId=3D'2cf3a254-8450-44cf-b023<wbr =
class=3D"">-e0a49827dac0') Failed to migrate (migration:429)<br =
class=3D""> if ret =3D=3D -1: raise
libvirtError =
('virDomainMigrateToURI3() failed', dom=3Dself)<br =
class=3D"">libvirtError: internal error: unable to execute QEMU command =
'migrate': qxl: guest bug: command not in ram bar</span><br
class=3D""><br=
class=3D""></div>Seems as a guest agent bug for Windows 10? Is there
=
any fix?<br class=3D""><br class=3D""></div>Thanx,
<br =
class=3D""></div>Alex<br class=3D""></div>
</blockquote></div><br class=3D""></div>
</div></div></blockquote></div><br
class=3D""></div>
_______________________________________________<br class=3D"">Users =
mailing list<br class=3D""><a href=3D"mailto:Users@ovirt.org"
=
class=3D"">Users(a)ovirt.org</a><br =
class=3D"">http://lists.ovirt.org/mailman/listinfo/users<br =
class=3D""></div></blockquote></div><br
class=3D""></body></html>=
--Apple-Mail=_5717A820-FDA3-454E-8943-1F7473E17809--
8:50 p.m.
On Sun, Feb 18, 2018 at 4:25 PM, Michal Skrivanek <
michal.skrivanek(a)redhat.com> wrote:
On 18 Feb 2018, at 13:09, Alex K <rightkicktech(a)gmail.com> wrote:
I see that the latest guest tools for 4.1 are dated 27-04-2017.
http://resources.ovirt.org/pub/ovirt-4.1/iso/oVirt-toolsSetup/
http://resources.ovirt.org/pub/ovirt-4.2/iso/oVirt-
toolsSetup/4.2-1.el7.centos/
Can I use the tools from 4.2 at and install them at Windows VMs running on
top 4.1?
yes you can, tools are compatible and it almost always makes sense to run
latest regardless what’s your ovirt cluster version
Great!. I will try those.
Thanx,
Alex
On Sun, Feb 18, 2018 at 1:53 PM, Alex K <rightkicktech(a)gmail.com> wrote:
> Seems that this is due to:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1446147
>
> I will check If i can find newer guest agents.
>
> On Sun, Feb 18, 2018 at 1:46 PM, Alex K <rightkicktech(a)gmail.com> wrote:
>
>> Hi all,
>>
>> I am running a 3 node ovirt 4.1 selft hosted setup.
>> I have consistently observed that windows 10 VMs with SPICE console fail
>> to live migrate. Other VMs (windows server 2016) do migrate normally.
>>
>> VDSM log indicates:
>>
>> internal error: unable to execute QEMU command 'migrate': qxl: guest
>> bug: command not in ram bar (migration:287)
>> 2018-02-18 11:41:59,586+0000 ERROR (migsrc/2cf3a254) [virt.vm]
>> (vmId='2cf3a254-8450-44cf-b023-e0a49827dac0') Failed to migrate
>> (migration:429)
>> if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed',
>> dom=self)
>> libvirtError: internal error: unable to execute QEMU command 'migrate':
>> qxl: guest bug: command not in ram bar
>>
>> Seems as a guest agent bug for Windows 10? Is there any fix?
>>
>> Thanx,
>> Alex
>>
>
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
2469
days inactive
2469
days old
4 comments
2 participants
participants (2)
-
Alex K -
Michal Skrivanek