- Users - libvirt List Archives

Re: [libvirt-users] no luck with filesystem storage type [solved]
by Boylan, Ross 27 Mar '15

27 Mar '15

I needed one more option to make it work: # mount -t 9p /mnt/SASInstaller /mnt/SASInstaller/ mount: wrong fs type, bad option, bad superblock on /mnt/SASInstaller, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so # mount -t 9p -o trans=virtio /mnt/SASInstaller /mnt/SASInstaller The page you referenced also mentions using -oversion=9p2000.L. There is some additional info on the versions at http://landley.net/kdocs/Documentation/filesystems/9p.txt; that page says .L is the default, while http://wiki.qemu.org/Documentation/9psetup#Starting_the_Guest_using_libvirt says it's .U. I don't know how to tell which I ended up with. Thanks for the pointer. Ross ________________________________________ From: Ján Tomko [jtomko(a)redhat.com] Sent: Thursday, March 26, 2015 1:43 AM To: Boylan, Ross Cc: libvirt-users(a)redhat.com Subject: Re: [libvirt-users] no luck with filesystem storage type On Thu, Mar 26, 2015 at 01:37:06AM +0000, Boylan, Ross wrote: > I have a directory on the host that I would like to be visible in the guest/domain. Using virt-manager I selected the directory, resulting in this configuration: > <filesystem type='mount' accessmode='passthrough'> > <source dir='/mnt/SASInstaller'/> > <target dir='/mnt/SASInstaller'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> > </filesystem> > I created the /mnt/SASInstaller manually in the VM. > > Nothing shows up. What am I missing? Do I need to run something in the VM (running Linux) to make it work? You need to mount it: mount -t 9p /mnt/SASInstaller /mnt/SASInstaller The target 'dir' is not really a directory, it's just a mount tag. See: http://wiki.qemu.org/Documentation/9psetup#Starting_the_Guest_using_libvirt Jan

1 0

[libvirt-users] no luck with filesystem storage type
by Boylan, Ross 26 Mar '15

26 Mar '15

I have a directory on the host that I would like to be visible in the guest/domain. Using virt-manager I selected the directory, resulting in this configuration: <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/SASInstaller'/> <target dir='/mnt/SASInstaller'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </filesystem> I created the /mnt/SASInstaller manually in the VM. Nothing shows up. What am I missing? Do I need to run something in the VM (running Linux) to make it work? Thanks. Ross Boylan

2 1

[libvirt-users] libvirtd can't start
by 梅磊 26 Mar '15

26 Mar '15

Hi experts, The libvirtd can’t start on my server after the server interruption of power supply, the status is below: [root@openstack3 libvirt]# service libvirtd status Redirecting to /bin/systemctl status libvirtd.service libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: failed (Result: signal) since Tue 2015-03-24 16:10:31 CST; 7min ago Process: 27372 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=killed, signal=SEGV) Main PID: 27372 (code=killed, signal=SEGV) Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000: 27383: debug : virFileClose:90 : Closed fd 22 Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000: 27383: debug : virFileClose:90 : Closed fd 22 Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000: 27383: debug : virFileClose:90 : Closed fd 22 Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000: 27383: debug : virFileClose:90 : Closed fd 22 Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.413+0000: 27383: debug : virFileClose:90 : Closed fd 22 Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.413+0000: 27383: debug : virStateInitialize:847 : Running global init for netcf state driver Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.413+0000: 27383: debug : virObjectNew:199 : OBJECT_NEW: obj=0x7f73f0080d00 classname=virNetcfDriverState Mar 24 16:10:31 openstack3 libvirtd[27372]: ====== end of log ===== Mar 24 16:10:31 openstack3 systemd[1]: libvirtd.service: main process exited, code=killed, status=11/SEGV Mar 24 16:10:31 openstack3 systemd[1]: Unit libvirtd.service entered failed state. And the attachment is the log after restart the libvirtd. After long time search on google, I didn’t get any useful information, so anyone can give me some hint on this issue? -BR, Andy

3 3

[libvirt-users] machine='pc-q35-2.1' and sata controller
by Thomas Stein 26 Mar '15

26 Mar '15

Hello. I'm not able to disable the sata controller on a machine='pc-q35-2.1' type VM. Whenever i delete: <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> it gets added again when i close the editor. The reason i would like to delete the sata controller is this error while trying to migrate the machine: 2015-02-23 19:04:11.181+0000: 1972: error : qemuMonitorJSONCheckError:381 : internal error: unable to execute QEMU command 'migrate': State blocked by non-migratable device '0000:00:1f.2/ich9_ahci' Someone has an idea to solve this? thanks and cheers t.

4 9

[libvirt-users] Listing on Host sFlow under Applications>Monitoring
by Peter Phaal 26 Mar '15

26 Mar '15

Would it be possible to list the Host sFlow project in the Monitoring section of http://libvirt.org/apps.html? Host sFlow <http://host-sflow.sourceforge.net/> Host sFlow is a light weight agent running on KVM hypervisors that links to libvirt library and exports standardized cpu, memory, network and disk metrics for all virtual machines using sFlow protocol. Thanks, Peter

2 2

[libvirt-users] virsh dom state
by Fiorenza Meini 25 Mar '15

25 Mar '15

Hi there, I'm running KVM under Openstack . When I give virsh list command, I see some VM in NON persistent state. What does it mean? How can I move it to a persisten state ? I found that I cannot make a snapshot, from Openstack , of a machine which is in a NON PERSISTENT state. Regards Fiorenza -- Spazio Web S.r.l. V. Dante, 10 13900 Biella Tel.: +39 015 2431982 Fax.: +39 015 2522600 Numero d'Iscrizione al Registro Imprese presso CCIAA Biella, Cod.Fisc.e P.Iva: 02414430021 Iscriz. REA: BI - 188936 Cap. Soc.: €. 30.000 i.v.

6 5

[libvirt-users] java binding in central maven repository
by Laszlo Hornyak 24 Mar '15

24 Mar '15

Hi, The last libvirt artifact published to the maven central repository was 0.4.7 in 2011. The libvirt.org/maven2 repository is updated, but - sometimes the libvirt.org webserver is not responding and that breaks the build. - for similar reasons projects depending on other maven repositories can not upload to central repository Can we get back updates to maven central repo? Best regards, Laszlo -- EOF

1 0

Re: [libvirt-users] getting oriented/networking [some success]
by Boylan, Ross 24 Mar '15

24 Mar '15

I seem to have run into https://bugzilla.redhat.com/show_bug.cgi?id=855640, because when I tried the fix/work-around at the end (comment 11), ethtool -K eth0 gro off, my download speed by speedtest went from undetectable to ~150Mb/s. However, it was not able to connect for the upload test, and so something may still be off. Non-virtual machines can do the upload test, so it's not just a firewall issue. The comment refers to another source for more info, but it seems to be behind a Redhat paywall. Ross ________________________________________ From: Boylan, Ross Sent: Friday, March 20, 2015 11:01 AM To: Dominique Ramaekers; libvirt-users(a)redhat.com Subject: RE: [libvirt-users] getting oriented/networking Thanks very much. Unfortunately, networking is currently so slow as to be non-functional (most operations time out). It's also erratic: I had 2 VM that were close to identical--they were both based on the same disk image--and even when I set the networking the same one was fine and one was very slow. Today I started up the VM that had good networking, and it now has bad networking. Here's one of the network specifications: <interface type='direct'> <mac address='52:54:00:61:7c:dc'/> <source dev='eth1' mode='vepa'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> The one that was originally fast also had a NAT network, and the one that was originally slow was mode bridge before I changed it to vepa, which didn't help. The drivers came from http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/virtio-win-0.… in the 32 bit windows 7 directory of the iso (host is 64 bit, as is the emulated machine; Windows 7 is 32 bit). I've tried shutting down, removing and reinstalling the network adaptor, and various other things. Ross ________________________________________ From: Dominique Ramaekers [dominique.ramaekers(a)cometal.be] Sent: Thursday, March 19, 2015 11:21 PM To: Boylan, Ross; libvirt-users(a)redhat.com Subject: RE: [libvirt-users] getting oriented/networking Dear Boyland, In collaboration with some of this mailing list users, I had put some effort in optimising the guest settings in function of a windows guest. The libvirt-gui doesn't include these options. You'll have to edit the XML in virsh. This was my conclusion on 15-03-2015 but I added the hugepages tip in this list today. As for networking, I only use or bridged or the default virtual network (NAT), so can't help you more here. Here below, a summary of tips: - Setting video to QXL and the display channel to Spice <video> <model type='qxl' ram='65536' vram='65536' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> - Using HyperV enlightenemt timer <features> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> <features/> <clock ...> <timer name='hypervclock' present='yes'/> </clock> - Delete the tablet entry in the input section or set the USB-bus to USB2 or USB3 - Use hugepages <memoryBacking> <hugepages/> </memoryBacking> Again thanks Daniel and Andrey. Hope this helps. Grts, Dominique. -----Oorspronkelijk bericht----- Van: Boylan, Ross [mailto:Ross.Boylan@ucsf.edu] Verzonden: vrijdag 20 maart 2015 1:52 Aan: libvirt-users(a)redhat.com Onderwerp: [libvirt-users] getting oriented/networking I've been using virt-manager and kvm with a disk image (as in the raw bits) from a physical windows 7 machine. Initial performance was dreadful, but improved as I switched to virtio and spice. I've been running linux VM's somewhat longer (much longer if you count kvm without libvirt). There are lots of choices exposed by virt-manager. How do I find out what the choices mean, and which are good ones? This was true for the video (resolved by following instructions for spice, though I still wonder what the other settings are for), disks and the network. In particular, I have a choice of lots of interfaces for my network; I picked eth1:macvtap because I wanted to bridge eth1. But there is a "Source Mode" which I left at VEPA, even though Bridged was another choice. But the bridge would already seem implicit in picking a source device of eth1:macvtap. I don't know what "source mode" means. The choices in the GUI seem like some of the options listed under forward on http://libvirt.org/formatnetwork.html; is that a good place to look for clarification. I started a 2nd VM that also used eth1:macvtap (with virtio) and it had almost no network throughput. So maybe I should use some other method? I notice the network manager connection gui allows creation of bridges on the network; should I be using that? I have been reading documentation, but I haven't found either a task-oriented discussion ("to get a windows machine working well, use these options" or "follow these steps") or an easy way to go from the choices in the GUI to a discussion of their meaning. Thanks for any help you can offer. Ross Boylan _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users

1 1

[libvirt-users] still possible to use traditional bridge network setup ?
by Lentes, Bernd 24 Mar '15

24 Mar '15

Hi, i'm currently installing a SLES 12 64bit system. libvirt-client-1.2.5-13.3.x86_64 and libvirt-daemon-1.2.5-13.3.x86_64. Formerly I created my vm's (KVM) using a traditional bridge in my host systems, mostly SLES 11 SP3. But with SLES 12 I don't succeed. I can use the macvtap device in the host, but I like to be able to communicate between host and guest. Is the traditional bridge setup not any longer available ? Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/idg Je suis Charlie Helmholtz Zentrum München Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH) Ingolstädter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDir´in Bärbel Brumme-Bothe Geschäftsführer: Prof. Dr. Günther Wess, Dr. Nikolaus Blum, Dr. Alfons Enhsen Registergericht: Amtsgericht München HRB 6466 USt-IdNr: DE 129521671

2 7

[libvirt-users] KVM live migration i/o error
by Francesc Guasch 24 Mar '15

24 Mar '15

Hi. I have three Ubuntu Server 14.04 trusty with KVM. Two of them are HP servers and one is Dell. Both brands run fine the KVM virtual servers, and I can do live migration between the HPs. But I get I/O errors in the vda when I migrate to or from the Dell server. I have shared storage with NFS, mounted the same way in all of them: nfs.sever:/kvm /var/lib/libvirt/images nfs auto,vers=3 I checked the version of all the packages to make sure are the same. I got: kernel: 3.13.0-43-generic #72-Ubuntu SMP x86_64 libvirt: libvirt: 1.2.2-0ubuntu13.1.9 qemu-utils: 2.0.0+dfsg-2ubuntu1.10 qemu-kvm: 2.0.0+dfsg-2ubuntu1.10 I made sure the Cache in the Storage is set to None. Disk bus: virtio Cache mode: none IO mode: default I run this to do live migration: virsh migrate --live virtual qemu+ssh://dellserver/system I open two consoles with virt-manager, one in the origin host and another one in the destination. As soon as it starts in the origin console I spot I/O error messages, when it finishes I got them in the console in the destination server. The file system is read only and I have to shut it down hard. end request I/O error, /dev/vda, sector 8790327 When I migrate to the other HP server the process runs fine. I don't know what else to check, I wonder if such different hardware could be a problem. These are the CPU flags in the HP server: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm c onstant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 po pcnt lahf_lm dtherm tpr_shadow vnmi flexpriority ept vpid And those in the Dell server: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant _tsc pebs bts nopl pni dtes64 monitor ds_cpl vmx est cid cx16 xtpr pdcm lahf_lm tpr_shadow I tried to check the log files in /var/log/libvirt but I can't see any different message when I migrate from HP to HP than when I do from HP to Dell. I think I found something checking SELinux. ls -Z and getfattr return nothing. But ps -eZ showed something very different in the Dell server. This is in the HP server: /usr/sbin/libvirtd 1034 ? 11:51:44 libvirtd libvirt-09540b5d-82 701 ? 05:28:40 qemu-system-x86 unconfined 1 ? 00:01:00 init In the Dell server init is confined in lxc and there are also lxc-start processes. /usr/sbin/libvirtd 1622 ? 05:07:07 libvirtd libvirt-8a0f9087-32d... 29926 ? 00:00:01 qemu-system-x86 lxc-container-default 1774 ? 00:00:00 init /usr/bin/lxc-start 1763 ? 00:00:00 lxc-start There is also LXC installed in that server ! Maybe that is messing with kvm. The qemu processes look fine to me but there is a chance the problem comes from there. I could move the LXC somewhere else or I can keep it there to try to fix this issue. What do you advice I should do now ?

1 0