- Users - libvirt List Archives

[libvirt-users] question about libvirt network Xml
by Robert Li (baoli) 24 Oct '14

24 Oct '14

Hi, I’m an openstack developer trying to use Assignment from a pool of SRIOV VFs in a libvirt <network> definition from this link http://wiki.libvirt.org/page/Networking My question is is it possible for nova (the openstack compute) to know which VF out of the pool will be allocated to a VM before it invokes libvirt to launch it? Thanks In advance, Robert

3 3

[libvirt-users] How can a user process be automatically started after the container is started?
by WANG Cheng D 24 Oct '14

24 Oct '14

Dear All, I want to start my application automatically after I start the container with a virsh command " virsh -c lxc:/// start mycontainer" How can I achieve this? Thank you in advance. Cheng

2 3

[libvirt-users] LXC container OS upgrade How?
by mallu mallu 24 Oct '14

24 Oct '14

Can someone tell me how I can upgrade OS on a lxc container? I want to upgrade my containers from centos 6.4 to centos 6.5. I have upgraded the host on which these containers are running on to centos. But want to know how to upgrade the containers. Thank you

2 1

[libvirt-users] Public IP addresses are not logged in VMs
by Roland Giesler 24 Oct '14

24 Oct '14

Anyone that can help me solve this one? I have around 4 VM's on a server and the network is bridged and a /28 public IP range assigned to it . When a client connects to one of the VM's, they all always log the address of the host server, never the client ip address. How can I fix this? Things I have investigated: 1. Switch to routed network. That would not help, since I would firstly need another public IP subnet to route to (the virtual machines). 2. Could have something to do with the libvirt firewall rules, but they are default, I didn't touch them I have read many posts in forums and websites, but none make any mention of this behaviour. Help would really be great!

2 1

[libvirt-users] Libvirt with containers
by Anjali Kulkarni 20 Oct '14

20 Oct '14

Hi, I am trying to define a container using libvirt, and I need to allow access of the device /dev/uio0 on the host on the container as well. That is, I have the following line in the container config file: lxc.mount.entry = /dev/uio0 dev/uio0 none bind,create=file lxc.cgroup.devices.allow = c 249:1 rwm And I want to add it in the libvirt XML file for the container. I tried something like: <filesystem accessmode="passthrough" type="mount"> <source file="/dev/uio0" /> <target dir="/dev/uio0" /> </filesystem> But it gave me error: root# virsh -c lxc:/// define lxc_v.xml error: Failed to define domain from lxc_v.xml error: missing source information for device /dev/uio0 Can someone pls help, how I can add the /dev/uio0 to the xml file? Thanks Anjali

1 0

[libvirt-users] HostDevev SCSI Devices
by Fl＠sh 20 Oct '14

20 Oct '14

http://libvirt.org/formatdomain.html#elementsHostDevSubsys At this description used "drive"-typed address for SCSI. But when i get xml-description of scsi-devices by <code> unsigned int flags = VIR_CONNECT_LIST_NODE_DEVICES_CAP_SCSI_HOST ; int ret = virConnectListAllNodeDevices (currWorkConnect, &nodeDevices, flags); then get by virNodeDeviceGetXMLDesc(nodeDevices[i], 0)); </code> i have same: <device> <name>scsi_host2</name> <path>/sys/devices/pci0000:00/0000:00:1f.2/ata3/host2</path> <parent>pci_0000_00_1f_2</parent> <capability type='scsi_host'> <host>2</host> <unique_id>3</unique_id> </capability> </device> . I understand that this device description contains a "pci"-typed addresses. Then where to get the "scsi"-typed address? -- Fl@sh

2 2

[libvirt-users] drive-backup command permission denied.. and need some clarification
by Jd 16 Oct '14

16 Oct '14

Hi * Trying to get drive-backup command, getting permission denied. :( sudo virsh qemu-monitor-command --hmp my-instance --cmd drive_backup drive-virtio-disk0 /tmp/foo.vda.img Looks like apparmor issue. What can I modify to make this work ? * Couple of other questions drive-backup : * The doc seems to claim that it gives a point in time copy of the drive. So I assume that no need to take any snapshot etc.. and merge back in. * does it internally use snapshot ? Does this hook in to doing fsfreeze and unfreeze using guest agent and does it automagically ? I do not see any options here. * Suppose I have base <-- sn1 --<-- sn2 (QEMU active) . does it take data from sn2 only ? or base+sn1+sn2 .. full drive and creates a new qcow2 sparse file. Thanks /Jd

3 5

[libvirt-users] Fwd: Hotadd memory and hotplug cpu
by ra va 16 Oct '14

16 Oct '14

Hello, Does KVM support hotadd memory and hot-plug cpu? I checked it using the virsh command but I can only increase the memory to the maximum memory that is initially set But setmaxmem command is failing. Which means this require a reboot of the guest # virsh setmaxmem 4 1048576 error: Unable to change MaxMemorySize error: Requested operation is not valid: cannot resize the maximum memory on an active domain #virsh setvcpus 4 4 error: internal error: unable to execute QEMU command 'cpu-add': Not supported Thanks ravargs

2 1

[libvirt-users] VGA as vfio-pci and vnc server's blank/black display
by lejeczek 15 Oct '14

15 Oct '14

hi, I'm having a Radeon as vfio-pci, which seems to work perfectly fine, but... Qemu's model type='vga' gets "exlaimed" in win2k8's Device Manager with: " Windows has stopped this device because it has reported problems. (Code 43) " Now, that does not bother me that much as all I need on regular basis is RDP but VNC connection gets me nowhere. I get blank/black screen, it connects without errors/problems but nothing more. I know you would say VGA passthrough is only supported for very few VGA adapters but is the situation I describe normal/expected? regards

1 3

Re: [libvirt-users] passthrough of PCI-device
by Weis, Michael (DWIE) 14 Oct '14

14 Oct '14

Good morning, there is a typo in my description; the line <address domain='0x0' bus='0x1' slot='0x00' function='0x0'/> should be <address domain='0x0' bus='0x2' slot='0x00' function='0x0'/> That was correct in my xml-file. Isn't there anybody how can help me with that? Regards Michael Weis Von: Weis, Michael (DWIE) Gesendet: Dienstag, 7. Oktober 2014 11:45 An: 'libvirt-users(a)redhat.com' Betreff: passthrough of PCI-device Hello, I try to passthrough a PCI-card to a VM named testvm I want to do that with an xml-file named hga.xml including the following content: <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0' bus='0x1' slot='0x00' function='0x0'/> </source> </hostdev> When I execute virsh attach-device testvm hga.xml I get the following error: Fehler: Fehler beim Anhängen des Geräts von hga.xml (error: error while attaching device from hga.xml) Fehler: Interner Fehler: Kann Qemu-Befehl 'device_add' nicht ausführen: Device initialization failed. (error: internal error: cannot execute 'device_add': In the syslog of the host I get the following errors: Oct 7 11:32:34 artemis2 journal: Interner Fehler: Kann Qemu-Befehl 'device_add' nicht ausführen: Device initialization failed. Oct 7 11:32:53 artemis2 kernel: ffff880220fadd10 ffffffff810f924a ffff880220fadd28 0000000000000246 Oct 7 11:32:53 artemis2 kernel: ffff8800bd07a400 000000007265756d ffffffffa0866ee0 0000000000000000 Oct 7 11:32:53 artemis2 kernel: Call Trace: Oct 7 11:32:53 artemis2 kernel: [<ffffffff815e237b>] dump_stack+0x19/0x1b Oct 7 11:32:53 artemis2 kernel: [<ffffffff810f924a>] __setup_irq+0x54a/0x570 Oct 7 11:32:53 artemis2 kernel: [<ffffffffa0866ee0>] ? virqfd_wakeup+0xc0/0xc0 [vfio_pci] Oct 7 11:32:53 artemis2 kernel: [<ffffffff810f93cc>] request_threaded_irq+0xcc/0x170 Oct 7 11:32:53 artemis2 kernel: [<ffffffffa0866b8a>] vfio_intx_set_signal+0x10a/0x1f0 [vfio_pci] Oct 7 11:32:53 artemis2 kernel: [<ffffffffa08670e8>] vfio_pci_set_intx_trigger+0xc8/0x1b0 [vfio_pci] Oct 7 11:32:53 artemis2 kernel: [<ffffffffa086799b>] vfio_pci_set_irqs_ioctl+0x7b/0x100 [vfio_pci] Oct 7 11:32:53 artemis2 kernel: [<ffffffff8115d352>] ? memdup_user+0x42/0x70 Oct 7 11:32:53 artemis2 kernel: [<ffffffffa0865e74>] vfio_pci_ioctl+0x314/0xa00 [vfio_pci] Oct 7 11:32:53 artemis2 kernel: [<ffffffff81194b6a>] ? kmem_cache_alloc+0x1ba/0x1d0 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811b156c>] ? get_empty_filp+0x5c/0x190 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811f1891>] ? fsnotify+0x251/0x350 Oct 7 11:32:53 artemis2 kernel: [<ffffffff81251806>] ? security_file_alloc+0x16/0x20 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811b15a0>] ? get_empty_filp+0x90/0x190 Oct 7 11:32:53 artemis2 kernel: [<ffffffffa084f163>] vfio_device_fops_unl_ioctl+0x23/0x30 [vfio] Oct 7 11:32:53 artemis2 kernel: [<ffffffff811c2af5>] do_vfs_ioctl+0x2e5/0x4c0 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811af780>] ? vfs_write+0x160/0x1e0 Oct 7 11:32:53 artemis2 kernel: [<ffffffff811c2d71>] SyS_ioctl+0xa1/0xc0 Oct 7 11:32:53 artemis2 kernel: [<ffffffff815f2a59>] system_call_fastpath+0x16/0x1b Oct 7 11:32:53 artemis2 journal: Interner Fehler: Kann Qemu-Befehl 'device_add' nicht ausführen: Device initialization failed. My version-information: OS: CentOS Linux release 7.0.1406 (Core) Kernel: Linux artemis2 3.10.0-123.8.1.el7.x86_64 libvirt-daemon-driver-secret-1.2.8-1.el7.centos.x86_64 libvirt-1.2.8-1.el7.centos.x86_64 libvirt-daemon-kvm-1.2.8-1.el7.centos.x86_64 libvirt-client-1.2.8-1.el7.centos.x86_64 libvirt-daemon-driver-qemu-1.2.8-1.el7.centos.x86_64 libvirt-daemon-config-network-1.2.8-1.el7.centos.x86_64 libvirt-daemon-driver-interface-1.2.8-1.el7.centos.x86_64 libvirt-daemon-1.2.8-1.el7.centos.x86_64 libvirt-daemon-driver-nodedev-1.2.8-1.el7.centos.x86_64 libvirt-daemon-driver-storage-1.2.8-1.el7.centos.x86_64 libvirt-daemon-config-nwfilter-1.2.8-1.el7.centos.x86_64 libvirt-daemon-driver-network-1.2.8-1.el7.centos.x86_64 libvirt-daemon-driver-lxc-1.2.8-1.el7.centos.x86_64 libvirt-daemon-driver-nwfilter-1.2.8-1.el7.centos.x86_64 The PCI-Card I want to passthrough: 02:00.0 Ethernet controller: PLX Technology, Inc. Device 235e Subsystem: PLX Technology, Inc. Device 235e Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 16 Region 0: Memory at f0810000 (32-bit, non-prefetchable) [disabled] [size=256] Region 1: I/O ports at e000 [disabled] [size=256] Region 2: Memory at e0000000 (32-bit, non-prefetchable) [disabled] [size=256M] Region 3: Memory at f0000000 (32-bit, non-prefetchable) [disabled] [size=8M] Expansion ROM at f0800000 [disabled] [size=64K] Capabilities: [40] Power Management version 1 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [48] CompactPCI hot-swap <?> Capabilities: [4c] Vital Product Data Unknown large resource type 35, will not decode more. Kernel driver in use: vfio-pci Please help. Best regards Michael Weis PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail.

2 4