[libvirt-users] Hyper-V 2008 R2 support ?
by Jean-François FILIPPI
Hi,
I'm trying libvirt to connect to Hyper-V servers. It works fine for
Hyper-V 2012 servers, however it doesn't work for Hyper-V 2008 R2 (the
exact error is |
Call to virConnectOpenAuth failed: internal error: Transport error
during enumeration: Could not connect (7) (Libvirt::ConnectionError)|.).
I'm using the code provided by libvirt documentation
(http://libvirt.org/ruby/examples/open_auth.rb) and have authorized
basic auth plus unencrypted connection on both 2008 R2 & 2012 servers
(http://libvirt.org/drvhyperv.html#auth).
Surfing the Internet to find some solutions, I found this
(https://www.redhat.com/archives/libvir-list/2014-April/msg00802.html)
where a developer talks about stopping 2008 R2 support (because of some
technical stuff), while in the documentation
(http://libvirt.org/drvhyperv.html) it is explicitely said to be
supporting 2008 R2.
My question is : does the support has been stopped or does the code to
connect to a 2008 R2 server is different from the 2012 server ?
I'm using libvirt 1.2.2 and ruby-libvirt 1.2.2.
Thanks for your help,
Jean-François FILPPI
10 years
[libvirt-users] ANNOUNCE: Oz 0.13.0 release
by Chris Lalancette
All,
I'm pleased to announce release 0.13.0 of Oz. Oz is a program
for doing automated installation of guest operating systems with
limited input from the user. Release 0.13.0 is a bugfix and feature
release for Oz. Some of the highlights between Oz 0.12.0 and 0.13.0
are:
- For Fedora, if the user specifies a version, but that isn't
supported yet, try the last supported version (in this case), as that
will often work.
- Fix a regression where we forgot to force the qcow2 image type
- Allow installs that use more than one installation device
- Add support for RHEL 6.5
- Rename OEL-6 to OL-6
- Add support for Ubuntu 14.04
- Add Windows 8.1 support
- Add CentOS-7 support
- Add the ability to specify kernel parameters in the TDL
- Make sure to remove dhcp leases from guests after the install
- Fix support for FreeBSD
- Add in support for TDL "precommands"; these are commands that are
run *before* package installation
- Fix up file locking
- Add support for RHEL 5.11
- Remove Ubuntu ssh keys at the end of installation
- Add support for Ubuntu 14.10
- Add support for XInclude, for merging various TDLs together
- Add Fedora 21 support
- Add support for ppc64 and ppc64le
A tarball and zipfile of this release is available on the Github
releases page: https://github.com/clalancette/oz/releases . Packages
for Fedora-20, Fedora-21, Fedora-22, EPEL-6, and EPEL-7 have been
built in Koji and will eventually make their way to stable.
Instructions on how to get and
use Oz are available at http://github.com/clalancette/oz/wiki .
If you have questions or comments about Oz, please feel free to
contact me at clalancette at gmail.com, or open up an issue on the
github page: http://github.com/clalancette/oz/issues .
Thanks to everyone who contributed to this release through bug reports,
patches, and suggestions for improvement.
Chris Lalancette
10 years
[libvirt-users] live migration - qemu hook
by Martin Klepáč
Hi,
I am using qemu hook script to track status of VM live migration - libvirt
1.2.9 as included in Debian Wheezy backports.
I would like to be informed of the fact that VM migration has successfully
finished as soon as possible. Based on the steps below, when would that be
possible?
Sample VM migration as detected by qemu hook script:
1.) Destination hypervisor:
[10:27:42.224] Args: one-16 migrate begin
2.) Destination hypervisor:
[10:27:42.253] Args: one-16 prepare begin
3.) Destination hypervisor:
[10:27:42.472] Args: one-16 start begin
4.) Destination hypervisor:
[10:27:42.890] Args: one-16 started begin
5.) Actual VM migration...takes approximately 10 seconds in this case.
6.) Source hypervisor:
[10:27:51.847] Args: one-16 stopped end
7.) Source hypervisor:
[10:27:51.882] Args: one-16 release end
Based on the website, "Unless an error occurs during the migration process,
the *qemu* hook script on the *source* host is then executed with the
"stopped" and "release" operations to indicate it is no longer running on
this host."
So the source hypervisor in steps no. 6 and 7 knows that it is no longer
running a VM, right? Does that mean that the destination hypervisor is
already running the VM at the moment corresponding to step no. 6? If so, is
there any hook on the destination hypervisor, which would inform of the
fact that the hypervisor has copied the last portions of VM memory and has
become responsible for the VM in question?
Thank you,
Martin
10 years
Re: [libvirt-users] [virt-tools-list] libvirt/virt-manager source integration with xen
by Cole Robinson
On 03/02/2015 10:55 AM, Wayne Mills wrote:
> Hi,
>
> I built and installed Xen 4.5.0 from source, on top of Ubuntu 14.04.2, using
> "make world" and "make install" targets. I then installed latest virt-manager
> from pre-built packages. After bringing up virt-manager I attempt to connect
> to Xen hypervisor and got:
>
> unable to connect to libvirt
> Failed to connect socket to /var/run/libvirt/libvirt-sock' No such file
> or directory
>
> I then noticed libvirt-bin isn't running. If I try to issue 'service
> libvirt-bin start' it gives me back a process number, but it apparently dies
> quickly because the service still shows as down. Three log files are touched
> during my start attempt:
>
> -rw-r--r-- 1 root root 39757 Feb 27 06:00 /var/log/xenstored-access.log
> -rw-r--r-- 1 root root 44908 Feb 27 06:00
> /var/log/libvirt/libxl/libxl-driver.log
> -rw------- 1 root root 46396 Feb 27 06:00 /var/log/libvirt/libvirtd.log
>
> * xenstored-access.log has 22 new entries, grouped into pairs that increment
> an "Axx" identifier and go from A63 to A73. Here is the A63 logs:
>
> [20150227T11:00:29.478Z] A63 newconn
> [20150227T11:00:29.479Z] A63 endconn
>
> * libxl-driver.log also has 11 log groupings that are just the same set of
> logs repeated 11 times. Here is the first group:
>
> xc: detail: sysctl operation failed -- need to rebuild the user-space
> tool set?
> libxl: error: libxl.c:4320:libxl_get_physinfo: getting physinfo:
> Permission denied
> xc: debug: hypercall buffer: total allocations:7 total releases:7
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:1
> xc: debug: hypercall buffer: cache current size:1
> xc: debug: hypercall buffer: cache hits:6 misses:1 toobig:0
>
> * libvirtd.log also has 11 log groupings, that are just the same set of logs
> repeated 11 times. Here is that group:
>
> 2015-02-27 11:00:29.479+0000: 4842: info : libvirt version: 1.2.2
> 2015-02-27 11:00:29.479+0000: 4842: error : libxlDriverConfigNew:1131 :
> Unable to configure libxl's memory management parameters
> 2015-02-27 11:00:29.479+0000: 4842: error : virStateInitialize:749 :
> Initialization of LIBXL state driver failed: Unknown problem
> 2015-02-27 11:00:29.479+0000: 4842: error : daemonRunStateInit:920 :
> Driver state initialization failed
>
> When I google for libxl_get_physinfo I see other reported errors during "xl
> info" and other "xl" commands. I tried "xl info" and that works for me and
> does not alter the log files:
>
> root@<server>:~# xl info
> host : server
> release : 3.13.0-46-generic
> version : #75-Ubuntu SMP Tue Feb 10 15:24:04 UTC 2015
> machine : x86_64
> nr_cpus : 8
> max_cpu_id : 7
> nr_nodes : 2
> cores_per_socket : 4
> threads_per_core : 1
> cpu_mhz : 2400
> hw_caps :
> bfebfbff:2c100800:00000000:00003f00:17bee3ff:00000000:00000001:00000000
> virt_caps : hvm hvm_directio
> total_memory : 98168
> free_memory : 128
> sharing_freed_memory : 0
> sharing_used_memory : 0
> outstanding_claims : 0
> free_cpus : 0
> xen_major : 4
> xen_minor : 5
> xen_extra : .0
> xen_version : 4.5.0
> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset : Mon Jan 12 11:30:05 2015 -0500 git:a8ac229
> xen_commandline : placeholder
> cc_compiler : gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
> cc_compile_by : root
> cc_compile_domain : cisco.com <http://cisco.com>
> cc_compile_date : Thu Feb 19 07:26:00 EST 2015
> xend_config_format : 4
> root@<server>:~#
>
> After consulting with xen-users mailer, I was given this response by "Ian":
>
> "Did you install libvirt from source or from packages? If the latter then you
> may have a disconnect between the packaged version and your source-built Xen.
> You'll probably need to rebuild libvirt against your Xen libraries."
>
> What are the virt-related steps to take to test out Ian's idea? I have root
> access to one machine that serves both as a host to VM's as well as a build
> environment for source builds such as this. I already built xen 4.5.0 and
> installed it. Do I now need to separately download and build libvirt, then
> download and build virt-manager? Is it important to place the virt* code
> within the xen source tree, or do something else so that the virt* code
> compiles "against" an appropriate xen environment?
>
> In summary, I would like some guidance on how to build libvirt, and if needed,
> virt-manager, source against a specific Xen version.
>
Distro packages of virt-manager should work fine, once you get libvirt building.
I recommend you download the ubuntu .deb config files for libxl, and
rebuild+install libxl with the exact same build flags your distro packages
use. They've already figured out the necessary flags to make things work
together with the other distro packages. Then do the same with libvirt.
- Cole
10 years
[libvirt-users] Broken OS when booting rootfs from 9p share
by Olivier Mauras
Hello,
I've been trying to boot a VM with the rootfs being a 9P
share from the host. The VM OS is centos 7.
The OS boots but no services
can work and it appears that the authentication system is broken.
Now
the funny thing is that booting the same OS on the same 9P share
manually with Qemu works as expected with a fully functionnal OS... So
I'm wondering what could libvirt do that render the OS on the share
broken - Something with rights ?
Selinux is disabled on the host, and
accessmode to the share is set to passthrough in both cases.
Here's my
working Qemu line:
qemu -kernel
/srv/overlay/kernels/grsec-3.14.33-101/vmlinuz-3.14.33-101.el6.x86_64
-initrd
/srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img
-fsdev
local,id=r,path=/srv/overlay/run/irc,security_model=passthrough
-device virtio-9p-pci,fsdev=r,mount_tag=root
-nographic
-m 256M
-machine pc-i440fx-2.1,accel=kvm
-netdev tap,id=net0 -device
virtio-net,netdev=net0,mac=52:54:00:12:36:34
-smp 1,sockets=1,cores=1
-append 'root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro
rootfstype=9p console=ttyS0'
And here my libvirt VM config:
<domain
type='kvm'>
<name>irc</name>
<uuid>ffbd32eb-a693-eadd-8923-18de80137472</uuid>
<memory
unit='KiB'>262144</memory>
<currentMemory
unit='KiB'>262144</currentMemory>
<vcpu placement='static'>1</vcpu>
<os>
<type arch='x86_64' machine='pc-i440fx-2.1'>hvm</type>
<kernel>/srv/overlay/kernels/grsec-3.14.33-101/vmlinuz-3.14.33-101.el6.x86_64</kernel>
<initrd>/srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img</initrd>
<cmdline>root=virtfs:root rootflags=trans=virtio,version=9p2000.u ro
rootfstype=9p</cmdline>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<controller type='usb'
index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01'
function='0x2'/>
</controller>
<controller type='pci' index='0'
model='pci-root'/>
<filesystem type='mount' accessmode='passthrough'>
<source dir='/srv/overlay/run/irc'/>
<target dir='root'/>
<address
type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</filesystem>
<interface type='bridge'>
<mac
address='52:54:00:00:36:34'/>
<source bridge='br0'/>
<model
type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x03' function='0x0'/>
</interface>
<serial type='pty'>
<target
port='0'/>
</serial>
<console type='pty'>
<target type='serial'
port='0'/>
</console>
<input type='mouse' bus='ps2'/>
<input
type='keyboard' bus='ps2'/>
<graphics type='vnc' port='-1'
autoport='yes'/>
<video>
<model type='cirrus' vram='9216' heads='1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02'
function='0x0'/>
</video>
<memballoon model='virtio'>
<address
type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</memballoon>
</devices>
</domain>
My libvirt version is 1.2.9, and
qemu is 2.1.2.
Thanks for your help,
Olivier
10 years, 1 month
[libvirt-users] simple network and firewalld errors
by lejeczek
hi everybody
I have a simple network:
<network>
<name>default</name>
<uuid>1e71fa47-4893-4435-8b60-575d2b51c231</uuid>
<forward mode='nat'>
<nat>
<port start='1024' end='65535'/>
</nat>
</forward>
<bridge name='virbr0' stp='on' delay='0' />
<mac address='52:54:00:58:47:4b'/>
<ip address='192.168.4.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.4.2' end='192.168.4.254' />
</dhcp>
</ip>
</network
and I wonder what might be wrong, I get many errors in
firewalld when I restart libvirtd
Main PID: 13194 (firewalld)
CGroup: /system.slice/firewalld.service
└─13194 /usr/bin/python -Es /usr/sbin/firewalld
--nofork --nopid
2015-03-01 17:12:46 ERROR: COMMAND_FAILED: '/sbin/iptables
--table filter --delete FORWARD --out-interface virbr0
--jump REJECT' failed: iptables: No chain/target/match by
that name.
2015-03-01 17:12:46 ERROR: COMMAND_FAILED: '/sbin/iptables
--table filter --delete FORWARD --in-interface virbr0 --jump
REJECT' failed: iptables: No chain/target/match by that name.
2015-03-01 17:12:47 ERROR: COMMAND_FAILED: '/sbin/iptables
--table filter --delete INPUT --in-interface virbr0
--protocol udp --destination-port 53 --jump ACCEPT' failed:
iptables: Bad rule (does a matching rule exist in that chain?).
2015-03-01 17:12:47 ERROR: COMMAND_FAILED: '/sbin/iptables
--table filter --delete INPUT --in-interface virbr0
--protocol tcp --destination-port 53 --jump ACCEPT' failed:
iptables: Bad rule (does a matching rule exist in that chain?).
2015-03-01 17:12:47 ERROR: COMMAND_FAILED: '/sbin/iptables
--table mangle --delete POSTROUTING --out-interface virbr0
--protocol udp --destination-port 68 --jump CHECKSUM
--checksum-fill' failed: iptables: No chain/target/match by
that name.
2015-03-01 17:12:48 ERROR: COMMAND_FAILED: '/sbin/iptables
--table filter --delete INPUT --in-interface virbr0
--protocol udp --destination-port 67 --jump ACCEPT' failed:
iptables: Bad rule (does a matching rule exist in that chain?).
2015-03-01 17:12:48 ERROR: COMMAND_FAILED: '/sbin/iptables
--table filter --delete INPUT --in-interface virbr0
--protocol tcp --destination-port 67 --jump ACCEPT' failed:
iptables: Bad rule (does a matching rule exist in that chain?).
2015-03-01 17:36:03 ERROR: NOT_ENABLED
2015-03-01 17:36:04 ERROR: NOT_ENABLED
2015-03-01 18:19:35 ERROR: NOT_ENABLED
grateful for all suggestions
thanks
10 years, 1 month
