[Users] failed nestd vm only with spice and not vnc

[Gianluca Cecchi]

On Mon, Feb 10, 2014 at 10:22 AM, Gianluca Cecchi  wrote:
> On Sun, Feb 9, 2014 at 11:13 PM, Itamar Heim wrote:
>
>>
>> is there a bug for tracking this?
>
> Not yet. What to bug against? spice or spice-protocol or qemu-kvm itself?
>
> Gianluca

Actually it seems more complicated because also with vnc as display, I
don't get the L2 VM in paused state as in spice, but if I run once and
select CentOS 6.4 CD it starts and then it blocks at this screen (see
link below), so it has to do with nested itself that is not so viable,
at least with this cpu (Intel(R) Xeon(R) CPU E7- 4870  @ 2.40GHz) and
this L0

https://drive.google.com/file/d/0BwoPbcrMv8mvVHJybUw2dGFlTjg/edit?usp=sharing

At least with console set as vnc I can power off without problem my L2
VM and continue to work; instead with spice console as soon as I power
off the paused L2 VM, the hypervisor (that is L1 vm) completely
freezes with black console and I need to power off it.

My problem is similar to this one:
https://bugzilla.redhat.com/show_bug.cgi?id=922075

but in my case L0 is ESXi 5.1, 799733 so I think I have no much chance
to trick it...

Gianluca