Re: [libvirt] [Libvirt-announce] 0.9.0 freeze week, RC2 version to test
On 04/04/2011, at 8:51 PM, Justin Clift wrote: On 02/04/2011, at 6:34 PM, Matthias Bolte wrote: snip Thanks. It's looking like some kind of problem interacting with VirtualBox (v4.0.4): This is the full gdb backtrace from the process: (gdb) thread apply all bt Thread 1 (process 85784): #0 0x7fff8549b3a6 in swtch_pri () #1 0x7fff854d5b51 in _pthread_find_thread () snip Strange point to get stuck. I assume VirtualBox for OSX comes with it's own GUI tool. Is it also affected or only virsh? Does this happen with VirtualBox 4.0.4 only, or is 4.x or even 3.x affected too? Just tried with the earlier versions of 4.0.2 and 3.2.12, with full libvirt autogen.sh and recompile after each installation. Exact same behaviour, hang point, everything. :( The VirtualBox GUI seems completely unaffected. While virsh is stuck, the GUI can be started, VM's started/stopped, GUI shut down, all as per normal. I guess this is going to take a bunch more debugging, which I personally don't have the time for atm. (ugh) :( Are there any other OSX users around that could take a look? As additional info, connecting to a remote RHEL 6.0 libvirtd using ssh works: $ tools/virsh -c qemu+ssh://root@servername/system?socket=/var/run/libvirt/libvirt-sock root@servername's password: Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # ^D $ Which is nice, as from memory it didn't used to (for ssh specifically). + Justin -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [Libvirt-announce] 0.9.0 freeze week, RC2 version to test
On 02/04/2011, at 6:34 PM, Matthias Bolte wrote: snip Thanks. It's looking like some kind of problem interacting with VirtualBox (v4.0.4): This is the full gdb backtrace from the process: (gdb) thread apply all bt Thread 1 (process 85784): #0 0x7fff8549b3a6 in swtch_pri () #1 0x7fff854d5b51 in _pthread_find_thread () snip Strange point to get stuck. I assume VirtualBox for OSX comes with it's own GUI tool. Is it also affected or only virsh? Does this happen with VirtualBox 4.0.4 only, or is 4.x or even 3.x affected too? Just tried with the earlier versions of 4.0.2 and 3.2.12, with full libvirt autogen.sh and recompile after each installation. Exact same behaviour, hang point, everything. :( The VirtualBox GUI seems completely unaffected. While virsh is stuck, the GUI can be started, VM's started/stopped, GUI shut down, all as per normal. I guess this is going to take a bunch more debugging, which I personally don't have the time for atm. (ugh) :( Are there any other OSX users around that could take a look? Regards and best wishes, Justin Clift -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [Libvirt-announce] 0.9.0 freeze week, RC2 version to test
2011/3/31 Justin Clift jcl...@redhat.com: On 01/04/2011, at 12:44 AM, Daniel P. Berrange wrote: On Wed, Mar 30, 2011 at 02:16:28AM +1100, Justin Clift wrote: snip Same problem with virsh on OSX. Straight out hangs and never gets to the prompt. Please run virsh with LIBVIRT_DEBUG=1 set and capture the logs. Also when it hangs please capture a full stack trace showing where it has got stuck Thanks. It's looking like some kind of problem interacting with VirtualBox (v4.0.4): This is the full gdb backtrace from the process: (gdb) thread apply all bt Thread 1 (process 85784): #0 0x7fff8549b3a6 in swtch_pri () #1 0x7fff854d5b51 in _pthread_find_thread () #2 0x7fff8551cb3e in pthread_getschedparam () #3 0x0001013c8752 in PR_SetThreadPriority () #4 0x0001013c88f1 in _PR_InitThreads () #5 0x0001013bbc26 in _PR_ImplicitInitialization () #6 0x0001013c8916 in PR_GetCurrentThread () #7 0x0001013a048f in nsIThread::GetCurrent () #8 0x0001013a04c1 in nsIThread::SetMainThread () #9 0x0001013524ee in NS_InitXPCOM2 () #10 0x0001004c022a in com::Initialize () #11 0x0001004bef8f in VBoxComInitialize () #12 0x00010015fa7f in vboxInitialize () #13 0x000100160039 in vboxOpen () #14 0x0001000abbcb in do_open () #15 0x0001000ac712 in virConnectOpenAuth () #16 0x00010001a7ef in vshInit () #17 0x00010001bef1 in main () (gdb) Any of that helpful? Strange point to get stuck. I assume VirtualBox for OSX comes with it's own GUI tool. Is it also affected or only virsh? Does this happen with VirtualBox 4.0.4 only, or is 4.x or even 3.x affected too? Matthias -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [Libvirt-announce] 0.9.0 freeze week, RC2 version to test
On Wed, Mar 30, 2011 at 02:16:28AM +1100, Justin Clift wrote: On 30/03/2011, at 1:46 AM, Daniel Veillard wrote: On Mon, Mar 28, 2011 at 02:25:38PM +0800, Daniel Veillard wrote: [...] I will regenerate a rc2 as soon as Eric pending patch queue and outgoing fd patches are in as I think they should really make 0.9.0 There may be more infrastrcucture patches from Dan too, I'm unsure and as usual pushing bug fixes are okay too, Okay, patches from Eric, Dan, Markus and Osier are in, so it was time for RC2 , and I guess we are really starting the freeze now :-) ftp://libvirt.org/libvirt/libvirt-0.9.0-rc2.tar.gz Please give it some testing, Same problem with virsh on OSX. Straight out hangs and never gets to the prompt. Please run virsh with LIBVIRT_DEBUG=1 set and capture the logs. Also when it hangs please capture a full stack trace showing where it has got stuck Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [Libvirt-announce] 0.9.0 freeze week, RC2 version to test
On 01/04/2011, at 12:44 AM, Daniel P. Berrange wrote: On Wed, Mar 30, 2011 at 02:16:28AM +1100, Justin Clift wrote: snip Same problem with virsh on OSX. Straight out hangs and never gets to the prompt. Please run virsh with LIBVIRT_DEBUG=1 set and capture the logs. Also when it hangs please capture a full stack trace showing where it has got stuck Thanks. It's looking like some kind of problem interacting with VirtualBox (v4.0.4): snip 01:26:36.870: -1: debug : virConnectOpenAuth:1288 : name=(null), auth=0x100237e20, flags=0 01:26:36.870: -1: debug : do_open:1025 : no name, allowing driver auto-select 01:26:36.870: -1: debug : do_open:1062 : trying driver 0 (Test) ... 01:26:36.870: -1: debug : do_open:1068 : driver 0 Test returned DECLINED 01:26:36.870: -1: debug : do_open:1062 : trying driver 1 (OPENVZ) ... 01:26:36.870: -1: debug : do_open:1068 : driver 1 OPENVZ returned DECLINED 01:26:36.870: -1: debug : do_open:1062 : trying driver 2 (VMWARE) ... 01:26:36.870: -1: debug : do_open:1068 : driver 2 VMWARE returned DECLINED 01:26:36.870: -1: debug : do_open:1062 : trying driver 3 (VBOX) ... this is where the hang is, and I hit ^C to break out of virsh (full log file attached) virsh_debug.log Description: Binary data This is the full gdb backtrace from the process: (gdb) thread apply all bt Thread 1 (process 85784): #0 0x7fff8549b3a6 in swtch_pri () #1 0x7fff854d5b51 in _pthread_find_thread () #2 0x7fff8551cb3e in pthread_getschedparam () #3 0x0001013c8752 in PR_SetThreadPriority () #4 0x0001013c88f1 in _PR_InitThreads () #5 0x0001013bbc26 in _PR_ImplicitInitialization () #6 0x0001013c8916 in PR_GetCurrentThread () #7 0x0001013a048f in nsIThread::GetCurrent () #8 0x0001013a04c1 in nsIThread::SetMainThread () #9 0x0001013524ee in NS_InitXPCOM2 () #10 0x0001004c022a in com::Initialize () #11 0x0001004bef8f in VBoxComInitialize () #12 0x00010015fa7f in vboxInitialize () #13 0x000100160039 in vboxOpen () #14 0x0001000abbcb in do_open () #15 0x0001000ac712 in virConnectOpenAuth () #16 0x00010001a7ef in vshInit () #17 0x00010001bef1 in main () (gdb) Any of that helpful? Regards and best wishes, Justin Clift-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [Libvirt-announce] 0.9.0 freeze week, RC2 version to test
On 30/03/2011, at 2:16 AM, Justin Clift wrote: On 30/03/2011, at 1:46 AM, Daniel Veillard wrote: On Mon, Mar 28, 2011 at 02:25:38PM +0800, Daniel Veillard wrote: [...] I will regenerate a rc2 as soon as Eric pending patch queue and outgoing fd patches are in as I think they should really make 0.9.0 There may be more infrastrcucture patches from Dan too, I'm unsure and as usual pushing bug fixes are okay too, Okay, patches from Eric, Dan, Markus and Osier are in, so it was time for RC2 , and I guess we are really starting the freeze now :-) ftp://libvirt.org/libvirt/libvirt-0.9.0-rc2.tar.gz Please give it some testing, Same problem with virsh on OSX. Straight out hangs and never gets to the prompt. The commit that seems to be causing the problem on OSX is this one: commit 2ed6cc7bec41dd344d41ea1531f6760c93099128 Author: Daniel P. Berrange berra...@redhat.com Date: Wed Mar 2 16:59:54 2011 + Expose event loop implementation as a public API Not all applications have an existing event loop they need to integrate with. Forcing them to implement the libvirt event loop integration APIs is an undue burden. This just exposes our simple poll() based implementation for apps to use. So instead of calling virEventRegister(callbacks...) The app would call virEventRegisterDefaultImpl() And then have a thread somewhere calling static bool quit = false; while (!quit) virEventRunDefaultImpl() * daemon/libvirtd.c, tools/console.c, tools/virsh.c: Convert to public event loop APIs * include/libvirt/libvirt.h.in, src/libvirt_private.syms: Add virEventRegisterDefaultImpl and virEventRunDefaultImpl * src/util/event.c: Implement virEventRegisterDefaultImpl and virEventRunDefaultImpl using poll() event loop * src/util/event_poll.c: Add full error reporting * src/util/virterror.c, include/libvirt/virterror.h: Add VIR_FROM_EVENTS Moving to the commit right before it, and virsh works starts up fine. With the above commit though, virsh just hangs on OSX. The options compiled in for the above testing were: Compiled with support for: Hypervisors: OpenVZ VirtualBox ESX Test Networking: Remote Storage: Miscellaneous: Debug Readline Anyone have ideas for a workaround or other useful things to test? Regards and best wishes, Justin Clift -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [Libvirt-announce] 0.9.0 freeze week, RC2 version to test
On 30/03/2011, at 1:46 AM, Daniel Veillard wrote: On Mon, Mar 28, 2011 at 02:25:38PM +0800, Daniel Veillard wrote: [...] I will regenerate a rc2 as soon as Eric pending patch queue and outgoing fd patches are in as I think they should really make 0.9.0 There may be more infrastrcucture patches from Dan too, I'm unsure and as usual pushing bug fixes are okay too, Okay, patches from Eric, Dan, Markus and Osier are in, so it was time for RC2 , and I guess we are really starting the freeze now :-) ftp://libvirt.org/libvirt/libvirt-0.9.0-rc2.tar.gz Please give it some testing, Same problem with virsh on OSX. Straight out hangs and never gets to the prompt. I'll try to figure out which commit(s) causes that, tomorrow. Regards and best wishes, Justin Clift -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
