[Bug 195480] Re: libvirt: virsh -c qemu+ssh://host.example.com/session connects to 'system', not session
No, I was misreading the results. 0 ✓ serge@sl ~ $ virsh -c qemu:///system list --all IdName State - fedora20 shut off - p9-p shut off - ubuntuprecise shut off - wily1 shut off - wily1-cgmu shut off - wily1-cloneshut off - wily1-lxc1 shut off - wily1-lxd1 shut off - win2k8 shut off 0 ✓ serge@sl ~ $ !!:s/system/session/ virsh -c qemu:///session list --all IdName State This appears to be fixed. ** Changed in: libvirt (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/195480 Title: libvirt: virsh -c qemu+ssh://host.example.com/session connects to 'system', not session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/195480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195480] Re: libvirt: virsh -c qemu+ssh://host.example.com/session connects to 'system', not session
Interestingly, virsh -c qemu+ssh://localhost/system list versus virsh -c qemu+ssh://localhost/session list works correctly. But using just 'qemu:///session list' does inded show system entries. ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/195480 Title: libvirt: virsh -c qemu+ssh://host.example.com/session connects to 'system', not session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/195480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195480] Re: libvirt: virsh -c qemu+ssh://host.example.com/session connects to 'system', not session
What do you mean by 'a root model libvirtd'? If you change it to 'virsh -c qemu://127.0.0.1/system -list --all', does it become 'nc -q 0 -U /var/run/libvirt/libvirt-sock-ro' ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/195480 Title: libvirt: virsh -c qemu+ssh://host.example.com/session connects to 'system', not session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/195480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195480] Re: libvirt: virsh -c qemu+ssh://host.example.com/session connects to 'system', not session
I run virsh -c qemu:///session list --all and virsh -c qemu:///system list --all when run virsh -c qemu:///session list , it run a temp libvirtd --timeout 30 by non-root model virsh -c qemu:///system list --all ,it access root model libvirtd when run virsh -c qemu://127.0.0.1/session list --all it run a ssh like this: ssh 127.0.0.1 sh -c 'nc -q 2>&1 | grep -q "requires an argument";if [ $? -eq 0 ] ; then CMD="nc -q 0 -U /var/run/libvirt/libvirt-sock";else CMD="nc -U /var/run/libvirt/libvirt-sock";fi;eval "$CMD";' so ,does it use a root model libvirtd ?? is here a mistake ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/195480 Title: libvirt: virsh -c qemu+ssh://host.example.com/session connects to 'system', not session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/195480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195480] Re: libvirt: virsh -c qemu+ssh://host.example.com/session connects to 'system', not session
Confirmed in Lucid. -- libvirt: virsh -c qemu+ssh://host.example.com/session connects to 'system', not session https://bugs.launchpad.net/bugs/195480 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
