- Users - libvirt List Archives

[libvirt-users] Understanding and converting between type='drive' and type='pci'
by Leroy Tennison 02 Dec '16

02 Dec '16

First, if this isn't the right list please tell me where i should post. I've searched for an explanation and I'm either searching for the wrong thing or it's not there. I'm trying to get an understanding of the "controller='0' bus='0' target='0' unit='0' " parameters for 'drive' compared to the "domain='0x0000' bus='0x00' slot='0x05' function='0x0' " parameters for 'pci'. It appears that 'dev hda' to 'dev hdd' is the maximum associated with 'drive', how many are available with 'pci' and what are the valid ranges for those parameters? If I have an xml using 'drive' and want to convert it to 'pci' what do I need to do? I've had trouble with this when moving disk images between hypervisors but have never had the time to investigate fully, does it have to do with how the drives are referenced (/dev/disk/by0id or /dev/[h|s|v]da as opposed to UUID)? Thanks for your help.

2 1

[libvirt-users] sudo user to access xen server remotely.
by ganesh kg 29 Nov '16

29 Nov '16

HI, i am trying to use sudo user to access xen server remotely. As its documented, libvirtd can be accessed only through root user or users from libvirtd usergroup. is there any tweak or possibility to access libvirt remotely through sudo user? or by using certificate? code snippet: #!/usr/bin/env python import sys import libvirt conn = libvirt.open('xen+ssh://sudo_user@xen_server') <== Trying to establish connection to the remote xen using sudo user. if conn == None: print('Failed to open connection to xen+ssh:xen_server') exit(1) host = conn.getHostname() print('Hostname:'+host) conn.close() exit(0)

1 0

[libvirt-users] Routed mode problem with SSH
by Marcelo Palma 27 Nov '16

27 Nov '16

Hi guys, I describe the context of the problem below: I installed a Tor relay on a virtual machine on my server with IP 9.1.1.101. This virtual machine needs to use a static IP (9.1.1.102) to work as a Tor relay. After that I create a virtual network in *Routed mode* to connect to the physical network (used as a bridge between the virtual machine and the external network (Internet)). Since I change the NAT to Routed mode, I can't access my server via ssh user(a)9.1.1.101. Will it be a Routed mode problem? How can I solve this problem? Thank you Marcelo

2 1

[libvirt-users] stream finish throws exception via python API
by Shahar Havivi 27 Nov '16

27 Nov '16

Hi, The following snippet works fine e.g. receiving the data but when calling stream.finish() we get the following error: stream = con.newStream() vol.download(stream, 0, 0, 0) buf = stream.recv(1024) stream.finish() libvirt: I/O Stream Utils error : internal error: I/O helper exited abnormally Traceback (most recent call last): File "./helpers/kvm2ovirt", line 149, in <module> download_volume(vol, item[1], diskno, disksitems, pksize) File "./helpers/kvm2ovirt", line 102, in download_volume stream.finish() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 5501, in finish if ret == -1: raise libvirtError ('virStreamFinish() failed') libvirt.libvirtError: internal error: I/O helper exited abnormally Am I doing something wrong? Thank you, Shahar.

5 12

[libvirt-users] locking domain memory
by Dennis Jacobfeuerborn 26 Nov '16

26 Nov '16

Hi, is there a way to lock a guests memory so it doesn't get swapped out? I now there is memoryBacking->locked but that says it requires memtune->hard_limit and the description of that basically "don't ever do this" rendering the locked element kind of pointless. How can I prevent the guests memory from being swapped out without shooting myself in the foot? Regards, Dennis

3 3

[libvirt-users] NUMA VM and assigning interfaces
by Amir Shehata 26 Nov '16

26 Nov '16

Hello, Hope all is well. I've been looking at how I can create a virtual machine which is NUMA capable. I was able to do that by: 140 <qemu:commandline> 143 <qemu:arg value='-numa'/> 144 <qemu:arg value='node'/> 145 <qemu:arg value='-numa'/> 146 <qemu:arg value='node'/> 147 </qemu:commandline> This creates two NUMA nodes. Now I would like to assign my virtual network interfaces, of which I have three, to the different NUMA nodes on the VM. Anyone know how I can do that? Any help/pointers would be much appreciated. I'm trying to create a VM that will enable me to test a NUMA based feature. thanks amir

2 5

[libvirt-users] Fwd: Re: Attach libvirt guest to an existing openvswitch port
by Ivan Borodin 25 Nov '16

25 Nov '16

Thank you, Laine for you time and patience to give me a detailed answer. I missed the interfaceid parameter in the docs, but now I didn't manage to get it working. > http://www.libvirt.org/formatdomain.html The docs state: "The Open vSwitch type virtualport accepts two parameters in its <parameters> element - an interfaceid which is a standard uuid used to uniquely identify this particular interface to Open vSwitch (if you do not specify one, a random interfaceid will be generated for you when you first define the interface[...]" This interfaceid doesn't seem to have anything to do with ovsdb values. $ ovs-vsctl find Port 'name=vm_test' _uuid : f0f06327-6fcc-4073-b8c8-3f42944d43ca bond_downdelay : 0 bond_fake_iface : false bond_mode : [] bond_updelay : 0 external_ids : {} fake_bridge : false interfaces : [eb7fad6e-3728-4bf7-b31e-4a1693e2ec4b] lacp : [] mac : [] name : "vm_test" other_config : {} qos : [] statistics : {} status : {} tag : [] trunks : [] vlan_mode : [] The "_uuid" is ovsdb internal id of a record. If you take "interfaces" value for "interfaceid", libvirt will silently create its own new ovs port, with its own new uuid and defining a libvirt guest's interface with a unique uuid in "interfaceid"... Libvirt will create a new ovs port, and the ovsdb-"interfaces" value will be the interfaceid... And I could not find anything specific about this ovsdb/Port/interfaces. Actually, my point was to find a way to control ovs vlans outside libvirt. Since virsh doesn't have capabilities to edit interface's vlan options, the only way to do it is editing domains' xml-configs through virsh-edit, which is a bit tiresome. (By the way, there must be some technical reason(beyond virt-xml-validate) for designing libvirt writing it's own configuration files instead of reading them...) There should be.. There must be a way to do this. Port parameters are ovs authority. If there is no such way, could you, please, tell me the reason. On 11/21/2016 09:46 PM, Laine Stump wrote: > On 11/13/2016 01:23 PM, Ivan Borodin wrote: >> Somehow with interface types 'bridge' and 'network', libvirt does attach >> domain to the existing port specified in <target dev=''/>, wiping the >> exixting settings and always deletes this port upon domain shutdown, >> thus making me loose ovs configuration.

1 0

[libvirt-users] virt-manager wont connect to remote libvirt instance
by bherman 23 Nov '16

23 Nov '16

I am using virt-manager on debian 8 and I am remotely connecting to a libvirt instance on a server. It was all working fine until today when I discovered that I cannot remotely connect to the libvirt server anymore. ● libvirtd.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Tue 2016-11-22 10:27:09 CST; 46min ago Docs: man:libvirtd(8) http://libvirt.org Process: 27630 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 27823 (libvirtd) CGroup: /system.slice/libvirtd.service ├─ 4787 /usr/sbin/libvirtd ├─ 8187 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --dhcp-script=/usr/lib/libvi... ├─ 8188 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --dhcp-script=/usr/lib/libvi... └─27823 /usr/sbin/libvirtd It says it is running however I cant connect to it either remotely or on the server using virt-manager. When I do a virsh --list It just hangs and doesn't output anything. Any ideas? -- Thanks, Brian Herman IT O: (773)299-7557 F: (773)299-7505

2 2

[libvirt-users] Routed mode problem with SSH
by Marcelo Palma 22 Nov '16

22 Nov '16

Hi guys, I describe the context of the problem below: I installed a Tor relay on a virtual machine on my server with IP 9.1.1.101. This virtual machine needs to use a static IP (9.1.1.102) to work as a Tor relay. After that I create a virtual network in *Routed mode* to connect to the physical network (used as a bridge between the virtual machine and the external network (Internet)). Since I change the NAT to Routed mode, I can't access my server via ssh user(a)9.1.1.101. Will it be a Routed mode problem? How can I solve this problem? Thank you Marcelo

1 0

[libvirt-users] blockcommit and gluster network disk path
by Sahina Bose 22 Nov '16

22 Nov '16

Hi, I'm running into problems with blockcommit and gluster network disks - wanted to check how to pass path for network disks. How's the protocol and host parameters specified? For a backing volume chain as below, executing virsh blockcommit fioo5 vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c --base vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/d4c23ec6-20ce-4a2f-9b32-ca91e65a114a --top vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c --verbose --wait gives "error: invalid argument: No device found for specified path". <disk type='network' device='disk' snapshot='no'> <driver name='qemu' type='qcow2' cache='none' error_policy='stop' io='threads'/> <source protocol='gluster' name='vmstore/912d9062-3881-47 9b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6 d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c'> <host name='10.70.37.28' port='0'/> </source> <backingStore type='network' index='1'> <format type='qcow2'/> <source protocol='gluster' name='vmstore/912d9062-3881-47 9b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6 d8a4/d4c23ec6-20ce-4a2f-9b32-ca91e65a114a'> <host name='10.70.37.28' port='0'/> </source> <backingStore type='network' index='2'> <format type='raw'/> <source protocol='gluster' name='vmstore/912d9062-3881-47 9b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6 d8a4/f5098809-e719-404b-8d80-3f824f4333a2'> <host name='10.70.37.28' port='0'/> </source> <backingStore/> </backingStore> </backingStore> <target dev='vda' bus='virtio'/> <serial>27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4</serial> <boot order='2'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> thanks sahina

1 1