[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821771
Title:
KVM guest d
The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.
If you still think this bug report here is valid, then please switch
the
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/110
** Changed in: qemu
Status: New => Expired
** Bug watch
Hi Thomas,
On 2/9/21 2:32 AM, Huacai Chen wrote:
> I think it can be removed.
>
> Huacai
>
> On Tue, Feb 9, 2021 at 12:40 AM Jiaxun Yang wrote:
>> On Mon, Feb 8, 2021, at 3:39 AM, Thomas Bogendoerfer wrote:
>>> On Wed, Feb 03, 2021 at 08:52:34PM +0800, Jiaxun Yang wrote:
On Wed, Feb 3, 202
I think it can be removed.
Huacai
On Tue, Feb 9, 2021 at 12:40 AM Jiaxun Yang wrote:
>
>
>
> On Mon, Feb 8, 2021, at 3:39 AM, Thomas Bogendoerfer wrote:
> > On Wed, Feb 03, 2021 at 08:52:34PM +0800, Jiaxun Yang wrote:
> > >
> > >
> > > On Wed, Feb 3, 2021, at 8:34 PM, Thomas Bogendoerfer wrote:
On Mon, Feb 8, 2021, at 3:39 AM, Thomas Bogendoerfer wrote:
> On Wed, Feb 03, 2021 at 08:52:34PM +0800, Jiaxun Yang wrote:
> >
> >
> > On Wed, Feb 3, 2021, at 8:34 PM, Thomas Bogendoerfer wrote:
> > > Hi,
> > >
> > > Does kvm guest kernel still work ? I'm playing with current mips-next
> > >
Documentation describing the current qemu behaviour is captured here,
https://www.mail-archive.com/qemu-devel@nongnu.org/msg726442.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821771
Title:
David: Indeed ! How stupid I am. I missed the root cause inside QUEMU log file.
This was clear enough...
error: kvm run failed Device or resource busy
This is probably because your SMT is enabled.
So I switch SMT (Power Simultaneous Multi-Threading) off and now it's
OK; VMs are running and instal
Fabrice: That's probably a different error given that this lp seems to be with
x86 vmx flags.
Check your /var/log/libvirt/qemu/ on the host to see if there's a particular
error shown in the destination qemu after migration.
--
You received this bug notification because you are a member of qemu-
Same issue here. I've upgraded my IBM Power ppc64le system to ubuntu 20.04. Now
I'm trying to create KVM VMs and whatever I'm doing, the VM is created but
before any installation step starts, it's falling into "paused" mode. When
trying to resume it, I get:
"
Error unpausing domain: internal err
Thanks Thomas for Your suggestion. Unfortunately I cannot achieve the
reconnection:
KVM runs with following parameters:
-usb -device usb-host,vendorid=0x04e8,productid=0x3242,id=drucker
-monitor unix:qemu-monitor-socket,server,nowait
With the Unix socket, I can now pipe commands to the qemu moni
Hi Christian.
Just filed bug: #1877052
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
Invalid
Status in qemu package
Hi Andreas,
so the only upgrade you did to trigger this for you was to bump the kernel from
5.4.0-28.33 to 5.4.0-29.34 - nothing else? I have not (yet?) heard other
similar reports, but it might be just too early?
At least on my system for now things still work with the new kernel like before.
I
Hello!
Unfortunately the bug has apparently reappeared. I have a Windows 10 running in
a VM, which after my today's "apt upgrade" goes into pause mode after a few
seconds of running time.
Tail output of my /var/log/libvirt/qemu/win10.log
char device redirected to /dev/pts/1 (label charserial0)
2
Thank you Boris and Tstrike for the report and your help.
It was a great bug to identify and fix before the release of 20.04, I
appreciate you using (and hereby testing) it ahead of time!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEM
I can confirm that this bug has been fixed (zapped). Thank you all for
your hard work and determination. A job well done indeed! As a former
programmer I love you all's zeal for attacking this bug.
As a side note, knowing what you all go through, I always look things
up, walk through at least leve
Works for me. F31 KVM guest is installing on Q9550 box.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
Invalid
Status
apt-get will be enough once it's published, and looks like it just was
published.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status
Can I just apt update && apt upgrade to get this fix or do I need to
patch?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QE
This bug was fixed in the package seabios - 1.13.0-1ubuntu1
---
seabios (1.13.0-1ubuntu1) focal; urgency=medium
* d/p/lp-1866870-build-use-fcf-protection-none-when-available.patch
fix breakage on older chips due to fcf-protection (LP: #1866870)
-- Christian Ehrhardt Thu, 19
Sent to seabios for their consideration:
=>
https://mail.coreboot.org/hyperkitty/list/seab...@seabios.org/thread/IXAWMA2HWW75LSR3NBBYQKWT3TI5WVVP/
I deleted the experimental PPAs that we had and created a new one with a new
seabios:
=> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/seabios/+git/seabios/+merge/380881
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses aft
I *think* it's the cf-protection that's adding the endbr32 instructions
that I spotted as being the failing instruction each time; but I don't
understand why they would be CPU type specific.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
** Changed in: qemu
Status: New => Invalid
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
** Also affects: seabios (Ubuntu)
Importance: Undecided
Status: New
** Changed in: seabios (Ubuntu)
Status: New => Triaged
--
You received this bug notification
Starting from the Disco build env that I had I changed the packages
Step #1 binutils:
Unpacking binutils-x86-64-linux-gnu (2.33-2ubuntu1.2) over (2.32-7ubuntu4) ...
Unpacking libbinutils:amd64 (2.33-2ubuntu1.2) over (2.32-7ubuntu4) ...
Unpacking binutils (2.33-2ubuntu1.2) over (2.32-7ubuntu4) ...
That's getting more fun :-)
You could look at whether seabios's config works out hte same in the two
environments, or whether something makes use of new build flags - try looking
at the gcc lines that are invoked in the good/bad cases and see if they're
passing any options that the other doesn't
Turns out 1.12 is a fairly old build and the working version in Ubuntu was from
in Disco, therefore about a year ago.
=> https://launchpad.net/ubuntu/+source/seabios/1.12.0-1/+build/16284605
Therefore I built it in Eoan and even Disco.
As an overview:
Disco: gcc 4:8.3.0-1ubuntu3 binutils 2.32-7
I wanted to make sure why different qemu configs make it trigger or not,
and after finding seabios to be related the candidates were obvious.
Default config gets us:
BIOS directory/usr/local/share/qemu
The long conf had:
--firmwarepath=/usr/share/qemu:/usr/share/seabios:/usr/lib/ipxe/qemu
Ad
With that confirmed I checked if I can just point to a bios to break it, and
indeed adding
-bios /root/seabios_1.12.0-1/usr/share/seabios/bios.bin
-bios /root/seabios_1.13.0-1/usr/share/seabios/bios.bin
respectively is a make or break change.
As a next step I reproduced the error with seabi
I've tested smoe more cmbinations and found that I van have v4.2 work on focal.
Eventually I have realized that when I install start the qemu from Ubuntu not
only that but also the formerly working build of v4.2.0 from git start to fail
(without rebuilding).
A bit of package bisect later I found
Ok, upstream tag v4.2.0 and these configure options reproduced the
crash:
export LDFLAGS="-Wl,--warn-common -Wl,-z,relro -Wl,-z,now -pie -m64 -g
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed"
export CFLAGS="-O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -g"
Full configure output: https://pas
Also crashed with the packages from the other ppa:
ubuntu@f1:~$ qemu-system-x86_64 --help 2>&1|head -n 1
QEMU emulator version 4.2.0 (Debian 1:4.2-3ubuntu3~exp1)
ubuntu@f1:~$ qemu-system-x86_64 --enable-kvm -cpu Penryn,vmx=on -m 512
--nodefaults --nographic
qemu-system-x86_64: warning: host does
The package from the PPA failed the same way for me:
ubuntu@f1:~$ qemu-system-x86_64 --enable-kvm -cpu Penryn,vmx=on -m 512
--nodefaults --nographic
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.01H:ECX.sse4.1 [bit 19]
KVM internal error. Suberror: 1
emulation failur
Verification new packages to be installed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package i
Log file for f31wks guest
** Attachment added: "Log file for f31wks guest"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337553/+files/fedora31wks.log
** Attachment removed: "PPA packages installed"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337552/+files/report
** Attachment added: "Check PPA [2} installed"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337555/+files/ppa2installed.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Titl
No luck when testing [2]. Reports are attached
** Attachment added: "PPA packages installed"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5337552/+files/report.install.ppa
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEM
Thanks David!
While bisecting on upstream git with just "-cpu Penryn" we have seen that it
always works there.
So it might be an interaction with some Ubuntu build/packaging/configure detail
together with these old chips.
While we still can't be sure if the VMX warnings are a red-herring
chance
I think the one I was thinking of is 0723cc8a5558c94388db75ae1f4991314914edd3
which is in a 4.2.0 rc
and there was 2605188240f939fa9ae9353f53a0985620b34769 - but that's a
different crash to what you have.
So hmm.
--
You received this bug notification because you are a member of qemu-
devel-m
Andreas was so kind to try kenels 4.4, 4.15 and 5.6 all fail (with qemu 4.2)
He then tried Eoan (qemu 4.0) and Focal (qemu 4.2).
4.0 worked and 4.2 failed.
We will set up a bisect run on Monday and hopefully find the offending
change.
@David - I agree that the messages might be a red-herring, but
The vmx things make me wonder about a fix Paolo did a while ago for
enabling inidivudal vmx features rather than vmx as a whole; but I
can't remember if that was a kernel or qemu fix.
One thing I notice, that may be a red-herring, all of the machine code
in the errors are 'f3 0f 1e fb' which is t
Yeah @Boris - it really seems to be an issue bound to the Merom/Penryn
processor generation.
I asked Andreas to check through some kernels and qemu versions so that
we maybe eventually can consider bisecting something. But that will take
a bit of time.
Of course everyone able to spend some time c
Seems to work fine on i4790 (Haswell) box.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu package
Penryn's architecture confirmed
** Attachment added: "/proc/cpuinfo file uploaded"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5336211/+files/cpuinfo.penryn
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bu
By using host-model Andreas also was able to get the same signature:
2020-03-12T15:06:22.560159Z qemu-system-x86_64: warning: host doesn't support
requested feature: MSR(48EH).vmx-vnmi-pending [bit 22]
2020-03-12T15:06:22.560708Z qemu-system-x86_64: warning: host doesn't support
requested featur
After changing cpu to :
I got this log (still in a paused state):
char device redirected to /dev/pts/3 (label charserial0)
2020-03-12T15:06:22.560159Z qemu-system-x86_64: warning: host doesn't support
requested feature: MSR(48EH).vmx-vnmi-pending [bit 22]
2020-03-12T15:06:22.560708Z qemu-system-
AppArmor is completely disabled on my server.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
New
Status in qemu packa
virsh domcapabilities
** Attachment added: "virsh-domcapabilities.xml"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1866870/+attachment/5336149/+files/virsh-domcapabilities.xml
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEM
I tried launching a focal vm on a focal host, and the vm launched but is
in a paused state.
Attached is its log.
This is on an old E660 intel core system.
** Attachment added: "f1.log"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1866870/+attachment/5336146/+files/f1.log
--
You rece
virsh capabilities
** Attachment added: "virsh-capabilities.xml"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1866870/+attachment/5336148/+files/virsh-capabilities.xml
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https:
I also have these two apparmor denied messages in dmesg:
[ 1380.529549] audit: type=1400 audit(1584023445.093:139): apparmor="DENIED"
operation="open" profile="libvirt-aa346a1d-8caa-4c55-bef9-c3acbe17bdac"
name="/" pid=19712 comm="qemu-system-x86" requested_mask="r" denied_mask="r"
fsuid=64055 o
/proc/cpuinfo
** Attachment added: "cpuinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1866870/+attachment/5336147/+files/cpuinfo.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/
It detects host as Penryn as well for @tstrike.
Which is fine if it is a chip of around that era.
He reported to have an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz"
And for that chip the detection and chip used might be correct.
So to summarize all repro fails, but on Penryn ERA chips 2/2 cases
tstrike39@islandhealthcenter-media:~$ sudo cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPUQ9400 @ 2.66GHz
stepping: 10
microcode : 0xa0b
cpu MHz : 2416.548
cache s
Thanks Boris!
@tstrike - is your system also "really an old penryn" or is it something newer?
Maybe share /proc/cpuinfo?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest paus
Done on Penryn's box
** Attachment added: "Requested reporting submitted"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5336044/+files/Penryn.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.n
Thanks a lot . I will do it at my earliest convenience this night.
Haswell i4770 is installed on small server 32 GB. Department's policy
doesn't allow me to test Ubuntu whichever release on bare metal. I
could test only on outdated CPU's box and it seems to be a core reason.
--
You received this
This particular command seems to hang on:
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.01H:ECX.vmx [bit 5]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.8001H:ECX.svm [bit 2]
I tried to execute (thinking I was in a shell):
{"execut
** Attachment added: "virshdomcapabilities.txt"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5336031/+files/virshdomcapabilities.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/18668
** Attachment added: "virshcapabilities.txt"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5336030/+files/virshcapabilities.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Ti
@Boris - in your log I've seen that you also got the Penryn cpu which I find
odd.
"-cpu
Penryn,vme=on,vmx=on,x2apic=on,tsc-deadline=on,xsave=on,hypervisor=on,arat=on,tsc-adjust=on,arch-capabilities=on,skip-l1dfl-vmentry=on
\"
Assuming you also only used default I wonder how it got to that, maybe
I fetched
https://download.fedoraproject.org/pub/fedora/linux/releases/31/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-31-1.9.iso
And installed it on Ubuntu 20.04 via virt-manager (keeping all things on
its default).
- New
- Local Media
- select ISO (Autodetects F31)
- Forward, Forward,
I've got the same issue starting guest via virt-install even with serial
console.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status
Thanks Boris for chiming in!
Maybe it is something in the guest (or the way virt-manager sets things up)
after all - will install an F31 via virt-manager as well ...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launch
I tried with a guest XML matching yours (other than disk setup).
I didn't get those errors you reported even when using your config.
Notable differences to my default - your guest has:
- a rather old chip type (Penryn is a 2007 chip)
- a rather old machine type (uses xenial which matches ~pc-i440
Reproduced via attempt to install KVM Guest F31 Server on Ubuntu 20.04
(bare metal)
** Attachment added: "/var/log/libvirt/qemu/fedora31.log - attempt to launch
F31 Server VM via Virt-manager on Ubuntu 20.04"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5336017/+files/fedora31.lo
Thank you @tstrike:
In your logs I see a bunch of qemu warnings right at the beginning:
2020-02-12T15:09:37.773025Z qemu-system-x86_64: warning: host doesn't support
requested feature: MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12]
2020-02-12T15:09:37.773107Z qemu-system-x86_64: warning: host
** Attachment added: "Windows 10 Guest Logfile"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5335799/+files/win10.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KV
** Attachment added: "Windows 10 Guest"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5335798/+files/win10.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest
** Attachment added: "List of Domains"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5335795/+files/libvirttstrike_domains.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Tit
** Attachment added: "Zabbix_Serviio.txt"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5335797/+files/Zabbix_Serviio.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
** Attachment added: "dmesg"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5335796/+files/libvirttstrike_dmesg.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Gu
** Attachment added: "Centos 8 Logfile"
https://bugs.launchpad.net/qemu/+bug/1866870/+attachment/5335800/+files/Zabbix_Serviio.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
K
Christian,
Thanks for getting my report in the proper syntax. I would be extremely
happy to follow through on the tasks you laid out to me. Give me about 3
hours and I will update the report with the items requested.
--
You received this bug notification because you are a member of qemu-
devel-m
@tstrike: finally for the sake of apparmor denials or any other odd
error that might be mentioned in there attaching the output of `dmesg`
on your host might be useful as well.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
@tstrike - can you trigger the same issue with all your guests?
You list Windows and Centos guests, does it triggers with Centos as well or
only the Windows guests?
Also if you have a chance (just to be sure) does it trigger with an Ubuntu
guest as well? This would help for people retrying not us
Hi tstrike,
thanks for the report.
I have slightly modified the description and changed the bug tasks accordingly
for you.
** Bug watch added: Red Hat Bugzilla #1378006
https://bugzilla.redhat.com/show_bug.cgi?id=1378006
** Bug watch added: Red Hat Bugzilla #1464654
https://bugzilla.redhat
I first checked the related known fixes from the old case that is linked.
Just in case if we might miss one in Ubuntu 20.04 that you are using.
Kernel:
=> https://marc.info/?l=kvm&m=155085391830663&w=2
Tested and verified https://bugs.launchpad.net/qemu/+bug/1813165/comments/13
This got upstream
Copied here from the other bug about the system setup that is in use:
L0 DistroRelease: Ubuntu 20.04 on Kernel Linux 5.4.0-14-generic x86_64
L1 3 guests Windows 10, Centos 8
No L2s
No guests are enabled for UEFI Boot
libvirt: 6.0.0-0ubuntu4
qemu 1:4.2-3ubuntu1
Issue triggers without nesting (ens
** Description changed:
+ Symptom:
+ Error unpausing domain: internal error: unable to execute QEMU command
'cont': Resetting the Virtual Machine is required
+
+ Traceback (most recent call last):
+ File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
+ callback(
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1866870
Title:
KVM Guest pauses after upgrade
** Also affects: 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/1866870
Title:
KVM Guest pauses after upgrade to Ubuntu 20.04
Status in QEMU:
Ne
Closing according to the previous comment
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1488901
Title:
KVM guest crashes when doing a block c
I guess switching the printer off and on again is like attaching a new
USB device to your host (so it only shows up in the host, of course, and
not in the guest). Have you already tried to do a new "device_add usb-
host,..." in the QEMU monitor to attach it to the guest again while the
VM is runnin
This is a very annoying bug, and it is still not solved after 2.7 years.
Last versions tested and affected by this bug:
KVM host qemu version 2.9.0
KVM host Linux version 4.9.6 x86_64
Please fix this.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is su
Problem is solved in current master branch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1488901
Title:
KVM guest crashes when doing a block commit command
Status in QEMU:
New
Bug description:
This is a very annoying bug, and it is still not solved after six
months, last versions tested with the bug:
KVM host qemu version 2.2.1
KVM host Linux version 3.14.37
Please fix this.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU
qemu does provide life cycle management of a non-running guest.
For that, I'd recommend a tool such as libvirt.
** Changed in: qemu
Status: New => Invalid
--
KVM guest O.S not booting properly when shutdown or restarting Host machine
https://bugs.launchpad.net/bugs/556424
You received th
88 matches
Mail list logo
