Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: qemu (Ubuntu Artful)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Would it be possible to get a fixed QEMU version into the Xenial-Ocata
cloud archive?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763649
Title:
qemu segfaults after re-attaching ceph volume to in
I can confirm that upgrading from Xenial-Ocata to Xenial-Pike (both
Cloud Archive) solves the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763649
Title:
qemu segfaults after re-attaching ce
I was confused by your "versions on Bionic/Queens are good" statement.
Openstack was upgraded to Queens, it's correct, I am using cloud archive
repositories for OpenStack packages, while base system is still based on
Xenial.
So final summary is correct,
--
You received this bug notification bec
So it is not fixed by your upgrade to queens as you first thought?
=> Ubuntu 16.04 + UCA-Queens fails other than stated in comment #2?
We these different versions here to consider:
- Xenial as-is (no report on it yet)
- Artful as-is (no report on it yet)
- Xenial-Ocata (initial report, fails)
- Xe
Well, still Xenial with cloud archive repos for queens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763649
Title:
qemu segfaults after re-attaching ceph volume to instance
To manage notificatio
Thanks Crazik for reporting that, at least that means newer versions on
Bionic/Queens are good.
** Also affects: qemu (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Problem was solved by upgrade to Queens.
Looks like it was caused by ceph/rados libs w/ qemu issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763649
Title:
qemu segfaults after re-attaching
@Corey / James - I have no ceph around at all, also this is reported
against a cloud-archive qemu (Ocata if I read it correctly).
Can you confirm this issue and if so are there further insights how to
handle it further?
@Crazik - to what extend could you try on your existing setup with different
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763649
Title:
qemu segfaults after re-attaching ceph volume to instance
To
** Description changed:
I have OpenStack compute nodes with qemu-system-x86. Using Ceph as
storage backend for base disks and volumes (no local storage).
When I create a new volume on ceph and attach to instance - it's working.
When I detach volume, and re-attach again, with limited num
11 matches
Mail list logo
