2014-03-07 1:59 GMT+04:00 Richard W.M. Jones rjo...@redhat.com:
On Tue, Mar 04, 2014 at 09:13:40AM +0100, Paolo Bonzini wrote:
Il 04/03/2014 03:40, Ian Pilcher ha scritto:
Is this a known problem? I just tried using nested vmx for the first
time since upgrading my system from F19 (3.12.?? at
On Fri, Mar 14, 2014 at 03:52:03PM +0400, Vasiliy Tolstov wrote:
If i use 3.13.6 kernel that have alredy this patch, but sometimes i
get kernel panic, what can i do?
P.S. I'm using nested virt, fault from L2
It could be there is another, less frequent, bug in nested KVM.
I'm assuming this is
2014-03-14 15:58 GMT+04:00 Richard W.M. Jones rjo...@redhat.com:
It could be there is another, less frequent, bug in nested KVM.
I'm assuming this is on Intel hardware?
From the libguestfs point of view what you can do is to force TCG:
export LIBGUESTFS_BACKEND_SETTINGS=force_tcg
On Fri, Mar 14, 2014 at 04:11:13PM +0400, Vasiliy Tolstov wrote:
2014-03-14 15:58 GMT+04:00 Richard W.M. Jones rjo...@redhat.com:
It could be there is another, less frequent, bug in nested KVM.
I'm assuming this is on Intel hardware?
From the libguestfs point of view what you can do is to
2014-03-14 16:16 GMT+04:00 Richard W.M. Jones rjo...@redhat.com:
You can set the VM domain type=qemu. Of course it'll run quite
slowly.
is that possible to debug this issue ? How can i help?
Complete logs from the guest.
Any messages from qemu or the host.
put all of that into a full bug
On Fri, Mar 14, 2014 at 04:39:48PM +0400, Vasiliy Tolstov wrote:
2014-03-14 16:16 GMT+04:00 Richard W.M. Jones rjo...@redhat.com:
You can set the VM domain type=qemu. Of course it'll run quite
slowly.
is that possible to debug this issue ? How can i help?
Complete logs from the
On Tue, Mar 04, 2014 at 09:13:40AM +0100, Paolo Bonzini wrote:
Il 04/03/2014 03:40, Ian Pilcher ha scritto:
Is this a known problem? I just tried using nested vmx for the first
time since upgrading my system from F19 (3.12.?? at the time) to F20,
and I cannot start any L2 guests. The L2
Il 04/03/2014 03:40, Ian Pilcher ha scritto:
Is this a known problem? I just tried using nested vmx for the first
time since upgrading my system from F19 (3.12.?? at the time) to F20,
and I cannot start any L2 guests. The L2 guest appears to hang almost
immediately after starting, consuming
On Tue, Mar 04, 2014 at 09:13:40AM +0100, Paolo Bonzini wrote:
Il 04/03/2014 03:40, Ian Pilcher ha scritto:
Is this a known problem? I just tried using nested vmx for the first
time since upgrading my system from F19 (3.12.?? at the time) to F20,
and I cannot start any L2 guests. The L2
On Tue, Mar 04, 2014 at 03:00:22PM +0530, Kashyap Chamarthy wrote:
On Tue, Mar 04, 2014 at 09:13:40AM +0100, Paolo Bonzini wrote:
Il 04/03/2014 03:40, Ian Pilcher ha scritto:
Is this a known problem? I just tried using nested vmx for the first
time since upgrading my system from F19
On 03/04/2014 03:30 AM, Kashyap Chamarthy wrote:
If you want to try, I made a Fedora Kernel scratch build (i.e. not
official) with fix Paolo pointed to below and this works for me:
http://koji.fedoraproject.org/koji/taskinfo?taskID=6577700
Works here. Thanks!
--
11 matches
Mail list logo
