[libvirt] Installing libvirt 0.8.6 Ubuntu 9.10
Hello When installing libvirt 0.8.6, I've passed ./configure, but when I execute make, I've got CCLD libvirtd ../src/.libs/libvirt_driver_qemu.a(libvirt_driver_qemu_la-qemu_driver.o): In function `qemudVPAssociatePortProfiles': /home/chubut/libvirt-0.8.6/src/qemu/qemu_driver.c:11881: undefined reference to `vpAssociatePortProfileId' /home/chubut/libvirt-0.8.6/src/qemu/qemu_driver.c:11898: undefined reference to `vpDisassociatePortProfileId' collect2: ld returned 1 exit status make[3]: *** [libvirtd] Error 1 make[3]: Leaving directory `/home/chubut/libvirt-0.8.6/daemon' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/chubut/libvirt-0.8.6/daemon' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/chubut/libvirt-0.8.6' make: *** [all] Error 2 chubut@chubut:~/libvirt-0.8.6$ Do you have any help? Thank you. Marcela
2011/1/20 Marcela Castro León <mcastrol@gmail.com>:
Hello When installing libvirt 0.8.6, I've passed ./configure, but when I execute make, I've got
CCLD libvirtd ../src/.libs/libvirt_driver_qemu.a(libvirt_driver_qemu_la-qemu_driver.o): In function `qemudVPAssociatePortProfiles': /home/chubut/libvirt-0.8.6/src/qemu/qemu_driver.c:11881: undefined reference to `vpAssociatePortProfileId' /home/chubut/libvirt-0.8.6/src/qemu/qemu_driver.c:11898: undefined reference to `vpDisassociatePortProfileId' collect2: ld returned 1 exit status make[3]: *** [libvirtd] Error 1 make[3]: Leaving directory `/home/chubut/libvirt-0.8.6/daemon' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/chubut/libvirt-0.8.6/daemon' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/chubut/libvirt-0.8.6' make: *** [all] Error 2 chubut@chubut:~/libvirt-0.8.6$
Unfortunately 0.8.6 contains this compile error on systems without macvtap support, like Ubuntu. You either need to backport this patch [1] to 0.8.6 or use the latest libvirt release 0.8.7 instead. [1] http://libvirt.org/git/?p=libvirt.git;a=commit;h=474b1c1487828a17fe9e1025901... Matthias
thank you, i've solved installing 0.8.7 2011/1/20 Matthias Bolte <matthias.bolte@googlemail.com>
2011/1/20 Marcela Castro León <mcastrol@gmail.com>:
Hello When installing libvirt 0.8.6, I've passed ./configure, but when I execute make, I've got
CCLD libvirtd ../src/.libs/libvirt_driver_qemu.a(libvirt_driver_qemu_la-qemu_driver.o): In function `qemudVPAssociatePortProfiles': /home/chubut/libvirt-0.8.6/src/qemu/qemu_driver.c:11881: undefined reference to `vpAssociatePortProfileId' /home/chubut/libvirt-0.8.6/src/qemu/qemu_driver.c:11898: undefined reference to `vpDisassociatePortProfileId' collect2: ld returned 1 exit status make[3]: *** [libvirtd] Error 1 make[3]: Leaving directory `/home/chubut/libvirt-0.8.6/daemon' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/chubut/libvirt-0.8.6/daemon' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/chubut/libvirt-0.8.6' make: *** [all] Error 2 chubut@chubut:~/libvirt-0.8.6$
Unfortunately 0.8.6 contains this compile error on systems without macvtap support, like Ubuntu.
You either need to backport this patch [1] to 0.8.6 or use the latest libvirt release 0.8.7 instead.
[1] http://libvirt.org/git/?p=libvirt.git;a=commit;h=474b1c1487828a17fe9e1025901...
Matthias
Hello I've finished the installation. The daemon is not up, so I've tried in that way: chubut@chubut:/usr/local/sbin$ sudo ./libvirtd start start 11:23:17.543: 6168: warning : networkAddGeneralIptablesRules:1097 : Could not add rule to fixup DHCP response checksums on network 'default'. 11:23:17.543: 6168: warning : networkAddGeneralIptablesRules:1098 : May need to update iptables package & kernel to support CHECKSUM rule. 11:23:17.577: 6168: warning : qemudStartup:1331 : Unable to create cgroup for driver: No such device or address 11:23:17.704: 6168: warning : lxcStartup:2128 : Unable to create cgroup for driver: No such device or address And stay there, doesn't finish, and not start. Can you tell me if i'm doing in the right way? thank you. Marcela 2011/1/20 Marcela Castro León <mcastrol@gmail.com>
thank you, i've solved installing 0.8.7
2011/1/20 Matthias Bolte <matthias.bolte@googlemail.com>
2011/1/20 Marcela Castro León <mcastrol@gmail.com>:
Hello When installing libvirt 0.8.6, I've passed ./configure, but when I execute make, I've got
CCLD libvirtd
../src/.libs/libvirt_driver_qemu.a(libvirt_driver_qemu_la-qemu_driver.o): In
function `qemudVPAssociatePortProfiles': /home/chubut/libvirt-0.8.6/src/qemu/qemu_driver.c:11881: undefined reference to `vpAssociatePortProfileId' /home/chubut/libvirt-0.8.6/src/qemu/qemu_driver.c:11898: undefined reference to `vpDisassociatePortProfileId' collect2: ld returned 1 exit status make[3]: *** [libvirtd] Error 1 make[3]: Leaving directory `/home/chubut/libvirt-0.8.6/daemon' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/chubut/libvirt-0.8.6/daemon' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/chubut/libvirt-0.8.6' make: *** [all] Error 2 chubut@chubut:~/libvirt-0.8.6$
Unfortunately 0.8.6 contains this compile error on systems without macvtap support, like Ubuntu.
You either need to backport this patch [1] to 0.8.6 or use the latest libvirt release 0.8.7 instead.
[1] http://libvirt.org/git/?p=libvirt.git;a=commit;h=474b1c1487828a17fe9e1025901...
Matthias
On 20/01/2011, at 9:26 PM, Marcela Castro León wrote: Hello
I've finished the installation. The daemon is not up, so I've tried in that way:
chubut@chubut:/usr/local/sbin$ sudo ./libvirtd start start 11:23:17.543: 6168: warning : networkAddGeneralIptablesRules:1097 : Could not add rule to fixup DHCP response checksums on network 'default'. 11:23:17.543: 6168: warning : networkAddGeneralIptablesRules:1098 : May need to update iptables package & kernel to support CHECKSUM rule. 11:23:17.577: 6168: warning : qemudStartup:1331 : Unable to create cgroup for driver: No such device or address 11:23:17.704: 6168: warning : lxcStartup:2128 : Unable to create cgroup for driver: No such device or address
And stay there, doesn't finish, and not start.
Can you tell me if i'm doing in the right way?
Hi Marcela, When you start the libvirt daemon from the command line, it keeps in the foreground, without going back to a shell prompt. ie: $ sudo./libvirtd (various messages print out here, but libvirtd doesn't exit) Since the libvirt daemon has effectively taken over that terminal session, if I start another terminal session, I can generally use virsh to connect to it. Have you tried that? Starting a new terminal session while libvirtd is running, and then using virsh or virt-manager or something. ? Regards and best wishes, Justin Clift
Hello I've got this error. *chubut@chubut:/usr/local$ virsh -c qemu:///system list error: unable to connect to '/usr/local/var/run/libvirt/libvirt-sock', libvirtd may need to be started: No such file or directory error: failed to connect to the hypervisor* The daemon is not running, but i don't know how to start it. Thank you. 2011/1/20 Justin Clift <jclift@redhat.com>
On 20/01/2011, at 9:26 PM, Marcela Castro León wrote: Hello
I've finished the installation. The daemon is not up, so I've tried in
that way:
chubut@chubut:/usr/local/sbin$ sudo ./libvirtd start start 11:23:17.543: 6168: warning : networkAddGeneralIptablesRules:1097 : Could
not add rule to fixup DHCP response checksums on network 'default'.
11:23:17.543: 6168: warning : networkAddGeneralIptablesRules:1098 : May need to update iptables package & kernel to support CHECKSUM rule. 11:23:17.577: 6168: warning : qemudStartup:1331 : Unable to create cgroup for driver: No such device or address 11:23:17.704: 6168: warning : lxcStartup:2128 : Unable to create cgroup for driver: No such device or address
And stay there, doesn't finish, and not start.
Can you tell me if i'm doing in the right way?
Hi Marcela,
When you start the libvirt daemon from the command line, it keeps in the foreground, without going back to a shell prompt.
ie:
$ sudo./libvirtd (various messages print out here, but libvirtd doesn't exit)
Since the libvirt daemon has effectively taken over that terminal session, if I start another terminal session, I can generally use virsh to connect to it.
Have you tried that? Starting a new terminal session while libvirtd is running, and then using virsh or virt-manager or something.
?
Regards and best wishes,
Justin Clift
On 20/01/2011, at 9:52 PM, Marcela Castro León wrote: Hello
I've got this error. chubut@chubut:/usr/local$ virsh -c qemu:///system list error: unable to connect to '/usr/local/var/run/libvirt/libvirt-sock', libvirtd may need to be started: No such file or directory error: failed to connect to the hypervisor
The daemon is not running, but i don't know how to start it.
Ok, this might be a dumb question, but have you tried "sudo virsh -c qemu:///system list" (with the "sudo") when the libvirtd program is running?
Hello I think now is running. I've started doing *chubut@chubut:/usr/local/sbin$ sudo ./libvirtd & * and checked doing *chubut@chubut:~$ ps -ef | grep libvirtd chubut 1877 1700 0 12:16 pts/0 00:00:00 grep --color=auto libvirtd chubut@chubut:~$ ps -ef | grep libvirtd root 1945 1721 0 12:17 pts/1 00:00:00 ./libvirtd chubut 1993 1700 0 12:17 pts/0 00:00:00 grep --color=auto libvirtd chubut@chubut:~$ sudo virsh -c qemu:///system list Id Name State ---------------------------------- chubut@chubut:~$ * Do you think it's right? Thank you very much. Marcela 2011/1/20 Justin Clift <jclift@redhat.com>
I've got this error. chubut@chubut:/usr/local$ virsh -c qemu:///system list error: unable to connect to '/usr/local/var/run/libvirt/libvirt-sock',
On 20/01/2011, at 9:52 PM, Marcela Castro León wrote: Hello libvirtd may need to be started: No such file or directory
error: failed to connect to the hypervisor
The daemon is not running, but i don't know how to start it.
Ok, this might be a dumb question, but have you tried "sudo virsh -c qemu:///system list" (with the "sudo") when the libvirtd program is running?
On 01/20/2011 12:20 PM, Marcela Castro León wrote:
Hello I think now is running. I've started doing
*chubut@chubut:/usr/local/sbin$ sudo ./libvirtd & * and checked doing
*chubut@chubut:~$ ps -ef | grep libvirtd chubut 1877 1700 0 12:16 pts/0 00:00:00 grep --color=auto libvirtd chubut@chubut:~$ ps -ef | grep libvirtd root 1945 1721 0 12:17 pts/1 00:00:00 ./libvirtd chubut 1993 1700 0 12:17 pts/0 00:00:00 grep --color=auto libvirtd chubut@chubut:~$ sudo virsh -c qemu:///system list Id Name State ----------------------------------
chubut@chubut:~$ *
Do you think it's right? Thank you very much.
Marcela
Please try as a root or via sudo: # netstat -nlp | grep libvirt; you should see something like: --- SNIP --- root@anubis:~# netstat -nlp | grep libvirt unix 2 [ ACC ] STREAM LISTENING 5787 3271/libvirtd /var/run/libvirt/libvirt-sock --- SNIP --- Z.
2011/1/20 Justin Clift <jclift@redhat.com>
I've got this error. chubut@chubut:/usr/local$ virsh -c qemu:///system list error: unable to connect to '/usr/local/var/run/libvirt/libvirt-sock',
On 20/01/2011, at 9:52 PM, Marcela Castro León wrote: Hello libvirtd may need to be started: No such file or directory
error: failed to connect to the hypervisor
The daemon is not running, but i don't know how to start it.
Ok, this might be a dumb question, but have you tried "sudo virsh -c qemu:///system list" (with the "sudo") when the libvirtd program is running?
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
-- Zdenek Styblik Net/Linux admin OS TurnovFree.net email: stybla@turnovfree.net jabber: stybla@jabber.turnovfree.net
Hello: I've got this: Thanks. * chubut@chubut:/usr/local/sbin$ sudo netstat -nlp | grep libvirt unix 2 [ ACC ] STREAM LISTENING 10732 1945/libvirtd /usr/local/var/run/libvirt/libvirt-sock unix 2 [ ACC ] STREAM LISTENING 10734 1945/libvirtd /usr/local/var/run/libvirt/libvirt-sock-ro chubut@chubut:/usr/local/sbin$ * 2011/1/20 Zdenek Styblik <stybla@turnovfree.net>
Hello I think now is running. I've started doing
*chubut@chubut:/usr/local/sbin$ sudo ./libvirtd & * and checked doing
*chubut@chubut:~$ ps -ef | grep libvirtd chubut 1877 1700 0 12:16 pts/0 00:00:00 grep --color=auto
chubut@chubut:~$ ps -ef | grep libvirtd root 1945 1721 0 12:17 pts/1 00:00:00 ./libvirtd chubut 1993 1700 0 12:17 pts/0 00:00:00 grep --color=auto
On 01/20/2011 12:20 PM, Marcela Castro León wrote: libvirtd libvirtd
chubut@chubut:~$ sudo virsh -c qemu:///system list Id Name State ----------------------------------
chubut@chubut:~$ *
Do you think it's right? Thank you very much.
Marcela
Please try as a root or via sudo: # netstat -nlp | grep libvirt;
you should see something like: --- SNIP --- root@anubis:~# netstat -nlp | grep libvirt unix 2 [ ACC ] STREAM LISTENING 5787 3271/libvirtd /var/run/libvirt/libvirt-sock --- SNIP ---
Z.
2011/1/20 Justin Clift <jclift@redhat.com>
I've got this error. chubut@chubut:/usr/local$ virsh -c qemu:///system list error: unable to connect to '/usr/local/var/run/libvirt/libvirt-sock',
On 20/01/2011, at 9:52 PM, Marcela Castro León wrote: Hello libvirtd may need to be started: No such file or directory
error: failed to connect to the hypervisor
The daemon is not running, but i don't know how to start it.
Ok, this might be a dumb question, but have you tried "sudo virsh -c qemu:///system list" (with the "sudo") when the libvirtd program is running?
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
-- Zdenek Styblik Net/Linux admin OS TurnovFree.net email: stybla@turnovfree.net jabber: stybla@jabber.turnovfree.net
On 01/20/2011 12:32 PM, Zdenek Styblik wrote:
On 01/20/2011 12:20 PM, Marcela Castro León wrote:
Hello I think now is running. I've started doing
*chubut@chubut:/usr/local/sbin$ sudo ./libvirtd & * and checked doing
*chubut@chubut:~$ ps -ef | grep libvirtd chubut 1877 1700 0 12:16 pts/0 00:00:00 grep --color=auto libvirtd chubut@chubut:~$ ps -ef | grep libvirtd root 1945 1721 0 12:17 pts/1 00:00:00 ./libvirtd chubut 1993 1700 0 12:17 pts/0 00:00:00 grep --color=auto libvirtd chubut@chubut:~$ sudo virsh -c qemu:///system list Id Name State ----------------------------------
chubut@chubut:~$ *
Do you think it's right? Thank you very much.
Marcela
Please try as a root or via sudo: # netstat -nlp | grep libvirt;
you should see something like: --- SNIP --- root@anubis:~# netstat -nlp | grep libvirt unix 2 [ ACC ] STREAM LISTENING 5787 3271/libvirtd /var/run/libvirt/libvirt-sock --- SNIP ---
Z.
Oh goddie, I've replied to something old. Yes Marcela, that's just great. libvirt is up and running and "a okay" :) You should be able to create virtual machines and such now. I'm sorry for confusion. Zdenek -- Zdenek Styblik Net/Linux admin OS TurnovFree.net email: stybla@turnovfree.net jabber: stybla@jabber.turnovfree.net
On 20/01/2011, at 10:20 PM, Marcela Castro León wrote: Hello
I think now is running. I've started doing
chubut@chubut:/usr/local/sbin$ sudo ./libvirtd &
and checked doing
chubut@chubut:~$ ps -ef | grep libvirtd chubut 1877 1700 0 12:16 pts/0 00:00:00 grep --color=auto libvirtd chubut@chubut:~$ ps -ef | grep libvirtd root 1945 1721 0 12:17 pts/1 00:00:00 ./libvirtd chubut 1993 1700 0 12:17 pts/0 00:00:00 grep --color=auto libvirtd chubut@chubut:~$ sudo virsh -c qemu:///system list Id Name State ----------------------------------
chubut@chubut:~$
Do you think it's right? Thank you very much.
Hi Marcela, That does show it's running, and that virsh can connect to it. The "sudo" part for virsh was the important bit there, because you probably don't have user access set up, so only root could access the socket used for communication. On a different track completely, have you looked for libvirt 0.8.7 packages for Ubuntu 9.10? I'm thinking that if they exist, or if the version for latest Ubuntu could be recompiled, then that might be the better approach? That would probably have all the scripts in the right spots, have user access in a "known state" and so forth. ? Regards and best wishes, Justin Clift
could you check if --with-macvtap and --with-virtualport are enabled for you? And what's your kernel version, I guess your kernel doesn't support macvtap yet. Regards Osier 于 2011年01月20日 16:23, Marcela Castro León 写道:
Hello When installing libvirt 0.8.6, I've passed ./configure, but when I execute make, I've got
CCLD libvirtd ../src/.libs/libvirt_driver_qemu.a(libvirt_driver_qemu_la-qemu_driver.o): In function `qemudVPAssociatePortProfiles': /home/chubut/libvirt-0.8.6/src/qemu/qemu_driver.c:11881: undefined reference to `vpAssociatePortProfileId' /home/chubut/libvirt-0.8.6/src/qemu/qemu_driver.c:11898: undefined reference to `vpDisassociatePortProfileId' collect2: ld returned 1 exit status make[3]: *** [libvirtd] Error 1 make[3]: Leaving directory `/home/chubut/libvirt-0.8.6/daemon' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/chubut/libvirt-0.8.6/daemon' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/chubut/libvirt-0.8.6' make: *** [all] Error 2 chubut@chubut:~/libvirt-0.8.6$
Do you have any help? Thank you. Marcela
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
participants (5)
-
Justin Clift -
Marcela Castro León -
Matthias Bolte -
Osier Yang -
Zdenek Styblik