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?
Blue screen with 5.1
- Thread starter cybermcm
- Start date
Yes! I've got 2 servers the one with 700GB (former main server) And another with only 100 GB only datadisks i want to add the 700GB disk to the other server so it got the 700GB disk, then i can delete the main server (and make the 2. server to main) make it sense?
I've run into a similar error...see if this helps: https://forum.proxmox.com/threads/installing-proxmox-5-0b2-on-hp-dl360-g5.35382/
Shutdown both machines (or at least, shut down the one you are removing the drive from). Manually edit the config files for both VMs (in /etc/pve/qemuserver/ ) and move the line for the particular virtual drive from the one machine to the other. The VM-id in the name of the virtual disk should stay the same - it should be the old one's ID, not the new one's. Save the configs, and start the new machine if you had shut it down. Now it should see both disks. Use Disk Management to change the drive letters if you need to.Yes! I've got 2 servers the one with 700GB (former main server) And another with only 100 GB only datadisks i want to add the 700GB disk to the other server so it got the 700GB disk, then i can delete the main server (and make the 2. server to main) make it sense?
In order to get all the data on a properly-named virtual disk, add a new disk to the VM, then copy all the data over to it, either at teh virtual disk level (using command line) or inside the virtual machine.
If you need more assistance on this, please create a new thread as this is not an issue related to this topic.
OK I’ve just hit this problem now. My host normally runs around 25 - 50% utilised on RAM so wasn’t hitting it. However have some BSOD Windows boxes this morning and looking my RAM is full. KSM has kicked in along with swap.
There’s no way this should have got to 100% RAM usage so think the memory leak I’ve read about affected me as well. Going back to the 4.10 kernel.
Can I suggest that you continue updates on the 4.10 kernel line until 4.13 is fixed and safe to use? Seems like this might take quite a bit of work and time to get resolved.
@cybermcm Thank you for the hint. A newer version of the kernel make my VM crash...we get BSOD! So I'm stucked which is not good...
don't known if it's related, but new qemu patches have been sent on qemu-devel,
with fix for hyperv and msr.
https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg04221.html
with fix for hyperv and msr.
https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg04221.html
Thx for the info, but this will disable all CPU cores and leave only one for the system, which is not really s solution.
I can also confirm that the new kernel 4.13.4-1 still has problems with BSOD...
@wolfgang Maybe it would be nice to have a sticky post in the forum. I've lost two weeks trying to debug this and the information is between 3 different posts in the forum. Just a suggestion. Thanks for the effort to track down the issue.
Same here... BSOD on 3 days old Win Server 2016 standart. mostly over night. QEMU Agent is on. VIRTIO drivers installed.
Any solution ?
Any solution ?
@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
https://forum.proxmox.com/threads/blue-screen-with-5-1.37664/page-7#post-188496
@aderumier: I never tried that. If I change this option after the machine is created will the feature be disabled as well?
yes you can change it after install.
it's just add or remove some hyperv cpu flags to qemu command line.
any news for today ?
just wonder if this qemu fix for hyperv and msr could help
https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg04221.html
@aderumier: I canceled my test yesterday because of some unhappy circumstances. I'll try again today, starting now..