- Users - libvirt List Archives

[libvirt-users] USB Passthrough of two identical devices
by Hendrik Friedel 19 Apr '12

19 Apr '12

Hello, I re-post my question from some days ago, as I got no reply.. Please let me know, if my question is unclear, or if I can do anything to make answering it easier. I appreciate your help. Greetings, Hendrik Hello, I'd like to pass throug two identical devices to my VM. (using libvirt, guest is debian). For one device, it works like this: <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x4fa'/> <product id='0x2490'/> </source> <boot order='2'/> </hostdev> But now, I have another device just like this one: Bus 001 Device 007: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter Bus 001 Device 005: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter Unfortunately, only one of these two devices appears for the Guest, even if I duplicate the above entry. Now, there's this option to pass devices: <address bus='0x06' device='0x02''/> But the Bus/Device can/might change... Maybe this can be overcome by udev (and maybe this is the default in ubuntu? can someone confirm?) I have tried the latter syntax aswell. Here the log-file: Code: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc -cpu qemu32 -enable-kvm -m 256 -smp 1 -name WG -uuid fd90f0d6-122c-992f-a399-4105ee30d6e3 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/WG.monitor,server,nowait -monitor chardev:monitor -boot c -drive file=/var/lib/zentyal/machines/WG/WG-Test.qcow2,if=scsi,index=0,boot=on,format=qcow2 -net nic,macaddr=00:16:3e:5d:c7:9e,vlan=0,name=nic.0 -net tap,fd=29,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice mouse -vnc 0.0.0.0:0,password -k de -vga cirrus -usbdevice host:04fa:2490 -usbdevice host:04fa:2490 usb_create: no bus specified, using "usb.0" for "usb-host" husb: open device 1.5 husb: config #1 need -1 husb: 1 interfaces claimed for configuration 1 husb: grabbed usb device 1.5 usb_create: no bus specified, using "usb.0" for "usb-host" What's odd in this: -usbdevice host:04fa:2490 -usbdevice host:04fa:2490 And this, although I had used the bus/device syntax... So, what would you recommend? Regards, Hendrik

1 0

[libvirt-users] CfP 7th Workshop on Virtualization in High-Performance Cloud Computing (VHPC'12)
by VHPC 12 19 Apr '12

19 Apr '12

we apologize if you receive multiple copies of this CFP. =================================================================== CALL FOR PAPERS 7th Workshop on Virtualization in High-Performance Cloud Computing VHPC '12 as part of Euro-Par 2012, Rhodes Island, Greece =================================================================== Date: August 28, 2012 Workshop URL: http://vhpc.org SUBMISSION DEADLINE: Rolling abstract submission June 4, 2012 - Full paper submission SCOPE: Virtualization has become a common abstraction layer in modern data centers, enabling resource owners to manage complex infrastructure independently of their applications. Conjointly, virtualization is becoming a driving technology for a manifold of industry grade IT services. The cloud concept includes the notion of a separation between resource owners and users, adding services such as hosted application frameworks and queueing. Utilizing the same infrastructure, clouds carry significant potential for use in high-performance scientific computing. The ability of clouds to provide for requests and releases of vast computing resources dynamically and close to the marginal cost of providing the services is unprecedented in the history of scientific and commercial computing. Distributed computing concepts that leverage federated resource access are popular within the grid community, but have not seen previously desired deployed levels so far. Also, many of the scientific data centers have not adopted virtualization or cloud concepts yet. This workshop aims to bring together industrial providers with the scientific community in order to foster discussion, collaboration and mutual exchange of knowledge and experience. The workshop will be one day in length, composed of 20 min paper presentations, each followed by 10 min discussion sections. Presentations may be accompanied by interactive demonstrations. TOPICS Topics of interest include, but are not limited to: Higher-level cloud architectures, focusing on issues such as: - Languages for describing highly-distributed compute jobs - Workload characterization for VM-based environments - Optimized communication libraries/protocols in the cloud - Cross-layer optimization of numeric algorithms on VM infrastructure - System and process/bytecode VM convergence - Cloud frameworks and API sets - Checkpointing/migration of large compute jobs - Instrumentation interfaces and languages - VMM performance (auto-)tuning on various load types - Cloud reliability, fault-tolerance, and security - Software as a Service (SaaS) architectures - Research and education use cases - Virtualization in cloud, cluster and grid environments - Cross-layer VM optimizations - Cloud use cases including optimizations - VM-based cloud performance modelling - Performance and cost modelling Lower-level design challenges for Hypervisors, VM-aware I/O devices, hardware accelerators or filesystems in VM environments, especially: - Cloud, grid and distributed filesystems - Hardware for I/O virtualization (storage/network/accelerators) - Storage and network I/O subsystems in virtualized environments - Novel software approaches to I/O virtualization - Paravirtualized I/O subsystems for modified/unmodified guests - Virtualization-aware cluster interconnects - Direct device assignment - NUMA-aware subsystems in virtualized environments - Hardware Accelerators in virtualization (GPUs/FPGAs) - Hardware extensions for virtualization - VMMs/Hypervisors for embedded systems Data Center management methods, including: - QoS and and service levels - VM cloud and cluster distribution algorithms - VM load-balancing in Clouds - Hypervisor extensions and tools for cluster and grid computing - Fault tolerant VM environments - Virtual machine monitor platforms - Management, deployment and monitoring of VM-based environments - Cluster provisioning in the Cloud PAPER SUBMISSION Papers submitted to the workshop will be reviewed by at least two members of the program committee and external reviewers. Submissions should include abstract, key words, the e-mail address of the corresponding author, and must not exceed 10 pages, including tables and figures at a main font size no smaller than 11 point. Submission of a paper should be regarded as a commitment that, should the paper be accepted, at least one of the authors will register and attend the conference to present the work. Accepted papers will be published in the Springer LNCS series - the format must be according to the Springer LNCS Style. Initial submissions are in PDF; authors of accepted papers will be requested to provide source files. Format Guidelines: http://www.springer.de/comp/lncs/authors.html Style template: ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip Abstract Submission Link: http://edas.info/newPaper.php?c=11943 IMPORTANT DATES Rolling abstract submission June 4, 2012 - Full paper submission June 29, 2012 - Acceptance notification July 20, 2012 - Camera-ready version due August 28, 2012 - Workshop Date CHAIR Michael Alexander (chair), TU Wien, Austria Gianluigi Zanetti (co-chair), CRS4, Italy Anastassios Nanos (co-chair), NTUA, Greece PROGRAM COMMITTEE Paolo Anedda, CRS4, Italy Giovanni Busonera, CRS4, Italy Brad Calder, Microsoft, USA Roberto Canonico, University of Napoli Federico II, Italy Tommaso Cucinotta, Alcatel-Lucent Bell Labs, Ireland Werner Fischer, Thomas-Krenn AG, Germany William Gardner, University of Guelph, USA Marcus Hardt, Forschungszentrum Karlsruhe, Germany Sverre Jarp, CERN, Switzerland Shantenu Jha, Louisiana State University, USA Xuxian Jiang, NC State, USA Nectarios Koziris, National Technical University of Athens, Greece Simone Leo, CRS4, Italy Ignacio Llorente, Universidad Complutense de Madrid, Spain Naoya Maruyama, Tokyo Institute of Technology, Japan Jean-Marc Menaud, Ecole des Mines de Nantes, France Dimitrios Nikolopoulos, Foundation for Research&Technology Hellas, Greece Jose Renato Santos, HP Labs, USA Walter Schwaiger, TU Wien, Austria Yoshio Turner, HP Labs, USA Kurt Tutschku, University of Vienna, Austria Lizhe Wang, Indiana University, USA Chao-Tung Yang, Tunghai University, Taiwan DURATION: Workshop Duration is one day. GENERAL INFORMATION The workshop will be held as part of Euro-Par 2012. Euro-Par 2012: http://europar2012.cti.gr/

1 0

[libvirt-users] Problems using latest qemu-kvm and latest libvirt ( hvm missing )
by Bhasker C V 18 Apr '12

18 Apr '12

Hi all I have faced this issue already and the solution was to go back to a old version of qemu-kvm and/or libvirt and things start falling into place but this time I would want to solve this. I have used these versions as per the o/p of the commands below. To jumpstart a new machine which is libvirt capable, it always is a hastle to find out which of the version combination of libvirt,qemu-kvm will work. Just by picking the latest of the two versions does not help and ends up not supporting hvm at all $ sudo virsh capabilities <capabilities> <host> <uuid>34373030-3635-435a-4a32-313230485156</uuid> <cpu> <arch>x86_64</arch> <model>Westmere</model> <vendor>Intel</vendor> <topology sockets='2' cores='4' threads='2'/> <feature name='rdtscp'/> <feature name='pdpe1gb'/> <feature name='dca'/> <feature name='pdcm'/> <feature name='xtpr'/> <feature name='tm2'/> <feature name='est'/> <feature name='smx'/> <feature name='vmx'/> <feature name='ds_cpl'/> <feature name='monitor'/> <feature name='dtes64'/> <feature name='pclmuldq'/> <feature name='pbe'/> <feature name='tm'/> <feature name='ht'/> <feature name='ss'/> <feature name='acpi'/> <feature name='ds'/> <feature name='vme'/> </cpu> <power_management/> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> </uri_transports> </migration_features> </host> </capabilities> $ virsh --version 0.9.11 $ qemu-system-x86_64 --version QEMU emulator version 1.0,1 (qemu-kvm-1.0.1), Copyright (c) 2003-2008 Fabrice Bellard $ sudo virsh uri qemu:///system $ sudo virsh version Compiled against library: libvir 0.9.11 Using library: libvir 0.9.11 Using API: QEMU 0.9.11 error: failed to get the hypervisor version error: internal error Cannot find suitable emulator for x86_64 $ which kvm /usr/local/bin/kvm Can someone tell me, please, what is the version of qemu-kvm which will work well with the latest libvirt 0.9.11 ? since clearly the latest versions of qemu-kvm and libvirt are not compatible fully (atleast not hvm). Even better if this is documented somewhere visible so that a lot of time can be saved in iterating through the versions of qemu-kvm to find out which one will work. -- Bhasker C V Secure Mails: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4D05FEEC54E47413

1 1

[libvirt-users] [API reference] Are there XML-handling API to retrieve info directly from xml configure file
by Zhihua Che 18 Apr '12

18 Apr '12

Hi, everyone I'm writing a application using libvirt and need to query guest os's virtual network interface usage, like bytes read or written through a given interface. I know int virDomainInterfaceStats(virDomainPtr dom, const char * path, virDomainInterfaceStatsPtr stats, size_t size) is designed for my purpose but I 'm not sure how I determine the second parameter path. I'm now think of determining the virtual interface by parsing the domain's xml configure file. But I don't find that libvirt supply such functions, that means, I have to resort to other library lik libxml? thanks

4 15

[libvirt-users] Guests can't connect to each other
by Anthony Bourguignon 18 Apr '12

18 Apr '12

Hi, I'm using libvirt and qemu on Debian Wheezy. I'm having a strange behavior. Guests can't connect to each other when they're on the same host. On the host I'm using bonding (in active / backup mode) and vlan. It looks like this : eth0 \ / macvtap0 bond0 --- vlan222 eth1 / \ macvtap1 So I've got two guests, let's say A and B. When I try to ping B from A, it works : # ping -s 3000 -c 5 78.109.95.11 PING 78.109.95.11 (78.109.95.11) 3000(3028) bytes of data. 3008 bytes from 78.109.95.11: icmp_req=1 ttl=64 time=0.065 ms 3008 bytes from 78.109.95.11: icmp_req=2 ttl=64 time=2.19 ms 3008 bytes from 78.109.95.11: icmp_req=3 ttl=64 time=1.43 ms --- 78.109.95.11 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4001ms rtt min/avg/max/mdev = 0.065/0.960/2.197/0.760 ms But nothing happens when I try to ssh it (not even a timeout). You'll find enclosed the tcpdump captures on the source and the destination. It's the same when I use netcat in udp. At the same time, connection from the host to one guest is working perfectly. There is no iptables rule on the host, and nothing too on the guests. Here are the virsh dumpxml of the different components : # virsh dumpxml vm1 <domain type='kvm' id='11'> <name>vm1</name> <uuid>4eaaed00-c610-b468-ad55-600a0b4e244c</uuid> <memory>2048000</memory> <currentMemory>2048000</currentMemory> <memoryBacking> <hugepages/> </memoryBacking> <vcpu cpuset='0,2,4,8,10,12,14'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0,8'/> <vcpupin vcpu='1' cpuset='2,10'/> <vcpupin vcpu='2' cpuset='4,12'/> <vcpupin vcpu='3' cpuset='6,14'/> <vcpupin vcpu='4' cpuset='0,8'/> <vcpupin vcpu='5' cpuset='2,10'/> <vcpupin vcpu='6' cpuset='4,12'/> <vcpupin vcpu='7' cpuset='6,14'/> </cputune> <os> <type arch='x86_64' machine='pc-1.0'>hvm</type> <boot dev='hd'/> <boot dev='network'/> </os> <features> <acpi/> <apic/> </features> <cpu match='exact'> <model>Westmere</model> <vendor>Intel</vendor> <topology sockets='1' cores='8' threads='1'/> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds'/> <feature policy='require' name='smx'/> <feature policy='require' name='ss'/> <feature policy='require' name='vme'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='rdtscp'/> <feature policy='require' name='ht'/> <feature policy='require' name='dca'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='pclmuldq'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='acpi'/> <feature policy='require' name='monitor'/> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/vps/vm1'/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <interface type='network'> <mac address='52:54:00:0e:58:ae'/> <source network='vlan222'/> <target dev='macvtap0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' listen='0.0.0.0' keymap='fr'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vga' vram='9216' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> # virsh dumpxml vm2 <domain type='kvm' id='13'> <name>vm2</name> <uuid>4f760831-22b1-ff3b-26e7-6b3fec49e918</uuid> <memory>2048000</memory> <currentMemory>2048000</currentMemory> <memoryBacking> <hugepages/> </memoryBacking> <vcpu cpuset='1,3,5,7,9,11,13,15'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='1' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='2' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='3' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='4' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='5' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='6' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='7' cpuset='1,3,5,7,9,11,13,15'/> </cputune> <os> <type arch='x86_64' machine='pc-1.0'>hvm</type> <boot dev='hd'/> <boot dev='network'/> </os> <features> <acpi/> <apic/> </features> <cpu match='exact'> <model>Westmere</model> <vendor>Intel</vendor> <topology sockets='1' cores='4' threads='2'/> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds'/> <feature policy='require' name='smx'/> <feature policy='require' name='ss'/> <feature policy='require' name='vme'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='rdtscp'/> <feature policy='require' name='ht'/> <feature policy='require' name='dca'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='pclmuldq'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='acpi'/> <feature policy='require' name='monitor'/> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/vps/vm2'/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <interface type='network'> <mac address='52:54:00:cb:ce:41'/> <source network='vlan222'/> <target dev='macvtap1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5901' autoport='yes' listen='0.0.0.0' keymap='fr'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vga' vram='9216' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> # virsh net-dumpxml vlan222 <network> <name>vlan222</name> <uuid>2b763b5c-4ec1-9b5f-b29d-b7a7ea0f743d</uuid> <forward dev='vlan222' mode='bridge'> <interface dev='vlan222'/> </forward> </network> Thanks in advance to help me understand this issue.

3 7

[libvirt-users] help:any docs for open vswitch supporting?
by yue wang 18 Apr '12

18 Apr '12

hi everybody, i saw the new feature: network: support Open vSwitch. how to use this feature? are there any documents about that? i didn't find it on the website. Thanks, Heuye

5 6

[libvirt-users] USB Passthrough with two identical devices
by Hendrik Friedel 17 Apr '12

17 Apr '12

Hello, I'd like to pass throug two identical devices to my VM. (using libvirt, guest is debian). For one device, it works like this: <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x4fa'/> <product id='0x2490'/> </source> <boot order='2'/> </hostdev> But now, I have another device just like this one: Bus 001 Device 007: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter Bus 001 Device 005: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter Unfortunately, only one of these two devices appears for the Guest, even if I duplicate the above entry. Now, there's this option to pass devices: <address bus='0x06' device='0x02''/> But the Bus/Device can/might change... Maybe this can be overcome by udev (and maybe this is the default in ubuntu? can someone confirm?) I have tried the latter syntax aswell. Here the log-file: Code: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc -cpu qemu32 -enable-kvm -m 256 -smp 1 -name WG -uuid fd90f0d6-122c-992f-a399-4105ee30d6e3 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/WG.monitor,server,nowait -monitor chardev:monitor -boot c -drive file=/var/lib/zentyal/machines/WG/WG-Test.qcow2,if=scsi,index=0,boot=on,format=qcow2 -net nic,macaddr=00:16:3e:5d:c7:9e,vlan=0,name=nic.0 -net tap,fd=29,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice mouse -vnc 0.0.0.0:0,password -k de -vga cirrus -usbdevice host:04fa:2490 -usbdevice host:04fa:2490 usb_create: no bus specified, using "usb.0" for "usb-host" husb: open device 1.5 husb: config #1 need -1 husb: 1 interfaces claimed for configuration 1 husb: grabbed usb device 1.5 usb_create: no bus specified, using "usb.0" for "usb-host" What's odd in this: -usbdevice host:04fa:2490 -usbdevice host:04fa:2490 And this, although I had used the bus/device syntax... So, what would you recommend? Regards, Hendrik

1 0

[libvirt-users] What does cpu_time returned by virDomainGetCPUStats mean?
by Zhihua Che 17 Apr '12

17 Apr '12

hi, everyone. I find an 'interesting' thing involving virDomainGetCPUStats(). I call it for cpu usage consumed by a domain and get a array of virTypedParameter. My system is 2-core and hyperviser return 1 parameter per cpu. So the contents of the array is like this. virTypedParameter[0] { .fiedl = "cpu_time" .type = 4 .value.ul = 51640610899 } virTypedParameter[1] { .field = "cpu_time" .type = 4 .value.ul = 55302820304 } I thought this value store the run time of the cpu since last boot. But I find I was wrong because this value would increase until it wraps down and doesn't reset even the domain is restarted. So, what does this value mean? How can I get the CPU usage of the domain? I found nothing on the API reference doc page:-(. No word is related with the meaning of the returned array of virTypedParameter by virDomainGetCPUStats().

3 7

[libvirt-users] Ansis Atteka has invited you to use Google Talk
by Ansis Atteka 16 Apr '12

16 Apr '12

------------------------------------------------------------------------ Ansis Atteka has invited you to sign up for Google Talk so you can talk to each other for free over your computers. To sign-up, go to: http://www.google.com/accounts/NewAccount?service=talk&sendvemail=true&skip… Google Talk is a downloadable Windows* application that offers: - Free calls over your computer anytime, from anywhere, and for as long as you want - A simple and intuitive user interface for sending instant messages or making calls--no clutter, pop-ups or ads - Superior voice quality through just a microphone and computer speaker - Fast file transfers with no restrictions on file type After signing-up, download Google Talk and sign in with your new Google Account username and password. You can then begin inviting anyone you want to talk to for free. Google Talk works with any computer speaker and microphone, such as the ones built-in to many PC laptops today, as well as with wired and wireless headsets and USB phones. Google Talk also works across all firewalls. Google Talk is still in beta. Just like with Gmail, we're working hard to add features and make improvements, so we might also ask for your comments and suggestions periodically. We appreciate your help in making it even better! Thanks, The Google Talk Team To learn more about Google Talk before signing up, visit: http://www.google.com/talk/about.html (If clicking the URLs in this message does not work, copy and paste them into the address bar of your browser). * Not a Windows user? No problem. You can also connect to the Google Talk service from any platform using third-party clients (http://www.google.com/talk/otherclients.html)

1 0

[libvirt-users] [API reference] confused by CPU time term
by Zhihua Che 16 Apr '12

16 Apr '12

Hi, everyone I'm writing a virtual machine monitor based on libvirt. As I read the api reference, I found I'm confused by some terms. 1, What is cumulative I/O wait CPU time? API reference says that VIR_NODE_CPU_STATS_IOWAIT indicate cumulative I/O wait CPU time. I'm confused by this time. As far as I know, when cpu meets IO wait situation, it will schedule another task, so, how this IO wait time is accounted? 2, How do I get VCPU runtime? In my mind, VIR_DOMAIN_CPU_STATS_CPUTIME indicates the physical cpu time consumed by the domain. Is there any API by which I can query virtual CPU running stats in one domain?

3 3