[libvirt-users] Libvirt not getting connected to ESX server
by varun bhatnagar
Hi,
I was trying to connect to ESX server using libvirt's virsh console but I
am getting the following error:
*virsh# connect esx://172.16.73.14*
*Enter username for 172.16.73.14 [root]: root*
*Enter root's password for 172.16.73.14:*
*error: Failed to connect to the hypervisor*
*error: internal error curl_easy_perform() returned an error: Peer
certificate cannot be authenticated with known CA certificates (60) : SSL
certificate problem, verify that the CA cert is OK. Details:*
*error: 14090086:SSL routine:SSL3_GET_SERVER_CERTIFICATE:certificate verify
failed.*
*
*
Can anyone please help me out with this one and tell me how to resolve this
error?
Regards,
Varun
10 years, 11 months
[libvirt-users] Please remove pm-utils dep from libvirt-clients
by Richard Hughes
Hi,
I'm going to be retiring pm-utils from Fedora soon; it's completely
dead upstream and it not needed anymore by upower or anything else.
Nothing other than libvirt-clients depends on it, so when I tried to
remove this from rawhide I noticed this commit:
commit 7069f75cb8dad58715f723fd542e4ff69dbff51b
Author: Daniel Veillard <veillard(a)redhat.com>
Date: Thu Dec 8 17:03:16 2011 +0800
update to libvirt-0.9.8
added:
+# Needed for probing the power management features of the host.
+Requires: pm-utils
Is this true? You really don't want to be parsing pm-is-supported, it
often doesn't work and isn't used by anything else any more. Would it
be possible to port away from pm-is-supported if you're actually using
it, and drop the dep for F20 please? Any questions please CC me as I'm
not subscribed.
Thanks,
Richard
10 years, 12 months
[libvirt-users] Installing libvirt
by Peeyush Gupta
Hi,
I am trying to install new libvirt version on Ubuntu 12.04 LTS. Now I downloaded libvirt 1.0.5 from libvirt.org/sources then I issued three commands:
./autogen.sh
make
make install
This installs the libvirt on my system. But there are some issues, I have to run libvirtd explicitly everytime I reboot my system. And whenever I try to run virt-manager from terminal, it says "No D-Bus daemon running". But when I do "sudo virt-manager", it runs fine. Any idea what am I doing wrong?
Thanks.
~Peeyush Gupta
10 years, 12 months
[libvirt-users] start lxc container on fedora 19
by Aarti Sawant
hello,
i am new to lxc, i have created a lxc container on fedora 19
i created a container rootfs of fedora 19 by using
yum --installroot=/containers/test1 --releasever=19 install openssh
test1.xml file for container test1
<domain type="lxc">
<name>test1</name>
<vcpu placement="static">1</vcpu>
<cputune>
<shares>1024</shares>
<period>1000000</period>
</cputune>
<memtune>
<hard_limit unit="M">1024</hard_limit>
<soft_limit unit="M">128</soft_limit>
<min_guarantee unit="M">64</min_guarantee>
</memtune>
<blkiotune>
<weight>800</weight>
</blkiotune>
<memory unit="KiB">102400</memory>
<os>
<type>exe</type>
<init>/bin/bash</init>
</os>
<clock offset="utc"/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/libexec/libvirt_lxc</emulator>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/"/>
<target dir="/"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/var"/>
<target dir="/var"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/dev"/>
<target dir="/dev"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/root"/>
<target dir="/root"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/home"/>
<target dir="/home"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/opt"/>
<target dir="/opt"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/media"/>
<target dir="/media"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/bin"/>
<target dir="/bin"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/lib64"/>
<target dir="/lib64"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/etc"/>
<target dir="/etc"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/lib"/>
<target dir="/lib"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/run"/>
<target dir="/run"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/srv"/>
<target dir="/srv"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/sys"/>
<target dir="/sys"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/tmp"/>
<target dir="/tmp"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/boot"/>
<target dir="/boot"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/usr"/>
<target dir="/usr"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/mnt"/>
<target dir="/mnt"/>
</filesystem>
<filesystem accessmode="passthrough" type="mount">
<source dir="/containers/test1/sbin"/>
<target dir="/sbin"/>
</filesystem>
<interface type="bridge">
<source bridge="br0"/>
</interface>
<console port="0" type="pty"/>
</devices>
</domain>
the host network files:
/etc/sysconfig/network-script/ifcfg-br0
DEVICE="br0"
TYPE="Bridge"
USERCTL="no"
BOOTPROTO="dhcp"
ONBOOT="yes"
NM_CONTROLLED="no"
/etc/sysconfig/network-script/ifcfg-p2p1
DEVICE="p2p1"
BOOTPROTO="dhcp"
BRIDGE="br0"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="Ethernet"
the fstab of host
#
# /etc/fstab
# Created by anaconda on Fri Jul 26 05:26:08 2013
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=b49ce5dc-afb7-4c8e-9487-c1ed101d9166 / ext4
defaults 1 1
UUID=3dfa07fd-a06b-4a1a-a3fd-4e2f5e0d0e6a /boot ext4
defaults 1 2
UUID=3d1cb255-721a-48d2-b2e9-86f52b5fbec6 swap swap
defaults 0 0
none /sys/fs/cgroup cgroup defaults 0 0
when i try to start the container using virsh i get error
virsh --connect lxc://
virsh # define /containers/test1/test1.xml
Domain test1 defined from /containers/test1/test1.xml
virsh # start test1
error: Failed to start domain test1
error: internal error guest failed to start: PATH=/bin:/sbin TERM=linux
container=lxc-libvirt container_uuid=05a7239d-f610-4ae9-ad47-4bf47f2f9b54
LIBVIRT_LXC_UUID=05a7239d-f610-4ae9-ad47-4bf47f2f9b54
LIBVIRT_LXC_NAME=test1 /bin/lxc_defaultinit.sh
Unable to send container continue message: Broken pipe
has anyone face the same problem with fedora 19.
can anyone guide me..
Thanks,
Aarti Sawant
10 years, 12 months
[libvirt-users] Segfault with ruby-libvirt 0.4.0 and libvirt 1.1.1
by Bertrand Paquet
Hi,
I have upgraded my libvirt version, and I have a crash using ruby-libvirt
(0.4.0). The same code ruby worked well before upgrade.
ruby(92500,0x107092000) malloc: *** error for object 0x7fdc03ea7658:
pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Abort trap: 6
I'm under Mac Os, but my colleague is under Linux and have the same problem.
Any idea ?
Any information to how diagnosis the problem ?
Regards,
Bertrand
10 years, 12 months
