[libvirt-users] UTS namespace
by Aarti Sawant
Hello,
I am trying to set up UTS name space on centos 6.4 LXC container.
one method is that we set the host name in /etc/sysconfig/network.
hostname=test1
Is there any way so that i can set the hostname in libvirt xml while
creating a container?
I know using lxc-tools we can set hostname while creating by 2 ways
- first while creating container using lxc-create -u test1
- Second by specifying lxc.utsname=test1 in config file
Thanks
Aarti Sawant
NTTDATA OSS Center Pune
11 years, 1 month
[libvirt-users] User Namespace in LXC
by Saurabh Deochake
Hi all,
I'm trying to restrict privileges of root user inside the container. I
searched about it and got to know about "idmap" element in domain XML.
I added "idmap" element in my container's XML file:
<idmap>
<uid start='0' target='1000' count='10'/>
<gid start='0' target='1000' count='10'/>
</idmap>
I restarted the container with updated XML file.
When I execute "id" command to know if root user inside the container has
been mapped with an user from host, i still get output uid as 0
# id -u root
0
Am I doing the steps right to check the user namespacing? Please help me
out with this.
Thanks in advance,
Saurabh Deochake.
NTT DATA OSS Center, Pune, India
11 years, 1 month
[libvirt-users] Doc/web site problems
by Greg Ward
Hi all --
I have one meta-question, and two real questions.
1) What's the best place to report bugs in the docs, FAQ, web site, or
wiki? I have found two -- see next points. (I'm happy to make the fixes
myself if I can, but I'm pretty ignorant about libvirt. Can't fix the
docs without knowing the truth.)
2) In the FAQ, under "networking is unavailable in virt-manager / virsh
- libvirt's default network fails to start", it says "Here is a list of
the networking-related packages that need to be installed for libvirt
networking to work properly:". But it does not say if those packages are
supposed to be installed on the host or the guest! It might be obvious
to you, but it isn't to me.
3) In http://wiki.libvirt.org/page/Networking#Guest_configuration, it
says "the following XML would be used in the guest:" ... but it doesn't
say WHERE to put that configuration! Is it a snippet to add to an
existing file? A new file I have to create? Something else? Very
frustrating! ;-(
Thanks --
Greg
11 years, 1 month
[libvirt-users] Migration function is not supported by the connection driver: virDomainMigrate2
by Joseph Perrin
Greetings;
I'm running Fedora 19, Xen 4.2.3, libvirt 1.0.5.6. I have two identical
servers x1 & x2. I've read http://libvirt.org/migration.html & I've
created certificates for tls according to
http://wiki.libvirt.org/page/TLSSetup
I can do this on both servers, and from a third admin server:
# virsh -c xen+tls://x1.localdomain hostname
x1.localdomain
and...
# virsh -c xen+tls://x2.localdomain hostname
x2.localdomain
It appears I can connect without issues.
No matter what I try, I cannot get migration to work :-( x 1000! I've
created a test DomU named "z19", which uses a DRBD block device between the
two hosts. It's running on x1, (and obviously not on x2), and I want to
migrate it to x2.
When I attempt to migrate I get the following. (Although, I've tried every
permutation of syntax I've read about. The following appears to be most
reasonable for my situation?)
# virsh migrate --live z19 xen+tls://x2.localdomain
error: this function is not supported by the connection driver:
virDomainMigrate2
# virsh -c xen+tls://x1.localdomain migrate z19 xen+tls://x2.localdomain
error: this function is not supported by the connection driver:
virDomainMigrate2
# virsh migrate --live z19 xen+ssh://root@x2.localdomain
error: this function is not supported by the connection driver:
virDomainMigrate2
I've set libvirtd.conf:
log_level=1
Which reports nothing.
There is a great amount of conflicting information on this topic. It's
difficult to ascertain which to listen to. Any suggestions you could give
me would be greatly appreciated.
-Joseph
11 years, 1 month
[libvirt-users] Lots of threads and increased IO load
by Gergely Horváth
Hello guys,
We have a lot of small computers on top of two servers running QEMU/KVM
virtualisation with libvirt. In this case, most of the VMs are not doing
much work, some of them barely touches any "hardware" resources.
I have two problems, they might be connected.
When I do a bigger IO job on one of the VMs (like downloading files to
local disk) all other VMs' IO load increases. Even our LDAP server's IO
load is triggering an alert in our monitoring system - though that
server barely does any IO throughout the day.
The big IO job can NOT be considered big in the terms of the host
computers IO capabilities, as it has two really fast SSD drives in
hardware RAID 0 configuration. It can easily do hundreds of megabytes
per second random write. The file copy I was running barely touched 50
MB/s. So this should not be a problem for the host's disks and I also do
not understand why other computers IO load is increased.
The second problem came when I looked at `iotop`, to see how much IO
read and write is going on. The computer, that was doing the copying
easily had like 20-30 threads writing pieces to the disk. Some of the
threads are obviously "processor emulators" - they been running since
the birth of the VM, but what are these other threads?
TL;DR;
Two questions than, to sum up everything:
* How can I control and maybe decrease the number of threads spawned for
a virtual machine?
* How can I know what is the default IO caching for a VM, and what
caching mechanism/policy should I set to minimise IO latency (i.e. I do
not really care if the data is written to the disk later than the guest
thinks)
Thank you.
P.S: We have been running hypertable servers the whole time, and even
those did not generate such mess with IO...
--
Üdvözlettel / Best regards
Horváth Gergely | gergely.horvath(a)inepex.com
IneTrack - Nyomkövetés egyszerűen | Inepex Kft.
Ügyfélszolgálat: support(a)inetrack.hu | +36 30 825 7646 | support.inetrack.hu
Web: www.inetrack.hu | nyomkovetes-blog.hu | facebook.com/inetrack
Inepex - The White Label GPS fleet-tracking platform | www.inepex.com
11 years, 1 month
[libvirt-users] Problem with bridged network configuration
by Bob Doolittle
Hi,
When I initially boot my system, it fails to bring up the network.
Once booted, if I run "systemctl restart network.service", or even stop,
wait a while, then start, it starts up fine and all is well.
I'm running Fedora 19 (updated).
I followed the instructions on this page to set up a bridged network:
http://wiki.libvirt.org/page/Networking
I note however that I did *not* have any bridge (for NAT use) configured
initially by default on my system, and followed the directions on this
page to create it:
https://fedoraproject.org/wiki/Getting_started_with_virtualization
I have disabled the NetworkManager service, and created network
initscripts for my em1 and br0 interfaces.
I notice from the systemctl status output, that the network failure is
logged, and only *after* that the br0 interface comes up. So I wonder if
there is some ordering problem in spite of the fact that I have
specified DELAY=0 for br0.
I have included output from the following commands:
systemctl status network.service (initially, when failed to come up)
brctl show
ip link
ip address
Also attached are the network initscripts for my em1 and br0 interfaces.
Any guidance would be much appreciated!
Thanks,
Bob
11 years, 1 month
[libvirt-users] Turning off polling
by Timothy Ehlers
Is it possible to turn off polling, we have 50~60 kvm instances per machine
and have found that when libvirtd is running each KVM pid has 20%
additional cpu usage.
I turned on debug logging for 10 minutes and it seems to be 99% of this:
virEventPollDispatchHandle
But i cannot find a way to disable it.
--
Tim Ehlers
11 years, 1 month
[libvirt-users] newer libvirt version issues
by Franky Van Liedekerke
Hi,
since we're running more than 20 hosts per KVM server, we needed to
update libvirt to at least 1.1.2 for virtlockd to be able to cope with
this (due to an old hardcoded limit that was in there before).
But where 1.1.0 compiles and runs just fine on a fully-patched CentOS
6.4 server, newer version have all kinds of issues:
Every version of libvirt >= 1.1.2 crashes with a segfault on up-to-date
CentOS 6.4 servers (see below).
Also, versions of libvirt >= 1.1.3 need a change in the spec file to be
able to compile:
apparently the %doc entries that are different with 1.1.2 prevent
rpmbuild to succeed on
CentOS servers. Using the %doc lines as per the 1.1.2 spec file results
in a working rpmbuild.
The 1.1.4 version has issues with a symbol not found after compiling
and letting it run:
error : virDriverLoadModule:78 : failed to load module
/usr/lib64/libvirt/connection-driver/libvirt_driver_network.so
/usr/lib64/libvirt/connection-driver/libvirt_driver_network.so:
undefined symbol: virNetworkList
error : virDriverLoadModule:78 : failed to load module
/usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so
/usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so:
undefined symbol: virAsprintf
error : virDriverLoadModule:78 : failed to load module
/usr/lib64/libvirt/connection-driver/libvirt_driver_nodedev.so
/usr/lib64/libvirt/connection-driver/libvirt_driver_nodedev.so:
undefined symbol: virNodeDeviceList
31677: error : virDriverLoadModule:78 : failed to load module
/usr/lib64/libvirt/connection-driver/libvirt_driver_secret.so
/usr/lib64/libvirt/connection-driver/libvirt_driver_secret.so: undefined
symbol: virAsprintf
31677: error : virDriverLoadModule:78 : failed to load module
/usr/lib64/libvirt/connection-driver/libvirt_driver_nwfilter.so
/usr/lib64/libvirt/connection-driver/libvirt_driver_nwfilter.so:
undefined symbol: virAsprintf
31677: error : virDriverLoadModule:78 : failed to load module
/usr/lib64/libvirt/connection-driver/libvirt_driver_interface.so
/usr/lib64/libvirt/connection-driver/libvirt_driver_interface.so:
undefined symbol: virAsprintf
31677: error : virDriverLoadModule:78 : failed to load module
/usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so
/usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so: undefined
symbol: networkAllocateActualDevice
31677: error : virDriverLoadModule:78 : failed to load module
/usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so
/usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so: undefined
symbol: networkAllocateActualDevice
And every time libvirt segfaults, there's this in the logs:
debug : virJSONValueToString:1133 :
result={"id":"libvirt-6","error":{"class":"CommandNotFound","desc":"The
command qom-list has not been found","data":{"name":"qom-list"}}}
debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=32
timeout=1684
9479: debug : qemuMonitorJSONCheckError:341 : unable to execute QEMU
command
{"execute":"qom-list","arguments":{"path":"/"},"id":"libvirt-6"}:
{"id":"libvirt-6","error":{"class":"CommandNotFound","desc":"The command
qom-list has not been found","data":{"name":"qom-list"}}}
9479: error : qemuMonitorJSONCheckError:352 : internal error: unable to
execute QEMU command 'qom-list': The command qom-list has not been found
Any insights on any of these issues?
Franky
11 years, 1 month
[libvirt-users] Unable to shutdown/reboot a SLES 10 SP4 VM
by Padma Narwankar
Hello,
I am unable to do a graceful shutdown or reboot of SLES 10 SP4 virtual machines (Kernel version: 2.6.16.60-0.85.1-default) with virsh shutdown or virsh reboot commands. (e.g virsh shutdown "vmname" ). On issuing these commands there is no impact on the VM. Also unable to perform the shutdown or reboot operations from the menu options available on the console when accessing the VM via the virt-manager.
The virsh shutdown/reboot commands and the shutdown/reboot menu operations work fine for SLES 11 SP2 VMs.
I've verified that the acpi daemon is running with the SLES 10 SP4 VM
linux-kb8x:~ # ps aux | grep acpi
root 8 0.0 0.0 0 0 ? S< 16:27 0:00 [kacpid]
root 9 0.0 0.0 0 0 ? S< 16:27 0:00 [kacpi_notify]
root 1830 0.0 0.0 2688 528 ? Ss 16:27 0:00 /sbin/acpid
Is there any other process that needs to running for these operations to work or is there a known issue with SLES 10 SP4?
Thanks,
Padmaja
11 years, 1 month
