[Ovirt-devel] Re: blocked on virt-viewer in Ovirt install preparation
Perry N. Myers
pmyers at redhat.com
Thu Aug 7 12:49:11 UTC 2008
Before we get started on debugging this... I noticed in your earlier
emails that you're using the following versions of software:
> kernel-2.6.25-0.218.rc8.git7.fc9.x86_64
> kvm-65-1.fc9.x86_64
> libvirt-0.4.1-4.fc9.x86_64
> virt-manager-0.5.4-2.fc9.x86_64
> virt-viewer-0.0.3-1.fc9.x86_64
I'm using:
kernel-2.6.25.11-97.fc9.x86_64
kvm-65-7.fc9.x86_64
libvirt-0.4.4-2.fc9.x86_64
virt-manager-0.5.4-4.fc9.x86_64
virt-viewer-0.0.3-1.fc9.x86_64
The versions of the kernel and kvm shouldn't be causing any problems, but
the version of libvirt is very old. Please run a yum update on your
system and try your tests again with the latest version of the RPMs
available for F9.
We probably need to add a check to the create-wui-appliance script to
check for a specific minimum version of libvirt. The assumption for right
now is that oVirt should be used on a Fedora 9 box with the latest updates
installed.
Also... Make sure to restart libvirt after the upgrade, otherwise the
daemon won't be the latest version. Try things out after that and let me
know if you're seeing the same problems.
Perry
>
>
> I tried several times but still fails for me.
> Here is the steps of my installation.
>
> 1) #bash create-wui-appliance.sh -d "`pwd`" -v
>
>
> Domain node3 defined from /tmp/tmp.uf02Scb6Jq
>
> Domain node4 defined from /tmp/tmp.oYYPU1RmEJ
>
> Domain node5 defined from /tmp/tmp.sfDi0RKEwA
>
> Network dummybridge destroyed
>
> Network dummybridge has been undefined
>
> Network dummybridge defined from /tmp/tmp.K0RCG16KS2
>
> Network dummybridge started
>
> Network dummybridge marked as autostarted
>
> Domain developer defined from /tmp/tmp.LWLYom3gGz
>
> Application defined using disk located at
> /var/lib/libvirt/images/developer.img.
> Run virsh start developer to start the appliance
>
> 2) #virsh start developer
>
> Domain developer started
>
> 3��#virt-viewer developer
> libvir: Remote error : unsupported authentication type 2
> unable to connect to libvirt xen
>
> The command of 'virt-viewer developer' connect to the guest running
> under xen, we have to connect to the guest developer running under QEMU.
> (Maybe it's better to do some explanation of this command in Ovirt
> install instruction)
>
> I try to connect to developer as follows, still fail for me.
>
> [root at test]# virt-viewer -c qemu:///system developer
> libvir: Remote error : unsupported authentication type 2
> unable to connect to libvirt qemu:///system
>
> [root at test]# virt-viewer -c qemu:///system 6
> libvir: Remote error : unsupported authentication type 2
> unable to connect to libvirt qemu:///system
>
> [root at test]# virt-viewer --connect qemu:///system 6
> libvir: Remote error : unsupported authentication type 2
> unable to connect to libvirt qemu:///system
>
> Actually, the developer domain run normally.
>
> virsh # list --all
> Id Name State
> ----------------------------------
> 6 developer running
> - node3 shut off
> - node4 shut off
> - node5 shut off
>
>
> virsh # dumpxml developer
> <domain type='kvm' id='6'>
> <name>developer</name>
> <uuid>bae8bbf9-2b42-4e3d-326d-db6869874ee5</uuid>
> <memory>786432</memory>
> <currentMemory>786432</currentMemory>
> <vcpu>1</vcpu>
> <os>
> <type arch='i686' machine='pc'>hvm</type>
> <boot dev='hd'/>
> </os>
> <clock offset='utc'/>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>destroy</on_crash>
> <devices>
> <emulator>/usr/bin/qemu-kvm</emulator>
> <disk type='file' device='disk'>
> <source file='/var/lib/libvirt/images/developer.img'/>
> <target dev='hda' bus='ide'/>
> </disk>
> <interface type='network'>
> <mac address='52:54:00:8f:9e:3f'/>
> <source network='default'/>
> <target dev='vnet0'/>
> </interface>
> <interface type='network'>
> <mac address='52:54:00:f3:8e:92'/>
> <source network='dummybridge'/>
> <target dev='vnet1'/>
> </interface>
> <input type='mouse' bus='ps2'/>
> <graphics type='vnc' port='5900' autoport='yes' listen='127.0.0.1'/>
> </devices>
> </domain>
>
> I tried to connect developer again and again, but still fail for me.
>
> [root at test]# virt-viewer -c qemu:///system developer
> libvir: Remote error : unsupported authentication type 2
> unable to connect to libvirt qemu:///system
>
> [root at test]# virt-viewer -c qemu+tcp://localhost/system developer
> libvir: Remote error : Connection refused
> unable to connect to libvirt qemu+tcp://localhost/system
>
> [root at test]# virt-viewer -c qemu+tcp:///system developer
> libvir: Remote error : Connection refused
> unable to connect to libvirt qemu+tcp:///system
>
> [root at test]# virt-viewer -c qemu+tcp://root@localhost/system developer
> libvir: Remote error : Connection refused
> unable to connect to libvirt qemu+tcp://root@localhost/system
>
> However, I can connect to it by virsh successfully.
>
> [root at test]# virsh -c qemu:///system
> Welcome to virsh, the virtualization interactive terminal.
>
> Type: 'help' for help with commands
> 'quit' to quit
>
>
>
> > Also, give me the output of:
> > virsh list --all
> > virsh dumpxml developer
> >
> > > Here is the dummybridge output for my own machine.
> > >
> > > dummybridge Link encap:Ethernet HWaddr 00:FF:99:97:1A:8F
> > > inet addr:192.168.50.1 Bcast:192.168.50.255
> Mask:255.255.255.0
> > > inet6 addr: fe80::3cb0:b6ff:feed:cab/64 Scope:Link
> > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:0
> > > RX bytes:0 (0.0 b) TX bytes:4427 (4.3 KiB)
> > >
> > > #ssh -fY root at 192.168.50.1 firefox -no-remote
> > > Error: no display specified
> >
> > This is sshing to your physical host running Fedora 9, so this is not
> > going to work.
> >
> > > Does this fail because of putty? The set up machine isn't on my
> hand, I
> > > connect to it
> > > by putty. Do I have to install it on my local machine?
> >
> > The command is trying to run firefox on a remote display using X
> > forwarding. If you are running these commands in Putty on a Windows box
> > none of this will work since Windows can't natively display X
> > applications. The easiest way to do this is to log into the local
> console
> > of the host that is running F9 and the developer appliance. From the
> > local console open up an xterm and run the ssh commands from there.
>
> Thanks for your advise and I do again. I can't ssh to it yet.
>
> [root at test]# ssh -fY root at 192.168.50.2 firefox -no-remote
> ssh: connect to host 192.168.50.2 port 22: No route to host
>
> Then I try to ssh to my physical host(ssh -fY root at 192.168.50.1
> firefox -no-remote), and I can bring up
> the main firefox screen on the guest, which verify the Xterm and
> display X works for me.
>
> Thanks!
>
> >
> > Perry
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ovirt-devel mailing list
> Ovirt-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/ovirt-devel
--
|=- Red Hat, Engineering, Emerging Technologies, Boston -=|
|=- Email: pmyers at redhat.com -=|
|=- Office: +1 412 474 3552 Mobile: +1 703 362 9622 -=|
|=- GnuPG: E65E4F3D 88F9 F1C9 C2F3 1303 01FE 817C C5D2 8B91 E65E 4F3D -=|
More information about the ovirt-devel
mailing list