hardcore_2031 Posted June 1, 2019 Share Posted June 1, 2019 I have a Win10 VM that I have been using for about 18 months. When it was originally set up it was done to the methods set forth by SpaceInvader One at the time. The VM worked like a dream for me for a long time, but then there was a period where I stopped using it for a few months. When I've come back to it now it no longer boots, or if it does I get no indication of such. When I try to RDP to the instance as I used to, I get a connection timeout, and if I try the built in VNC, I get a message. Guest has Initialized the display (yet). I've tried removing some of the extra vdisks that used to be attached to this instance to simplify the boot, but with no luck. Any help is greatly appreciated! prism-diagnostics-20190601-1547.zip Quote Link to comment
tjb_altf4 Posted June 2, 2019 Share Posted June 2, 2019 Try a newer machine type version for i440fx, 3.1 should be available in the drop down. Quote Link to comment
hardcore_2031 Posted June 3, 2019 Author Share Posted June 3, 2019 (edited) Appreciate the response. I changed the machine type to a v3.1 but I'm still seeing the same thing. When I attempt to start this VM, the CPU1 core goes to 100% and stays there until I have to force kill the vm instance. Edited June 3, 2019 by hardcore_2031 double img Quote Link to comment
tjb_altf4 Posted June 3, 2019 Share Posted June 3, 2019 I did notice there is a bios update available for your board, not necessarily the cause of the problem, but lots has changed in the kernel in the last 12 months due to all the security mitigations, as such Limetech recommends updating, in particular for VM users. 1 Quote Link to comment
hardcore_2031 Posted June 5, 2019 Author Share Posted June 5, 2019 I did do that bios update, because I think it was the Intel CPU microcode update for Spectre/Meltdown. As expected it didn't help, nor did a dozen other things I tried, but I did find a workaround. I tried creating and booting a new Win10 VM and it worked, which told me that it was an issue exclusive to my VM and not the KVM subsystem overall or something. When I booted the new VM (which was created with an identical hardware config to the old VM) and saw it get to the "press a button to install windows....", I immediately shut it down. I then went to the domains share and deleted the vdisk of the new VM. Then I copied the old vdisk1.img file from the old VM to the new VM's folder. I again tried to boot the new VM (which was now using the old VM's vdisk) and this time it booted all the way into Windows. Horray! Now I just have 6 months of Windows updates to do. Because this really wasn't a fix for the old VM I'm not going to mark anything solved, but I did want to update what had worked for me in case anyone stumbles across this in the future, and thank tjb_altf4 for their attempts at helping. 1 Quote Link to comment
Fiservedpi Posted June 5, 2019 Share Posted June 5, 2019 (edited) whats up with your debian folder? /mnt/user/domains/Debian/vdisk2.img' your getting a bunch of errors about that vdsik In regards to flood have you changed any file structure? naming? Any gpu pass-through? Also try lowering your ram to 2 or 4gb (just for troubleshooting purposes) did you get the .iso from the windows website? on may 21 seems like someone was hitting your telnet port a few times May 21 21:49:43 PRISM nginx: 2019/05/21 21:49:43 [error] 6717#6717: *1100787 user "admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:44 PRISM nginx: 2019/05/21 21:49:44 [error] 6717#6717: *1100792 user "admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:49 PRISM nginx: 2019/05/21 21:49:49 [error] 6717#6717: *1100802 user "Admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:51 PRISM nginx: 2019/05/21 21:49:51 [error] 6717#6717: *1100802 user "Admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:51 PRISM nginx: 2019/05/21 21:49:51 [error] 6717#6717: *1100806 user "Admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:53 PRISM nginx: 2019/05/21 21:49:53 [error] 6717#6717: *1100806 user "Admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:53 PRISM nginx: 2019/05/21 21:49:53 [error] 6717#6717: *1100810 user "Administrator" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:55 PRISM nginx: 2019/05/21 21:49:55 [error] 6717#6717: *1100810 user "Administrator" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:55 PRISM nginx: 2019/05/21 21:49:55 [error] 6717#6717: *1100817 user "Administrator" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:57 PRISM nginx: 2019/05/21 21:49:57 [error] 6717#6717: *1100817 user "Administrator" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:57 PRISM nginx: 2019/05/21 21:49:57 [error] 6717#6717: *1100822 user "administrator" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:59 PRISM nginx: 2019/05/21 21:49:59 [error] 6717#6717: *1100822 user "administrator" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:49:59 PRISM nginx: 2019/05/21 21:49:59 [error] 6717#6717: *1100826 user "administrator" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:01 PRISM nginx: 2019/05/21 21:50:01 [error] 6717#6717: *1100826 user "administrator" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:01 PRISM nginx: 2019/05/21 21:50:01 [error] 6717#6717: *1100831 user "root": password mismatch, client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:03 PRISM nginx: 2019/05/21 21:50:03 [error] 6717#6717: *1100831 user "root": password mismatch, client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:03 PRISM nginx: 2019/05/21 21:50:03 [error] 6717#6717: *1100835 user "root": password mismatch, client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:05 PRISM nginx: 2019/05/21 21:50:05 [error] 6717#6717: *1100835 user "root": password mismatch, client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:05 PRISM nginx: 2019/05/21 21:50:05 [error] 6717#6717: *1100842 user "admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:07 PRISM nginx: 2019/05/21 21:50:07 [error] 6717#6717: *1100842 user "admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:07 PRISM nginx: 2019/05/21 21:50:07 [error] 6717#6717: *1100846 user "admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:09 PRISM nginx: 2019/05/21 21:50:09 [error] 6717#6717: *1100846 user "admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:09 PRISM nginx: 2019/05/21 21:50:09 [error] 6717#6717: *1100850 user "admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:11 PRISM nginx: 2019/05/21 21:50:11 [error] 6717#6717: *1100850 user "admin" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:11 PRISM nginx: 2019/05/21 21:50:11 [error] 6717#6717: *1100854 user "user" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" May 21 21:50:13 PRISM nginx: 2019/05/21 21:50:13 [error] 6717#6717: *1100854 user "user" was not found in "/etc/nginx/htpasswd", client: 10.20.1.191, server: , request: "GET /Main HTTP/1.1", host: "10.20.1.20" Edited June 5, 2019 by Fiservedpi Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.