Can you rebase your fix on 1:2.5+dfsg-5ubuntu10.4 (due to the regression fix
mentioned in #25)?
Another thing about your backport is that it dropped the qem2 bits from the
patch. Is there a reason for this? If so please mention it in the debian/patch
file.
--
You received this bug notification
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
Hello Paul, or anyone else affected,
Accepted qemu into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.25 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
Can you please test with the 4.2.0-19.23 kernel on Xenial as well?
Thanks
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1516203
Title:
Hello Li, or anyone else affected,
Accepted qemu into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.2+dfsg-
5expubuntu9.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Hello Li, or anyone else affected,
Accepted qemu into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.20 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
** Changed in: qemu (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1463172
Title:
destination arm board hangs after migration from x86 source
Status in QEMU
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1448985
Title:
Ubuntu 14.04 LTS, 14.10, 15.04, 15.10 guests do not boot to Unity from
** Also affects: qemu (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Trusty)
Importanc
** Tags added: upstream
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1323758
Title:
Mouse stops working when connected usb-storage-device
Status in QEMU:
New
Status in qemu package in Ubuntu:
Can you test with the latest version to see if this still affects you?
If this still is a problem, any information on how to obtain the Guest OS in
question that would also be helpful.
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because yo
** No longer affects: qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption on non-extent filesystems (ext3)
Status in qemu package in Ubuntu:
In Progress
Bug
.
Thanks!
--chris j arges
** Summary changed:
- qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
+ qcow2 image corruption on non-extent filesystems (ext3)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1292234
Ti
FWIW, just re-reproduced this with latest upstream kernel / qemu / fresh
qcow2 image.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption in trusty (qemu 1.7 and 2.0
** Changed in: qemu (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
Stat
Just to clarify it's bug 1292234 in the previous comment.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
Status in OpenStack Co
Tony,
Yea, its a different bug. I tested with the above patched package and
upstream qemu from git, and I can still hit bug 129224. I was hoping
this also fixed my issue, but unfortunately it seems to be a different
issue that occurs when using the same types of filesystems. I have a
solid reprodu
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output imag
Looking at the fixes, I also see the following commits remove the above
changes, which could mean we might encounter this again:
c4875e5 raw-posix: SEEK_HOLE suffices, get rid of FIEMAP
d1f06fe raw-posix: The SEEK_HOLE code is flawed, rewrite it
Note there is also a related issue:
bug 1292234
So
Serge,
So I was able to just compile my own qemu and test with that.
I did attempt a reverse bisect, and was able to reproduce as early as v1.1 and
also reproduce on master HEAD.
v1.0 was inconclusive because qcow2 format I made with the newer binary seemed
to be incompatible with v1.0; however
Uploaded fixed package for Vivid:
https://launchpad.net/ubuntu/+source/qemu/2.1+dfsg-7ubuntu3
Please let me know if this fixes the issue.
** Changed in: qemu (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, wh
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: qemu (Ubuntu)
Status: New => In Progress
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of qemu-
Also I've been able to reproduce this with the latest master in qemu,
and even with the latest daily 3.18-rcX kernel on the host.
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
Hello Michael, or anyone else affected,
Accepted qemu into utopic-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/qemu/2.1+dfsg-
4ubuntu6.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Hello Michael, or anyone else affected,
Accepted qemu into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.8 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
@Serge
Gotcha, I misinterpreted your statement. Yes we are in agreement.
@dpb:
Have you had any further failures after installing qemu-kvm?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1387881
Titl
Answers to some of your questions:
Can you only get this on one particular host (i.e. hardware type)?
- No as I can repro in KVM
-Is there anything in syslog?
- Nothing relevant
Which packages (dpkg -l | grep qemu)
ii qemu-utils 2.0.0+dfsg-2ubuntu1.6 amd64
** Also affects: virtinst (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1387881
Title:
qemu fails to recognize full virtualization
Status in QE
I can reproduce this in a VM:
1) boot a clean cloud images (uvt-kvm create lp1387881)
2) apt-get install virtinst
3) sudo virt-install --name juju-bootstrap --ram=2048 --vcpus=1 --hvm
--virt-type=kvm --pxe --boot network,hd --os-variant=ubuntutrusty --graphics
vnc --noautoconsole --os-type=linux
So I'm not completely sure virtinst should depend on qemu-kvm, since we
assume one can use it without --virt-type=kvm, so my thoughts would be
you should install additional package as necessary to use qemu w/ KVM.
I'll let hallyn comment as well.
--
You received this bug notification because you
This is a package dependency issue and not a kernel issue. Once
davidpbritton installed 'qemu-kvm' he was able to install using virt-
install just fine.
So overall either the packages davidpbritton was installing weren't
sufficient to use qemu with KVM, or we have a dependency problem in the
Ubunt
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
** This bug is no longer a duplicate of bug 1307473
guest hang due to missing clock interrupt
** This bug has been marked a duplicate of bug 1346917
Using KSM on NUMA capable machines can cause KVM gue
I should have refreshed my browser before commenting. : ) Thanks Jesse
and Paolo.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1285708
Title:
FreeBSD Guest crash on boot due to xsave instruction i
Testing with the identified patch doesn't solve the issue, in addition
looking at the cpu flags (core2duo +xsave) this may not be a valid
configuration since xsave assumes additional features will be there
(instead of creating an older cpu model with xsave.) Therefore I believe
this is a configurat
** Changed in: linux (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1285708
Title:
FreeBSD Guest crash on boot due to xsave instruction issue
Status
As a workaround use the 'host' cpu type so the proper bits are enabled:
-cpu host,+xsave
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1285708
Title:
FreeBSD Guest crash on boot due to xsave instr
: Incomplete => Fix Released
** Changed in: linux (Ubuntu Trusty)
Status: New => In Progress
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
** Also affects: linux (Ub
*** This bug is a duplicate of bug 1307473 ***
https://bugs.launchpad.net/bugs/1307473
** This bug has been marked a duplicate of bug 1307473
guest hang due to missing clock interrupt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
** Changed in: qemu-kvm (Ubuntu Quantal)
Assignee: Chris J Arges (arges) => (unassigned)
** Changed in: qemu-kvm (Ubuntu Raring)
Assignee: Chris J Arges (arges) => (unassigned)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscri
I have verified this on my local machine using virt-manager's save
memory, savevm/loadvm via the qemu monitor , and migrate via qemu
monitor.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of qemu-
devel-ml, wh
** Description changed:
SRU Justification
[Impact]
* Users of QEMU that save their memory states using savevm/loadvm or migrate
experience worse performance after the migration/loadvm. To workaround these
issues VMs must be completely rebooted. Optimally we should be able to restore
a VM
** Description changed:
SRU Justification
- [Impact]
- * Users of QEMU that save their memory states using savevm/loadvm or migrate
experience worse performance after the migration/loadvm. To workaround these
issues VMs must be completely rebooted. Optimally we should be able to restore
a V
** Description changed:
+ SRU Justification
+ [Impact]
+ * Users of QEMU that save their memory states using savevm/loadvm or migrate
experience worse performance after the migration/loadvm. To workaround these
issues VMs must be completely rebooted. Optimally we should be able to restore
a V
I found that two patches need to be backported to solve this issue:
ad0b5321f1f797274603ebbe20108b0750baee94
211ea74022f51164a7729030b28eec90b6c99a08
I've added the necessary bits into precise and tried a few tests:
1) Measure performance before and after savevm/loadvm.
2) Measure performance bef
Importance: High
Assignee: Chris J Arges (arges)
Status: In Progress
** Changed in: qemu-kvm (Ubuntu Precise)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: qemu-kvm (Ubuntu Quantal)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: qemu-k
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1100843
Title:
Live Migration Causes Performance Issues
Status in QEMU:
New
S
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) => Chris J Arges (arges)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1100843
Title:
Live Migration Causes Performance Issues
Sta
49 matches
Mail list logo