[libvirt-users] problem with dependencies
by monitz
hello
i have been having trouble installing libvirt
i installed kvm-kmod on rhel 5.4 kernel 2.6.18 without issues using an rpm
from the redhat website
after installation i tested it by creating an img file with qemu image and
went ahead to install libvirt and libvirt-python for virtmanager
however during installation of libvirt i get the following error:
failed dependencies /usr/bin/qemu-img
since qemu-img is in /usr/local/kvm/bin on my system i tried adding it to
$PATH, symlinking the file and even copying the binery to /usr/bin but to no
use
compilation from source seemed to go fine but after that libvirt-python
could still not find libvirt
is there any solution to this issue? , i would imagine it is a known one
thanks in advance
matan
14 years, 9 months
[libvirt-users] virt-manager and openvz
by Angel Bosch Mora
hi,
on main page of libvirt i can see that there's support for OpenVZ.
how can i connect with virt-manager to an OpenVZ machine?
im using virt-manager 0.8.2
Thanks,
angbosch
14 years, 9 months
[libvirt-users] pre/post vm start commands
by Soeren Grunewald
Hi there,
for development i use a windows vm. which is installed into a disk
image. because the compiler generates a lot of temporary files into the
user tempdir (C:\\Documents And Users\\User\\Local Settings\\Temp) the
vm becomes quite slow after a couple of weeks and i register a lot
activity on the disk.
so i moved the temp directory to a ram disk and no more problems.
but because the ram disk is not formated on startup i need to do this by
hand. so i disabled autostart for the vm and do the following:
$ sudo mkfs.ntfs -q -L TEMP -I /dev/ram0
$ sudo virsh start windows
so the question is, does libvirt provide some kind of pre startup script
which is will be executed before the libvirtd does the autostart for the vm.
--
Best Regards
Soeren
14 years, 9 months
[libvirt-users] error: unable to connect to libvirtd at 'a.b.c.d': Connection refused
by antonela_other＠yahoo.com
Greetings:
I have an issue with connecting to the esx hypervisor from my guest Vm. The purpose of the connection is to obtain host related information (like network, devices etc).
I am not sure what is it that rejects the connect at the server side, and what i am missing.
I am running lib0.7.5, i have libvirtd running on guest-vm.
The host ESX has the ip address a.b.c.d.
Any thoughts?
Below the error with some debug output from libvirt.
root > virsh -c esx://a.b.c.d/system
......................
17:06:16.065: debug : virConnectOpenAuth:1337 : name=esx://10.59.56.109/system, auth=0xb80ac638, flags=0
17:06:16.065: debug : do_open:1106 : name "esx://10.59.56.109/system" to URI components:
scheme esx
opaque (null)
authority (null)
server 10.59.56.109
user (null)
port 0
path /system
17:06:16.065: debug : do_open:1116 : trying driver 0 (Test) ...
17:06:16.066: debug : do_open:1122 : driver 0 Test returned DECLINED
17:06:16.066: debug : do_open:1116 : trying driver 1 (Xen) ...
17:06:16.066: debug : do_open:1122 : driver 1 Xen returned DECLINED
17:06:16.066: debug : do_open:1116 : trying driver 2 (OPENVZ) ...
17:06:16.066: debug : do_open:1122 : driver 2 OPENVZ returned DECLINED
17:06:16.066: debug : do_open:1116 : trying driver 3 (VBOX) ...
17:06:16.066: debug : do_open:1122 : driver 3 VBOX returned DECLINED
17:06:16.066: debug : do_open:1116 : trying driver 4 (remote) ...
17:06:16.067: debug : doRemoteOpen:564 : proceeding with name = esx:///system
17:06:16.069: debug : initialise_gnutls:1145 : loading CA file /etc/pki/CA/cacert.pem
17:06:16.070: debug : initialise_gnutls:1158 : loading client cert and key from files /etc/pki/libvirt/clientcert.pem and /etc/pki/libvirt/private/clientkey.pem
17:06:16.074: debug : do_open:1122 : driver 4 remote returned ERROR
17:06:16.074: debug : virUnrefConnect:259 : unref connection 0x903e078 1
17:06:16.074: debug : virReleaseConnect:216 : release connection 0x903e078
error: unable to connect to libvirtd at a.b.c.d': Connection refused
error: failed to connect to the hypervisor
I tried to use uri like: esx://a.b.c.d/, esx://a.b.c.d, esxi://a.b.c.d/system etc. They all give same issue.
Thanks.
Antonela
14 years, 9 months
[libvirt-users] libvirt attaching wrong usb device?
by Tom Hughes
I'm trying to attach a USB device which is attached to my host to a
guest instance. The device definition in the XML looks like:
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x046d'/>
<product id='0xc111'/>
</source>
</hostdev>
and the device appears in lsusb as USB device 002:018:
Bus 002 Device 018: ID 046d:c111 Logitech, Inc.
but when I try and start the guest libvirt appears to try and use a
different device which doesn't exist:
error: unable to set security context '107:107' on
'/dev/bus/usb/002/022': No such file or directory
This is using the current libvirt-0.7.6-1.fc12.x86_64 package from the
F12 virt-preview repository.
Tom
--
Tom Hughes (tom(a)compton.nu)
http://www.compton.nu/
14 years, 9 months
[libvirt-users] virt-manager can't start
by Stephen Liu
Hi folks,
KVM
Virt-manager
host - Debian 5.0
Starting;
Gnome
Applications -> System Tools - Virtual Machine Manager
popup following error;
Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager.py", line 346, in <module>
main()
File "/usr/share/virt-manager/virt-manager.py", line 248, in main
setup_logging()
File "/usr/share/virt-manager/virt-manager.py", line 124, in setup_logging
os.mkdir(vm_dir)
OSError: [Errno 17] File exists: '/home/satimis/.virt-manager'
- end -
$ ls -al /home/satimis/ | grep virt-manager
drwxr-xr-x 2 root root 4096 2009-05-31 06:11 .virt-manager
$ mv /home/satimis/.virt-manager /home/satimis/.virt-manager.old01
Restart
Applications -> System Tools - Virtual Machine Manager
starting GUI virt-manager but without asking for login as root
$ ls -al /home/satimis/ | grep virt-manager
drwxr-xr-x 2 satimis satimis 4096 2010-01-31 10:00 .virt-manager
If changing the owner by running
$ sudo chown root:root /home/satimis/.virt-manager
GUI virt-manage can't start with abovementioned warning pop.
Please advise how to fix this problem. I expect with root-password to start GUI
virt-manager
TIA
B.R.
Stephen L
Send instant messages to your online friends http://uk.messenger.yahoo.com
14 years, 9 months
[libvirt-users] No sound
by Stephen Liu
Hi folks,
Host - Debian 5.0
KVM
VM - Ubuntu 9.10
No sound on playing youtube. Volume on host and VM has been turned to max,
Virtual Machine Manager
Edit -> Preferences
Install Audio Device [check] Local VM
Please help. TIA
B.R.
Stephen L
Send instant messages to your online friends http://uk.messenger.yahoo.com
14 years, 9 months
[libvirt-users] Problem creating VM: "tap: not a valid disk type"
by Arik Raffael Funke
Hi,
I am having problems creating VMs in virt-manager.
I have played with different xen hypervisor versions 3.0 & 3.4 (with rpm
-i --force) but have in principle gone back to the originals. - Though I
cannot absolutely exclude that something has gone wrong.
In principle I am using rhel 5.4 with the gitco xen 3.4 hypervisor.
Can anybody put me on the right track with the attached error message?
Note, the storage file I am attempting to use does exist.
Many thanks,
Arik
===
Unable to complete install 'libvirt.libvirtError POST operation failed:
xend_post: error from xen daemon: (xend.err 'Error creating domain:
Invalid Configuration: tap: not a valid disk type')
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 1485, in
do_install
dom = guest.start_install(False, meter = meter)
File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 628,
in start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 726,
in _do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib64/python2.4/site-packages/libvirt.py", line 1077, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: POST operation failed: xend_post: error from xen daemon:
(xend.err 'Error creating domain: Invalid Configuration: tap: not a
valid disk type')
'
14 years, 9 months
