I never had a problem accessing my MyhtBuntu VM via VNC.  I don't know if my migration from b15 to rc4 did something (or I did something when I was drunk), but I can no longer connect via VNC.  I *think* I may have opened the XML in the XML editor and clicked the "Update" button without making any changes to the content.  Would this have done something?

 

Why is it trying to connect to port 5700 when port 5900 is defined:

 

 

 

 

Here is my XML:

 

<domain type='kvm'>
  <name>PVRSERVER</name>
  <uuid>7467f622-dfe7-0120-e5d1-2e9b921df490</uuid>
  <metadata>
    <vmtemplate name="Custom" icon="linux.png" os="linux"/>
  </metadata>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='3'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-2.2'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='2' threads='1'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/cache/VMs/PVRSERVER/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/Images/mythbuntu-14.04.2-desktop-amd64.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0' multifunction='on'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='dmi-to-pci-bridge'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
    </controller>
    <controller type='pci' index='2' model='pci-bridge'>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
    </controller>
    <filesystem type='mount' accessmode='passthrough'>
      <source dir='/mnt/'/>
      <target dir='unraid'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
    </filesystem>
    <interface type='bridge'>
      <mac address='52:54:00:a9:7b:12'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/PVRSERVER.org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='vmvga' vram='16384' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
</domain>

Drunk administration can lead to faulty operation. Maybe need to add that to the wiki ;-)

 

I'll have to review the xml when I get home (mobile right now).

Thanks Jon.

 

I imagine this is the relevant section:

 

    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>

 

port = '-1'

websocket = '-1'

 

John

Thanks Jon.

 

I imagine this is the relevant section:

 

    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>

 

port = '-1'

websocket = '-1'

 

John

 

Hmm, I'm not sure why that's not working for you right now.  The port 5700 isn't an issue, as I see the same on mine, even though the webGui reports 5900.  The 5900 should be right.

 

Websocket = -1 enables you to connect via VNC through a browser.  If that wasn't set, you wouldn't be able to connect.  However, I believe websocket connections for VNC go to port 5700, whereas a regular VNC connection from a client would be 5900 (I could be wrong on the 5700 port thing, but I vaguely remember the details reading about this at one point).

 

If you use a client like RealVNC or TigerVNC to connect to your unRAID server's IP but port 5900, does that work?

EDIT:  Must be a Chrome issue.  I can connect from IE.

 

Yepper...

 

Hmm, can you go to the VM settings page, click Help, then at the bottom, there is a link to the libvirt log directly. Anything in there popping out?

And I use chrome right now and its working fine.

 

 

EDIT:  Same issue on my otehr machine using Chrome.

 

And I have always used Chrome in the past.  Wonder if I mucked with the settings or installed a plugin that novnc doesn't like.

 

I'll try my other machine that has Chrome and see if I get the same result.

I find I often have trouble getting the web based VNC (I am using Chrome) to connect to the VM.  Using a different client such as realVNC or UltraVNC works fine.

Well, I deleted the VM (not the vdisk) and recreated it just in case there was something funky in the old one.  No help.

Well, I deleted the VM (not the vdisk) and recreated it just in case there was something funky in the old one.  No help.

Hmm, wondering if you have an old domain image file from when this was a plugin.

Well, I deleted the VM (not the vdisk) and recreated it just in case there was something funky in the old one.  No help.

Hmm, wondering if you have an old domain image file from when this was a plugin.

 

That is very possible.  Tomorrow when I have some time I am going to start from scrath with a new mythbuntu VM.

 

I'll report back.

Well, I deleted the VM (not the vdisk) and recreated it just in case there was something funky in the old one.  No help.

Hmm, wondering if you have an old domain image file from when this was a plugin.

 

That is very possible.  Tomorrow when I have some time I am going to start from scrath with a new mythbuntu VM.

 

I'll report back.

I meant the domain.img file on your flash device.

Ohhhh...didn't think of that.  TBH...i feel like my flash drive has gotten quite junked up over the course of beta/rc releases.  I may just burn it down and start from scratch.

 

 

Ohhhh...didn't think of that.  TBH...i feel like my flash drive has gotten quite junked up over the course of beta/rc releases.  I may just burn it down and start from scratch.

"took my stapler..."

 

I burned it down but of course forgot to add my necessary changes to the syslinux.cfg:

 

intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1

 

Rebooting...again.

OK, I did a complete reinstall (clean...no plugins) and Chrome clients still cannot connect to VNC.  IE and TightVNC work fine.

 

As I said before, I used Chrome almost exclusively and never had any issues.  Maybe Google released a patch that buggered things?  My Chrome version is...

 

Version 43.0.2357.81 m

 

John

Defect Report -->  http://lime-technology.com/forum/index.php?topic=40492.0