Re: [kvm-devel] [ANN] gfxboot-disable
On Wed, 2007-24-10 at 10:53 -0500, Anthony Liguori wrote: > Just wanted to let people know, I wrote a stupid little tool that > modifies an ISO image to disable GFXBOOT. This lets you install OSes > that use GFXBOOT under KVM on Intel (Ubuntu, OpenSuSE). > > It's a horrible, horrible hack. But it works :-) Hey cool, thanks for this! -- Matthew Kent <[EMAIL PROTECTED]> http://magoazul.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] web interface?
On Wed, 2007-01-08 at 01:52 +1000, Paul J R wrote: > Hi guys, I had a quick question. > > I was playing around writing a php-based web interface for KVM. Well since KVM uses QEMU you'd really be writing a frontend for that. I've already seen a number of other projects for QEMU frontends, google should turn up a few. > Basically something that would allow you to use a tiny distro and let > you manage disk/net etc via php (atm its crude to say the least). > > It all seems relatively straight forward except for one component - the > console bits. I wanted to make it so you could click on your new vm, > then click on a "console" link and *poof* your console appears on your > web browser via an embedded java applet. Try http://www.oszoo.org/wiki/index.php/Free_Live_OS_Zoo > The problem is security, > Authenticating users on the page is simple enough, but i cant see a > method by which i could put a password on the vnc port in qemu? > http://fedoraproject.org/wiki/Releases/FeatureVirtSecurity is a project tasked with improving VNC security among other things, right now qemu doesn't have many options in that regard. > Ideally, what i would like to be able to do is when someone accesses the > console it sets the password randomly, then embed's it into the request. > Once everyone disconnects it resets the password (but thats not quite so > important at this point). > Xen has patches to qemu vnc for supporting passwords if you need a starting point. Though iirc they are pulled from the xenstore or whatever they call it, so it would need some work I'd imagine. -- Matthew Kent \ SA \ bravenet.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] web interface?
On Tue, 2007-31-07 at 17:57 +0100, Daniel P. Berrange wrote: > On Wed, Aug 01, 2007 at 01:52:39AM +1000, Paul J R wrote: > > Hi guys, I had a quick question. > > > > I was playing around writing a php-based web interface for KVM. > > Basically something that would allow you to use a tiny distro and let > > you manage disk/net etc via php (atm its crude to say the least). > > > > It all seems relatively straight forward except for one component - the > > console bits. I wanted to make it so you could click on your new vm, > > then click on a "console" link and *poof* your console appears on your > > web browser via an embedded java applet. The problem is security, > > Authenticating users on the page is simple enough, but i cant see a > > method by which i could put a password on the vnc port in qemu? > > Watch this space. I will be submitting patches to upstream QEMU either > today or tomorrow which will enable password support in VNC. It will > also provide for optional TLS encryption, and x509 certificates for both > client and server validation & authentication. Oh that's great stuff. I'll be sure to help test it out thoroughly. -- Matthew Kent \ SA \ bravenet.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] vnc improvement/bugfix patches from xen
After some issues with qemu vnc I happened upon the patches xen carries in xen-unstable.hg/tools/ioemu/patches/. After getting them to apply cleanly they have vastly improved my experience with vnc. I've taken these, omitted any that are xen specific or add extra features to qemu, and made some patches that apply cleanly to the latest qemu and kvm-33 sources. http://magoazul.com/proj/qemu/from_xen-unstable.hg_7c5c3aa858cc/ They seem to resolve the following issues for me: - having the vncviewer 4.1.2 die with: Rect too big: 4260x16389 at 4259,4323 exceeds 720x400 Aborted - having some odd stuck bits on the display when using the mouse via gdm or vim -> fixed by vnc-backoff-screen-scan/vnc-cleanup/vnc-fixes - occasionally having the vnc server go into an infinite loop thus screwing up the entire vm (verified with gdb) -> fixed by vnc-protocol-fixes - keypad not working -> fixed by vnc-keypad-handling [vnc-altgr-keysym/vnc-fix-text-display-shift-key not sure, included em anyway] Obviously I had *zero* hand in creating these patches and the original authors deserve the credit, I'm merely providing them for anyone experiencing the same issues. What I have done though is abused the patched qemu and kvm installs pretty thoroughly with vnc over the past week without issue. Also, in the course of this I read the recent 'Merging QEMU-DM upstream' slides from XenSummit by Anthony Liguori who I've seen on this list. Wondering if this is ongoing and I just duplicated some work that's already done? :) -- Matthew Kent <[EMAIL PROTECTED]> http://magoazul.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] kvm very slow
On Wed, 2007-01-08 at 07:22 +0200, Ulrich Schreiner wrote: > hi, > > im using a 64 bit fedora7 system with a quad-core processor to host > multiple virtual machines. > literally the exact same setup here > my current kernel is: > > Linux testserver 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 > x86_64 x86_64 x86_64 GNU/Linux > > (now there is a 2.6.22.1-33.fc7 to download, but i think it is not the > point here). > 2.6.22.1-41.fc7 x86_64 host > i installed > > kvm.x86_64: 31-1.fc8 kvm-33 > > because of a crash i reported as a bug with the older kvm module. > > this system starts a F7 image with the following command: > > /usr/bin/qemu-kvm > -net nic,macadr=52.54.00.12.34.57 > -net tap,script=./ifup.py,ifname=tap0 > -hda /var/qemu/vm_images/F7image.img > -boot c: -m 512 -vnc :2 -k de > > inside the image there is fedora 7, but a 32bit system. > almost exact same as here except using 32 bit fedora rawhide (development) guest running kernel 2.6.23-0.74.rc2.git1.fc8 > almost everything works (reboot hangs), but the system is extremely > slow! the clock inside the system is extremely slow: every *virtual* > second in the image is about two or more seconds in the *real* world. and I'm having the exact same issue here. The hardware clock works fine (least from the output of /proc/driver/rtc and hwclock) but the system time quickly falls behind in the guest, approx 0.5 secs for every 1 real second. No combination of selecting different clocksources in the guest, disabling CONFIG_NO_HZ, etc seemed to make any difference. And the fact is my fc7 x86_64 install works just great so I doubt its the host. What I did notice though was ACPI wasn't being enabled by default for the 32bit kernel with the message ACPI: no DMI BIOS year, acpi=force is required to enable ACPI and that the acpi_pm clocksource the x86_64 guest picked by default, which worked fine, was missing. eg: 2.6.23-0.74.rc2.git1.fc8 i686 default boot: /sys/devices/system/clocksource/clocksource0/available_clocksource pit jiffies tsc /sys/devices/system/clocksource/clocksource0/current_clocksource pit 2.6.23-0.74.rc2.git1.fc8 i686 with acpi=force: /sys/devices/system/clocksource/clocksource0/available_clocksource tsc acpi_pm pit jiffies /sys/devices/system/clocksource/clocksource0/current_clocksource tsc and now everything seems great, hardware and system time seem 1:1 again. Attached is a diff of the dmesg from each boot. As to why this is... -- Matthew Kent <[EMAIL PROTECTED]> http://magoazul.com --- dmesg.f7_32bit_default 2007-08-09 16:00:00.0 -0700 +++ dmesg.f7_32bit_forced_acpi 2007-08-09 15:59:55.0 -0700 @@ -34,21 +34,30 @@ ACPI: FACS 1FFF00C0, 0040 ACPI: APIC 1FFF0938, 0040 (r1 QEMU QEMUAPIC1 QEMU1) ACPI: no DMI BIOS year, acpi=force is required to enable ACPI -ACPI: Disabling ACPI support +ACPI: acpi=force override +ACPI: PM-Timer IO Port: 0xb008 +ACPI: Local APIC address 0xfee0 +ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) +Processor #0 6:2 APIC version 17 +ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) +IOAPIC[0]: apic_id 1, version 17, address 0xfec0, GSI 0-23 +ACPI: IRQ11 used by override. +Enabling APIC mode: Flat. Using 1 I/O APICs +Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3000 (gap: 2000:dffc) swsusp: Registered nosave memory region: 0009f000 - 000a swsusp: Registered nosave memory region: 000a - 000e8000 swsusp: Registered nosave memory region: 000e8000 - 0010 Built 1 zonelists in Zone order. Total pages: 129265 -Kernel command line: ro root=/dev/VolGroup00/LogVol00 console=tty0 console=ttyS0 debug -Found and enabled local APIC! +Kernel command line: ro root=/dev/VolGroup00/LogVol00 console=tty0 console=ttyS0 debug acpi=force mapped APIC to b000 (fee0) +mapped IOAPIC to a000 (fec0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c0817000 soft=c07f7000 PID hash table entries: 2048 (order: 11, 8192 bytes) -Detected 2400.636 MHz processor. +Detected 2400.387 MHz processor. Console: colour VGA+ 80x25 console [tty0] enabled console [ttyS0] enabled @@ -75,7 +84,7 @@ .text : 0xc040 - 0xc063074d (2241 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. SLUB: Genslabs=22, HWalign=64, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 -Calibrating delay using timer specific routine.. 9619.97 BogoMIPS (lpj=4809986) +Calibrating delay using timer specific routine.. 9622.99 BogoMIPS (lpj=4811496) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode @@ -92,8 +101,13 @@ Checking 'hlt' instruction... O
Re: [kvm-devel] kvm very slow
[oops sorry. should have included the full dmesg from the bad boot and cc'd the original poster] On Thu, 2007-09-08 at 16:23 -0700, Matthew Kent wrote: > On Wed, 2007-01-08 at 07:22 +0200, Ulrich Schreiner wrote: > > hi, > > > > im using a 64 bit fedora7 system with a quad-core processor to host > > multiple virtual machines. > > > > literally the exact same setup here > > > my current kernel is: > > > > Linux testserver 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 > > x86_64 x86_64 x86_64 GNU/Linux > > > > (now there is a 2.6.22.1-33.fc7 to download, but i think it is not the > > point here). > > > > 2.6.22.1-41.fc7 x86_64 host > > > i installed > > > > kvm.x86_64: 31-1.fc8 > > kvm-33 > > > > > because of a crash i reported as a bug with the older kvm module. > > > > this system starts a F7 image with the following command: > > > > /usr/bin/qemu-kvm > > -net nic,macadr=52.54.00.12.34.57 > > -net tap,script=./ifup.py,ifname=tap0 > > -hda /var/qemu/vm_images/F7image.img > > -boot c: -m 512 -vnc :2 -k de > > > > inside the image there is fedora 7, but a 32bit system. > > > > almost exact same as here except using 32 bit fedora rawhide > (development) guest running kernel 2.6.23-0.74.rc2.git1.fc8 > > > almost everything works (reboot hangs), but the system is extremely > > slow! the clock inside the system is extremely slow: every *virtual* > > second in the image is about two or more seconds in the *real* world. > > and I'm having the exact same issue here. The hardware clock works fine > (least from the output of /proc/driver/rtc and hwclock) but the system > time quickly falls behind in the guest, approx 0.5 secs for every 1 real > second. > > No combination of selecting different clocksources in the guest, > disabling CONFIG_NO_HZ, etc seemed to make any difference. And the fact > is my fc7 x86_64 install works just great so I doubt its the host. > > What I did notice though was ACPI wasn't being enabled by default for > the 32bit kernel with the message > > ACPI: no DMI BIOS year, acpi=force is required to enable ACPI > > and that the acpi_pm clocksource the x86_64 guest picked by default, > which worked fine, was missing. eg: > > 2.6.23-0.74.rc2.git1.fc8 i686 default boot: > > /sys/devices/system/clocksource/clocksource0/available_clocksource > pit jiffies tsc > /sys/devices/system/clocksource/clocksource0/current_clocksource > pit > > 2.6.23-0.74.rc2.git1.fc8 i686 with acpi=force: > > /sys/devices/system/clocksource/clocksource0/available_clocksource > tsc acpi_pm pit jiffies > /sys/devices/system/clocksource/clocksource0/current_clocksource > tsc > > and now everything seems great, hardware and system time seem 1:1 > again. > > Attached is a diff of the dmesg from each boot. > > As to why this is... -- Matthew Kent <[EMAIL PROTECTED]> http://magoazul.com Linux version 2.6.23-0.74.rc2.git1.fc8 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070723 (Red Hat 4.1.2-17)) #1 SMP Tue Aug 7 19:21:07 EDT 2007 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e8000 - 0010 (reserved) BIOS-e820: 0010 - 1fff (usable) BIOS-e820: 1fff - 2000 (ACPI data) BIOS-e820: fffc - 0001 (reserved) 0MB HIGHMEM available. 511MB LOWMEM available. Using x86 segment limits to approximate NX protection Entering add_active_range(0, 0, 131056) 0 entries of 256 used Zone PFN ranges: DMA 0 -> 4096 Normal 4096 -> 131056 HighMem131056 -> 131056 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 -> 131056 On node 0 totalpages: 131056 DMA zone: 56 pages used for memmap DMA zone: 0 pages reserved DMA zone: 4040 pages, LIFO batch:0 Normal zone: 1735 pages used for memmap Normal zone: 125225 pages, LIFO batch:31 HighMem zone: 0 pages used for memmap Movable zone: 0 pages used for memmap DMI not present or invalid. Using APIC driver default ACPI: RSDP 000FA670, 0014 (r0 QEMU ) ACPI: RSDT 1FFF, 002C (r1 QEMU QEMURSDT1 QEMU1) ACPI: FACP 1FFF002C, 0074 (r1 QEMU QEMUFACP1 QEMU1) ACPI: DSDT 1FFF0100, 0832 (r1 BXPC BXDSDT1 INTL 20060912) ACPI: FACS 1FFF00C0, 0040 ACPI: APIC 1FFF0938, 0040 (r1 QEMU QEMUAPIC1 QEMU1) ACPI: no DMI BIOS year, acpi=force is required to enable ACPI ACPI: Disabling ACPI support Allocating PCI resources starting at 3000 (gap: 2000:d
[kvm-devel] [PATCH] hint your using kvm
Signed-off-by: Matthew Kent <[EMAIL PROTECTED]>
---
qemu/vnc.c | 12 ++--
1 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/qemu/vnc.c b/qemu/vnc.c
index 37d5e35..4430651 100644
--- a/qemu/vnc.c
+++ b/qemu/vnc.c
@@ -1109,8 +1109,16 @@ static int protocol_client_init(VncState *vs, char
*data, size_t len)
vnc_write(vs, pad, 3); /* padding */
-vnc_write_u32(vs, 4);
-vnc_write(vs, "QEMU", 4);
+#if USE_KVM
+if (kvm_allowed) {
+vnc_write_u32(vs, 8);
+vnc_write(vs, "QEMU/KVM", 8);
+} else
+#endif
+{
+vnc_write_u32(vs, 4);
+vnc_write(vs, "QEMU", 4);
+}
vnc_flush(vs);
vnc_read_when(vs, protocol_client_msg, 1);
--
1.5.2.2
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] paravirtualizaton support
On Thu, 2007-16-08 at 16:32 +0200, Gunther Persoons wrote: > Hey, > > Is there already paravirtualizaton support in KVM? If so how can I enable it? > > Thankx Right now as is my understanding paravirt in KVM is only a patch series at http://hg.codemonkey.ws/kvm-paravirt Not sure which kvm release those patches will apply cleanly to though. -- Matthew Kent <[EMAIL PROTECTED]> http://magoazul.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH/RFC 4/4] Add support for dynamic ticks.
> If DYNAMIC_TICKS is defined qemu does not attepmt to generate SIGALRM at a > constant rate. Rather, the system timer is set to generate SIGALRM only > when it is needed. DYNAMIC_TICKS reduces the number of SIGALRMs sent to > idle dynamic-ticked guests. > Original patch from Dan Kenigsberg <[EMAIL PROTECTED]> > > Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]> Wow, this patch sure made a difference for some timings I've been doing with kvm-35 and hackbench. All tests using 2.6.23-rc3+hrtimers patch for x86_64/i386 tickless and a quad core intel: [EMAIL PROTECTED] ~]$ time ./hackbench 50 x86_64 host : real 0m10.845s x86_64 host, bound to 1 cpu : real 0m21.884s i386 guest+unix clock : real 0m49.206s i386 guest+hpet clock : real 0m48.292s i386 guest+dynticks clock : real 0m28.835s Results are repeatable and verfied with a stopwatch because I didn't believe them at first :) Great stuff. -- Matthew Kent <[EMAIL PROTECTED]> http://magoazul.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [Qemu-devel] [PATCH 3/4] Add support for HPET periodic timer.
On Sat, 2007-18-08 at 01:11 +0200, Luca Tettamanti wrote: > plain text document attachment (clock-hpet) > Linux operates the HPET timer in legacy replacement mode, which means that > the periodic interrupt of the CMOS RTC is not delivered (qemu won't be able > to use /dev/rtc). Add support for HPET (/dev/hpet) as a replacement for the > RTC; the periodic interrupt is delivered via SIGIO and is handled in the > same way as the RTC timer. > > Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]> I must be missing something silly here.. should I be able to open more than one instance of qemu with -clock hpet? Because upon invoking a second instance of qemu HPET_IE_ON fails. I also tried running the example in the kernel docs under Documentation/hpet.txt [EMAIL PROTECTED] [/home/mkent]# ./demo poll /dev/hpet 1 1000 -hpet: executing poll hpet_poll: info.hi_flags 0x0 hpet_poll: expired time = 0x8 hpet_poll: revents = 0x1 hpet_poll: data 0x1 [EMAIL PROTECTED] [/home/mkent]# ./demo poll /dev/hpet 1 1000 -hpet: executing poll hpet_poll: info.hi_flags 0x0 hpet_poll, HPET_IE_ON failed This is on 2.6.23-rc3 x86_64 with the patch-2.6.23-rc3-hrt2.patch hrtimers patch. -- Matthew Kent <[EMAIL PROTECTED]> http://magoazul.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [Qemu-devel] [PATCH 3/4] Add support for HPET periodic timer.
On Tue, 2007-21-08 at 21:40 +0200, Luca wrote: > On 8/21/07, Matthew Kent <[EMAIL PROTECTED]> wrote: > > On Sat, 2007-18-08 at 01:11 +0200, Luca Tettamanti wrote: > > > plain text document attachment (clock-hpet) > > > Linux operates the HPET timer in legacy replacement mode, which means that > > > the periodic interrupt of the CMOS RTC is not delivered (qemu won't be > > > able > > > to use /dev/rtc). Add support for HPET (/dev/hpet) as a replacement for > > > the > > > RTC; the periodic interrupt is delivered via SIGIO and is handled in the > > > same way as the RTC timer. > > > > > > Signed-off-by: Luca Tettamanti <[EMAIL PROTECTED]> > > > > I must be missing something silly here.. should I be able to open more > > than one instance of qemu with -clock hpet? Because upon invoking a > > second instance of qemu HPET_IE_ON fails. > > It depends on your hardware. Theoretically it's possible, but I've yet > to see a motherboard with more than one periodic timer. Ah thank you, after re-reading the docs I think I better understand this. -- Matthew Kent <[EMAIL PROTECTED]> http://magoazul.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] linux verify_pmtmr_rate() issue
Issue here that's beyond my skill set to resolve: I've been starting multiple linux 2.6.23-rc3 x86 guests up in parallel with qemu/kvm and noticed pm-timer is being disabled in some of them with PM-Timer running at invalid rate: 126% of normal - aborting. in dmesg when I start about 6 at a time. Unfortunately without the timer a tickless kernel in my guests is disabled. I also replicated the issue by starting a single vm when the host system was busy enough. After some amateurish debugging added to verify_pmtmr_rate() in the kernel acpi_pm driver and get_pmtmr() in qemu acpi I can indeed see it returning just slowly enough to throw off the sanity check. [ 10.264772] DEBUG: PM-Timer running value1: 2925874 value2: 3058371 expected_rate: 107385 delta: 132497 count: 2269 [ 10.270766] PM-Timer running at invalid rate: 123% of normal - aborting. For now I've just disabled verify_pmtmr_rate() in the kernel for my guests and they seem to be keeping time just fine. Not sure if a patch for the linux kernel making the sanity check optional with a kernel parameter would make sense or there's something else that can be done at the qemu level. Thanks. -- Matthew Kent <[EMAIL PROTECTED]> http://magoazul.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
