- Users - libvirt List Archives

[libvirt-users] question about libvirt and qemu
by Ahmed Amer 27 Jun '13

27 Jun '13

Hello, I am wondering what is the difference between libvirt and qemu?and how they are related to KVM? -- Ahmed Amer **+2 0111 0353505

2 1

[libvirt-users] Permission denied
by Roland Giesler 25 Jun '13

25 Jun '13

System: $ cat /etc/issue Ubuntu 12.10 \n \l $ uname -a Linux Matt-HP 3.5.0-34-generic #55-Ubuntu SMP Thu Jun 6 20:20:19 UTC 2013 i686 i686 i686 GNU/Linux I have a converted VMWare virtual machine which I converted by using: $ vmware2libvirt -f ./WinXPPro.vmx > WinXPPro.xml $ virsh -c qemu:///system define WinXPPro.xml After various efforts to start the machine, I changed some of the setting (as advised by the error messages I got). My changes were: <domain type='kvm'> to <domain type='qemu'> and <emulator>/usr/bin/kvm</emulator> to <emulator>/usr/bin/qemu-system-i386</emulator> and whatever it was before (i guess type 'raw') to <driver name='qemu' type='vmdk'/> Now "virsh edit WinXPPro" gives me: <domain type='qemu'> <name>WinXPPro</name> <uuid>8f83332d-d1c7-4ca9-a171-48823aeb30a8</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='i686' machine='pc-1.2'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-i386</emulator> <disk type='file' device='disk'> <driver name='qemu' type='vmdk'/> <source file='/home/roland/WinXPPro/WinXPPro.vmdk'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='network'> <mac address='00:0c:29:1e:37:c4'/> <source network='default'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' listen='127.0.0.1'> <listen type='address' address='127.0.0.1'/> </graphics> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </memballoon> </devices> </domain> When I got the "permission denied" error, I found advice to change the user to libvirt-qemu and the group to kvm. Both exist on my system. $ ls -la total 15899728 drwxrwxr-x 2 roland roland 4096 Jun 25 16:05 . drwxr-xr-x 92 roland roland 4096 Jun 25 18:15 .. -rw------- 1 libvirt-qemu kvm 1474560 Jun 24 20:00 floppy_disk_image -rw------x 1 libvirt-qemu kvm 1073741824 Jun 24 20:27 WinXPPro-c21a8baf.vmem -rw------x 1 libvirt-qemu kvm 135507536 Jun 24 20:12 WinXPPro-c21a8baf.vmss -rw----r-x 1 libvirt-qemu kvm 8684 Jun 24 20:18 WinXPPro.nvram -rw----r-x 1 libvirt-qemu kvm 2145255424 Jun 24 20:12 WinXPPro-s001.vmdk -rw----r-x 1 libvirt-qemu kvm 2146238464 Jun 24 20:33 WinXPPro-s002.vmdk -rw----r-x 1 libvirt-qemu kvm 2146631680 Jun 24 20:25 WinXPPro-s003.vmdk -rw----r-x 1 libvirt-qemu kvm 3211264 Jun 24 20:12 WinXPPro-s004.vmdk -rw----r-x 1 libvirt-qemu kvm 2106261504 Jun 24 20:18 WinXPPro-s005.vmdk -rw----r-x 1 libvirt-qemu kvm 2146697216 Jun 24 20:00 WinXPPro-s006.vmdk -rw----r-x 1 libvirt-qemu kvm 2162688 Jun 24 20:27 WinXPPro-s007.vmdk -rw----r-x 1 libvirt-qemu kvm 2146107392 Jun 24 20:06 WinXPPro-s008.vmdk -rw----r-x 1 libvirt-qemu kvm 2099511296 Jun 24 19:58 WinXPPro-s009.vmdk -rw-rw-r-x 1 libvirt-qemu kvm 128446464 Jun 24 20:19 WinXPPro-s010.vmdk -rw----r-x 1 libvirt-qemu kvm 857 Jun 25 15:54 WinXPPro.vmdk -rw-r--r-x 1 libvirt-qemu kvm 0 Jun 24 20:12 WinXPPro.vmsd -rwxr-xr-x 1 libvirt-qemu kvm 4209 Jun 25 15:56 WinXPPro.vmx -rw-r--r-x 1 libvirt-qemu kvm 2932 Jun 25 15:57 WinXPPro.vmxf -rw-rw-r-x 1 libvirt-qemu kvm 852 Jun 25 16:05 WinXPPro.xml $ virsh start WinXPPro error: Failed to start domain WinXPPro error: internal error process exited while connecting to monitor: qemu-system-i386: -drive file=/home/roland/WinXPPro/WinXPPro.vmdk,if=none,id=drive-ide0-0-0,format=vmdk: could not open disk image /home/roland/WinXPPro/WinXPPro.vmdk: Permission denied However, despite not using "sudo" and running the command as me, the WinXPPro.vmdk file is now owned by root, so I get the complaint that the file cannot be accessed. If I sudo the command, it gives me the exact same result. $ ls -la total 15899728 drwxrwxr-x 2 roland roland 4096 Jun 25 16:05 . drwxr-xr-x 92 roland roland 4096 Jun 25 18:15 .. -rw------- 1 libvirt-qemu kvm 1474560 Jun 24 20:00 floppy_disk_image -rw------x 1 libvirt-qemu kvm 1073741824 Jun 24 20:27 WinXPPro-c21a8baf.vmem -rw------x 1 libvirt-qemu kvm 135507536 Jun 24 20:12 WinXPPro-c21a8baf.vmss -rw----r-x 1 libvirt-qemu kvm 8684 Jun 24 20:18 WinXPPro.nvram -rw----r-x 1 libvirt-qemu kvm 2145255424 Jun 24 20:12 WinXPPro-s001.vmdk -rw----r-x 1 libvirt-qemu kvm 2146238464 Jun 24 20:33 WinXPPro-s002.vmdk -rw----r-x 1 libvirt-qemu kvm 2146631680 Jun 24 20:25 WinXPPro-s003.vmdk -rw----r-x 1 libvirt-qemu kvm 3211264 Jun 24 20:12 WinXPPro-s004.vmdk -rw----r-x 1 libvirt-qemu kvm 2106261504 Jun 24 20:18 WinXPPro-s005.vmdk -rw----r-x 1 libvirt-qemu kvm 2146697216 Jun 24 20:00 WinXPPro-s006.vmdk -rw----r-x 1 libvirt-qemu kvm 2162688 Jun 24 20:27 WinXPPro-s007.vmdk -rw----r-x 1 libvirt-qemu kvm 2146107392 Jun 24 20:06 WinXPPro-s008.vmdk -rw----r-x 1 libvirt-qemu kvm 2099511296 Jun 24 19:58 WinXPPro-s009.vmdk -rw-rw-r-x 1 libvirt-qemu kvm 128446464 Jun 24 20:19 WinXPPro-s010.vmdk -rw----r-x 1 root root 857 Jun 25 15:54 WinXPPro.vmdk -rw-r--r-x 1 libvirt-qemu kvm 0 Jun 24 20:12 WinXPPro.vmsd -rwxr-xr-x 1 libvirt-qemu kvm 4209 Jun 25 15:56 WinXPPro.vmx -rw-r--r-x 1 libvirt-qemu kvm 2932 Jun 25 15:57 WinXPPro.vmxf -rw-rw-r-x 1 libvirt-qemu kvm 852 Jun 25 16:05 WinXPPro.xml roland@Matt-HP:~/WinXPPro$ What is going on here? Roland

2 3

[libvirt-users] libvirt: xen error
by varun bhatnagar 24 Jun '13

24 Jun '13

Hi, I am trying to install xen and provide libvrit support to it but while installing at some point of time it tries to connect to GIT repository and creates a clone but I am behind firewall and it is getting timed out.... :( I am pasting a screenshot below. Can anyone of you please help me out with this one. // Varun

3 3

Re: [libvirt-users] libvirt hang on domain attemp to create domain
by Alexandr 24 Jun '13

24 Jun '13

On 20.06.2013 10:44, Michal Privoznik wrote: > On 20.06.2013 09:40, Александр wrote: >> В письме от Четверг, 20-июн-2013 09:15:14 Вы написали: >>> On 19.06.2013 21:24, Александр wrote: >>>> В письме от Среда, 19-июн-2013 09:35:27 пользователь Michal Privoznik >> написал: >>>>> On 18.06.2013 22:21, Александр wrote: >>>>>> В письме от Вторник, 18-июн-2013 12:10:41 пользователь Michal Privoznik >>>>>> >>>>>> написал: >>>>>>> On 18.06.2013 07:14, Александр wrote: >>>>>>>> good day, i am trying to create domain via virDomainDefineXML. and my >>>>>>>> program hanging, also i failed to caonnect to libvirt daemon with >>>>>>>> virt-manager after this, only killing libvirtd via SIGKILL and >>>>>>>> restarting >>>>>>>> it solveing hang (i mean after restart i able to connect with >>>>>>>> virt-manager), i using following domain xml >>>>>>>> >>>>>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>>>>> <domain type="kvm"> >>>>>>>> >>>>>>>> <tittle>Automatically created domain with default >>>>>>>> configuration</tittle> >>>>>>>> <name>vm1</name> >>>>>>>> <description>no description</description> >>>>>>>> <os> >>>>>>>> >>>>>>>> <type>hvm</type> >>>>>>>> <boot dev="cdrom"/> >>>>>>>> <boot dev="hd"/> >>>>>>>> >>>>>>>> </os> >>>>>>>> <vcpu>1</vcpu> >>>>>>>> <memory unit="MB">512</memory> >>>>>>>> <cpu model="host-model"> >>>>>>>> >>>>>>>> <topology sockets="1" cores="1" threads="1"/> >>>>>>>> >>>>>>>> </cpu> >>>>>>>> <clock offset="localtime"/> >>>>>>>> <devices> >>>>>>>> >>>>>>>> <graphics type="vnc" autoport="yes" password="admin"/> >>>>>>>> <channel type="unix"> >>>>>>>> >>>>>>>> <source mode="bind" path="/var/run/vm1.sock"/> >>>>>>>> <target type="virtio" name="org.guest_agent.0"/> >>>>>>>> >>>>>>>> </channel> >>>>>>>> >>>>>>>> </devices> >>>>>>>> >>>>>>>> </domain> >>>>>>>> >>>>>>>> i have this calls on stack >>>>>>>> >>>>>>>> 0 0x00007ffff48c1750 __poll_nocancel >>>>>>>> 1 0x00007ffff649e5ca virNetClientIOEventLoop >>>>>>> This is just probably a client waiting for the corresponding libvirtd >>>>>>> to >>>>>>> provide a reply message. Are you able to get libvirtd debug logs so we >>>>>>> can see what's going on? >>>>>>> >>>>>>> http://wiki.libvirt.org/page/DebugLogs >>>>>>> >>>>>>> BTW, what's the libvirt version you are running? >>>>>>> >>>>>>> Michal >>>>>>> >>>>>>>> 2 0x00007ffff649ed96 virNetClientSendInternal >>>>>>>> 3 0x00007ffff64a0443 virNetClientSendWithReply >>>>>>>> 4 0x00007ffff64a0daa virNetClientProgramCall >>>>>>>> 5 0x00007ffff6478566 callFull.isra.2 >>>>>>>> 6 0x00007ffff6487fa2 remoteDomainDefineXML >>>>>>>> 7 0x00007ffff6449d2f virDomainDefineXML >>>>>>>> 8 0x0000000000426941 virt_domain::create >>>>>>>> /home/sss/install/git/work/avirt/vm_pool/vm_pool/libvirt.cpp 295 >>>>>>>> 9 0x000000000040c1a9 main >>>>>>>> /home/sss/install/git/work/avirt/vm_pool/vm_pool/main.cpp 40 >>>>>>>> >>>>>>>> what i am doing wrong ? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> libvirt-users mailing list >>>>>>>> libvirt-users(a)redhat.com >>>>>>>> https://www.redhat.com/mailman/listinfo/libvirt-users >>>>>> i have libvirt version 1.0.6, debug log in attachment. >>>>> Yuck, this is 1.0.6; Well, from the logs it seems like the daemon is >>>>> stuck. Can you attach to the libvirtd while it's being stuck and run 't >>>>> a a bt' and post the result? I wonder if we have a deadlock somewhere. >>>>> >>>>> Michal >>>> if i correctly understand you, you need debugger backtrace after libvirtd >>>> stuck ?, if so, here is bt from gdb >>> You understand correctly. However, simple 'bt' doesn't show what's going >>> on in other threads - libvirtd is multi threaded. >>> >>>> (gdb) bt >>>> #0 0x00007f00c1ae876d in poll () from /lib64/libc.so.6 >>>> #1 0x00007f00c203cfcb in virEventPollRunOnce () from >>>> /usr/lib64/libvirt.so.0 #2 0x00007f00c203ba4d in virEventRunDefaultImpl >>>> () from >>>> /usr/lib64/libvirt.so.0 >>>> #3 0x00007f00c214a5cd in virNetServerRun () from /usr/lib64/libvirt.so.0 >>>> #4 0x00007f00c2aea08a in main () >>> So all we see here is the libvirtd event loop. That's why we need 't a a >>> bt' which is 'thread apply all backtrace' which will run 'bt' over all >>> threads. >>> >>> Michal >> how can i make it ? >> > The very same way as you did 'bt'. Just instead of typing 'bt' you'll > type 't a a bt'. > > Michal here is backtrace from all threads: (gdb) t a a bt Thread 11 (Thread 0x7fdd8db82700 (LWP 20321)): #0 0x00007fdd944b990c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdd9476515a in virCondWait () from /usr/lib64/libvirt.so.0 #2 0x00007fdd9476582b in virThreadPoolWorker () from /usr/lib64/libvirt.so.0 #3 0x00007fdd94764dfe in virThreadHelper () from /usr/lib64/libvirt.so.0 #4 0x00007fdd944b5d63 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fdd941ed04d in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fdd8d381700 (LWP 20322)): #0 0x00007fdd944b990c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdd9476515a in virCondWait () from /usr/lib64/libvirt.so.0 #2 0x00007fdd9476582b in virThreadPoolWorker () from /usr/lib64/libvirt.so.0 #3 0x00007fdd94764dfe in virThreadHelper () from /usr/lib64/libvirt.so.0 #4 0x00007fdd944b5d63 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fdd941ed04d in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fdd8cb80700 (LWP 20323)): #0 0x00007fdd944bc344 in __lll_lock_wait () from /lib64/libpthread.so.0 #1 0x00007fdd944b7e56 in _L_lock_511 () from /lib64/libpthread.so.0 #2 0x00007fdd944b7caa in pthread_mutex_lock () from /lib64/libpthread.so.0 #3 0x00007fdd94773861 in virDomainObjListSearchName () from /usr/lib64/libvirt.so.0 #4 0x00007fdd9473c8a5 in virHashSearch () from /usr/lib64/libvirt.so.0 #5 0x00007fdd9478cc3d in virDomainObjListAddLocked.isra.43 () from /usr/lib64/libvirt.so.0 #6 0x00007fdd9478cd47 in virDomainObjListAdd () from /usr/lib64/libvirt.so.0 #7 0x00007fdd875a311c in qemuDomainDefineXML () from /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so #8 0x00007fdd947ead2f in virDomainDefineXML () from /usr/lib64/libvirt.so.0 #9 0x00007fdd95206b4d in remoteDispatchDomainDefineXMLHelper () #10 0x00007fdd94848d27 in virNetServerProgramDispatch () from /usr/lib64/libvirt.so.0 #11 0x00007fdd94844068 in virNetServerHandleJob () from /usr/lib64/libvirt.so.0 #12 0x00007fdd94765795 in virThreadPoolWorker () from /usr/lib64/libvirt.so.0 #13 0x00007fdd94764dfe in virThreadHelper () from /usr/lib64/libvirt.so.0 #14 0x00007fdd944b5d63 in start_thread () from /lib64/libpthread.so.0 #15 0x00007fdd941ed04d in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7fdd8c37f700 (LWP 20324)): #0 0x00007fdd944b990c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdd9476515a in virCondWait () from /usr/lib64/libvirt.so.0 #2 0x00007fdd9476582b in virThreadPoolWorker () from /usr/lib64/libvirt.so.0 #3 0x00007fdd94764dfe in virThreadHelper () from /usr/lib64/libvirt.so.0 #4 0x00007fdd944b5d63 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fdd941ed04d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fdd8bb7e700 (LWP 20325)): #0 0x00007fdd944b990c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdd9476515a in virCondWait () from /usr/lib64/libvirt.so.0 #2 0x00007fdd9476582b in virThreadPoolWorker () from /usr/lib64/libvirt.so.0 #3 0x00007fdd94764dfe in virThreadHelper () from /usr/lib64/libvirt.so.0 #4 0x00007fdd944b5d63 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fdd941ed04d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fdd8b37d700 (LWP 20326)): #0 0x00007fdd944b990c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdd9476515a in virCondWait () from /usr/lib64/libvirt.so.0 #2 0x00007fdd9476584b in virThreadPoolWorker () from /usr/lib64/libvirt.so.0 #3 0x00007fdd94764dfe in virThreadHelper () from /usr/lib64/libvirt.so.0 #4 0x00007fdd944b5d63 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fdd941ed04d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fdd8ab7c700 (LWP 20327)): #0 0x00007fdd944b990c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdd9476515a in virCondWait () from /usr/lib64/libvirt.so.0 #2 0x00007fdd9476584b in virThreadPoolWorker () from /usr/lib64/libvirt.so.0 #3 0x00007fdd94764dfe in virThreadHelper () from /usr/lib64/libvirt.so.0 #4 0x00007fdd944b5d63 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fdd941ed04d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fdd8a37b700 (LWP 20328)): #0 0x00007fdd944b990c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 ---Type <return> to continue, or q <return> to quit--- #1 0x00007fdd9476515a in virCondWait () from /usr/lib64/libvirt.so.0 #2 0x00007fdd9476584b in virThreadPoolWorker () from /usr/lib64/libvirt.so.0 #3 0x00007fdd94764dfe in virThreadHelper () from /usr/lib64/libvirt.so.0 #4 0x00007fdd944b5d63 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fdd941ed04d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fdd89b7a700 (LWP 20329)): #0 0x00007fdd944b990c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdd9476515a in virCondWait () from /usr/lib64/libvirt.so.0 #2 0x00007fdd9476584b in virThreadPoolWorker () from /usr/lib64/libvirt.so.0 #3 0x00007fdd94764dfe in virThreadHelper () from /usr/lib64/libvirt.so.0 #4 0x00007fdd944b5d63 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fdd941ed04d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fdd89379700 (LWP 20330)): #0 0x00007fdd944b990c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fdd9476515a in virCondWait () from /usr/lib64/libvirt.so.0 #2 0x00007fdd9476584b in virThreadPoolWorker () from /usr/lib64/libvirt.so.0 #3 0x00007fdd94764dfe in virThreadHelper () from /usr/lib64/libvirt.so.0 #4 0x00007fdd944b5d63 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fdd941ed04d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fdd95166740 (LWP 20320)): #0 0x00007fdd941e376d in poll () from /lib64/libc.so.6 #1 0x00007fdd94737fcb in virEventPollRunOnce () from /usr/lib64/libvirt.so.0 #2 0x00007fdd94736a4d in virEventRunDefaultImpl () from /usr/lib64/libvirt.so.0 #3 0x00007fdd948455cd in virNetServerRun () from /usr/lib64/libvirt.so.0 #4 0x00007fdd951e508a in main () and also from my program if it important: 0 0x00007ffff48c1750 __poll_nocancel 1 0x00007ffff649e5ca virNetClientIOEventLoop 2 0x00007ffff649ed96 virNetClientSendInternal 3 0x00007ffff64a0443 virNetClientSendWithReply 4 0x00007ffff64a0daa virNetClientProgramCall 5 0x00007ffff6478566 callFull.isra.2 6 0x00007ffff6487fa2 remoteDomainDefineXML 7 0x00007ffff6449d2f virDomainDefineXML 8 0x0000000000426941 virt_domain::create /home/sss/install/git/work/avirt/vm_pool/vm_pool/libvirt.cpp 295 9 0x000000000040c1a9 main /home/sss/install/git/work/avirt/vm_pool/vm_pool/main.cpp 40

3 3

[libvirt-users] Libvirt and Qemu for Debian Squeeze
by McEvoy, James 24 Jun '13

24 Jun '13

Has anyone built current debs for Debian Squeeze (v6.0.7) that supports virtio-scsi, Fibre Channel World Wind Names and virt-install for the virtio-scis controller (0.600.4)? I have a need to run a RHEL 6.4 guest on a Debian Squeeze KVM host and I do not have experience building debs instead of rpms. --jim

1 0

[libvirt-users] cgroup error starting domains
by Matteo Bernardini 21 Jun '13

21 Jun '13

Hi, I've got a small problem using libvirt-1.0.5.1 (with the latest patch in the v1.0.5-maint branch on git added). I'm using slackware64-14.0 but the situation is exactly the same described on a debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707201 When trying to start a domain I got error: Failed to start domain debian-wheezy-xfce error: Unable to initialize /machine cgroup: Invalid argument with this in libvirtd.log virCgroupDetect:373 : Failed to detect mounts for /machine qemuInitCgroup:425 : Unable to initialize /machine cgroup: Invalid argument and the error goes away if I unmount /sys/fs/cgroup. Reverting to 1.0.4 fixes this, but this exposes another thing that I report even if I'm not sure it's an error: if I create a domain with 1.0.5.1 (I use the latest virt-manager to do this), in the xml of the domain there's a line that doesn't seem to have the close tag <controller type='pci' index='0' model='pci-root'/> If I revert to 1.0.4 the domain with this line in the xml doesn't even get listed between the available domains and I got this in libvirtd.log virDomainControllerDefParseXML:4838 : internal error Unknown controller type 'pci' deleting the interested line make it available again. Please let me know if you need further informations on the matters. Matteo

2 6

Re: [libvirt-users] Not able to open Xen Connection using libvirt
by varun bhatnagar 21 Jun '13

21 Jun '13

No it was not booted with xen kernel. Actually I tried booting it with xen kernel but I am getting a message saying Error No 15 : File not found. I tried editing the grub entry and noticed that there are 3 entries: 1) kernel /boot/xen.gz vga= mode-0x345 2) module /boot/vmlinuz-3.0.13-0.27-xen....... 3) module /boot/initrd-3.0.13-0.27-xen And in /boot i listed down the files, only xen.gz is there. Rest of the 2 files are not there (pasted the screenshot below). Even at one site it was given to remove /boot from the path but that also din't work. How shall I solve this one? // Varun On Wed, Jun 19, 2013 at 1:07 AM, Prasad <prasad(a)mukhedkar.com> wrote: > On 06/18/2013 10:03 PM, varun bhatnagar wrote: > > Hi, > > I am trying to create virtual machine through libvirt using xen > hypervisor. I was able to install xen successfully but when I tried > connecting to the hypervisor it gave an error. And while installing libvirt > (libvirt-1.0.1) I installed it with xen support. > I am pasting the snapshot of the error below: > > [image: Inline image 1] > > Can anyone tell me why I am getting this error? > > // > Varun > > > _______________________________________________ > libvirt-users mailing listlibvirt-users@redhat.comhttps://www.redhat.com/mailman/listinfo/libvirt-users > > Is this system booted with xen kernel? xen virtualization required > special kernel it doesn't work with standard kernel. > >

2 2

[libvirt-users] 32 bit client on 32bit host
by Roland Giesler 21 Jun '13

21 Jun '13

As mentioned in another post, I trying to set up an existing Windows7 partition on an Ubuntu desktop as a libvirt guest and now have the following configuration files for this: <domain type='qemu'> <name>Windows7</name> <uuid>b2c9c297-907a-159d-7e87-a24a01eb5a57</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='i686' machine='pc-1.2'>hvm</type> <boot dev='hd'/> <bootmenu enable='yes'/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>kvm32</model> <vendor>Intel</vendor> <feature policy='require' name='pbe'/> <feature policy='require' name='tm2'/> <feature policy='require' name='osxsave'/> <feature policy='require' name='ss'/> <feature policy='require' name='lm'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='ht'/> <feature policy='require' name='ds'/> <feature policy='require' name='lahf_lm'/> <feature policy='require' name='xsave'/> <feature policy='require' name='tm'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='pse36'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='cx16'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='acpi'/> </cpu> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-i386</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/sda1'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='network'> <mac address='52:54:00:22:60:93'/> <source network='default'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <sound model='ich6'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <video> <model type='vga' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> I manually changed the <emulator>/usr/bin/qemu-system-x86_64</emulator> to <emulator>/usr/bin/qemu-system-i386</emulator> since my hard drive partition contains 32bit Windows 7, although I'm not sure that this applies. My current machine setup it dual-boot, so I can boot Windows 7 from the first partition (/dev/sda1) using a grub boot menu. However, when I start the Windows 7 VM, I just get "Booting from Hard Disk" in the virt-manager console. What could be the problem? Lastly: /def/sda1 in a boot partition, but the rest of Windows is installed on /dev/sda2, but this partition is not marked bootable. thanks Roland

1 1

[libvirt-users] Question about vport operation for FC HBA
by Dennis Chen 21 Jun '13

21 Jun '13

Hi, When I want to use NPIV for a FC HBA in my Linux machine, I got the below error msg in virsh: virsh # nodedev-create /home/kvm/vHBA.xml error: Failed to create node device from /home/kvm/vHBA.xml error: internal error Parent device scsi_host20 is not capable of vport operations I checked the /sys/class folder for my HBA device that I want to use its NPIV feature, it's there: /sys/class/fc_host/host20/vport_create I can create a vHBA by using "echo 'xxxx:xxxx' > ./vport_create", a new fc host will be created after that. But I can't find any FC host with: #virsh nodedev-list --cap fc_host SCSI hosts can be found for above "nodedev-list --cap scsi_host". The libvirt I am working on is based ver 1.0.5, I checked the code and found below function is seems related with this issue: src/util/virutil.c: int virIsCapableVport(const char *sysfs_prefix, int host) This function looks up if there is "vport_create" file under /sys/class/fc_host/host20, as the way to decide if a HBA device is capable of vport operation. But seems this file is not compiled and virsh doesn't call it in my source code environment... is there any tips ? BRs, Dennis

2 2

[libvirt-users] Would a DOS on dovecot running under a VM cause host to crash?
by Hugh Davenport 21 Jun '13

21 Jun '13

Hey All, I'm just wondering whether this is what caused my server to crash. Started last night in NZ land. Jun 20 19:22:11 elm dovecot: imap-login: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=attackerip, lip=10.0.0.3, session=<0C8LzpDfZQDINsQC> occasionally get Jun 20 19:22:52 elm dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=attackerip, lip=10.0.0.3, session=<bHdz0JDfpwDINsQC> or in 0 secs last at Jun 20 19:26:24 elm dovecot: imap-login: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=attackerip, lip=10.0.0.3, session=<1MUR3ZDfcwDINsQC> and a minute later the server lost contact to the world. When I checked a bit later, the underlying host machine (dovecot runs on a VM (KVM)) had been powered off. Now, here in NZ land, there was also a crazy storm last night, and lots of brown outs. There could potentially of been a surge that killed it, but the UPS was still running fine when I started it again. The "attack" lasted around 4 minutes, in which there was 1161 lines in the log for a single attacker ip, and no other similar logs previously. Would this be enough to kill not only the VM running dovecot, but the underlying host machine? All up to date with patches, running debian stable (wheezy). dovecot-core debian package version 1:2.1.7-7 dovecot version 2.1.7 I notice there is a version 2.2.3 out, but not in debian yet. Could this fix this issue? I don't particularly want to have it happen again :D. The host is running debian oldstable (squeeze), so could update more. libvirt0 debian package version 0.8.3-5+squeeze5 libvirt version 0.8.3 I notice there is a version 1.0.6 out (debian stable only has 0.9.12-11+deb7u1, which is 0.9.12), would either of these versions fix an issue like this? qemu-kvm debian package version 0.12.5+dfsg-5+squeeze10 kernel is 2.6.32-5-amd64 Any thoughts? Cheers, Hugh

1 0