11:30 a.m.
----- Original Message -----
From: "Mikola Rose" <mrose(a)power-soft.com>
To: "Yedidyah Bar David" <didi(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Thursday, January 8, 2015 2:03:08 AM
Subject: Re: [ovirt-users] HostedEngine Deployment Woes
I am also Seeing this in the messages.log
Jan 7 13:55:39 pws-hv15 vdsm vds ERROR unexpected error#012Traceback (most
recent call last):#012 File "/usr/share/vdsm/BindingXMLRPC.py", line 1070,
in wrapper#012 res = f(*args, **kwargs)#012 File
"/usr/share/vdsm/BindingXMLRPC.py", line 314, in vmSetTicket#012 return
vm.setTicket(password, ttl, existingConnAction, params)#012 File
"/usr/share/vdsm/API.py", line 610, in setTicket#012 return
v.setTicket(password, ttl, existingConnAction, params)#012 File
"/usr/share/vdsm/vm.py", line 4560, in setTicket#012 graphics =
_domParseStr(self._dom.XMLDesc(0)).childNodes[0]. \#012AttributeError:
'NoneType' object has no attribute 'XMLDesc'
Jan 7 13:55:39 pws-hv15 sanlock[2152]: 2015-01-07 13:55:39-0800 6412 [2152]:
cmd 9 target pid 7899 not found
Jan 7 13:55:40 pws-hv15 vdsm vm.Vm WARNING
vmId=`edc69fdd-6188-4dce-b1dc-d5ed03f914e5`::_readPauseCode unsupported by
libvirt vm
When? When you try to connect with virsh?
Note that you need to create a temporary password with:
hosted-engine --add-console-password
On Jan 7, 2015, at 1:58 PM, Mikola Rose
<mrose@power-soft.com<mailto:mrose@power-soft.com>> wrote:
Also tried;
[root@pws-hv15 ~]# virsh -c qemu+tls://pws-hv15.power-soft.net/system console
HostedEngine
Connected to domain HostedEngine
Escape character is ^]
no prompts or interaction after the Escape character line
iirc 'console' connects you to the serial console, not vnc, no?
On Jan 7, 2015, at 1:42 PM, Mikola Rose
<mrose@power-soft.com<mailto:mrose@power-soft.com>> wrote:
I tried realvnc
How exactly?
You need to connect to the host where it runs.
BTW, do you have there other VMs? If you migrated the engine vm there
after you already had other VMs, it will not get console '0' but some
other.
The log file doesn’t really tell me whats going on that I can see
2015-01-07 21:35:15.381+0000: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name HostedEngine -S -M rhel6.5.0
-cpu Westmere -enable-kvm -m 4096 -realtime mlock=off -smp
2,sockets=2,cores=1,threads=1 -uuid edc69fdd-6188-4dce-b1dc-d5ed03f914e5
-smbios type=1,manufacturer=Red Hat,product=RHEV
Hypervisor,version=6Server-6.6.0.2.el6,serial=4C4C4544-0036-5210-8036-B1C04F4A3032_d4:ae:52:d1:91:7a,uuid=edc69fdd-6188-4dce-b1dc-d5ed03f914e5
-nodefconfig -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/HostedEngine.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=2015-01-07T21:35:15,driftfix=slew -no-reboot -no-shutdown -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive
file=/rhel-server-6.6-x86_64-dvd.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,serial=
-device
ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1
-drive
file=/var/run/vdsm/storage/9b103e2f-d35b-4b56-a380-a374c21219d1/bdfd32e0-8116-4d29-baa2-6f6a98d981c6/9d2b9c8d-9005-4cb9-836b-a3848a24b4c4,if=none,id=drive-virtio-disk0,format=raw,serial=bdfd32e0-8116-4d29-baa2-6f6a98d981c6,cache=none,werror=stop,rerror=stop,aio=threads
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0
-netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:64:dd:63,bus=pci.0,addr=0x3
-chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/edc69fdd-6188-4dce-b1dc-d5ed03f914e5.com.redhat.rhevm.vdsm,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
-chardev
socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/edc69fdd-6188-4dce-b1dc-d5ed03f914e5.org.qemu.guest_agent.0,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
-chardev pty,id=charconsole0 -device
virtconsole,chardev=charconsole0,id=console0 -vnc 0:0,password -vga cirrus
-msg timestamp=on
char device redirected to /dev/pts/1
Sorry, no idea.
Please try getting some more info from the vnc client.
I personally use tightvnc on linux and verified that it can connect to
a hosted-engine console.
I am also changing the subject to attract others...
On Jan 7, 2015, at 12:18 AM, Yedidyah Bar David
<didi@redhat.com<mailto:didi@redhat.com>> wrote:
----- Original Message -----
From: "Mikola Rose"
<mrose@power-soft.com<mailto:mrose@power-soft.com>>
To: "Yedidyah Bar David" <didi@redhat.com<mailto:didi@redhat.com>>
Cc: users@ovirt.org<mailto:users@ovirt.org>
Sent: Wednesday, January 7, 2015 3:29:24 AM
Subject: Re: [ovirt-users] HostedEngine Deployment Woes
Thanks for the tip. That seemed to work and after fixing my nfs issues and
removing that config the hosted setup completed to the point of creating the
vm and waiting for the os to be installed on it, however...
Thanks for the report!
I try to connect to the vm via vnc and it just flashes and closes vnc. Vnc
log indicated an unexpected close.
We're are the logs for the vnc server end of things so I can see why it's
closing the session?
The "vnc server" here is qemu. You should find its logs on the host in
/var/log/libvirt/qemu/HostedEngine.log or something like that.
What vnc client do you use?
I managed to connect using merely vncclient over an ssh tunnel, in case
more complicated tools (remote-viewer etc) fail.
Best,
--
Didi