- Users - libvirt List Archives

[libvirt-users] CPU-Capabilties for Nested Virtualization
by Michael Beham 25 Jul '12

25 Jul '12

Hi, I have some questions about the CPU-Capabilities for Virtualization especially for Nested Virtualization like the Turtles Project. I am trying to create a Nested Environment by following the instruction of: http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and… The bare-metal system is a Dell Server with following CPU-Flags (virsh capabilities) <cpu> <arch>x86_64</arch> <model>Opteron_G4</model> <vendor>AMD</vendor> <topology sockets='1' cores='8' threads='2'/> <feature name='nodeid_msr'/> <feature name='wdt'/> <feature name='skinit'/> <feature name='ibs'/> <feature name='osvw'/> <feature name='cr8legacy'/> <feature name='extapic'/> <feature name='cmp_legacy'/> <feature name='fxsr_opt'/> <feature name='mmxext'/> <feature name='osxsave'/> <feature name='monitor'/> <feature name='ht'/> <feature name='vme'/> </cpu> After adding this Flags to the XML of my first VM, the following XML-Attributes are written to the file, after reopening it. <cpu mode='custom' match='exact'> <model fallback='allow'>Opteron_G4</model> <vendor>AMD</vendor> <feature policy='require' name='nodeid_msr'/> <feature policy='require' name='wdt'/> <feature policy='require' name='skinit'/> <feature policy='require' name='ibs'/> <feature policy='require' name='osvw'/> <feature policy='require' name='cr8legacy'/> <feature policy='require' name='extapic'/> <feature policy='require' name='cmp_legacy'/> <feature policy='require' name='fxsr_opt'/> <feature policy='require' name='mmxext'/> <feature policy='require' name='osxsave'/> <feature policy='require' name='monitor'/> <feature policy='require' name='ht'/> <feature policy='require' name='vme'/> </cpu> The problem is, that after adding this attributes to the XML, I am not able to load the kvm-modules in the VM. So I?m not able to install the Nested VM in the VM. But when I?m not adding the attributes to the XML and keep the XML-File of the VM unmodified, I?m able to load the KVM modules in the VM and I can install the Nested Guest. So my first question is, what difference it makes for the Nested Virtualization, when I?m not adding the Attributes and keep the XML-Files unmodified? And my second qestion is, what essential difference is between the qemu version 0.14 which was used by the instruction of Kashyap Chamarthy and the version 1.0 related to Nested Virtualization? I hope you understand my problem because it is quite confusing for me and I?m not sure that I?m using the right techniqe for my Nested Environment!! Best Regards, Mike

1 0

[libvirt-users] Setting CPU type for a vm
by Mauricio Tavares 24 Jul '12

24 Jul '12

I have a Windows XP vm and would like to know how should I set its cpu so it is seen by the vm as a proper 32bit one. In its xml file, I have <os> <type arch='i686' machine='rhel6.2.0'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> <bootmenu enable='yes'/> </os> And this is the machine I have (an intel i5): [root@vmhost ~]# virsh nodeinfo CPU model: x86_64 CPU(s): 4 CPU frequency: 1600 MHz CPU socket(s): 1 Core(s) per socket: 4 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 5904548 kB and this is what virsh thinks my vm has: [root@vmhost ~]# virsh vcpuinfo xp VCPU: 0 CPU: 2 State: running CPU time: 521.3s CPU Affinity: yyyy [root@vmhost ~]# But, the vm reports it not only as a 286 but also claims not to have the right drivers for it. How can I make the vm see it as a 686 or something like that?

3 4

[libvirt-users] help about libvirt console
by lei yang 24 Jul '12

24 Jul '12

Hi list, My xml is like below, it works well with "virsh console qemu1" <domain type='kvm'> <name>qemu1</name> <memory>1024000</memory> <currentMemory>512000</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc'>hvm</type> <boot dev='hd' /> <kernel>/boot/bzImage</kernel> <cmdline>console=ttyS0 root=/dev/hda rw</cmdline> </os> <devices> <disk type='file' device='disk'> <source file='/boot/test.img.raw' /> <target dev='hda' bus='ide' /> </disk> <console type='pty'> <target type='serial' port='0'/> </console> </devices> </domain> I want to use virtio console, so I change <console type='pty'> <target type='virtio' port='0'/> then I do #virsh define newvm.xml #virsh start qemu1 #virsh console qemu1 it show nothing any help for the virtio console seting? Lei

1 0

[libvirt-users] libvirt shortcomings of virsh domxml-to-native and domxml-from-native
by 张光鹏 24 Jul '12

24 Jul '12

Hi,all. we use libvirt to manage some host and vms on vmware hypervisor.I have found the libvirt there are some shortcomings . Such as virsh domxml-to-native and domxml-from-native .I have reviewed the libvirt source --src/vmx/vmx.c, code as follows : libvirt0.9.13源码xml 转化成vmxvmx转化成xml /* def:os.arch -> vmx:guestOS */ if (def->os.arch == NULL || STRCASEEQ(def->os.arch, "i686")) { virBufferAddLit(&buffer, "guestOS = \"other\"\n"); } else if (STRCASEEQ(def->os.arch, "x86_64")) { virBufferAddLit(&buffer, "guestOS = \"other-64\"\n"); } else { VMX_ERROR(VIR_ERR_INTERNAL_ERROR, _("Expecting domain XML attribute 'arch' of entry 'os/type' " "to be 'i686' or 'x86_64' but found '%s'"), def->os.arch); goto cleanup; }/* vmx:guestOS -> def:os.arch */ if (virVMXGetConfigString(conf, "guestOS", &guestOS, true) < 0) { goto cleanup; } if (guestOS != NULL && virFileHasSuffix(guestOS, "-64")) { def->os.arch = strdup("x86_64"); } else { def->os.arch = strdup("i686"); } if (def->os.arch == NULL) { virReportOOMError(); goto cleanup; } Vmware support many guestOS types like "windows7srv-64 ",If I use 64-bit Windows virtual machine, other-64 this type is not correct. NIC e1000 system can not be used . So I suggest to The libvirt improve the vmware support, especially the mutual transformation of the xml and vmx format guestOS only one parameter. Thanks all. 张光鹏 tel: 13718913184 mail: zhanggp(a)neusoft.com 移动互联网事业部东软集团股份有限公司 http://www.neusoft.com --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------

1 0

[libvirt-users] INTERNAL ERROR:can not attach network interface for vm
by Gao Yongwei 23 Jul '12

23 Jul '12

hello,i got a error message when use virsh attach-interface for a vm: first, list the vm's interface,there's no interface now. virsh # domiflist ubuntum-124 Interface Type Source Model MAC ------------------------------------------------------- then,i did an attach-interface action: virsh # attach-interface ubuntum-124 bridge br0 --persistent Interface attached successfully virsh # domiflist ubuntum-124 Interface Type Source Model MAC ------------------------------------------------------- vnet0 bridge br0 - 52:54:00:3d:d1:ea second,detach the interface: virsh # detach-interface ubuntum-124 bridge Interface detached successfully virsh # domiflist ubuntum-124 Interface Type Source Model MAC ------------------------------------------------------- 3rd,attach interface again,at this step ,i got erros like below: virsh # attach-interface ubuntum-124 bridge br0 --persistent error: Failed to attach interface error: internal error unable to execute QEMU command 'device_add': Duplicate ID 'net0' for device virsh # attach-interface ubuntum-124 bridge br0 error: Failed to attach interface error: internal error unable to execute QEMU command 'device_add': Duplicate ID 'net0' for device virsh # version Compiled against library: libvir 0.9.10 Using library: libvir 0.9.10 Using API: QEMU 0.9.10 Running hypervisor: QEMU 0.12.1 any one can help?thanks.

2 2

[libvirt-users] vm grub errors
by aprender-caminando＠riseup.net 22 Jul '12

22 Jul '12

Hello, I've set up a kvm host and used virt-install to create a new guest VM installed to logical volumes. It works great! However all subsequent guests I attempt to create the same way refuse to boot. They all get stuck at the grub rescue menu reporting "no such device". I tried installing a new guest and dropping to a shell just before finalizing the installation so I could examine the contents of grub.cfg To my eyes it actually looks just fine. It is referencing the correct virtual drive. Here is a pastebin with a few commands and output I thought might be relevant. http://pastebin.com/GwqbY7X7 Once I finalize the installation the same thing happens. Grub reports the same error. At the grub rescue prompt if I attempt to: ls (hd0,msdos1)/ error: unknown filesystem. In the host I can see that the logical volume where I installed the root partition of the VM above is in fact active. This is exactly the same way I installed the first VM on the same host and that one i still working fine. On a local machine I practiced setting up multiple VM's this way and had no problem so it's not an error I can reproduce anywhere other than the production server. Can anyone offer ideas of other things I should try or check?

2 1

[libvirt-users] Preferred CPU model not allowed by hypervisor
by Jared 22 Jul '12

22 Jul '12

Hi, all. I posted this message to libvir-list last night, but just realized that was geared toward development rather than support. Apologies to those who are subscribed to both for the dupe. I'm having a weird problem where libvirt/qemu/kvm won't let me use the model processor I have defined in my domain's config file. Instead, I get the error message in libvirtd.log that: warning : x86Decode:1346 : Preferred CPU model Nehalem not allowed by hypervisor; closest supported model will be used If I review the qemu log for that particular domain, I see that my CPU has been changed to this: -cpu kvm64,+lahf_lm,+popcnt,+sse4.2,+sse4.1,+ssse3 (in other places, I see it set to core2duo rather than kvm64) However, it *should* be Nehalem. For some background, I'm running kvm on a westmere proc, which is the successor to Nehalem. I'm specifying Nehalem as the target platform, though, to make it easier to migrate to another server if necessary. I do have this same problem if I set this to Westmere, though, so it's not unique to Nehalem. As for support and capabilities, libvirt correctly detects my host CPU as Westmere: $ virsh capabilities | grep model <model>Westmere</model> qemu-kvm does (as far as I can tell) support Nehalem: $ qemu-kvm -cpu ?model | grep Nehalem x86 Nehalem Intel Core i7 9xx (Nehalem Class Core i7) Nehalem is defined in qmeu's target-x86_64.conf: grep Nehalem /etc/qemu/target-x86_64.conf name = "Nehalem" model_id = "Intel Core i7 9xx (Nehalem Class Core i7)" And if I run a cpu check on the processor, it seems to work fine: $ qemu-kvm -cpu Nehalem,check VNC server running on `127.0.0.1:5900' So, I I'm creating the new domain as a virt-install with the qemu-kvm backend as follows: virt-install --name=test --ram=1024 --arch=x86_64 --vcpus=2 --cpu=Nehalem --virt-type=kvm <SNIP> This results in the following cpu configuration: <cpu mode='custom' match='exact'> <model fallback='allow'>Nehalem</model> </cpu> But then, when I start this domain, I get the error message posted above. Any ideas what's going on here? I'm at a loss, and unfortunately I don't have much experience with kvm/libvirt just yet so I don't know what I should be focusing on for troubleshooting. Would appreciate any suggestions or guidance. Thanks. -- Jared

1 0

[libvirt-users] duplicate domain ids!?
by matt cowan 20 Jul '12

20 Jul '12

Somehow I've ended up with duplicate domids. domid=15 name=node14 (names sanitized) # virsh list --all Id Name State ---------------------------------------------------- 1 node1 running 2 node2 running 3 node3 running 5 node4 running 6 node5 running 7 node6 running 8 node7 running 9 node8 running 10 node9 running 11 node10 running 12 node11 running 13 node12 running 14 node13 running 15 node14 running 15 node14 running 16 node16 running node15 is up and running, can ssh into it. virt manager only lists 15 guests (ie, doesn't show the duplicate domid) # virsh domid node14 15 # virsh domid node15 15 Doesn't *seem* to be causing a problem (other than above virsh/virt-manager issues), but this shouldn't happen right? Any potential for screwiness I should be concerned about? I was actually checking that node15 (a test system we don't need running at the moment) wasn't running when I noticed this; now I'm tempted to just leave it be until a maintenance period when node14 (production db server) can afford potential downtime, at which point I'd try 'shutdown -h now' within node14 and then 'virsh shutdown node15; virsh start node14'? node15 has been up for 9 days, other nodes for 50 days, so guess it's been like this for 9 days. hrm... yum.log also shows libvirt-client and libvirt-python were both updated 9 days ago. suggestions? thanks. -matt Scientific Linux release 6.2 (Carbon) 2.6.32-220.17.1.el6.x86_64 qemu-kvm-0.12.1.2-2.209.el6_2.4.x86_64 libvirt-0.9.10-21.el6.x86_64 libvirt-client-0.9.10-21.el6.x86_64 libvirt-python-0.9.10-21.el6.x86_64 virt-manager-0.9.0-7.el6.x86_64 python-virtinst-0.600.0-5.el6.noarch

2 1

[libvirt-users] Virsh Failing to Snapshot VMWare VM with Multiple Disks
by Elizabeth Griffith 20 Jul '12

20 Jul '12

I am trying to use virsh's snapshot-create command on a VMWare vm that has multiple disks in its device list, but the command is failing with the error: "Could not create snapshot: FileNotFound - file [pool] filename.vmx". However, this command works if my vm only has one disk in its device list. I am using libvirt 0.9.10, and the storage pool is nfs mounted between the machine that I am running virsh on and the hypervisor. Can anyone tell me what I am doing wrong or if this is even supported by virsh? Thanks.

3 4

[libvirt-users] Matching host and guest CPU
by Alex 19 Jul '12

19 Jul '12

Hi, I have an fc17 server with an Opteron 6128 with a few fc17/16 guests. How can I be sure I'm best matching the guest CPU with that of the server? I've used virt-manager to create the guests, and it currently shows the processor is a "Phenom(tm) 9550 Quad-Core": processor : 1 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom(tm) 9550 Quad-Core Processor stepping : 3 microcode : 0x1000065 cpu MHz : 2000.138 cache size : 512 KB fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch npt bogomips : 4000.27 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: The guests seem to run very slowly, and just wondered if this may be the cause. Can someone recommend some basic optimizations I may already be missing from my guest config? <domain type='kvm'> <name>boxtech-new</name> <uuid>66887405-a34b-2ec2-1d6c-308aafb1f32e</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>2</vcpu> <os> <type arch='x86_64' machine='pc-0.14'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu match='exact'> <model>Opteron_G3</model> <vendor>AMD</vendor> <feature policy='require' name='skinit'/> <feature policy='require' name='vme'/> <feature policy='require' name='mmxext'/> <feature policy='require' name='fxsr_opt'/> <feature policy='require' name='cr8legacy'/> <feature policy='require' name='ht'/> <feature policy='require' name='3dnowprefetch'/> <feature policy='require' name='3dnowext'/> <feature policy='require' name='wdt'/> <feature policy='require' name='extapic'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='osvw'/> <feature policy='require' name='cmp_legacy'/> <feature policy='require' name='3dnow'/> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/boxtech-new.img'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' unit='0'/> </disk> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='52:54:00:bc:55:64'/> <source bridge='br0'/> <model type='virtio'/> <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='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='0x06' function='0x0'/> </memballoon> </devices> </domain> Thanks, Alex

1 0