[virt-tools-list] Virt-manager just sits at Connecting...
Hello Everyone, I didn't see an archive search function... So here we go. When I open virt-manager it opens up, and sits there with "QEMU/KVM - Connecting..." And doesn't advance. When I first installed this machine, VMM was able to open, and I was able to create guests. However, I was unable to view their consoles. After rebooting the host, now VMM seems unable to connect. I've verified that qemu is running. If I do virsh - connect qemu:///system list I do see the list of created guests. And I can even start them from the command line. I'm running centos 7. The console I'm logged into is a non privileged user. I open a terminal and launch VMM as root. I appreciate your help. -Greg T ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
Re: [virt-tools-list] Virt-manager just sits at Connecting...
On 01/14/2016 11:39 AM, Greg Teiber wrote: > Hello Everyone, > > > > I didn’t see an archive search function… So here we go. > There isn't one. But if you google 'virt-tools-list ' it's pretty close > > > When I open virt-manager it opens up, and sits there with “QEMU/KVM – > Connecting…” And doesn’t advance. > > When I first installed this machine, VMM was able to open, and I was able to > create guests. However, I was unable to view their consoles. After rebooting > the host, now VMM seems unable to connect. > > > > I’ve verified that qemu is running. If I do virsh – connect qemu:///system > list I do see the list of created guests. And I can even start them from the > command line. > > I’m running centos 7. The console I’m logged into is a non privileged user. > I open a terminal and launch VMM as root. > How are you launching it as root? Exact command please. sudo, su, su -, su -c, etc. Generally running a UI app as root from a regular desktop session can cause all sorts of issues with dbus access. Better to run virt-manager as a regular user, then feed it your root password via the polkit prompt. - Cole ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
Re: [virt-tools-list] Virt-manager just sits at Connecting...
On 01/14/2016 11:51 AM, Greg Teiber wrote: > I'll give the google route a shot. > > I su, and become root in the terminal. Then type virt-manager. > > [sa@vm02 ~]$ su > Password: For one thing you pretty much never want to run plain 'su' if trying to launch a modern desktop app. Use 'su -', which invokes a full login shell, giving root it's own environment, etc. This has caused issues with virt-manager in the past Also, are you at the physical machine, or running over ssh ? > [root@vm02 sa]# virt-manager > > I have tried running virt-manager and giving it the root password when it > opens. I get the same result, where it just sits there "Connecting..." > Try running virt-manager --debug and see what output it shows when it hangs, maybe there's some obvious error that needs fixing. > > > -Original Message- > From: Cole Robinson [mailto:crobi...@redhat.com] > Sent: Thursday, January 14, 2016 10:45 AM > To: Greg Teiber; virt-tools-list@redhat.com > Subject: Re: [virt-tools-list] Virt-manager just sits at Connecting... > > On 01/14/2016 11:39 AM, Greg Teiber wrote: >> Hello Everyone, >> >> >> >> I didn't see an archive search function... So here we go. >> > > There isn't one. But if you google 'virt-tools-list ' it's > pretty close > >> >> >> When I open virt-manager it opens up, and sits there with "QEMU/KVM - >> Connecting..." And doesn't advance. >> >> When I first installed this machine, VMM was able to open, and I was >> able to create guests. However, I was unable to view their consoles. >> After rebooting the host, now VMM seems unable to connect. >> >> >> >> I've verified that qemu is running. If I do virsh - connect >> qemu:///system list I do see the list of created guests. And I can >> even start them from the command line. >> >> I'm running centos 7. The console I'm logged into is a non privileged user. >> I open a terminal and launch VMM as root. >> > > How are you launching it as root? Exact command please. sudo, su, su -, su > -c, etc. > > Generally running a UI app as root from a regular desktop session can cause > all sorts of issues with dbus access. Better to run virt-manager as a regular > user, then feed it your root password via the polkit prompt. > > - Cole > ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
Re: [virt-tools-list] Virt-manager just sits at Connecting...
I'll give the google route a shot. I su, and become root in the terminal. Then type virt-manager. [sa@vm02 ~]$ su Password: [root@vm02 sa]# virt-manager I have tried running virt-manager and giving it the root password when it opens. I get the same result, where it just sits there "Connecting..." -Greg -Original Message- From: Cole Robinson [mailto:crobi...@redhat.com] Sent: Thursday, January 14, 2016 10:45 AM To: Greg Teiber; virt-tools-list@redhat.com Subject: Re: [virt-tools-list] Virt-manager just sits at Connecting... On 01/14/2016 11:39 AM, Greg Teiber wrote: > Hello Everyone, > > > > I didn't see an archive search function... So here we go. > There isn't one. But if you google 'virt-tools-list ' it's pretty close > > > When I open virt-manager it opens up, and sits there with "QEMU/KVM - > Connecting..." And doesn't advance. > > When I first installed this machine, VMM was able to open, and I was > able to create guests. However, I was unable to view their consoles. > After rebooting the host, now VMM seems unable to connect. > > > > I've verified that qemu is running. If I do virsh - connect > qemu:///system list I do see the list of created guests. And I can > even start them from the command line. > > I'm running centos 7. The console I'm logged into is a non privileged user. > I open a terminal and launch VMM as root. > How are you launching it as root? Exact command please. sudo, su, su -, su -c, etc. Generally running a UI app as root from a regular desktop session can cause all sorts of issues with dbus access. Better to run virt-manager as a regular user, then feed it your root password via the polkit prompt. - Cole ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
Re: [virt-tools-list] Virt-manager just sits at Connecting...
I'm using VNC to get to the desktop on a physical server. I tried it with su - and no joy. So I tried virt-manager --debug I got back a couple pages of this: " Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/baseclass.py", line 135, in wrap_func self.disconnect(id_list[0]) File "/usr/share/virt-manager/virtManager/baseclass.py", line 96, in disconnect ret = GObject.GObject.disconnect(self, handle) File "/usr/lib64/python2.7/site-packages/gi/overrides/GObject.py", line 429, in wrapper return func(_get_instance_for_signal(obj), *args, **kwargs) File "/usr/lib64/python2.7/site-packages/gi/types.py", line 113, in function return info.invoke(*args, **kwargs) TypeError: argument instance: Expected GObject.Object, but got PyCObject" That's an obvious problem, but I'm not sure what direction to go in repairing it. -Greg -Original Message- From: Cole Robinson [mailto:crobi...@redhat.com] Sent: Thursday, January 14, 2016 10:56 AM To: Greg Teiber; virt-tools-list@redhat.com Subject: Re: [virt-tools-list] Virt-manager just sits at Connecting... On 01/14/2016 11:51 AM, Greg Teiber wrote: > I'll give the google route a shot. > > I su, and become root in the terminal. Then type virt-manager. > > [sa@vm02 ~]$ su > Password: For one thing you pretty much never want to run plain 'su' if trying to launch a modern desktop app. Use 'su -', which invokes a full login shell, giving root it's own environment, etc. This has caused issues with virt-manager in the past Also, are you at the physical machine, or running over ssh ? > [root@vm02 sa]# virt-manager > > I have tried running virt-manager and giving it the root password when it > opens. I get the same result, where it just sits there "Connecting..." > Try running virt-manager --debug and see what output it shows when it hangs, maybe there's some obvious error that needs fixing. > > > -Original Message- > From: Cole Robinson [mailto:crobi...@redhat.com] > Sent: Thursday, January 14, 2016 10:45 AM > To: Greg Teiber; virt-tools-list@redhat.com > Subject: Re: [virt-tools-list] Virt-manager just sits at Connecting... > > On 01/14/2016 11:39 AM, Greg Teiber wrote: >> Hello Everyone, >> >> >> >> I didn't see an archive search function... So here we go. >> > > There isn't one. But if you google 'virt-tools-list ' > it's pretty close > >> >> >> When I open virt-manager it opens up, and sits there with "QEMU/KVM - >> Connecting..." And doesn't advance. >> >> When I first installed this machine, VMM was able to open, and I was >> able to create guests. However, I was unable to view their consoles. >> After rebooting the host, now VMM seems unable to connect. >> >> >> >> I've verified that qemu is running. If I do virsh - connect >> qemu:///system list I do see the list of created guests. And I can >> even start them from the command line. >> >> I'm running centos 7. The console I'm logged into is a non privileged user. >> I open a terminal and launch VMM as root. >> > > How are you launching it as root? Exact command please. sudo, su, su -, su > -c, etc. > > Generally running a UI app as root from a regular desktop session can cause > all sorts of issues with dbus access. Better to run virt-manager as a regular > user, then feed it your root password via the polkit prompt. > > - Cole > ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
Re: [virt-tools-list] Virt-manager just sits at Connecting...
On 01/14/2016 04:57 PM, Greg Teiber wrote: > I'm using VNC to get to the desktop on a physical server. > > I tried it with su - and no joy. So I tried virt-manager --debug > > I got back a couple pages of this: > > " Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/baseclass.py", line 135, in > wrap_func > self.disconnect(id_list[0]) > File "/usr/share/virt-manager/virtManager/baseclass.py", line 96, in > disconnect > ret = GObject.GObject.disconnect(self, handle) > File "/usr/lib64/python2.7/site-packages/gi/overrides/GObject.py", line > 429, in wrapper > return func(_get_instance_for_signal(obj), *args, **kwargs) > File "/usr/lib64/python2.7/site-packages/gi/types.py", line 113, in function > return info.invoke(*args, **kwargs) > TypeError: argument instance: Expected GObject.Object, but got PyCObject" > > That's an obvious problem, but I'm not sure what direction to go in repairing > it. > Me neither, that's a new one to me. What version of centos is this? Please provide: rpm -q virt-manager gtk3 pygobject3 Thanks, Cole > -Greg > > -Original Message- > From: Cole Robinson [mailto:crobi...@redhat.com] > Sent: Thursday, January 14, 2016 10:56 AM > To: Greg Teiber; virt-tools-list@redhat.com > Subject: Re: [virt-tools-list] Virt-manager just sits at Connecting... > > On 01/14/2016 11:51 AM, Greg Teiber wrote: >> I'll give the google route a shot. >> >> I su, and become root in the terminal. Then type virt-manager. >> >> [sa@vm02 ~]$ su >> Password: > > For one thing you pretty much never want to run plain 'su' if trying to > launch a modern desktop app. Use 'su -', which invokes a full login shell, > giving root it's own environment, etc. This has caused issues with > virt-manager in the past > > Also, are you at the physical machine, or running over ssh ? > >> [root@vm02 sa]# virt-manager >> >> I have tried running virt-manager and giving it the root password when it >> opens. I get the same result, where it just sits there "Connecting..." >> > > Try running virt-manager --debug and see what output it shows when it hangs, > maybe there's some obvious error that needs fixing. > >> >> >> -Original Message- >> From: Cole Robinson [mailto:crobi...@redhat.com] >> Sent: Thursday, January 14, 2016 10:45 AM >> To: Greg Teiber; virt-tools-list@redhat.com >> Subject: Re: [virt-tools-list] Virt-manager just sits at Connecting... >> >> On 01/14/2016 11:39 AM, Greg Teiber wrote: >>> Hello Everyone, >>> >>> >>> >>> I didn't see an archive search function... So here we go. >>> >> >> There isn't one. But if you google 'virt-tools-list ' >> it's pretty close >> >>> >>> >>> When I open virt-manager it opens up, and sits there with "QEMU/KVM - >>> Connecting..." And doesn't advance. >>> >>> When I first installed this machine, VMM was able to open, and I was >>> able to create guests. However, I was unable to view their consoles. >>> After rebooting the host, now VMM seems unable to connect. >>> >>> >>> >>> I've verified that qemu is running. If I do virsh - connect >>> qemu:///system list I do see the list of created guests. And I can >>> even start them from the command line. >>> >>> I'm running centos 7. The console I'm logged into is a non privileged >>> user. >>> I open a terminal and launch VMM as root. >>> >> >> How are you launching it as root? Exact command please. sudo, su, su -, su >> -c, etc. >> >> Generally running a UI app as root from a regular desktop session can cause >> all sorts of issues with dbus access. Better to run virt-manager as a >> regular user, then feed it your root password via the polkit prompt. >> >> - Cole >> > ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
[virt-tools-list] [virt-manager][PATCH 3/3] virtconvtest: Fix vmx2libvirt test
The test consists of translating VMX configuration into domain
XML and converting disks. Cool. But the disk is zipped in a file
and the test tries to string match unzipping command. Problem is,
the absolute path is passed to the unzip command which makes it
impossible for the test to succeed on other hosts.
Signed-off-by: Michal Privoznik
---
tests/virtconv-files/libvirt_output/vmx2libvirt_test-vmx-zip.libvirt | 2 +-
tests/virtconvtest.py| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
a/tests/virtconv-files/libvirt_output/vmx2libvirt_test-vmx-zip.libvirt
b/tests/virtconv-files/libvirt_output/vmx2libvirt_test-vmx-zip.libvirt
index b046c66..b13662c 100644
--- a/tests/virtconv-files/libvirt_output/vmx2libvirt_test-vmx-zip.libvirt
+++ b/tests/virtconv-files/libvirt_output/vmx2libvirt_test-vmx-zip.libvirt
@@ -73,5 +73,5 @@
-test-vmx-zip.zip appears to be an archive, running: unzip -o -d
/var/tmp/virt-convert-tmp
/home/crobinso/src/virt-manager/tests/virtconv-files/vmx_input/test-vmx-zip.zip
+test-vmx-zip.zip appears to be an archive, running: unzip -o -d
/var/tmp/virt-convert-tmp vmx_input/test-vmx-zip.zip
Copying MS-DOS.vmdk to /var/lib/libvirt/images/MS-DOS
diff --git a/tests/virtconvtest.py b/tests/virtconvtest.py
index 622117f..859e8e0 100644
--- a/tests/virtconvtest.py
+++ b/tests/virtconvtest.py
@@ -49,7 +49,7 @@ class TestVirtConv(unittest.TestCase):
ignore, out_xml = guest.start_install(return_xml=True)
out_expect = out_xml
if outbuf.getvalue():
-out_expect += ("\n\n" + outbuf.getvalue())
+out_expect += ("\n\n" + outbuf.getvalue().replace(base_dir, "" ))
if not conn.check_support(conn.SUPPORT_CONN_VMPORT):
self.skipTest("Not comparing XML because vmport isn't supported")
--
2.4.10
___
virt-tools-list mailing list
virt-tools-list@redhat.com
https://www.redhat.com/mailman/listinfo/virt-tools-list
[virt-tools-list] [virt-manager][PATCH 2/3] virt-convert: Don't detect existing paths in test suite
We have this option --dry-run that should run through the
installation process but don't actually touch anything. Just
pretend the installation. And we have a test that uses it
heavily. However, the test is failing:
Traceback (most recent call last):
File "/home/zippy/work/virt-manager.git/tests/clitest.py", line 161, in
_launch_command
ret = virtconvert.main(conn=conn)
File "virt-convert", line 111, in main
destdir=options.destination, dry=options.dry)
File "/home/zippy/work/virt-manager.git/virtconv/formats.py", line 314, in
convert_disks
newpath)
RuntimeError: New path name '/var/lib/libvirt/images/fedora.qcow2' already
exists
Problem is, even in test suite we really touch the host paths.
This in general will spit unpredictable results. Resolution
consists of making this specific part of the code fault tolerant
if ran under test suite.
Signed-off-by: Michal Privoznik
---
virtconv/formats.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/virtconv/formats.py b/virtconv/formats.py
index ed8a66e..a7f88cb 100644
--- a/virtconv/formats.py
+++ b/virtconv/formats.py
@@ -309,7 +309,7 @@ class VirtConverter(object):
if disk_format:
newpath += ("." + disk_format)
newpath = os.path.join(destdir, newpath)
-if os.path.exists(newpath):
+if os.path.exists(newpath) and not _is_test():
raise RuntimeError(_("New path name '%s' already exists") %
newpath)
--
2.4.10
___
virt-tools-list mailing list
virt-tools-list@redhat.com
https://www.redhat.com/mailman/listinfo/virt-tools-list
[virt-tools-list] [virt-manager][PATCH 1/3] tests: Update virt-install-many-devices.xml
Libvirt started to put type='raw' to element to disks when no type has been provided. We should reflect that change in our tests too. Signed-off-by: Michal Privoznik --- tests/cli-test-xml/compare/virt-install-many-devices.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/cli-test-xml/compare/virt-install-many-devices.xml b/tests/cli-test-xml/compare/virt-install-many-devices.xml index 79eb189..248a59f 100644 --- a/tests/cli-test-xml/compare/virt-install-many-devices.xml +++ b/tests/cli-test-xml/compare/virt-install-many-devices.xml @@ -76,12 +76,12 @@ - + - + -- 2.4.10 ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
[virt-tools-list] [virt-manager][PATCH 0/3] Couple of test fixes
Finally, I've managed to find time to fix the tests. Michal Privoznik (3): tests: Update virt-install-many-devices.xml virt-convert: Don't detect existing paths in test suite virtconvtest: Fix vmx2libvirt test tests/cli-test-xml/compare/virt-install-many-devices.xml | 4 ++-- tests/virtconv-files/libvirt_output/vmx2libvirt_test-vmx-zip.libvirt | 2 +- tests/virtconvtest.py| 2 +- virtconv/formats.py | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) -- 2.4.10 ___ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
