VM KVM não é capaz de se conectar via SSH ou virt-manager Ubuntu 16.04

0

Atualmente, estou usando esse XML para criar uma VM

<domain type="kvm">
<name>ubuntu01</name>
<description>Guest-System Ubuntu</description>
  <memory unit='GB'>1</memory>
  <vcpu>1</vcpu>
<os>
    <type arch='x86_64' machine='pc-i440fx-xenial'>hvm</type>
    <boot dev='cdrom'/>
</os>
<iothreads>1</iothreads>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>preserve</on_crash>
<devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='iso/ubuntu-16.04.3-desktop-amd64.iso'/>
      <target dev='hdb' bus='ide'/>
      <address type='drive' controller='0' bus='1' unit='0'/>
    </disk>
    <interface type='bridge'>
      <source bridge='br0'/>
    <model type='virtio'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
  </devices>
</domain>

Meu /etc/network/interfaces é o seguinte

auto lo
iface lo inet loopback
auto br0
iface br0 inet dhcp
      bridge_ports wlx00e61801639d
      bridge_stp off
      bridge_maxwait 0

Quando executo virsh -c qemu:///system list --all , obtenho

 Id    Name                           State
----------------------------------------------------
 1     ubuntu00                       running
 -     ubuntu01                       shut off

meu ifconfig mostra isso

br0       Link encap:Ethernet  HWaddr fe:54:00:d5:86:42  
          inet6 addr: fe80::e8:99ff:fe12:5853/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:440 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:70954 (70.9 KB)  TX bytes:11807 (11.8 KB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:5494 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5494 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:981645 (981.6 KB)  TX bytes:981645 (981.6 KB)

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vnet0     Link encap:Ethernet  HWaddr fe:54:00:d5:86:42  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:440 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:77114 (77.1 KB)  TX bytes:327 (327.0 B)

wlp2s0    Link encap:Ethernet  HWaddr 34:68:95:ee:a3:a3  
          inet addr:192.168.43.33  Bcast:192.168.43.255  Mask:255.255.255.0
          inet6 addr: fe80::f36b:48dd:9c17:aee/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:33736 errors:0 dropped:0 overruns:0 frame:52448
          TX packets:30996 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:28655919 (28.6 MB)  TX bytes:3344218 (3.3 MB)
          Interrupt:19 

se eu fizer arp -a out coloca

? (192.168.43.1) at 1c:99:4c:81:9a:c9 [ether] on wlp2s0

O que estou tentando descobrir agora é como acessar a VM via ssh?

Eu tentei ssh 0.0.0.0 -L 5900:127.0.0.1:5900 ou ssh 0.0.0.0 -L 5900:127.0.0.1:22 , mas isso é só o meu ssh depois de instalar o sudo apt-get install openssh-server em minha própria máquina com bind: Address already in use

Desde Se eu tentar acessá-lo via virt-manager eu recebo

Error connecting to graphical console:
internal error: unable to execute QEMU command 'getfd': No file descriptor supplied via SCM_RIGHTS

E eu tenho esgotado maneiras de tentar resolver isso também.

    
por nadermx 04.02.2018 / 23:25

0 respostas