Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-14 Thread Vasiliy Tolstov
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 the time) to F20,
 and I cannot start any L2 guests.  The L2 guest appears to hang almost
 immediately after starting, consuming 100% of one of the L1 guest's
 VCPUs.
 
 If I reboot with kernel-3.12.10-300.fc20.x86_64, the problem does not
 occur.
 
 Any known workaround?  (Other than using 3.12.10?)

 There is a fix on the way to the 3.13 kernel.

 You can open a Fedora bug and ask them to include
 http://article.gmane.org/gmane.linux.kernel.stable/82043/raw in the
 kernel.

 Thanks for fixing this.  It affects a lot of libguestfs users too.

 I opened this bug:

 https://bugzilla.redhat.com/show_bug.cgi?id=1073663

 Rich.


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

[   10.942007] PANIC: double fault, error_code: 0x0
[   10.942007] CPU: 0 PID: 182 Comm: systemd-journal Not tainted 3.13.6 #3
[   10.942007] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[   10.942007] task: 88001cc08000 ti: 88001d70e000 task.ti:
88001d70e000
[   10.942007] RIP: 0033:[7fe61b2fce8a]  [7fe61b2fce8a]
0x7fe61b2fce8a
[   10.942007] RSP: 002b:7fffee7468d8  EFLAGS: 00010286
[   10.942007] RAX:  RBX: 0043344e RCX: 00430a70
[   10.942007] RDX: 0010 RSI:  RDI: 00430a70
[   10.942007] RBP: 7fffee747130 R08: 0003 R09: 7fe61be81780
[   10.942007] R10:  R11: 0246 R12: 0001
[   10.942007] R13: 01c9c380 R14: 0003 R15: 7fffee747148
[   10.942007] FS:  7fe61be81780() GS:88001f80()
knlGS:
[   10.942007] CS:  0010 DS:  ES:  CR0: 80050033
[   10.942007] CR2:  CR3: 1e1a2000 CR4: 06f0
[   10.942007]
[   10.942007] Kernel panic - not syncing: Machine halted.


-- 
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
jabber: v...@selfip.ru
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-14 Thread Richard W.M. Jones
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 on Intel hardware?

From the libguestfs point of view what you can do is to force TCG:

export LIBGUESTFS_BACKEND_SETTINGS=force_tcg

Unfortunately this only has an effect in libguestfs = 1.25.24.  We're
going to have the new version in Fedora 20 real soon -- probably
before the end of this month.  Or you can compile the Rawhide version
on F20.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-14 Thread Vasiliy Tolstov
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

 Unfortunately this only has an effect in libguestfs = 1.25.24.  We're
 going to have the new version in Fedora 20 real soon -- probably
 before the end of this month.  Or you can compile the Rawhide version
 on F20.


Thanks for answer. I'm not using libguestfs. I'm try tun vm inside vm
via libvirt.
is that possible to debug this issue ? How can i help?
P.S. Yes i'm using intel hardware.

-- 
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
jabber: v...@selfip.ru
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-14 Thread Richard W.M. Jones
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 force TCG:
 
  export LIBGUESTFS_BACKEND_SETTINGS=force_tcg
 
  Unfortunately this only has an effect in libguestfs = 1.25.24.  We're
  going to have the new version in Fedora 20 real soon -- probably
  before the end of this month.  Or you can compile the Rawhide version
  on F20.
 
 
 Thanks for answer. I'm not using libguestfs. I'm try tun vm inside vm
 via libvirt.

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 report.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-14 Thread Vasiliy Tolstov
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 report.


Where i can find submission form for bug report? (I'm using exherbo
linux, but it does not have like debian or sles personal patches and
using only upstream)

-- 
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
jabber: v...@selfip.ru
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-14 Thread Richard W.M. Jones
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 guest.
  Any messages from qemu or the host.
   put all of that into a full bug report.
 
 
 Where i can find submission form for bug report? (I'm using exherbo
 linux, but it does not have like debian or sles personal patches and
 using only upstream)

I suspect this is going to be a kernel bug, in which case:

https://bugzilla.kernel.org/

For libvirt bugs it would be:

https://bugzilla.redhat.com/enter_bug.cgi?component=libvirtproduct=Virtualization+Tools

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-06 Thread Richard W.M. Jones
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 guest appears to hang almost
 immediately after starting, consuming 100% of one of the L1 guest's
 VCPUs.
 
 If I reboot with kernel-3.12.10-300.fc20.x86_64, the problem does not
 occur.
 
 Any known workaround?  (Other than using 3.12.10?)
 
 There is a fix on the way to the 3.13 kernel.
 
 You can open a Fedora bug and ask them to include
 http://article.gmane.org/gmane.linux.kernel.stable/82043/raw in the
 kernel.

Thanks for fixing this.  It affects a lot of libguestfs users too.

I opened this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1073663

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-04 Thread Paolo Bonzini

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 100% of one of the L1 guest's
VCPUs.

If I reboot with kernel-3.12.10-300.fc20.x86_64, the problem does not
occur.

Any known workaround?  (Other than using 3.12.10?)


There is a fix on the way to the 3.13 kernel.

You can open a Fedora bug and ask them to include 
http://article.gmane.org/gmane.linux.kernel.stable/82043/raw in the kernel.


Paolo
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-04 Thread Kashyap Chamarthy
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 guest appears to hang almost
 immediately after starting, consuming 100% of one of the L1 guest's
 VCPUs.
 
 If I reboot with kernel-3.12.10-300.fc20.x86_64, the problem does not
 occur.
 
 Any known workaround?  (Other than using 3.12.10?)

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

(NOTE: Fedora Scratch build URLs won't last more than 10 days or so)

 
 There is a fix on the way to the 3.13 kernel.
 
 You can open a Fedora bug and ask them to include
 http://article.gmane.org/gmane.linux.kernel.stable/82043/raw in the
 kernel.
 
 Paolo
 --
 To unsubscribe from this list: send the line unsubscribe kvm in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
/kashyap
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-04 Thread Kashyap Chamarthy
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 (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 100% of one of the L1 guest's
  VCPUs.
  
  If I reboot with kernel-3.12.10-300.fc20.x86_64, the problem does not
  occur.

Err, I missed to read this. Sorry about that.

  
  Any known workaround?  (Other than using 3.12.10?)
 
 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
 
 (NOTE: Fedora Scratch build URLs won't last more than 10 days or so)
 
  
  There is a fix on the way to the 3.13 kernel.
  
  You can open a Fedora bug and ask them to include
  http://article.gmane.org/gmane.linux.kernel.stable/82043/raw in the
  kernel.
  
  Paolo
  --
  To unsubscribe from this list: send the line unsubscribe kvm in
  the body of a message to majord...@vger.kernel.org
  More majordomo info at  http://vger.kernel.org/majordomo-info.html
 
 -- 
 /kashyap

-- 
/kashyap
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [fedora-virt] 3.13 - Nested KVM (vmx) totally broken?

2014-03-04 Thread Ian Pilcher
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!

-- 

Ian Pilcher arequip...@gmail.com
   Sent from the cloud -- where it's already tomorrow

--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html