10

I setup KVM on a remote host, and have a few .iso files out there that I want to play with.

I setup Virt-manager initially on a Ubuntu-mate 15.10 machine, and it seemed to work fine (slow as heck starting the virtual machines) but worked.

Now, I'm trying to do the same with virt-manager from my Ubuntu 16.04 install, and first out of the gate I got a message that I needed ssh-askpass-gnome to be prompted for the password, so I installed it.

Now, when I start the Virt-Manager GUI monitor, it continuously prompts me for my SSH password, and the virtual machine never gets booted? Shouldn't it be booting "headless" when I run it without the monitor anyway?

So, 2 questions to clarify?

  1. why does it keep prompting for my ssh password? I know some people say use keys, but seriously...for new users like me, shouldn't the username password thing work on ssh for playing around?

  2. Why doesn't the VM boot "headless" before the monitor even starts?

Thanks,

BTW - I do have it set to use VNC over Spice...just in case anyone thought that might be the issue.

bmcgonag
  • 171
  • 1
  • 2
  • 12

3 Answers3

6
  • Shut down the guest machine.
  • In the 'Display' section, select All interfaces instead of 'Only localhost'.
  • Restart the guest machine
Erik Norman
  • 29
  • 1
  • 6
4

I have the same trouble. In order to resolve it:

  1. Run ssh-copy-id <your kvm server>.

    In my case, from my laptop: ssh-copy-id hypervisor@IP_OF_MY_UBUNTU_SERVER_RUN_KVM

  2. Now when I connect to virt-manager it doesn't ask for a password and when I want view the GUI console I can without any password request.

David Foerster
  • 36,890
  • 56
  • 97
  • 151
mlemos
  • 41
3

So, I'm a bit of an idiot I guess. I found a different place to set the VNC vs. Spice setting. Not sure why it's in 2 places.

But, to help those trying to find it, should any others fall into what I did, when you start the Monitor (to see the UI), then you'll want to click the 'i' button in the circle on that window.

Then find 'Display' in the left pane, and from there, select VNC. Now shutdown, and restart the VM session, and you should be ok.

bmcgonag
  • 171
  • 1
  • 2
  • 12