All of lore.kernel.org
 help / color / mirror / Atom feed
From: Serge Hallyn <1353947@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1353947] Re: Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with CirrOS or Ubuntu 12.04
Date: Thu, 07 Aug 2014 15:47:42 -0000	[thread overview]
Message-ID: <20140807154742.7237.70115.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20140807104056.23920.38524.malonedeb@wampee.canonical.com

Sorry, I'm having trouble following your findings.  Could you please give a new table, like
this:

======================================================================================================================
GuestOS  | Guestkernel  |  HostOS  | Hostkernel |  qemu version        | libvirt version  | nic type       | Pass/Fail
======================================================================================================================
cirros   | ???          | 12.04    | 3.2        | 1.0+noroms-0ubuntu13 | 0.9.8-2ubuntu17  |  intel SR-IOV  | F
======================================================================================================================
cirros   | ???          | 12.04    | 3.13       | 1.0+noroms-0ubuntu13 | 0.9.8-2ubuntu17  |  intel SR-IOV  | P
======================================================================================================================
(...0
======================================================================================================================

Ideally we could determine whether the kernel version is at all related, or whether it
is purely tied to qemu version.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1353947

Title:
  Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with
  CirrOS or Ubuntu 12.04

Status in QEMU:
  New

Bug description:
  The issue observed when running an hypervisor with QEMU 2.0/libvirtd 1.2.2
  The VM network interface is attached to a PCI virtual function (SR-IOV).

  When we ran VM with guest OS CirrOS or Ubuntu 12.04 we observed an hipervisor hang shortly after the VM is loaded
  We observed the same issue with Mellanox NIC and with Intel NIC

  We’ve tried few combinations of {GuestOS}X{Hypervisor} and we got the following findings:
  When a hypervisor is running QEMU 1.5/libvirtd 1.1.1 - no issue observed
  When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CirrOS and Ubuntu 12.04 guest OSes caused hypervisor hang
  When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CentOS 6.4 and Ubuntu 13.10 - no issue observed

  The problematic guest OSes are with kernel versions ~3.2.y

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1353947/+subscriptions

  reply	other threads:[~2014-08-07 15:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 10:40 [Qemu-devel] [Bug 1353947] [NEW] Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with CirrOS or Ubuntu 12.04 Eyal Perry
2014-08-07 15:47 ` Serge Hallyn [this message]
2014-08-11 11:02 ` [Qemu-devel] [Bug 1353947] " Eyal Perry
2014-08-11 16:32 ` Serge Hallyn
2014-08-11 16:33 ` Serge Hallyn
2014-08-11 17:00 ` [Qemu-devel] [Bug 1353947] Missing required logs Brad Figg
2014-08-12  7:47 ` [Qemu-devel] [Bug 1353947] Re: Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with CirrOS or Ubuntu 12.04 Eyal Perry
2014-08-12  8:12 ` Eyal Perry
2014-08-12 14:10 ` Serge Hallyn
2014-08-12 14:31 ` Eyal Perry
2017-09-07 19:19 ` Thomas Huth
2018-05-23 10:09 ` Thomas Huth
2018-07-23  4:17 ` Launchpad Bug Tracker
2018-07-23  4:17 ` Launchpad Bug Tracker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140807154742.7237.70115.malone@chaenomeles.canonical.com \
    --to=1353947@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.