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 unab
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
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 -', w
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 "Connecti
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.dis
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/virt
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 oth
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/t
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 --gi
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 ++--
t
10 matches
Mail list logo
