Jump to content

(SOLVED) VM not booting after 6.6.7 update


lotetreemedia

Recommended Posts

Updated to 6.6.7 this morning. Everything seems dandy bar one VM issue.

 

Windows 10 VM 

with a GTX1070 passed through.

 

tried to start the VM after update and I couldn't RDP into it.

 

Switched the Graphics card to VNC / QXL to see what was happening and it booted just fine. 

I noticed however that the network adapter was replaced with another one Red Hat .... #2 - So I changed the IP of the new adapter to the old static IP and I could RDP back into it just fine.

 

However If i switch back to the 1070 I can't RDP / ping the VM.

 

Any ideas?

 

limnas-diagnostics-20190223-1408.zip

Link to comment
2019-02-23T14:58:23.694736Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
2019-02-23T14:58:33.950288Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.950474Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.950687Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.950824Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.950957Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.951096Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.951355Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.951495Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.953427Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.957654Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.957876Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.958020Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.958177Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.958323Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.959068Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.959214Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.961088Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.965271Z qemu-system-x86_64: vhost_region_add_section:Section rounded to c0000000 prior to previous c0000030
2019-02-23T14:58:33.972969Z qemu-system-x86_64: VFIO_MAP_DMA: -14
2019-02-23T14:58:33.972975Z qemu-system-x86_64: vfio_dma_map(0x1528a63b1140, 0x800000000000, 0x2000000, 0x15268de00000) = -14 (Bad address)

Tried recreating the VM and same problem.

Clicking on logs for the VM shows this :/

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...