[libvirt-users] How to start guset os with specified IP address
by 落痕
Hi!
Dear everyone. I met a problem with virsh.
What should I do if I hope to start my guest os with specified IP address and guest os can be accessed by external computers?
I tried to use route mode to configure my virbr0, but it cannot assign an IP to my guest os!
If virbr0 are set NAT mode and act as a switch with dhcp, then the guest os cannot be accessed by external computer.
note: Ubuntu server are install in host without xwindows, so I have to work with command line.
Thanks!
9 years
[libvirt-users] virt-manager 1.3.1 - broken ?? (Ubuntu 14.04 )
by Adolf Augustin
Hi,
i just upgraded to virt-manager 1.3.1 (Kubuntu 14.04 with getdeb).
I can connect to a remote Hypervisor (libvirtd/KVM) but when i try to
"open" a VM, virt-manager gives me the following error:
==============================================================================
summary=Fehler beim Starten der Details: Namespace Vte not available for
version 2.91
details=Fehler beim Starten der Details: Namespace Vte not available for
version 2.91
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 823, in
_show_vm_helper
details = self._get_details_dialog(uri, vm.get_connkey())
File "/usr/share/virt-manager/virtManager/engine.py", line 801, in
_get_details_dialog
obj = vmmDetails(conn.get_vm(connkey))
File "/usr/share/virt-manager/virtManager/details.py", line 367, in
__init__
from .console import vmmConsolePages
File "/usr/share/virt-manager/virtManager/console.py", line 30, in
<module>
from .serialcon import vmmSerialConsole
File "/usr/share/virt-manager/virtManager/serialcon.py", line 32, in
<module>
gi.require_version("Vte", "2.91")
File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 83, in
require_version
(namespace, version))
ValueError: Namespace Vte not available for version 2.91
=================================================================================
Any Suggestions ?
virt-manager Verions 1.1.x-1.3.0 worked just fine.
What happened ?
--
Best regards
Adolf Augustin
E-mail: adolf.augustin(a)zettamail.de
PGP-Key: 0xC4709AFE
Fingerprint: 1806 35FA CAE8 0202 B7AF 12B9 5956 5BC0 C470 9AFE
9 years
[libvirt-users] Issues with installing Libvirt 1.2.7 on Ubuntu 12.04
by Waqas Riaz
Hi,
I am trying to manually install libvirt 1.2.7 on Ubuntu 12.04 LTS (64bit).
I have installed libxml2-dev libgnutls-dev libcurl4-gnutls-dev python-dev,
but I am facing dependency issues for libdevmapper libraries.
Is there any workaround for this dependency? OR is there any other way to
install libivirt 1.2.7 on Ubuntu 12.04.
Following is the output of the error
#apt-get install libdevmapper-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libdevmapper-dev : Depends: libdevmapper1.02.1 (= 2:1.02.48-4ubuntu7.4)
but 2:1.02.90-2ubuntu1 is to be installed
Depends: libdevmapper-event1.02.1 (=
2:1.02.48-4ubuntu7.4) but 2:1.02.90-2ubuntu1 is to be installed
E: Unable to correct problems, you have held broken packages.
Kind Regards,
Waqas Riaz
MTS, xFlow Research Inc.
+92-332-6396672
waqas.riaz(a)xflowresearch.com <ashok(a)xflowresearch.com>
www.xflowresearch.com
This electronic message transmission contains information from the Company
that may be proprietary, confidential and/or privileged. The information
is intended only for the use of the individuals or entity named above. If
you are not the intended recipient, be aware that any disclosure, copying
or distribution or use of the contents of this information is prohibited.
If you have received this electronic transmission in error, please notify
the sender immediately by replying to the address listed in the “From:”
field.
9 years
[libvirt-users] Destroy autostarted network on shutdown
by Jan Grashöfer
Hi all,
I just ran into problem properly stopping a network. I have defined a
network and network hook script to accomplish some preparations and
cleanup. Testing my configuration (virsh net-start and virsh
net-destroy) was successfully.
Now I wanted to automate the lifecycle. Unfortunately I realized that an
autostarted network has to be persistent and thus will not be destroyed
(even if the host gets shutdown). As it won't be destroyed, my cleanup
doesn't get executed and I run into trouble.
What would be the preferred way to implement an autostarting and
autostopping network?
Thanks,
Jan
9 years
[libvirt-users] virsh attach-device scripting ...
by Jean-Pierre Ribeauville
Hi,
Did anybody ever try to script « virsh attach-device ...... < response.txt" in order to give virsh user and password
needed when host is part of a ovirt cluster ?
Cos , although I put in my response.txt two lines one for user the other for password , then it always asks question concerning password.
( username is correctly got from the .txt file.)
Thanks for help.
Regards,
J.P. Ribeauville
P: +33.(0).1.47.17.20.49
.
Puteaux 3 Etage 5 Bureau 4
jpribeauville(a)axway.com<mailto:jpribeauville@axway.com>
http://www.axway.com<http://www.axway.com/>
P Pensez à l'environnement avant d'imprimer.
9 years
[libvirt-users] libvirt logging of virDomainAttachDeviceFlags()
by Jean-Pierre Ribeauville
Hi,
When using « virsh attach-device ....." to add a channel device to a Guest , I see following entry in libvirt log :
2015-12-07 11:14:47.307+0000: 14551: debug : virDomainAttachDeviceFlags:10433 : dom=0x7f2a58252fc0, ........
Great !!
But , when calling virDomainAttachDeviceFlags( ) from a C program , I got return code -1 but nothing appears related to virDomainAttachDeviceFlags( ) in the libvirt log file .
Others libvirt calls of this C program are correctly logged .
Did I misunderstand something ?
To add traces I've added these lines within /etc/libvirt/libvirtd.conf
log_level = 1
log_outputs="1:file:/var/log/libvirt/libvirtd.log"
Thx for help.
Regards,
J.P. Ribeauville
P: +33.(0).1.47.17.20.49
.
Puteaux 3 Etage 5 Bureau 4
jpribeauville(a)axway.com<mailto:jpribeauville@axway.com>
http://www.axway.com<http://www.axway.com/>
P Pensez à l'environnement avant d'imprimer.
9 years
[libvirt-users] virsh athentification failure
by Jean-Pierre Ribeauville
Hi,
I wrote a C program running in a KVM host.
Part of it adds a Unix Channel device in all Guests in order to have a dialog from Host to Guest.
As long as my host wasn't part of an Ovirt cluster , all was running fine.
I added my host in a ovirt cluster , and then , when running the script creating the channel device ( by using "virsh attach-device --persistent -live ....." ) , I got following error :
Please enter your authentication name:
Please enter your password:
error: failed to connect to the hypervisor
error: no valid connection
error: authentication failed: Failed to step SASL negotiation: -1 (SASL(-1): generic failure: All-whitespace username.)
What's the user/password I've to use then ?
BTW , I've seen that following channel device was added to the Guest at its creation :
/var/lib/libvirt/qemu/channels/ad1a8b0e-f8b6-4038-be3d-275f38e66eb3.org.qemu.guest_agent.0
What's used for ?
I presume I cannot use for my private purpose ?
I sent this topic to ovirt and libvirt mailing lists , cos I don't know which forum is the right one for this kind of subject.
Thanks for help.
Regards,
J.P. Ribeauville
P: +33.(0).1.47.17.20.49
.
Puteaux 3 Etage 5 Bureau 4
jpribeauville(a)axway.com<mailto:jpribeauville@axway.com>
http://www.axway.com<http://www.axway.com/>
P Pensez à l'environnement avant d'imprimer.
9 years
Re: [libvirt-users] snapshot of running vm's
by Lentes, Bernd
Dominique wrote:
>
> Never had that problem. Can it be a setting of the guest agent on the
> guest? With me all the commands of the ga are enabled...
>
Where can i change the settings of the agent ?
> You can check the commands by using this:
> virsh qemu-agent-command $VM '{"execute": "guest-info"}'
>
> This way you can at least check that the command is really disabled.
You'll
> have to find a way to enable the command then...
>
> I can't help you further with this...
>
> >
> > I managed to update to libvirt 1.2.11. Guest Agent is running in the
vm.
> > I'm trying to snapshot:
> >
> > virsh # snapshot-create-as --domain sles11 --name sn_sles11 --atomic
> > --disk- only --quiesce
> > error: internal error: unable to execute QEMU agent command
> > 'guest-fsfreeze-freeze': The command guest-fsfreeze-freeze has been
> > disabled for this instance
> >
> > What is now going on ?
> > Guest Agent in VM is qemu-guest-agent-2.0.2-1.35.
> >
virsh # qemu-agent-command sles11 '{"execute": "guest-info"}'
{"return":{"version":"2.0.2","supported_commands":[{"enabled":true,"name":
"guest-set-vcpus","success-response":true},{"enabled":true,"name":"guest-g
et-vcpus"
,"success-response":true},{"enabled":true,"name":"guest-network-get-interf
aces","success-response":true},{"enabled":true,"name":"guest-suspend-hybri
d","succe
ss-response":false},{"enabled":true,"name":"guest-suspend-ram","success-re
sponse":false},{"enabled":true,"name":"guest-suspend-disk","success-respon
se":false
},{"enabled":true,"name":"guest-fstrim","success-response":true},{"enabled
":true,"name":"guest-fsfreeze-thaw","success-response":true},
{"enabled":true,"name":"guest-fsfreeze-freeze","success-response":true}
,{"enabled":true,"name":"guest-fsfreeze-status","success-response":true},{
"enabled":true,"name":"guest-file-
flush","success-response":true},{"enabled":true,"name":"guest-file-seek","
success-response":true},{"enabled":true,"name":"guest-file-write","success
-response
":true},{"enabled":true,"name":"guest-file-read","success-response":true},
{"enabled":true,"name":"guest-file-close","success-response":true},{"enabl
ed":true,
"name":"guest-file-open","success-response":true},{"enabled":true,"name":"
guest-shutdown","success-response":false},{"enabled":true,"name":"guest-in
fo","succ
ess-response":true},{"enabled":true,"name":"guest-set-time","success-respo
nse":true},{"enabled":true,"name":"guest-get-time","success-response":true
},{"enabl
ed":true,"name":"guest-ping","success-response":true},{"enabled":true,"nam
e":"guest-sync","success-response":true},{"enabled":true,"name":"guest-syn
c-delimit
ed","success-response":true}]}}
It shows:
"...{"enabled":true,"name":"guest-fsfreeze-freeze","success-response":true
}
It understand this that it should work.
Bernd
Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir'in Baerbel Brumme-Bothe
Geschaeftsfuehrer: Prof. Dr. Guenther Wess, Dr. Nikolaus Blum, Dr. Alfons Enhsen
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671
9 years
[libvirt-users] FAIL: qemuxml2argvtest , FAIL: virsh-uriprecedence after make check
by Héctor Abreu
Hi there,
I'm new to libvirt and I'm trying to install it on a Debian Jessie system.
My goal is to create and use VMs from the command line.
When I get to the $ make check (not as root) I am getting the message
below. I am not sure if those "failed" messages should be corrected before
starting to use libvirt, not sure how important they are. I will appreciate
any hint or advise. Thanks.
=========================================
libvirt 1.3.0: tests/test-suite.log
=========================================
# TOTAL: 115
# PASS: 112
# SKIP: 1
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: qemuxml2argvtest
======================
TEST: qemuxml2argvtest
........................................ 40
........................................ 80
........................................ 120
...!.................................... 160
........................................ 200
........................................ 240
........................................ 280
........................................ 320
........................................ 360
........................................ 400
........................................ 440
........................................ 480
........................................ 520
............. 533 FAIL
FAIL: virsh-uriprecedence
=========================
TEST: virsh-uriprecedence
!!!! 4 FAILED
SKIP: virsh-all
===============
./virsh-all: skipping test:
This test is very expensive, so it is disabled by default.
To run it anyway, rerun: make check VIR_TEST_EXPENSIVE=1
9 years
