- Users - libvirt List Archives

[libvirt-users] SAS HBA address and SCSI passthrough
by Corinna Vinschen 12 Dec '13

12 Dec '13

Hi, For some time now (starting with the 3.10 or 3.11 kernels, but I'm not sure) I have the following problem: I have a machine with 6 SATA slots and two SAS controllers, one onboard HBA and one RAID controller in a PCIe slot. The problem is that the order of the SAS controllers changes randomly after a reboot, so the SCSI addresses of the devices change. One time lsscsi prints (empty lines and ellipsis added for clarity): $ lsscsi [0:0:0:0] disk ATA INTEL SSDSC2BA20 5DV1 /dev/sda [6:0:0:0] disk SmrtStor TXA2D20200GA6001 KT00 /dev/sdb [...] [6:0:7:0] tape TANDBERG LTO-4 HH U619 /dev/st0 [6:0:8:0] enclosu Intel RES2SV240 0d00 - [7:0:0:0] disk LSI 9750-8i DISK 5.12 /dev/sdh [7:0:2:0] disk LSI 9750-8i DISK 5.12 /dev/sdi After the next reboot it looks like this: $ lsscsi [0:0:0:0] disk ATA INTEL SSDSC2BA20 5DV1 /dev/sda [6:0:0:0] disk LSI 9750-8i DISK 5.12 /dev/sdb [6:0:2:0] disk LSI 9750-8i DISK 5.12 /dev/sdc [8:0:0:0] disk SmrtStor TXA2D20200GA6001 KT00 /dev/sdd [...] [8:0:7:0] tape TANDBERG LTO-4 HH U619 /dev/st0 [8:0:8:0] enclosu Intel RES2SV240 0d00 - That's really a problem. One of them, not so much a libvirt problem, is the fact that existing command line tools to maintain HBAs and RAID controllers access controller and devices via the host address. The other problem is with libvirt. If you want to access an arbitrary SAS device from a VM, you have to specify the address of the device as SCSI address. Consider this case in a VM xml file to attach to the host's tape drive: <hostdev mode='subsystem' type='scsi' managed='no' sgio='unfiltered'> <source> <adapter name='scsi_host6'/> <address bus='0' target='7' unit='0'/> </source> </hostdev> With the current behaviour of the kernel, this will be broken in all setups with multiple controllers. If the host adapter address changes arbitrarily after a reboot, the VM will have a broken link to the SCSI device. In the worst case, it will access another device connected to another controller and data on that other device may be destroyed. I asked elsewhere how to fix the order of the SAS controllers, but the only information I got was that it's apparently a deliberate choice to initialize HW in parallel, because the OS doesn't care for the order, and thus, the host address of the controllers. Sure, I can create a wrapper script and systemd foo to workaround this issue by creating the xml file content on the fly after a reboot, but, honestly, that can't be a *solution* for this behaviour. As far as I can see, it's kind of impossible to stick to the SCSI address for SCSI devices in the VM XML description. If the VM setup should survive a reboot in a multi-HBA environment, it's necessary to use unambiguous OS device names, like the udev entries under /dev/disk and /dev/tape(*). Is that already possible, or is there some work in progress? Or *is* there some way to make sure that the SAS controllers always have the same host bus address after reboot so libvirt doesn't get into trouble? Thanks, Corinna (*) But then again, assuming I want to import the enclosure at SCSI address [X:0:8:0] into a VM? /dev/sg9? But, no, this isn't unambiguous either. So... what? -- Corinna Vinschen Cygwin Maintainer Red Hat

1 0

[libvirt-users] internal error: unexcepted domain type lxc, excepted one of these: qemu, kqemu, kvm, xen
by Florian Klink 12 Dec '13

12 Dec '13

Hi, I'm not able to create lxc domains anymore with libvirt 1.2.0-1. The current arch linux package is affected by this bug: https://bugs.archlinux.org/task/38007) vm.xml: <domain type="lxc"> <name>test</name> <memory unit="GiB">2</memory> <os> <type>exe</type> <init>/sbin/init</init> </os> <devices> <filesystem type="mount"> <source dir="/var/lib/libvirt/filesysystems/test"/> <target dir="/"/> </filesystem> <interface type="network"> <source network="default"/> </interface> <console type="pty"/> </devices> </domain> # virsh create vm.xml error: Failed to create domain from vm.xml error: internal error: unexcepted domain type lxc, excepted one of these: qemu, kqemu, kvm, xen However, ./configure reports that LXC support is compiled in: configure: Drivers configure: configure: Xen: no configure: QEMU: yes configure: UML: yes configure: OpenVZ: yes configure: VMware: yes configure: VBox: yes configure: XenAPI: no configure: xenlight: no configure: LXC: yes configure: PHYP: yes configure: ESX: yes configure: Hyper-V: no configure: Parallels: no configure: Test: yes configure: Remote: yes configure: Network: yes configure: Libvirtd: yes configure: Interface: yes configure: macvtap: yes configure: virtport: yes configure: configure: Storage Drivers configure: configure: Dir: yes configure: FS: yes configure: NetFS: yes configure: LVM: yes configure: iSCSI: no configure: SCSI: yes configure: mpath: yes configure: Disk: yes configure: RBD: no configure: Sheepdog: no configure: Gluster: no Do you have any idea why it does not work anymore? I don't see any new changes in src/conf/domain_conf.c where the error is thrown (line 10960) on current git HEAD... Florian

2 2

[libvirt-users] guest daemon reading kvmclock - is it not needed or bad idea ?
by Edoardo Comar 11 Dec '13

11 Dec '13

Hi (apologies for the previous post in html - was scrubbed in the list digest) I've dug various posts and articles on host-guest time synchronization. I could not conclude why it might be better to use ntpd in a guest rather than a daemon that reads from kvmclock and having NTP running on the host only (assuming the guest OS is a recent linux and so the clock source is set to the paravirtualized kvm PVclock). any clarifications are welcome, thanks! Edoardo Comar Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

1 0

[libvirt-users] guest daemon reading kvmclock - not needed/ bad idea ?
by Edoardo Comar 11 Dec '13

11 Dec '13

1 0

[libvirt-users] assign static public IP to container
by scar 11 Dec '13

11 Dec '13

hello i have a server colocated in a datacenter with several external IP addresses available to use. the physical server is using one of these IPs, and i want to assign another, unused IP to the virtual machine. both the host and guest are running ubuntu server 12.04. i found someone else asking the same thing[1] for CentOS, but i already have a bridge setup so not sure if it pertains... either way the instructions provided are for a different OS. i followed these instructions[2] for setting up my bridge. anyway, i thought i could just do this by editing the container's /etc/network/interfaces, setting a static IP address for eth0 much like i did for br0 on the host machine.... but doesn't seem to be working. ifconfig shows eth0 has the public address but i can't resolve any hostnames nor telnet to a direct IP address (no route to host). if i change back to dhcp and let eth0 get a private address, i can at least access the internet but cannot access the virtual machine from the internet. what is the trick to giving a VM a routable, public IP address? thanks 1. https://www.redhat.com/archives/libvirt-users/2011-December/msg00056.html 2. https://help.ubuntu.com/12.04/serverguide/network-configuration.html#bridgi…

2 5

[libvirt-users] Determine ongoing shutdown via libvirt or preventing migrations to host
by Ondřej Kunc 10 Dec '13

10 Dec '13

Hi list, Is there any function in libvirt to determine runlevel of host or any possibility to prevent VM migrations to that host ? I'm developing simple cluster of 4 servers running KVM VMs. For management I decided to use python-libvirt. It is working in that way, that every VM is diskless and booting via PXE so I can run it on every host server. Every VM has assigned one host as monitor which is responsible to periodically check, that VM is running on one of other hosts. If it don't run, it will be started on first available server assigned for that VM. When one of hosts is shut down, it will migrate all VMs to another hosts, but that monitor which checks VMs will migrate it after reboot. But I have race condition there that monitors can check that host is running before it is shutdown and will migrate VM's back to server which will reboot. Thank you for any help -- Ondřej Kunc, Senior Linux Administrator IGNUM s.r.o., Vinohradská 190, Praha 3, 130 61, CZE Mobil: +420 603 111 111 | Fax: +420 296 332 222 www.ignum.cz | www.domena.cz | www.webcloud.cz

2 3

Re: [libvirt-users] gentoo linux, problem starting vm´s when cache=none
by Daniel P. Berrange 10 Dec '13

10 Dec '13

On Tue, Dec 10, 2013 at 03:21:59PM +0100, Marko Weber | ZBF wrote: > Hello Daniel, > > Am 2013-12-10 11:23, schrieb Daniel P. Berrange: > >On Tue, Dec 10, 2013 at 11:20:35AM +0100, Marko Weber | ZBF wrote: > >> > >>hello mailinglist, > >> > >>on gentoo system with qemu-1.6.1, libvirt 1.1.4, libvirt-glib-0.1.7, > >>virt-manager 0.10.0-r1 > >> > >>when i set on virtual machine "cache=none" in the disk-menu, the > >>machine faults to start with: > >> > >><< > >>Fehler beim Starten der Domain: Interner Fehler: Prozess während der > >>Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64: > >>-drive file=/raid6/virtual/debian-kaspersky.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native: > >>could not open disk image /raid6/virtual/debian-kaspersky.img: > >>Invalid argument > >> > >> > >>Traceback (most recent call last): > >> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 100, > >>in cb_wrapper > >> callback(asyncjob, *args, **kwargs) > >> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 122, > >>in tmpcb > >> callback(*args, **kwargs) > >> File "/usr/share/virt-manager/virtManager/domain.py", line 1210, > >>in startup > >> self._backend.create() > >> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 708, in > >>create > >> if ret == -1: raise libvirtError ('virDomainCreate() failed', > >>dom=self) > >>libvirtError: Interner Fehler: Prozess während der > >>Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64: > >>-drive file=/raid6/virtual/debian-kaspersky.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native: > >>could not open disk image /raid6/virtual/debian-kaspersky.img: > >>Invalid argument > >>>> > >> > >>when i switch back to cache=default, the machine start like a charm. > >> > >>any ideas why? i cant find anything in logs, only this "invalid > >>argument". > > > >cache=none uses O_DIRECT flag. if you get "Invalid argument" it usually > >means that your filesystem is bad and does not support O_DIRECT > > i use vanilla-kernel 3.10.23 and xfs on the partition where the vm > .img is lying. > > the mount options i use: /raid6 type xfs > (rw,noatime,nodiratime,largeio,nobarrier,logbsize=256k) > > any wrong here? XFS should support O_DIRECT, but possibly one of the mount option is causing trouble. I don't know enough about XFS to answer for sure. BTW, please keep your replies on the mailing list... Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|

1 0

[libvirt-users] gentoo linux, problem starting vm´s when cache=none
by Marko Weber | ZBF 10 Dec '13

10 Dec '13

hello mailinglist, on gentoo system with qemu-1.6.1, libvirt 1.1.4, libvirt-glib-0.1.7, virt-manager 0.10.0-r1 when i set on virtual machine "cache=none" in the disk-menu, the machine faults to start with: << Fehler beim Starten der Domain: Interner Fehler: Prozess während der Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64: -drive file=/raid6/virtual/debian-kaspersky.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native: could not open disk image /raid6/virtual/debian-kaspersky.img: Invalid argument Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 100, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 122, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1210, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 708, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: Interner Fehler: Prozess während der Verbindungsaufnahme zum Monitor beendet :qemu-system-x86_64: -drive file=/raid6/virtual/debian-kaspersky.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native: could not open disk image /raid6/virtual/debian-kaspersky.img: Invalid argument >> when i switch back to cache=default, the machine start like a charm. any ideas why? i cant find anything in logs, only this "invalid argument". the machine is created with profile "linux / debian squeeze" cause its a debian 6 marko

2 1

[libvirt-users] ANNOUNCE: ruby-libvirt 0.5.0
by Chris Lalancette 10 Dec '13

10 Dec '13

All, I'm pleased to announce the release of ruby-libvirt 0.5.0. ruby-libvirt is a ruby wrapper around the libvirt API. Version 0.5.0 brings new APIs, more documentation, and bugfixes: * Updated Network class, implementing almost all libvirt APIs * Updated Domain class, implementing almost all libvirt APIs * Updated Connection class, implementing almost all libvirt APIs * Updated DomainSnapshot class, implementing almost all libvirt APIs * Updated NodeDevice class, implementing almost all libvirt APIs * Updated Storage class, implementing almost all libvirt APIs * Add constants for almost all libvirt defines * Improved performance in the library by using alloca Version 0.5.0 is available from http://libvirt.org/ruby: Tarball: http://libvirt.org/ruby/download/ruby-libvirt-0.5.0.tgz Gem: http://libvirt.org/ruby/download/ruby-libvirt-0.5.0.gem It is also available from rubygems.org; to get the latest version, run: $ gem install ruby-libvirt As usual, if you run into questions, problems, or bugs, please feel free to mail me (clalancette(a)gmail.com) and/or the libvirt mailing list. Thanks to everyone who contributed patches and submitted bugs. Chris Lalancette

1 0

[libvirt-users] Question about setns recognising in libvirt autoconf
by hzguanqiang＠corp.netease.com 09 Dec '13

09 Dec '13

Hi experts, When I test lxc container with lxc-enter-namespace command, It reported an error as following: root@debian:~/github/libvirt# vir lxc-enter-namespace lxc --noseclabel /bin/df -hl error: Cannot get namespaces for 3145: Function not implemented It seems that setns is not supported by my kernel. But from the following info, It seemed the reason is just libvirt/autoconf doesn't recgonise setns. root@debian:~/github/libvirt# grep setns /proc/kallsyms ffffffff8105b78b T SyS_setns ffffffff8105b78b T sys_setns root@debian:~/github/libvirt# ./configure | grep setns checking for setns... no What the problem really is ? How can I fix this problem? Thanks~ ------------------ Best regards! GuanQiang 2013-12-09

2 4