Zach, thanks for the feedback.
Since we still struggle to recreate this on our side is there a chance that you
could test kernels from [1] to help spotting which version bump exactly it was?
Going further we might even need to bisect things, but one step at a time.
I'd not want to put this on
I do this because its the only other kernel I have installed. I am not
sure at what point between 5.0.0-31-generic and 5.3.0-20-generic this
bug appears.
I've attached my history from the point that the bug started occurring,
no references to qemu or libvirt though, only linux-
@Christian this is correct. I boot into 5.0.0-31-generic when I need to
use my VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
Running VM with Virtual NIC Crashes Host OS
To
My current suggestion would be to try changing the following CPU
features:
>From the virtual machines in question and checking if that mitigates the
issue (removing first half, and trying, removing the second half,
keeping the first one, and trying, and so
Meanwhile I'll try to find other HW I can test the same thing on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
Running VM with Virtual NIC Crashes Host OS
To manage notifications
** Attachment added: "win2019crashq35spice.xml"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1849720/+attachment/5303253/+files/win2019crashq35spice.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "win2019crashq35.xml"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1849720/+attachment/5303252/+files/win2019crashq35.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Clinton's VM did have virtio only network, as well as mine, and I also
thought the same about the e1000 emulation not being anywhere close to
host kernel. Anyway, I have been trying to reproduce this issue with the
attached VMs definition with no success.
To be honest, I'm starting to suspect on
@Zach - that is an interesting detail.
This might explain why I didn't see it (had kernel 5.0 together with the
userspace of Ubuntu 19.10)
So you can switch between good/bad mode by switching host kernels between 5.3
and others then?
Does this apply to others affected by this bug as well?
You
Hello, a little late to the party, but I have the what started as the
same VM image as Robert Strube. Its Windows 2019, default network
driver. My system is Pop OS 19.04, based on Ubuntu 19.04. After an
update I got kernel version 5.3.0-20-generic and this issue started
happening to me. Pasted
** Changed in: qemu (Ubuntu)
Status: Incomplete => In Progress
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See attached for host's lscpu output.
** Attachment added: "Host lscpu"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1849720/+attachment/5302757/+files/lscpu_clinton.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That is awesome. Thx, I'll get back to you soon, I'll try to get a
CascadeLake server in my lab so I can reproduce this closely to HW you
have and are using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
BTW Clinton, one last question, whats your exact host CPU model ? Sorry,
missed that question before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
Running VM with Virtual NIC
See attached picture of journalctl -f during a crash using the e1000e
NIC.
** Attachment added: "qemu windows 10 freeze journal"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1849720/+attachment/5302563/+files/qemucrash.jpg
--
You received this bug notification because you are a
apt list --installed | grep qemu
ipxe-qemu-256k-compat-efi-roms/eoan,eoan,now
1.0.0+git-20150424.a25a16d-0ubuntu3 all [installed,automatic]
ipxe-qemu/eoan,eoan,now 1.0.0+git-20190109.133f4c4-0ubuntu2 all
[installed,automatic]
qemu-block-extra/eoan,now 1:4.0+dfsg-0ubuntu9 amd64
Clinton, can you provide the answers to comment #27 then ?
- host kernel exact version (5.3.0-20-generic in your case)
- guest kernel exact version (windows kernel in this case)
- qemu packages exact version (?)
- virtual machine xml (virsh dumpxml ) (?)
--
You received this bug notification
I had the same issue:
Host system freeze whenever a Windows guest VM made it to the login
screen. The last thing I could see in journalctl -f was a DHCP exchange
with the VM before everything froze.
Solution:
Change NIC device model from e1000e to virtio, apply change and boot. No
freeze,
As an example, I have tried to reproduce with the following
configuration:
(k)rafaeldtinoco@win2019crashhost:~$ uname -a
Linux win2019crashhost 5.0.0-34-generic #36-Ubuntu SMP Wed Oct 30 05:16:14 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
(k)rafaeldtinoco@win2019crashhost:~$ lsb_release -a
i'm not suggesting anything related to a kernel dump as you've said its
not a host kernel crash, but a machine hang. usually a machine hang is
caused by HW misbehavior (that could have been caused by HW, firmware
and/or OS kernel). in those cases, the only way to get a kernel dump
would be to have
@robstrube,
would you mind stepping back a little bit and making a summary of
attempt changes and effects, and attaching the following information:
- host kernel exact version
- guest kernel exact version
- qemu packages exact version
- windows kernel exact version
- virtual machine xml (virsh
@ozdror, would you mind opening a new bug for your case ? looks like a
different issue as the original issue for this case was a host hang.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Did not work for me. The only thing that so far
seems to work (after 1 test) is restarting libvirtd daemon before
booting the VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
Sorry for all the messages. I've been doing a bit more research and I'd
like some of the folks having problems to try this.
It appears Q35 machines with qemu 4.0+ changed the default ioapic mode
to split, which does not work with with certain hardware combinations.
This is not a new issue with
@Christian, your suspicion is that it's related to this issue:
https://bugs.launchpad.net/qemu/+bug/1826422 ?
I have another system that i'll set 19.10 on and see if I can test out
your fix / get more logging information.
--
You received this bug notification because you are a member of Ubuntu
Looks like another person is having the same problem, I've asked them to post
more details here.
https://askubuntu.com/questions/1185341/qemu-system-freeze-unsigned-kernel-5-3-0-1004-kvm/1185536#1185536
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Not able to change this feature ()
I get the following error:
libvirt.libvirtError: unsupported configuration: unexpected feature 'irqchip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849720
This is a somewhat blind stab,
but I've seen another "windows guest issue on 19.10" report at [1].
I don't have any particular reason to expect it would help, but for a try if
one of the people here could try kernel_irqchip=on that would be nice.
[1]:
So it looks like the problem occurs when updating the kernel from 5.0.x
to 5.3.x. Zach is running Pop_OS 19.04, but System76 will push Ubuntu
kernel updates earlier, so he recently updated and received kernel 5.3,
despite still running a 19.04 base. Questionable practice for sure...
I realize
My colleague, Zach has also run into this exact issue. He's running a
Dell XPS laptop and we'll be posting more information here shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
Disabling the 'r8169' module has no affect on this issue. The system
still hangs when running the VM with networking enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
Running VM
Robert, Brian,
I'm trying to reproduce this issue today. I saw you both said you're
running this in System76 machines, is that correct ? Im asking because I
was wondering if this can be reproduced in any machine or not (thinking
of specific ways to get a kernel dump if I can't reproduce it on my
Here's the main bug report I was thinking about:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841040
The kernel module is 'r8169'.
Brian perhaps you could do an 'lsmod | grep r8169' to see if that module
is loaded for you as well?
If it is, perhaps you could try to blacklist the
One thing I thought of, is that both Brian and I have System76
computers, so perhaps there's a hardware issue specifically with our
computers? Brian, I have a Darter Pro 2019, what model do you have?
Just to clarify I've tried both Pop_OS 19.10 and Ubuntu 19.10 and the
issue is present on both
Hi Christian,
I can tell you what was happening for me.
I run all my VMs through virt-manager, so I first open up virt-manager
and then start my Windows Server 2019 VM. The VM boots fine and I get
to the login screen where I need to send a CTRL+ALT+DELETE to login. A
couple extra seconds after
Ok you both had e1000e as I had in my test.
The guest xml has no very special config that would make me wonder.
You said there is no crash report, and the guest log confirms that it seems to
end kind of normally.
2019-10-23T03:01:14.664402Z qemu-system-x86_64: terminating on signal 15 from
I have ran a win10 install on 19.10 in virt-manager with the e1000e card
that you used as well ... nothing is crashing :-/
And the network surely is used ...
$ virsh domifstat win10 vnet0
vnet0 rx_bytes 9306542
vnet0 rx_packets 51933
vnet0 rx_errs 0
vnet0 rx_drop 0
vnet0 tx_bytes 1591661
vnet0
This is the output of journalctl -u libvirtd. My computer was turned off
when I got home after work, so these logs are the ones that I got as
soon as I turned my machine on and ran my Windows VM:
-- Reboot --
Oct 25 16:49:21 brian-pc systemd[1]: Starting Virtualization daemon...
Oct 25 16:49:22
Hi Christian,
Thank for for the response. This is indeed a troubling bug - especially
since it crashes the entire system. The clarify, I originally posted
about the issue in /r/linux on Reddit, but because of a time critical
deadline I needed to uninstall 19.10. This is my production machine
We will need some more logs, please let me ask for:
"hard crash on the host" is the host kernel crashing and the whole system goes
down?
- If yes, then is there a way to get the log that contains the kernel crash?
- If no then I'd assume you mean that the associated qemu process dies right
Hmm, the only errors/fails I see in the log are related to gnome/xdg-
desktop :-/
So as I understand it Robert reported the bug, but Brian who chimed in
in comment #3 still has a setup to reproduce is that correct?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Brian and Robert,
interesting yet disturbing crash that is - thank you for the report.
The apparmor message you see (at least those in the log provided) are
just from being unable to access an extra disk in
"/home/brian/.seconddrive/windows10/WindowsVM.img".
Which on itself is odd as we ahve
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849720
Title:
I have the same issue with this bug. Can't run a Windows guest on
libvirt + qemu-kvm without my computer crashing. The only way to run a
Windows guest is to disable networking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Accidentally filed bug under qemu-kvm, which is no longer a package
being maintained. The bug affect Ubuntu 19.10 (Eoan).
** No longer affects: qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
45 matches
Mail list logo
