July 2012 - Users - libvirt List Archives

[libvirt-users] some problem with snapshot by libvirt
by xingxing gao 21 Nov '14

21 Nov '14

Hi,all,i am using libvirt to manage my vm,in these days i am testing the libvirt snapshot ,but meet some problem: the snapshot was created from this command: snapshot-create-as win7 --disk-only --diskspec vda,snapshot=external --diskspec hda,snapshot=no but when i tried to revert from the snapshot which created from the above command ,i got error below: virsh # snapshot-revert win7 1338041515 --force error: unsupported configuration: revert to external disk snapshot not supported yet version: virsh # version Compiled against library: libvir 0.9.4 Using library: libvir 0.9.4 Using API: QEMU 0.9.4 Running hypervisor: QEMU 1.0.93

4 8

[libvirt-users] About IBM PowerVM hypervisor support
by Dennis Chen 22 Nov '12

22 Nov '12

Hi, I noticed that libvirt support the following hypervisors currently: * The KVM/QEMU <http://libvirt.org/drvqemu.html> Linux hypervisor * The Xen <http://libvirt.org/drvxen.html> hypervisor on Linux and Solaris hosts. * The LXC <http://libvirt.org/drvlxc.html> Linux container system * The OpenVZ <http://libvirt.org/drvopenvz.html> Linux container system * The User Mode Linux <http://libvirt.org/drvuml.html> paravirtualized kernel * The VirtualBox <http://libvirt.org/drvvbox.html> hypervisor * The VMware ESX and GSX <http://libvirt.org/drvesx.html> hypervisors * The VMware Workstation and Player <http://libvirt.org/drvvmware.html> hypervisors * The Microsoft Hyper-V <http://libvirt.org/drvhyperv.html> hypervisor /"the goal of libvirt: *to provide a common and stable layer sufficient to securely manage domains on a node, possibly remote*."/ My question is, does redhat's libvirt team have the plan to support IBM PowerVM hypervisor? If the answer is NO, what's the reason to make the support for IBM PowerVM hypervisor doesn't make sense... BRs, Dennis

5 17

[libvirt-users] virsh list not working with xen 4
by Rogério Vinhal Nunes 21 Sep '12

21 Sep '12

Hi, I'm having some trouble to get libvirt to show the correct power state of my virtual machines. I'm using Ubuntu 10.04 + Xen 4.1.1 + libvirt 0.8.8. virsh list --all only shows turned off machines registered in xend. If I turn them on, they just "disappear", and when I start machines directly from xml, they just doesn't appear at all. Libvirt is correctly connecting to xen as I can use the other commands fine, just the list option doesn't seem to work at all. What can I do to change that? # virsh version Compiled against library: libvir 0.8.8 Using library: libvir 0.8.8 Using API: Xen 3.0.1 Running hypervisor: Xen 4.1.0

2 1

[libvirt-users] Live Block Migration with additional attached storage
by Chun-Hung Chen 07 Sep '12

07 Sep '12

Dear all, I am planning to use live block migration with one VM running on local disk and also attached additional disk from iSCSI or other shared storage. When block migration, not only local VM disk is copied to the destination but also the attached additional disk from shared storage. It is not desired in this situation. I just want the local VM disk is copied. Is there anyway to do this scenario? Does the concept of storage pool help this? I browse the source code but don't find hints right now. Thanks. Regards, Arnose

2 5

[libvirt-users] Using virsh to load scripts for the guest machine
by Mauricio Tavares 02 Aug '12

02 Aug '12

Right on the top of http://www.centos.org/docs/5/html/5.2/Virtualization/chap-Virtualization-Ma…, it seems to imply you can load/send scripts to the vm guest using virsh. Is that possible? How and what are the limitations? Can you query the vm guest?

4 7

[libvirt-users] live migration causes guest system to crash when accessing the network
by Sebastian J. Bronner 30 Jul '12

30 Jul '12

Hi all, we've been using libvirt/KVM ever since it was included in Ubuntu 10.04 LTS. At first, it wasn't possible to do live block migrations. We got used to that. And now block migration has been possible since Ubuntu 12.04 LTS. And we're excited. There's just one hitch: Many of migrations have the result that the system is successfully migrated, but will no longer run. Sometimes, it still runs but can't access the network. Sometimes it just freezes completely, and doesn't even show a kernel panic on the console. And sometimes the network still works but will crash when sending ICMP messages from within the guest. And every once in a while the guest system will continue to run. Most of our guests use virtio for both networking and storage. The guest OS's are mostly Ubuntu 12.04, but also one 11.04 and several 10.04's. A few older ones are still around, as well. The older ones don't support virtio though, so here we use the emulated intel e1000 network card and IDE storage. The guests are connected to a common bridge on the node, which provides access to the outside network. There is no NAT. Oh, and I read that different CPU capabilities (flags, etc.) can cause live migrations to fail. So I used the recommended procedure to determine the least common denominator of the CPUs on our nodes and configured all the guests to use only those CPU capabilities. After a restart, I verified that the kernel correctly identified the configured CPU type and flags. Does anyone have an idea how I can go about debugging the issue? Or has anyone experienced this issue and found a solution? Cheers, Sebastian -- *Sebastian J. Bronner* Administrator D9T GmbH - Magirusstr. 39/1 - D-89077 Ulm Tel: +49 731 1411 696-0 - Fax: +49 731 3799-220 Geschäftsführer: Daniel Kraft Sitz und Register: Ulm, HRB 722416 Ust.IdNr: DE 260484638 http://d9t.de - D9T High Performance Hosting info(a)d9t.de

1 0

[libvirt-users] mouse pointer not in sync after live migration
by Stefan 30 Jul '12

30 Jul '12

Hi everybody, I am using Opennebula 3.6 on a Debian Squeeze system. My configuration: Node-A kvm --version QEMU emulator version 1.0 (qemu-kvm-1.0 Debian 1.0+dfsg-8~bpo60+1), Copyright (c) 2003-2008 Fabrice Bellard virsh --version 0.9.11.3 Node-B kvm --version QEMU emulator version 1.0 (qemu-kvm-1.0 Debian 1.0+dfsg-8~bpo60+1), Copyright (c) 2003-2008 Fabrice Bellard virsh --version 0.9.11.3 After live-migration, my mouse pointer is not in sync. I just write an email to the opennebula-mailinglist, but maybe this a problem from libvirt or kvm? http://lists.opennebula.org/pipermail/users-opennebula.org/2012-July/009643… thanks in advance Stefan

1 0

Re: [libvirt-users] libvirt-users Digest, Vol 31, Issue 39
by Borden Rhodes 28 Jul '12

28 Jul '12

Hey everybody, Thanks for the help. It turns out that net.ipv4.ip_forward was set to = 0 and I had to change it to = 1, which I found from the excellent http://wiki.libvirt.org/page/Guest_can_reach_host%2C_but_can%27t_reach_outs… guide. All's well in the state of Denmark and I should be able to set to figuring out how to get libvirt to play nicely with Firestarter and Network Manager. Speaking from my own experience, when people are fooling around with the documentation, they may want to consider the following things: 1) In Debian (and probably Ubuntu by association), the command to restart libvirtd is (sudo) service libvirt-bin restart. For *tards like me who get easily confused and might think that a libvirt daemon is something specific to Red Hat, etc., it might be worth making this distinction. I'll probably also whine to the Debian to make this point clearer in their own documentation since it's not the libvirt project's fault that Debian feels compelled to 'improve' things. 2) Again, a *tard like me didn't think to look for the Troubleshooting page under the General Project Documentation section of the Wiki. Granted, I realise that makes me especially *tarded because it's, like, the first item after the table of contents, but someone like me expects Troubleshooting to be its own section in the ToC and/or linked generously within the sections discussing networking concepts. Perhaps it might be more useful to start a Troubleshooting sub-subsection under SS 1.7 and link all of the network troubleshooting docs to that? 3) One of the frustrations I had was trying to figure out what the responsibilities were for each of libvirt, virt-manager and qemu/kvm, especially in the context of seeing all of the settings jumbled together in virt-manager (I'm a little bash-phobic). So I'm not sure if this is libvirt's 'problem,' but as good as Virtual Networking concepts page is, it doesn't quite explain the difference between what appears in virt-manager as 'Virtual Networks' and 'Network Interfaces' under the connection settings. I think the difference is that the former is for simple NAT routing whereas the latter is for advanced bridging, but when I was setting up my virtual machines, I didn't understand which I had to configure and whether I had to set up both. Again, thanks for the help. I really appreciate it. Borden

1 0

[libvirt-users] Can't NAT in KVM
by Borden Rhodes 28 Jul '12

28 Jul '12

Good morning, list, I've been trying to get my KVM virtual machines to connect to the Interwebs for the last 3 hours with no success. I'm running Debian Wheezy (fully patched) and building virtual machines using KVM in Virt Manager. With the default, factory settings shown in virt manager, I have a default virtual network with the device name virbr0, which starts on boot and uses the default IPv4 subnets. I also have the default lo (loopback) network interface. I have tried creating a Windows 8 Release Preview machine and a Kubuntu Live CD machine. Despite recognising the hardware and network interface, neither machine will connect to the Internet. From what I can see in both virtual machines, it seems that neither is getting a DHCP lease from virbr0. I'm not sure what's broken or where to start looking for trouble because both the logs and the documentation are fairly sparse. Other possibly relevant information: I have a simple firewall configured with Firestarter in Wheezy. I use Network Manager to manage my only wireless connection to the world. I don't want to set up any fancy bridging or override /etc/interfaces because I only use virtual machines rarely but I rely on Network Manager to set up my laptop's networks so I don't have to. Any suggestions on how I can plug the v-machines to the web? With thanks, Borden

4 6

[libvirt-users] How can I make sVirt work with LXC (libvirt-0.9.13)?
by David Kang 26 Jul '12

26 Jul '12

Hi, I've installed libvirt-0.9.13 on RHEL6.2 from the source code. I cannot make sVirt working with LXC. (sVirt works well with KVM, though.) I can start an LXC instance, but the label of the process is not right. Can someone help me? I tried to change /etc/libvirtd/lxc.conf file to explicitly enable security_driver = "selinux". But it ends up with error saying "error : virSecurityDriverLookup:74 : internal error Security driver selinux not found". SELinux is in a permissive mode but is not enforcing. The current situation is as follows: * The label of an LXC container is not properly done: $ ps auxZ | grep lxc unconfined_u:system_r:virtd_t:s0-s0:c0.c1023 root 27998 0.0 0.0 34716 1160 ? Ss 11:54 0:00 /usr/libexec/libvirt_lxc --name instance-0000001f --console 16 --security=none --handshake 19 --background --veth veth1 * This is the lable of libvirtd process: $ ps auxZ | grep libvirtd unconfined_u:system_r:virtd_t:s0-s0:c0.c1023 root 27376 0.1 0.0 919052 5324 ? Sl 11:51 0:00 libvirtd --daemon * Here is the xml file that I used to run LXC instance, which was generated by OpenStack: <domain type="lxc"> <uuid>621adc56-2103-465c-bafd-1d0b51bea3a0</uuid> <name>instance-0000001f</name> <memory>2097152</memory> <vcpu>1</vcpu> <os> <type>exe</type> <cmdline>console=ttyS0</cmdline> <init>/sbin/init</init> </os> <clock offset="utc"/> <devices> <filesystem type="mount"> <source dir="/usr/local/nova/instances/instance-0000001f/rootfs"/> <target dir="/"/> </filesystem> <interface type="bridge"> <mac address="fa:16:3e:1e:33:f4"/> <model type="virtio"/> <source bridge="br100"/> <filterref filter="nova-instance-instance-0000001f-fa163e1e33f4"> <parameter name="IP" value="10.0.0.4"/> <parameter name="DHCPSERVER" value="10.0.0.3"/> <parameter name="PROJNET" value="10.0.0.0"/> <parameter name="PROJMASK" value="255.255.0.0"/> </filterref> </interface> <console type="pty"/> </devices> </domain> * Svirt works well with KVM as is shown below: $ ps auxZ | grep qemu system_u:system_r:svirt_t:s0:c128,c132 root 22710 6.9 0.2 895040 34332 ? Sl 11:17 0:07 /usr/libexec/qemu-kvm -name instance-0000001b -S -M pc-0.14 -cpu core2duo,+lahf_lm,+dca,+pdcm,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -uuid 12716b13-001c-40de-9537-ca847aead70b -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0000001b.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -kernel /usr/local/nova/instances/instance-0000001b/kernel -initrd /usr/local/nova/instances/instance-0000001b/ramdisk -append root=/dev/vda console=ttyS0 -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/usr/local/nova/instances/instance-0000001b/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=17,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:7a:5e:b6,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/usr/local/nova/instances/instance-0000001b/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 Thanks, David ---------------------- Dr. Dong-In "David" Kang Computer Scientist USC/ISI

1 1

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

26 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. ---------------------------------------------------------------------------------------------------

3 2

[libvirt-users] No /dev/tty device within LXC guest?
by Yufang Zhang 26 Jul '12

26 Jul '12

Hi all, When I create a LXC guest(RHEL5.4) via libvirt, the guest could boot successfully. I could ping to guest, but can not ssh into the it. The secure log in the guest shows that this is due to lack of '/dev/tty' device: # tail /path/to/rootfs/of/container/var/log/secure Jul 27 04:25:25 xen2143v sshd[671]: Accepted password for zhangyufang from 10.0.0.1 port 34102 ssh2 Jul 27 04:25:25 xen2143v sshd[671]: pam_unix(sshd:session): session opened for user zhangyufang by (uid=0) Jul 27 04:25:25 xen2143v sshd[671]: pam_loginuid(sshd:session): set_loginuid failed *Jul 27 04:25:25 xen2143v sshd[671]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session* *Jul 27 04:25:25 xen2143v sshd[674]: error: open /dev/tty failed - could not set controlling tty: No such file or directory* *Jul 27 04:25:25 xen2143v sshd[673]: Received disconnect from 10.0.0.1: 11: disconnected by user* The xml of the guest: # virsh --connect lxc:/// dumpxml instance-00000034 <domain type='lxc' id='30090'> <name>instance-00000034</name> <uuid>8387e0f1-6df3-41c8-82ba-cde7d2b60844</uuid> <memory>524288</memory> <currentMemory>524288</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/var/lib/nova/instances/instance-00000034/rootfs'/> <target dir='/'/> </filesystem> <interface type='bridge'> <mac address='fa:16:3e:3c:1d:95'/> <source bridge='demonetbr0'/> <target dev='veth0'/> <filterref filter='nova-instance-instance-00000034-fa163e3c1d95'> <parameter name='DHCPSERVER' value='10.0.0.1'/> <parameter name='IP' value='10.0.0.3'/> </filterref> </interface> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> </console> </devices> </domain> Could anyone point me to where the problem is? Thanks. Best Regards. Yufang

1 0

[libvirt-users] VM dies with error regarding "virConnectNumOfInterfaces"
by Helga Velroyen 25 Jul '12

25 Jul '12

Hi! I ran into a problem using a USB device and was wondering if you could help me. I'm running a Win XP SP3 in a VM with libvirt on a Xubuntu 11.10. I configured it to talk to several USB devices. With one particular device (a Phonak Compilot[1], admittedly a probably rather unusual device), the VM dies with the following error in the libvirtd.log: 2012-07-20 21:04:19.591+0000: 1282: error : virConnectNumOfInterfaces:9803 : this function is not supported by the connection driver: virConnectNumOfInterfaces 2012-07-20 21:05:05.762+0000: 1276: error : qemuMonitorIO:603 : internal error End of file from monitor This happens no matter if is it the only configured USB device or if there is another USB device present in the config or not. I configured it doing the following steps: - I looked up the vendor / product ID using lsub Bus 001 Device 003: ID 180f:1002 (Interestingly, it does not show a name of the device here.) - I added it to the VM's xml configuration using virsh / edit $vmname <domain> ... <devices> ... <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x180f'/> <product id='0x1002'/> </source> </hostdev> ... </devices> </domain> - I run the VM using the virt-manager UI. Any ideas what the problem could be? Do I need to run/configure differently than how I did it? To me it sounds as if there is some implementation missing? Is there a workaround for it? I hope you can give me some clues. Thank you! Helga [1] http://www.phonak.com/com/b2c/en/products/accessories/compilot-tvlink-s/ove…

2 4

[libvirt-users] virsh iface-list error
by Arun Sharma 25 Jul '12

25 Jul '12

Hello Facing below error while trying to access the iface-list. # virsh iface-list *error: Failed to list active interfaces error: this function is not supported by the connection driver: virConnectNumOfInterfaces* root@kvm-1:/usr/local/src/libvirt# virsh list Id Name State ---------------------------------------------------- 1 vm1 running After some finding, i saw it require me to build libvirt with --with-netcf. I tried that too but still facing the same problem. Here are the steps perform on Ubuntu 1204 (64 bit) + qemu KVM. # git clone git://libvirt.org/libvirt.git # ./autogen.sh --prefix=/usr --with-qemu --with-init-script=upstart --with-yajl --with-netcf --with-network --with-init-script=upstart --with-libvirtd # make # make install # /usr/sbin/libvirtd & # /usr/sbin/dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases --dhcp-lease-max=253 --dhcp-no-override Pl. let me know what could be the problem? Thanks Arun

4 3

[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

[libvirt-users] virsh define function question
by zhanggp 19 Jul '12

19 Jul '12

Hi, How do I view the libvirt virsh domxml-to-native function implementation? I think this function contains some error. Because we use libvirt to manage some host and vms on vmware hypervisor. We use openenbula generate a template for libvirt ,such as my attachment windows2008.xml. but when i use domxml-to-native to convert xml file to vmware config file vmx as below. This may not be accurate. For example: 1. guestOs type : could I config this parameter in xml file ,so after domxml-to-native to vmware.vmx , guestOS in my vmx file is "windows7srv-64 ". And also my pciBridge disappeared ! So could someone help me and tell us about 'virsh-c the esx :/ /@host?no_verify=1 define windows2008.xml' function realization。 Thanks all! virsh # domxml-to-native vmware-vmx windows2008.xml .encoding = "UTF-8" config.version = "8" virtualHW.version = "7" guestOS = "other-64" uuid.bios = "42 11 25 27 fd b6 7b 6d-72 3f 75 c6 25 fe ef 3e" displayName = "windows2008" memsize = "2048" numvcpus = "2" sched.cpu.shares = "normal" ide0:0.present = "true" ide0:0.deviceType = "ata-hardDisk" ide0:0.fileName = "/vmfs/volumes/349969f9-070dee8d/./windows2008.vmdk" floppy0.present = "false" floppy1.present = "false" ethernet0.present = "true" ethernet0.virtualDev = "e1000" ethernet0.networkName = "VM Network" ethernet0.connectionType = "bridged" ethernet0.addressType = "vpx" ethernet0.generatedAddress = "00:50:56:91:00:07" svga.vramSize = "8388608" zhanggp --------------------------------------------------------------------------------------------------- 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. ---------------------------------------------------------------------------------------------------

2 1