[Bug 528384] Re: virtinst fails to create effective config to boot new vm
Mr. Marc Deslauriers 2010-02-26 is over a year. I once installed a pre-release lucid when it was the up coming. Mr Hansen responded to me as you can see. That put a sharp end to exploring xen in ubuntu. I went on and explored it in squeeze and gentoo and resolved the issue with a redhat developer by submitting it there too. My current fight with xen is with xen itself not installing the latest in gentoo, my preferred distro, rather than with virtinst. libvirt was temperamental at best with xen but seems to offer preferential treatment to qemu kvm. A reply following Mr. Sorensen's reply at all is unexpected, a reply a year later more so. Last I tried virt-manager virtinst they had a full virt install blanked out in virt-manager's listbox options of two for doing an install. This supports Sorenson's claim to not only not support ubuntu as a dom0 but to downright sabotage it. xen is or has been dumped by redhat and centos and lacks interest support but I think for Suse. I know gentoo developer's are underwhelmed. Reproducing this as you know is unlikely and also invalid since the packages are a full year apart. Version updates generally fix prior bugs and I'm sure this has occurred. Just archive or delete this and my other submission at your pleasure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/528384 Title: virtinst fails to create effective config to boot new vm -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
boun...@canonical, according to soren from my other bug, Ubuntu has no support for running as a Xen dom0. This is no secret. When you insist on doing so anyway, don't expect us to be all over it trying to work out your bugs. .. So I proceed with uncertainty. I've not applied strace before. However, I have done as requested. Oh my, it is large. The first, trace1.txt is run and aborts due to the presence of the pid file, /var/run/libvirtd.pid. So I remove it, and re-run. I stopped at recording over 4,000 lines, trace2.txt It's obviously repetitive. Anyway, ** Attachment added: trace2.txt http://launchpadlibrarian.net/4004/trace2.txt -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
yes, ok, well thanks for that. Good comment. I'll take note and add it. -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
** Tags removed: verification-needed -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
Soren, or bounces, well, despite your position that you didn't have to, you did it. You were indeed right. I'm quite happy for that too. I did do so anyway (dom0 in xen). That makes this not a bug and resolved and the deficit in my setup, perhaps an invalid status. I could not have figured it. ide...@karmic:~$ uname -a Linux karmic 2.6.31-xen-r10 #6 SMP Wed Mar 3 21:31:58 WST 2010 i686 GNU/Linux ide...@karmic:~$ ls /var/run/libvirt libvirt-sock libvirt-sock-ro network qemu and my kernel more refined. That gives karmic a real lift. Thanks -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527864] Re: virtinst fails to offer full virt install from within virt-manager
** Changed in: virtinst (Ubuntu) Assignee: (unassigned) = Xen Team (xen) -- virtinst fails to offer full virt install from within virt-manager https://bugs.launchpad.net/bugs/527864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
** Tags added: verification-needed -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 528384] Re: virtinst fails to create effective config to boot new vm
Going by the other bugs listed prior to adding this one and number 527864, I shouldn't expect any reply ever. Is this a reflection of the status of xen and virtualisation in ubuntu? -- virtinst fails to create effective config to boot new vm https://bugs.launchpad.net/bugs/528384 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 528384] Re: virtinst fails to create effective config to boot new vm
yep, ok. kvm it is. Enough from me. You're the developers, so trying xen was not a good idea. I get that. Enough. -- virtinst fails to create effective config to boot new vm https://bugs.launchpad.net/bugs/528384 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
boun...@canonical, according to soren from my other bug, Ubuntu has no support for running as a Xen dom0. This is no secret. When you insist on doing so anyway, don't expect us to be all over it trying to work out your bugs. .. So I proceed with uncertainty. I've not applied strace before. However, I have done as requested. Oh my, it is large. The first, trace1.txt is run and aborts due to the presence of the pid file, /var/run/libvirtd.pid. So I remove it, and re-run. I stopped at recording over 4,000 lines, trace2.txt It's obviously repetitive. Anyway, ** Attachment added: trace2.txt http://launchpadlibrarian.net/4004/trace2.txt -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
yes, ok, well thanks for that. Good comment. I'll take note and add it. -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
** Tags removed: verification-needed -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
Soren, or bounces, well, despite your position that you didn't have to, you did it. You were indeed right. I'm quite happy for that too. I did do so anyway (dom0 in xen). That makes this not a bug and resolved and the deficit in my setup, perhaps an invalid status. I could not have figured it. ide...@karmic:~$ uname -a Linux karmic 2.6.31-xen-r10 #6 SMP Wed Mar 3 21:31:58 WST 2010 i686 GNU/Linux ide...@karmic:~$ ls /var/run/libvirt libvirt-sock libvirt-sock-ro network qemu and my kernel more refined. That gives karmic a real lift. Thanks -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
ok, you're going to hate me for this, I know it. As if I've not input enough. I did do a separate install of karmic, and I reproduced this state. I installed a 64 version. I installed, prepared the kernel for karmic. Unless I missed it, Ubuntu didn't provide a xen kernel for karmic. I provided my own, and it's run lenny 64, karmic 32, now karmic 64, gentoo 32 and gentoo 64. It may not be perfect. Anyway, having booted into xen. ide...@karmic64:~$ sudo libvirtd [sudo] password for idella: 22:58:12.769: error : qemudWritePidFile:457 : Failed to open pid file '/var/run/libvirtd.pid' : File exists ide...@karmic64:~$ ls /var/run/libvirt qemu ide...@karmic64:~$ sudo rm /var/run/libvirtd.pid ide...@karmic64:~$ sudo libvirtd libvir: Network Config error : cannot enable /proc/sys/net/ipv6/conf/virbr0/disable_ipv6: No such file or directory 23:00:47.610: warning : qemudStartup:521 : Unable to create cgroup for driver: No such device or address Segmentation fault ide...@karmic64:~$ ls /var/run/libvirt qemu ide...@karmic64:~$ uname -a Linux karmic64 2.6.31-xen-r10-AMD-64 #19 SMP Sun Feb 28 21:28:33 WST 2010 x86_64 GNU/Linux More of the same. Installed virt-manager, try connecting to xen by gui, Unable to open connection to hypervisor URI 'xen:///': class 'libvirt.libvirtError' unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory I booted into the freshly installed server kernel, and ide...@karmic64:~$ sudo libvirtd [sudo] password for idella: Sorry, try again. [sudo] password for idella: 22:39:18.849: error : qemudWritePidFile:457 : Failed to open pid file '/var/run/libvirtd.pid' : File exists ide...@karmic64:~$ sudo rm /var/run/libvirtd.pid ide...@karmic64:~$ sudo libvirtd 22:39:39.118: warning : qemudStartup:521 : Unable to create cgroup for driver: No such device or address 22:39:39.204: warning : lxcStartup:1460 : Unable to create cgroup for driver: No such device or address WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect ^X^Z [1]+ Stopped sudo libvirtd ide...@karmic64:~$ sudo libvirtd 22:40:21.411: error : qemudWritePidFile:457 : Failed to open pid file '/var/run/libvirtd.pid' : File exists ide...@karmic64:~$ ls /var/run/libvirt libvirt-sock libvirt-sock-ro network qemu ide...@karmic64:~$ uname -a Linux karmic64 2.6.31-19-server #56-Ubuntu SMP Thu Jan 28 03:40:48 UTC 2010 x86_64 GNU/Linux Those elusive sockets libvirt-sock libvirt-sock-ro are there, in an environment absent of xen. Yes well, I fear this may lead nowhere if you can't reproduce. What kernel would you use?? -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
libvirt is running in dom0. ide...@karmic64:~$ uname -a Linux karmic64 2.6.31-xen-r10-AMD-64 #19 SMP Sun Feb 28 21:28:33 WST 2010 x86_64 GNU/Linux Host. libvirt is intended for a host environment. Wouldn't be inclined to install it into a guest. It's all very well me confirming myself. Can someone confirm??? -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
ok, you're going to hate me for this, I know it. As if I've not input enough. I did do a separate install of karmic, and I reproduced this state. I installed a 64 version. I installed, prepared the kernel for karmic. Unless I missed it, Ubuntu didn't provide a xen kernel for karmic. I provided my own, and it's run lenny 64, karmic 32, now karmic 64, gentoo 32 and gentoo 64. It may not be perfect. Anyway, having booted into xen. ide...@karmic64:~$ sudo libvirtd [sudo] password for idella: 22:58:12.769: error : qemudWritePidFile:457 : Failed to open pid file '/var/run/libvirtd.pid' : File exists ide...@karmic64:~$ ls /var/run/libvirt qemu ide...@karmic64:~$ sudo rm /var/run/libvirtd.pid ide...@karmic64:~$ sudo libvirtd libvir: Network Config error : cannot enable /proc/sys/net/ipv6/conf/virbr0/disable_ipv6: No such file or directory 23:00:47.610: warning : qemudStartup:521 : Unable to create cgroup for driver: No such device or address Segmentation fault ide...@karmic64:~$ ls /var/run/libvirt qemu ide...@karmic64:~$ uname -a Linux karmic64 2.6.31-xen-r10-AMD-64 #19 SMP Sun Feb 28 21:28:33 WST 2010 x86_64 GNU/Linux More of the same. Installed virt-manager, try connecting to xen by gui, Unable to open connection to hypervisor URI 'xen:///': class 'libvirt.libvirtError' unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory I booted into the freshly installed server kernel, and ide...@karmic64:~$ sudo libvirtd [sudo] password for idella: Sorry, try again. [sudo] password for idella: 22:39:18.849: error : qemudWritePidFile:457 : Failed to open pid file '/var/run/libvirtd.pid' : File exists ide...@karmic64:~$ sudo rm /var/run/libvirtd.pid ide...@karmic64:~$ sudo libvirtd 22:39:39.118: warning : qemudStartup:521 : Unable to create cgroup for driver: No such device or address 22:39:39.204: warning : lxcStartup:1460 : Unable to create cgroup for driver: No such device or address WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect ^X^Z [1]+ Stopped sudo libvirtd ide...@karmic64:~$ sudo libvirtd 22:40:21.411: error : qemudWritePidFile:457 : Failed to open pid file '/var/run/libvirtd.pid' : File exists ide...@karmic64:~$ ls /var/run/libvirt libvirt-sock libvirt-sock-ro network qemu ide...@karmic64:~$ uname -a Linux karmic64 2.6.31-19-server #56-Ubuntu SMP Thu Jan 28 03:40:48 UTC 2010 x86_64 GNU/Linux Those elusive sockets libvirt-sock libvirt-sock-ro are there, in an environment absent of xen. Yes well, I fear this may lead nowhere if you can't reproduce. What kernel would you use?? -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
libvirt is running in dom0. ide...@karmic64:~$ uname -a Linux karmic64 2.6.31-xen-r10-AMD-64 #19 SMP Sun Feb 28 21:28:33 WST 2010 x86_64 GNU/Linux Host. libvirt is intended for a host environment. Wouldn't be inclined to install it into a guest. It's all very well me confirming myself. Can someone confirm??? -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
I decided to up the level of input. Please persevere. ide...@karmic:~$ sudo rm /var/run/libvirtd.pid ide...@karmic:~$ sudo gdb libvirtd GNU gdb (GDB) 7.0-ubuntu Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done. (gdb) run Starting program: /usr/sbin/libvirtd [Thread debugging using libthread_db enabled] 20:11:17.815: warning : qemudStartup:521 : Unable to create cgroup for driver: No such device or address Program received signal SIGSEGV, Segmentation fault. virDomainEventCallbackListFree (list=0x0) at domain_event.c:41 41 domain_event.c: No such file or directory. in domain_event.c (gdb) bt #0 virDomainEventCallbackListFree (list=0x0) at domain_event.c:41 #1 0x0808bece in ?? () #2 0x0808f992 in ?? () #3 0xb7e8a915 in virStateInitialize (privileged=1) at libvirt.c:786 #4 0x0805b5eb in ?? () #5 0xb7a1bb56 in __libc_start_main () from /lib/tls/i686/nosegneg/libc.so.6 #6 0x08053d11 in ?? () comment: I suspect this relates to attempting to qemu /kvm, which it can't connect to in this xen environ. ide...@karmic:~$ gdb virsh GNU gdb (GDB) 7.0-ubuntu Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/virsh...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/virsh [Thread debugging using libthread_db enabled] Connecting to uri: qemu:///session (Here it hangs, I interrupt) ^Z Program received signal SIGTSTP, Stopped (user). 0xb7fe2416 in __kernel_vsyscall () (gdb) run -c qemu:///system The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/bin/virsh -c qemu:///system [Thread debugging using libthread_db enabled] Connecting to uri: qemu:///system error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor Program exited with code 01. (gdb) run -c xen Starting program: /usr/bin/virsh -c xen [Thread debugging using libthread_db enabled] Connecting to uri: xen error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor Program exited with code 01. however ide...@karmic:~$ sudo gdb virsh GNU gdb (GDB) 7.0-ubuntu Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/virsh...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/virsh [Thread debugging using libthread_db enabled] Connecting to uri: qemu:///session error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor Program exited with code 01. (gdb) run -c xen Starting program: /usr/bin/virsh -c xen [Thread debugging using libthread_db enabled] Connecting to uri: xen [New Thread 0xb78d5b70 (LWP 14327)] Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # It goes in. virt-manager responds similarly. Does connect using sudo, or gksu, which does make sense. I think I'm going to install a whole separate 64 version and duplicate this setup and see what it yields. It's just paralised the way it is. -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 510658] Re: error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid' : File exists
Would like to add, realise I'm a regular user, not technical advocate like Arnd and Dustin Kirkland. On my system, ide...@karmic:~$ sudo /etc/init.d/libvirt-bin restart * Restarting libvirt management daemon /usr/sbin/libvirtd [fail] ide...@karmic:~$ sudo libvirtd 15:42:25.008: error : qemudWritePidFile:457 : Failed to open pid file '/var/run/libvirtd.pid' : File exists de...@karmic:~$ ls /var/run/ lktapctrl.pid libvirtd.pidudev-configure-printer ... ide...@karmic:~$ sudo rm /var/run/libvirtd.pid ide...@karmic:~$ sudo /etc/init.d/libvirt-bin restart * Restarting libvirt management daemon /usr/sbin/libvirtd[ OK ] On previous searching, I found this in place in another distro, ?? arch linux. So not new for ubuntu. -- error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid' : File exists https://bugs.launchpad.net/bugs/510658 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
Chuck Short, I hope to hear from you again, I can see you are a key participant in dealing with these bugs. It's Saturday now so I suppose I can't expect you to reply before Monday, and you are busy I'm sure. From what I've gleaned, you're not going to reproduce. The sockets are so fundamental that they surely would have been reported as a bug by someone else by now. So I suppose it follows that is is low priority at your end. But something has gone awry. I would hope for you to grant it some input so as to finally achieve a sane setup on my karmic. I've pursued libvirt quite a bit, on lenny for extended periods, and gentoo. http://bugs.gentoo.org/show_bug.cgi?id=305401 This flaw leaves my completely puzzled, short of being fluent in python programming, there is nowhere to go with it. From what I've read, creating the sockets and assigning permissions is one of the first things executed by libvirtd. How can this sytem do anything without them? i.e. Why does virsh connect to xen in their absence? The only link to xen I can trace that might bear some influence I've already mentioned. In xend-config.sxp, one of the fundamental choices to select is the type of server. The choice of (xend-http-server yes) (xend-port 8000) finally allowed connectivity. The promoted selection is (xend-unix-server yes), which I have just tried. It is absent as a selection in the xend-config.sxp, so I had to manually add it. It also works, but leaves me wondering, why is this selection absent? what is a recommended standard setup for karmic with its standard packages? It's too intricate for me. ** Bug watch added: Gentoo Bugzilla #305401 http://bugs.gentoo.org/show_bug.cgi?id=305401 -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
I decided to up the level of input. Please persevere. ide...@karmic:~$ sudo rm /var/run/libvirtd.pid ide...@karmic:~$ sudo gdb libvirtd GNU gdb (GDB) 7.0-ubuntu Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done. (gdb) run Starting program: /usr/sbin/libvirtd [Thread debugging using libthread_db enabled] 20:11:17.815: warning : qemudStartup:521 : Unable to create cgroup for driver: No such device or address Program received signal SIGSEGV, Segmentation fault. virDomainEventCallbackListFree (list=0x0) at domain_event.c:41 41 domain_event.c: No such file or directory. in domain_event.c (gdb) bt #0 virDomainEventCallbackListFree (list=0x0) at domain_event.c:41 #1 0x0808bece in ?? () #2 0x0808f992 in ?? () #3 0xb7e8a915 in virStateInitialize (privileged=1) at libvirt.c:786 #4 0x0805b5eb in ?? () #5 0xb7a1bb56 in __libc_start_main () from /lib/tls/i686/nosegneg/libc.so.6 #6 0x08053d11 in ?? () comment: I suspect this relates to attempting to qemu /kvm, which it can't connect to in this xen environ. ide...@karmic:~$ gdb virsh GNU gdb (GDB) 7.0-ubuntu Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/virsh...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/virsh [Thread debugging using libthread_db enabled] Connecting to uri: qemu:///session (Here it hangs, I interrupt) ^Z Program received signal SIGTSTP, Stopped (user). 0xb7fe2416 in __kernel_vsyscall () (gdb) run -c qemu:///system The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/bin/virsh -c qemu:///system [Thread debugging using libthread_db enabled] Connecting to uri: qemu:///system error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor Program exited with code 01. (gdb) run -c xen Starting program: /usr/bin/virsh -c xen [Thread debugging using libthread_db enabled] Connecting to uri: xen error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor Program exited with code 01. however ide...@karmic:~$ sudo gdb virsh GNU gdb (GDB) 7.0-ubuntu Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/virsh...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/virsh [Thread debugging using libthread_db enabled] Connecting to uri: qemu:///session error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory error: failed to connect to the hypervisor Program exited with code 01. (gdb) run -c xen Starting program: /usr/bin/virsh -c xen [Thread debugging using libthread_db enabled] Connecting to uri: xen [New Thread 0xb78d5b70 (LWP 14327)] Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # It goes in. virt-manager responds similarly. Does connect using sudo, or gksu, which does make sense. I think I'm going to install a whole separate 64 version and duplicate this setup and see what it yields. It's just paralised the way it is. -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 528384] [NEW] virtinst fails to create effective config to boot new vm
Public bug reported: Binary package hint: python-virtinst I am trying and testing xen and virt related packages in karmic ubuntu. Just installed a vm of squeeze via virtinst from the command line in a xen environment as a xen guest. The process had two separate short comings. 1. Once the new domain was created, virt-manager listed it, but was unable to offer a vnc console that connects. This is a separate problem addressed in the other entry I made, bug 527864, which is a general description. 2. Once made, the vm is now not able to be accessed due to the following -- the 'console' made by virt-manager is deficient in its profile of the new squeeze. Compared with an equivalent made by qemu or kvm, it offers NOTHING in the boot options of the profile. (i.e. a vm made with qemu or kvm includes options) -- the console option itself of the vm while being installed failed, listing parallel console on a black screen. -- once installed, the vm predictably failed to boot. By using virt-manager to open and then run the new vm, it reported error, boot loader is not executable. (If it had booted, it would still have failed to present a connected vnc console) On doing an xml dump of the new vm within virsh, it listed the boot source as pygrub, but the path to pygrub was just wrong. A path close to /var/lib/xen-default/boot. Anyway, I used file search and found pygrub in /usr/bin, not even close to the stipulated path. I made a sym link so it could be found. -- next, to seal complete failure, on starting the new vm, it then reports xend_post: error from xen daemon: (xend.err Boot loader didn't return any data!) So it's invoked pygrub but doesn't execute a boot. I figure this makes it another combined slip up between both libvirt0 and python-virtinst, since it would be libvirt0 creating an xml internal file of the vm with invalid data. It can start bootup by using kvm to boot it, for which it's not designed, proving the grub install during installation is ok. The result is a vm that can't be used. a debian vm created from within karmic. I may be able to boot it with a guest xen kernel, which would be a work around, not a fix. I don't expect it to work because it lacks the content in /lib/modules to support the guest kernel. It was created with the plan to utilise pygrub and it can't do it. I also can't mount it via -o loop, which probably can be done but I don't know how to adjust the required settings. Need I say I expected the new vm to be accessible via virt-manager with a full complement of valid settings which effectively booted the new vm. Overall, karmic is very xen incapable due to this type of error. It's far more capable under a regular kernel running kvm. I hoped for better in a current ubuntu. ide...@karmic:~$ lsb_release -rd Description:Ubuntu 9.10 Release:9.10 ** Affects: virtinst (Ubuntu) Importance: Undecided Status: New -- virtinst fails to create effective config to boot new vm https://bugs.launchpad.net/bugs/528384 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 528411] [NEW] debootstrap fails an effective install of squeeze
Public bug reported: Binary package hint: debootstrap Attempted to execute an install of squeeze from within this ubuntu karmic. Created an image file using dd, standard procedure. Mounted it standard via -o loop to a folder /mnt/ftp. Executed a simple debootstrap squeeze path/to/debian. I expected an effective install to the mounted file. Resulted in failed to download binary packages for i386. The entry was variations ofhttp://ftp.us.debian.org/debian/ such as ftp://ftp. . I tried us.debian , de.debian . , and au.debian ., then aborted. About the third step into installation and only about 10 seconds in, reported fails to download binary packages, i386. One reported corrupt packages, continued for a few seconds, then similarly bailed out. All terminated reporting failure to download binary packages, i386 ide...@karmic:~$ lsb_release -rd Description:Ubuntu 9.10 Release:9.10 ide...@karmic:~$ apt-cache policy debootstrap debootstrap: Installed: 1.0.20 Candidate: 1.0.20 ProblemType: Bug Architecture: i386 Date: Fri Feb 26 20:17:54 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: debootstrap 1.0.20 PackageArchitecture: all ProcEnviron: LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: debootstrap Uname: Linux 2.6.31-xen-r10 i686 ** Affects: debootstrap (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- debootstrap fails an effective install of squeeze https://bugs.launchpad.net/bugs/528411 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 528411] Re: debootstrap fails an effective install of squeeze
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/39815956/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/39815957/XsessionErrors.txt -- debootstrap fails an effective install of squeeze https://bugs.launchpad.net/bugs/528411 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
Thanks for answering so quickly. The output should be ide...@karmic:~/Documents$ ls /var/run/libvirt qemu It needs to list the sockets as listed above. libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock-ro': No such file or directory libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock-ro': No such file or and '/var/run/libvirt/libvirt-sock-rw. I can only say I've installed it and unistalled it a number of times, trying to get a workable state. I've determined these are key components to libvirt. In a regular kernel booted environment, they are made. It is sane That's what so ridiculous about this. It's occuring in a xen environment, NOT a regular kernel. How can xend or such interfere? I can't understand why libvirt actually connects to xen at all! There should be set of sockets under ~/.libvirt too, but bo. ide...@karmic:~$ ls .libvirt qemu storage Not there. Their absence is undermining every other thing that libvirt interacts with re virtinst and virt-manager, as I described above. It doesn't surprise me that it doesn't reproduce. I think something has gone haywire on my setup, but they are all standard packages installed in a standard way. I've just relied on re-installing to straighten it out, but no. Maybe can't be reproduced which is unfortunate on my part, since it still needs to be debugged. Key points, occurs in a xen environment, wrecks most everything else. Nothing radical in /etc/libvirt/libvirtd.conf -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/39783236/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/39783237/XsessionErrors.txt -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 527864] [NEW] virtinst fails to offer full virt install from within virt-manager
Public bug reported: Binary package hint: python-virtinst virtinst is the background python based application to perform installs in virt-manager, we all know this. The selection of a new install from virt-manager produces the first wizzard screen. Having finally got into a xen environment, I make this selection. The package actually appears to deliberately RESTRICT the capability of an install to the middle choice, network install. There are three options, the first and third are greyed out when selecting xen. Selecting kvm or qemu or the test://default allows all three options. This can't be right. No sensible reason why xen should be resticted. To use a cdrom or dvd, unable to make the selection. Once restricted only to network install, you are obliged to designate the cdrom or dvd drive as a network device. I've tried every possible combination and it is never achieved. So you can't do an install at all by cdrom or dvd, which is crazy. The only possible option is an internet based install, which leads to the next set of problems. The expected outcome ofcourse is to have all three options available, which allows the choice of a full virt install via cd or dvd. It works spot on in SUSE. You can manage install by using virt-install from a console or shell, but via virt-manager, no. The package is python-virtinst 0.400.3-4ubuntu1, in karmic ubuntu latest release. lsb_release -rd Description:Ubuntu 9.10 Release:9.10 ProblemType: Bug Architecture: i386 Date: Thu Feb 25 23:33:29 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: python-virtinst 0.400.3-4ubuntu1 PackageArchitecture: all ProcEnviron: LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: virtinst Uname: Linux 2.6.31-xen-r10 i686 ** Affects: virtinst (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- virtinst fails to offer full virt install from within virt-manager https://bugs.launchpad.net/bugs/527864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527864] Re: virtinst fails to offer full virt install from within virt-manager
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/39782641/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/39782642/XsessionErrors.txt -- virtinst fails to offer full virt install from within virt-manager https://bugs.launchpad.net/bugs/527864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] [NEW] libvirt0 unable to operate due to missing essential files
Public bug reported: Binary package hint: libvirt0 libvirt is the lynch pin to running virtual environments. In karmic, it curiously fails to create the essential files /var/run/libvirt/unix_sock_ro or something close to that, and /var/run/libvirt/unix_sock_rw. I've run libvirt in other distros and cannot figure what's going on here. By rights nothing should work. In a xen environment, it allows connection to xen and to test://default. It can't connect to qemu or kvm due to their absence. It causes failure in every other way that depends on their existance. namely connecting to vnc consoles. When creating a vm from virt-manager. a difficult task in itself, it can't offer a console from which to perform an installation or to run the vm. Trying to use the standard virt-viewer or vncviewer just come to grief from looking for the files ide...@karmic:~$ sudo virt-viewer -c xen Squeeze libvir: Xen Daemon error : internal error failed to connect to xend libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock-ro': No such file or directory libvir: warning : Failed to find the network: Is the daemon running ? libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock-ro': No such file or directory libvir: warning : Failed to find the interface: Is the daemon running ? libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock-ro': No such file or directory libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock-ro': No such file or directory libvir: warning : Failed to find a node driver: Is the libvirtd daemon running ? The curious thing about libvirt in xen in karmic is the choice in /etc/xen/xend-cofig.sxp. In every other distro it's recommended to use the choice (xend-unix-server yes) In karmic this choice is simply not there, so I'm running on (xend-http-server yes) (xend-port8000) The same error was is in place in lenny. Once creating a vm it fails in both debian distros to properly connect to a vnc console and display the vm. Totally useless. It lets virt-manager down and the lets theuser down who is trying to manage vms. These packages need to be properly integrated to work together. Currently they are disintegrated. Running in a regular kernel, these are created, and only then can you use qemu and kvm. ??? !! There is an influence of xen somehow upon libvirt to change this operating mode. libvirt0-0.7.0-1ubuntu13.1 ide...@karmic:~$ lsb_release -rd Description:Ubuntu 9.10 Release:9.10 ProblemType: Bug Architecture: i386 Date: Fri Feb 26 00:16:19 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: libvirt0 0.7.0-1ubuntu13.1 ProcEnviron: LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: libvirt Uname: Linux 2.6.31-xen-r10 i686 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527875] Re: libvirt0 unable to operate due to missing essential files
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/39783236/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/39783237/XsessionErrors.txt -- libvirt0 unable to operate due to missing essential files https://bugs.launchpad.net/bugs/527875 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
