Search results

I'll try with the new kernel 4.13 and 2003/XP mode and report back... [Update]: One machine with 2016 setting crashed, one machine with 2003/XP setting still running (normally crashes within one hour)

@aderumier: I never tried that. If I change this option after the machine is created will the feature be disabled as well?

@PeLLe: there is currently no solution but a workaround, revert back to kernel 4.10, see post: https://forum.proxmox.com/threads/blue-screen-with-5-1.37664/page-7#post-188496

@ktecho: This is something different, watch my thread here: https://forum.proxmox.com/threads/blue-screen-with-5-1.37664/ Quick summary: a bug in KVM, no solution until now. Workaround: Revert back to kernel 4.10, see: https://forum.proxmox.com/threads/blue-screen-with-5-1.37664/page-7#post-188496

I checked pve-kernel-4.13.8-1-pve_4.13.8-27.changelog in the test repository, nothing in it about this bug for now

I'm not sure if I get your question right. You have a Windows server with a hard disk (e.g. a data disk, not OS) and you want to transfer this harddisk (the vm disk) to another server?

@vankooch: it seems that you hit another bug, described here: https://forum.proxmox.com/threads/pve-5-1-kvm-broken-on-old-cpus.37666/ solution: upgrade to 4.13 :-( @AndyDK: can you check the grub start menu on boot? under advanced options you should see the kernel 4.10 line. Can you manually...

@AndyDK: You have to use a text file editor, try nano /etc/default/grub You can save your file when you leave nano, then update-grub and then reboot

@AndyDK: I can confirm that downgrading the kernel fixes the problem if your device is affected

@AndyDK: And to keep on booting the old kernel: https://forum.proxmox.com/threads/blue-screen-with-5-1.37664/page-5#post-186803

@morph027: I'm not using the qxl driver either and still have bluescreens... @wolfgang: any news, can we assist to help you track this down?

@wolfgang: I still have the issue with the 4.13 kernel and normally Windows crashes within one hour. How can I assist you to track this down?

it should be: GRUB_CMDLINE_LINUX_DEFAULT="quiet scsi_mod.use_blk_mq=n" but it didn't work, at least not for me, bug still exists with 4.13 kernel and don't forget to initiate update-grub before reboot

@mbaldini: currently it seems that there are 2 issues. The "easy" issue can be fixed by upgrading the VirtIO drivers to the last stable version. The "difficult" issue seems to be related to some CPU models. wolfgang from the proxmox team is currently looking into it

@canove: Thank you very much for the GRUB instructions, I'm now able to default boot the old kernel (where everything works)! I'm still interested if this bug can be solved, I think wolfgang from proxmox is still looking into it...

@mac.linux.free: still bluescreen, even with scsi_mod.use_blk_mq=n :-(

Thank you, I'll try and report back. I tried to read about this option but it is above my technical knowledge. Can you give a short summary what happens if I use this option?

sorry for my bad Linux knowledge, my grub file attached, there is no kernel line Where to put it?

@mac.linux.free: how can I do that? root@host04:~# sysctl -w scsi_mod.use_blk_mq=n sysctl: cannot stat /proc/sys/scsi_mod/use_blk_mq: No such file or directory @canove: Did you downgrade? How do you manage to start with the old kernel? I've to intercept during booting and change kernel in GRUB...

@canove: Don't forget to update your VirtIO drivers, it seems that this is also necessary...