- Users - libvirt List Archives

[libvirt-users] Creating a static Virtio-Serial 'Port'
by Matthew Harrold 02 Feb '14

02 Feb '14

Hi all, I'm having some problems getting Virtio-Serial running as I'd like. I have 10x USB <-> Serial adapters plugged into my VM Host / Hypervisor, acting as a console server. These are currently operated by the VM Host itself, but I would like to move them to a guest. I have used ISA-Serial but it's limited to 4 'ports' per guest. I've setup Virtio-Serial for the guest and it works, I can pass info via serial from the Host to Guest. I'd like to use socat to link the physical USB serial TTY's and the guest serial 'ports' in /dev/pts. This is works fine and the guest can communicate with the Serial <-> USB adapter, however the Guest serial 'ports' are in /dev/pts and they are assigned a number dynamically when the VM is started, so I can't automate socat to run at boot. Is it possible to assign static PTY's in the host, to the Guest? Or, if this needs to be scripted, is there a command I can run to find out which PTY it's on without parsing the XML from a dump? Thanks.

1 0

[libvirt-users] Libvirt Error Creating VMs for Nimbus Cloud
by Joshua McKee 01 Feb '14

01 Feb '14

Hello, I am having an issue with libvirt in my Nimbus cloud setup. When I use the Nimbus VM creation test scripts on a VMM node (using libvirt), the VM is created without a problem. However, when I attempt to create a new VM using Nimbus (which then tries to create the VM on the VMM node), I encounter the following error: --------------------------------------------------------------------------------------------------------------------------------------------- $ ./nimbus-cloud-client-022/bin/cloud-client.sh --run --name testimage --hours 1 Launching workspace. Workspace Factory Service: https://yellow:8443/wsrf/services/WorkspaceFactoryService Creating workspace "vm-035"... done. IP address: 172.29.99.20 Hostname: pub02 Start time: Fri Jan 31 13:48:57 MST 2014 Shutdown time: Fri Jan 31 14:48:57 MST 2014 Termination time: Fri Jan 31 14:50:57 MST 2014 Waiting for updates. Problem with vm-035: Unexpected issue STDERR: 2014-01-31 13:48:44,412 - WARNING - no qemu_img configuration, copy-on-write support is disabled libvir: QEMU error : Domain not found: no domain with matching name 'wrksp-33' libvir: error : An error occurred, but the cause is unknown 2014-01-31 13:48:45,587 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown 2014-01-31 13:48:45,587 - ERROR - An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/defaults/lvrt/lvrt_common.py", line 123, in create newvm = self._vmm().createXML(xml, 0) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 2189, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: An error occurred, but the cause is unknown 2014-01-31 13:48:45,589 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 155, in _common_withnetsecurity _common_withtmplease(nic_set, kernel, local_file_set, c, netsecurity, platform, justprint) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 174, in _common_withtmplease platform.create(local_file_set, nic_set, kernel) File "/opt/nimbus/src/python/workspacecontrol/defaults/lvrt/lvrt_common.py", line 128, in create raise UnexpectedError(shorterr) UnexpectedError: Problem creating the VM: An error occurred, but the cause is unknown 2014-01-31 13:48:45,589 - ERROR - Creation problem: going to back out tmp space lease 2014-01-31 13:48:45,589 - ERROR - Backed out tmp space lease 2014-01-31 13:48:45,589 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 137, in _common_withnetbootstrap _common_withnetsecurity(vm_name, nic_set, kernel, local_file_set, p, c, netsecurity, platform, justprint) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 164, in _common_withnetsecurity raise e UnexpectedError: Problem creating the VM: An error occurred, but the cause is unknown 2014-01-31 13:48:45,589 - ERROR - Creation problem: going to back out net security 2014-01-31 13:48:45,606 - ERROR - Backed out net security 2014-01-31 13:48:45,606 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 119, in _common_withnics _common_withnetbootstrap(vm_name, nic_set, kernel, local_file_set, p, c, netsecurity, platform, justprint) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 146, in _common_withnetbootstrap raise e UnexpectedError: Problem creating the VM: An error occurred, but the cause is unknown 2014-01-31 13:48:45,607 - ERROR - Creation problem: going to back out net bootstrap 2014-01-31 13:48:45,607 - ERROR - Backed out net bootstrap 2014-01-31 13:48:45,607 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 96, in _common _common_withnics(vm_name, nic_set, kernel, local_file_set, p, c, localnet, netbootstrap, netsecurity, platform, justprint) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 128, in _common_withnics raise e UnexpectedError: Problem creating the VM: An error occurred, but the cause is unknown 2014-01-31 13:48:45,607 - ERROR - Creation problem: going to back out net leases 2014-01-31 13:48:45,607 - ERROR - Backed out net leases 2014-01-31 13:48:45,608 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/main/wc_core.py", line 79, in core _core(vm_name, action, p, c) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core.py", line 168, in _core wc_core_creation.create(vm_name, p, c, async, editing, images, kernels, localnet, netbootstrap, netlease, netsecurity, persistence, platform) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 16, in create _create_local(vm_name, p, c, async, editing, images, kernels, localnet, netbootstrap, netlease, netsecurity, persistence, platform) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 31, in _create_local _common(local_file_set, vm_name, p, c, editing, kernels, localnet, netbootstrap, netlease, netsecurity, persistence, platform, justprint=justprint) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 107, in _common raise e UnexpectedError: Problem creating the VM: An error occurred, but the cause is unknown Problem executing: Problem creating the VM: An error occurred, but the cause is unknown Exiting with error code: 4 Workspace "vm-035" did NOT reach target state "Running" Problem running 'vm-035'. --------------------------------------------------------------------------------------------------------------------------------------------- I checked /var/log/libvirtd.log, and found the following: --------------------------------------------------------------------------------------------------------------------------------------------- 2014-01-31 20:48:39.311+0000: 2888: info : libvirt version: 0.9.8 2014-01-31 20:48:39.311+0000: 2888: error : virNetSocketReadWire:1006 : End of file while reading data: Input/output error --------------------------------------------------------------------------------------------------------------------------------------------- I don't know if this is relevant, but I also noticed this warning when creating the VM through the test scripts mentioned above: --------------------------------------------------------------------------------------------------------------------------------------------- 2014-01-31 05:41:44.018+0000: 1351: warning : qemuDomainObjTaint:1134 : Domain id=1 name='control-test' uuid=95f2d398-6b98-5359-7597-b0f596aae996 is tainted: high-privileges --------------------------------------------------------------------------------------------------------------------------------------------- I assumed this was a permissions issue, but I double checked and everything seems in order. I did not have this issue on my previous Nimbus cloud setup. Thanks, Josh

1 1

[libvirt-users] Looks like blockpull does not accept a subset of the entire chain of backing files
by Richard Gomes 01 Feb '14

01 Feb '14

Hello If I'm not terribly mistaken, looks like libvirt 1.2.1 does not provide ability of merging only a subset of the entire chain of backing files. So, if I have a chain like this: root <- a <-b <- c <- d <- active ... and I'd like to obtain a chain like this: root <- c <- d <- active ... looks like it's not supported, since I'm trying the command / //virsh blockpull domain --path /path/to/c --bandwidth 30 --base /path/to/root// (1) / ... but it complains because /--path /path/to/c/ is not recognized, since only /--path /path/to/active/ is acceptable: / //virsh blockpull domain --path /path/to/active --bandwidth 30 --base /path/to/root// (2) / So, command (1) fails but command (2) succeeds. The point is: How could I obtain the results I'm trying to achieve via command (1) ? I'm new to libvirt, but the article below made me think that what I'm trying to do would be possible: http://kashyapc.fedorapeople.org/virt/lc-2012/snapshots-handout.html ( see section on /blockpull/ ) Thoughts? For your information, my environment is: Compiled against library: libvirt 1.2.1 Using library: libvirt 1.2.1 Using API: QEMU 1.2.1 Running hypervisor: QEMU 1.7.0 Running against daemon: 1.2.1 Thanks -- Richard Gomes http://rgomes.info http://www.linkedin.com/in/rgomes mobile: +44(77)9955-6813 inum <http://www.inum.net/>: +883(5100)0800-9804 sip:rgomes@ippi.fr

5 6

[libvirt-users] Dynamically setting permanent memory libvirt-lxc
by mallu mallu 01 Feb '14

01 Feb '14

I'm trying to permanently change memory allocation for a libvirt-lxc domain. So far I tried changing memory in memory.limit_in_bytes under /cgroup/memory/libvirt/lxc/<container>/. This didn't help. It appears that libvirt is not reading changes in cgroup. My requirements are 1) Be able to dynamically change memory of a LXC domain without reboot 2) The memory change must survive LXC domain reboot. Any help would be greatly appreciated

2 5

[libvirt-users] libvirt-sandbox question.
by Christopher Stone 30 Jan '14

30 Jan '14

I hope this question isn't considered too off topic for this list, I am trying to reach the libvirt-sandbox developers, but I could not find a libvirt-sandbox specific mailing list, and it seemed to me that libvirt-sandbox was a part of libvirt itself. I am trying to port libvirt-sandbox to run on a CentOS 6.5 system. This wasn't too hard but, I had to do the following: I have used the CentOS repo addon ElRepo to upgrade the kernel to 3.10.28. CentOS normally runs a 2.6.32 kernel. I upgraded glib2 from 2.36 to 2.38.2. I did this by building 2.38.2 from source and installing it into /usr/local. Thus, the 2.36 version still exists in /lib64 and the normal CentOS applications use this version. I built libvirt 1.2.1 from source and installed it into /usr/local. I used: ./configure --with-lxc --with-selinux --with-secdriver-selinux --prefix=/usr/local I built libvirt-glib 0.1.7 from source and installed it into /usr/local. I used: PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --prefix=/usr/local I build libvirt-sandbox 0.5.1 from source and installed it into /usr/local. I used: PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure As a test, I am able to run the libvirt lxc helloworld example: [root@scwnet1 lxc_helloworld]# virsh -c lxc:/// define helloworld.xml Domain helloworld defined from helloworld.xml [root@scwnet1 lxc_helloworld]# virsh -c lxc:/// start helloworld Domain helloworld started [root@scwnet1 lxc_helloworld]# virsh -c lxc:/// list Id Name State ---------------------------------------------------- 9819 helloworld running [root@scwnet1 lxc_helloworld]# virsh -c lxc:/// console helloworld Connected to domain helloworld Escape character is ^] sh-4.1# exit exit Next, I try to use libvirt-sandbox, and I get the following error: [root@scwnet1 tests]# /usr/local/bin/virt-sandbox -c lxc:/// /bin/sh Unable to start sandbox: Failed to create domain: unsupported configuration: Unable to find security driver for label selinux My libvirt config.log shows the SELinux security driver as yes: configure:71172: Configuration summary configure:71174: ===================== configure:71176: configure:71178: Drivers configure:71180: configure:71182: Xen: no configure:71184: QEMU: yes configure:71186: UML: yes configure:71188: OpenVZ: yes configure:71190: VMware: yes configure:71192: VBox: yes configure:71194: XenAPI: no configure:71196: xenlight: no configure:71198: LXC: yes configure:71200: PHYP: no configure:71202: ESX: yes configure:71204: Hyper-V: no configure:71206: Parallels: yes configure:71208: Test: yes configure:71210: Remote: yes configure:71212: Network: yes configure:71214: Libvirtd: yes configure:71216: Interface: yes configure:71218: macvtap: yes configure:71220: virtport: yes configure:71222: configure:71224: Storage Drivers configure:71226: configure:71228: Dir: yes configure:71230: FS: yes configure:71232: NetFS: yes configure:71234: LVM: yes configure:71236: iSCSI: yes configure:71238: SCSI: yes configure:71240: mpath: yes configure:71242: Disk: yes configure:71244: RBD: no configure:71246: Sheepdog: no configure:71248: Gluster: no configure:71250: configure:71252: Security Drivers configure:71254: configure:71256: SELinux: yes (/sys/fs/selinux) configure:71258: AppArmor: no (install profiles: no) configure:71260: configure:71262: Driver Loadable Modules configure:71264: configure:71267: dlopen: -ldl configure:71273: configure:71275: Libraries configure:71277: configure:71296: apparmor: no configure:71326: attr: yes (CFLAGS='' LIBS='-lattr') configure:71356: audit: yes (CFLAGS='' LIBS='-laudit') configure:71386: avahi: yes (CFLAGS='-D_REENTRANT ' LIBS='-lavahi-common -lavahi-client ') configure:71416: blkid: yes (CFLAGS='-I/usr/include/blkid -I/usr/include/uuid ' LIBS='-lblkid ') configure:71446: capng: yes (CFLAGS='' LIBS='-lcap-ng') configure:71476: curl: yes (CFLAGS='-DCURL_DISABLE_TYPECHECK ' LIBS='-lcurl ') configure:71506: dbus: no configure:71536: fuse: no configure:71566: glusterfs: no configure:71596: hal: no configure:71626: netcf: yes (CFLAGS=' ' LIBS='-lnetcf ') configure:71656: numactl: yes (CFLAGS='' LIBS='-lnuma') configure:71686: openwsman: no configure:71716: pciaccess: yes (CFLAGS=' ' LIBS='-lpciaccess ') configure:71746: readline: yes (CFLAGS='' LIBS='-lreadline') configure:71776: sanlock: yes (CFLAGS='' LIBS='-lsanlock_client') configure:71806: sasl: yes (CFLAGS='' LIBS='-lsasl2') configure:71836: selinux: yes (CFLAGS='' LIBS='-lselinux') configure:71866: ssh2: no configure:71897: udev: yes (CFLAGS=' ' LIBS='-ludev ') configure:71927: yajl: yes (CFLAGS='' LIBS='-lyajl') configure:71940: libxml: -I/usr/include/libxml2 -lxml2 configure:71942: dlopen: -ldl configure:71948: openwsman: no configure:71952: gnutls: -DGCRYPT_NO_DEPRECATED -lgnutls -lgcrypt configure:71958: firewalld: no configure:71965: polkit: /usr/bin/pkcheck (version 1) configure:71976: xen: no configure:71983: xenapi: no configure:71990: xenlight: no configure:71994: pcap: -lpcap configure:72001: nl: -lnl configure:72011: mscom: no configure:72015: xdr: configure:72025: rbd: no configure:72029: configure:72031: Test suite configure:72033: configure:72035: Coverage: no configure:72037: Alloc OOM: no configure:72039: configure:72041: Miscellaneous configure:72043: configure:72045: Debug: yes configure:72047: Use -Werror: no My libvirt capabilites shows this: [root@scwnet1 tests]# virsh -c lxc:/// capabilities <capabilities> <host> <uuid>20b4e77c-3fb8-dc11-968d-c8600070189e</uuid> <cpu> <arch>x86_64</arch> </cpu> <power_management> <suspend_mem/> <suspend_disk/> </power_management> <topology> <cells num='1'> <cell id='0'> <memory unit='KiB'>8334880</memory> <cpus num='4'> <cpu id='0' socket_id='0' core_id='0' siblings='0-1'/> <cpu id='1' socket_id='0' core_id='1' siblings='0-1'/> <cpu id='2' socket_id='0' core_id='2' siblings='2-3'/> <cpu id='3' socket_id='0' core_id='3' siblings='2-3'/> </cpus> </cell> </cells> </topology> <secmodel> <model>none</model> <doi>0</doi> </secmodel> </host> <guest> <os_type>exe</os_type> <arch name='x86_64'> <wordsize>64</wordsize> <emulator>/usr/local/libexec/libvirt_lxc</emulator> <domain type='lxc'> </domain> </arch> </guest> <guest> <os_type>exe</os_type> <arch name='i686'> <wordsize>32</wordsize> <emulator>/usr/local/libexec/libvirt_lxc</emulator> <domain type='lxc'> </domain> </arch> </guest> </capabilities> I am not sure if secmodel none is the problem. Can someone give me some direction on how to fix this? Cheers, Chris.

2 1

[libvirt-users] dropping capabilities in lxc containers
by Thierry Parmentelat 30 Jan '14

30 Jan '14

Hi there I’m not quite proficient with libvirt yet, and have been using it so far primarily to manage lxc containers I was hoping to find a means to configure the set of capabilities that guests should drop, but came across a few web pages suggesting these were set in stone in the code is this correct, or is there a means to tweak this set from the host via the xml config or a virsh command ? any hint / pointer to documentation in this respect would be most appreciated — Thierry

2 3

[libvirt-users] Libvirt-LXC + systemd + user namespace
by Jan Olszak 29 Jan '14

29 Jan '14

Hi there! I am trying to turn on user namespace by adding following lines to the config: <idmap> <uid start='0' target='0' count='100000'/> <gid start='0' target='0' count='100000'/> </idmap> As you can see the root in container is mapped to the root outside. I was expected to see no difference after adding this lines, but unfortunately there are some (see details below). Am I missing something or is there a problem with system, libvirt or kernel? Full libvirt config: <domain type='lxc'> <name>test_with_idmap</name> <memory>102400</memory> <os> <type>exe</type> <init>/usr/lib/systemd/systemd</init> </os> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <idmap> <uid start='0' target='0' count='100000'/> <gid start='0' target='0' count='100000'/> </idmap> <devices> <console type='pty'/> <filesystem type='mount'> <source dir='/guest'/> <target dir='/'/> </filesystem> </devices> </domain> root:~> uname -a Linux localhost 3.10.19-01077-g4a19d28-dirty #5 SMP PREEMPT Mon Jan 13 12:56:09 CET 2014 armv7l GNU/Linux root:~> libvirtd --version libvirtd (libvirt) 1.2.1 root:~> systemd --version systemd 204 After adding idmap to config systemd can't start many of its services, in particular: Failed to mount Debug File System. Failed to mount Configuration File System. Failed to mount FUSE Control File System. Failed to start udev Kernel Device Manager. Failed to start Remount Root and Kernel File Systems. Failed to start Journal Service. systemctl status says: ExecMount=/bin/mount debugfs /sys/kernel/debug -t debugfs (code=exited, status=32) ExecMount=/bin/mount configfs /sys/kernel/config -t configfs (code=exited, status=32) ExecMount=/bin/mount fusectl /sys/fs/fuse/connections -t fusectl (code=exited, status=32) ExecStart=/usr/lib/systemd/systemd-udevd (code=exited,status=206/OOM_ADJUST) ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited,status=1/FAILURE) ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=218/CAPABILITIES) Thanks!

3 3

Re: [libvirt-users] How to find domain os type and ip address
by Rathidevi 29 Jan '14

29 Jan '14

Hi All, I am using the libvirt-0.5.1.jar and downloaded from this link ftp://libvirt.org/libvirt/java. 1) To find the os type of domain I use this method getOSType(). But it returns the kvm or hvm instead of windows and linux. Is the any way to find the original os type of domain? 2) Please give is there any option or method available to find the ipaddress of domain? Thanks & Regards Rathidevi

2 1

[libvirt-users] Does libvirt support attach volume to linux container now?
by Du Jun 29 Jan '14

29 Jan '14

Hi all, I am playing with linux container and using libvirt to manage linux container. I find I fail to attach volume to linux container via libvirt and I got the following error message: Failed to attach volume: data-111 to VM: lxc-111; org.libvirt.LibvirtException: unsupported configuration: Can't setup disk for non-block device. My question is that does libvirt support attaching volume to linux container? If it supports, what version should I use? Thanks, DuJun

1 0

[libvirt-users] Problems with pmsuspend/wakeup
by Alex 27 Jan '14

27 Jan '14

Hi, I've migrated a Windows7 vm from F17 to F20 and it appears to be working okay. Apparently when it's left idle for some period, it automatically goes into a pmsuspend state, and I'm unable to wake it. I've figured out the virsh dompmwakeup command, which then virsh shows it's running, but the vm is still unresponsive. It doesn't respond to ping and the display is just black when accessing it through virt-manager. Is there something I need to do in the guest for it to wake up properly? How can I just prevent it from ever suspending in the first place? Thanks, Alex

1 0