Re: [kvm-devel] [Qemu-devel] [PATCH 3/4] Add support for HPET periodic timer.
On Thu, Aug 23, 2007 at 12:09:47AM +0200, Andi Kleen wrote: $ dmesg |grep -i hpet ACPI: HPET 7D5B6AE0, 0038 (r1 A M I OEMHPET 5000708 MSFT 97) ACPI: HPET id: 0x8086a301 base: 0xfed0 hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0 hpet0: 4 64-bit timers, 14318180 Hz hpet_resources: 0xfed0 is busy What kernel version was that? There was a bug that caused this pre .22 I have vanilla 2.6.22.3 on that machine. Thanks, Dan. - 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] Vista 32 Premium 32 bit gets blue screen on boot
Haydn Solomon wrote: I've installed vista premium home 32 bit on previous versions of kvm, namely 24-1 which is packaged with fedora 7. Since then I've removed these packages and building kvm from releases from sourceforge provided qumranet website. When I try to install vista premium home 32 bit using kvm release 36 I'm getting blue screen. I'm running on a dell 1720 core 2 duo, 2 GB ram. I'm running fedora 7 64-bit. The previously installed windows xp ( installed using kvm release 35 ) is running fine under release 36. I'm starting kvm with the following: /usr/local/kvm/bin/qemu-system-x86_64 \ -hda vistahome.img \ -m 400 \ -no-rtc \ -localtime \ -boot d \ -cdrom /home/hsolomon/isos/VISTA_32_PREMIUM.iso The message from the blue screen is: ***STOP: 0X00A5 ( 0X0001000B, 0X50434146, 0XFFD0502C, 0X ) Any feedback would be appreciated. Thanks and great piece of work here guys. Can you check which version of kvm causes the regression? If kvm-35 works and kvm-36 doesn't, try copying kvm-35's bios.bin (from qemu/pc-bios) to the install location (/use/local/share/qemu/bios.bin by default) -- error compiling committee.c: too many arguments to function - 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] [ANNOUNCE] kvm-36 release
Gunther Persoons wrote: I noticed the idle cpu usage for kvm-36 running windows xp 32 bit as guest is much higher. For kvm-35 this was around 2-4%, running kvm-36 it's 22% - 26%. Hmm. Is this using the ACPI HAL, or the Standard PC HAL, or what? The fix was targeted at ACPI MP HALs (reducing cpu usage from 100% to something sane). -- error compiling committee.c: too many arguments to function - 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] Fix the updating of PPR after TPR shadow introduced
Yang, Sheng wrote: After TPR Shadow feature introduced, many TPR access won't cause vmexit, so the ordinary point of catching TPR and updating PPR is insufficient. This patch updates PPR everytime when possible reading PPR action occurs. I folded this into the TPR shadow patch. Thanks. -- error compiling committee.c: too many arguments to function - 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] Fix BIOS CPU enumeration
Current BIOS delays 10ms for AP to boot up, but we found it may be too
short : on some machine 10ms is OK, some other not. And if we look at
the OS side, Linux waits for 5s for AP to boot up, so I would suggest to
wait for a much longer time, like 2000ms, is that OK?
-Xin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Li, Xin B
Sent: Wednesday, August 22, 2007 10:08 PM
To: kvm-devel@lists.sourceforge.net
Subject: [kvm-devel] [PATCH] Fix BIOS CPU enumeration
KVM BIOS uses the following code to delay an expected milliseconds
void delay_ms(int n)
{
int i, j;
for(i = 0; i n; i++) {
/* approximative ! */
for(j = 0; j 100; j++);
}
}
It's OK when we run APIC in user level, but when APIC is in kernel, the
delayed time is not enough and causes BSP delays a too short peroid
that APs have no enough time to reach the point BIOS enumerates CPU,
so BIOS always reports only one CPU is detected in this VM.
The following patch fixed this issue.
Signed-off-by: Xin Li [EMAIL PROTECTED]
diff --git a/bios/rombios32.c b/bios/rombios32.c
index 1562047..9b200b9 100644
--- a/bios/rombios32.c
+++ b/bios/rombios32.c
@@ -355,7 +355,8 @@ void delay_ms(int n)
{
int i, j;
for(i = 0; i n; i++) {
-#ifdef BX_QEMU
+#if 0
+//#ifdef BX_QEMU
/* approximative ! */
for(j = 0; j 100; j++);
#else
---
--
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
-
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] [ANNOUNCE] kvm-36 release
Avi Kivity wrote: Gunther Persoons wrote: I noticed the idle cpu usage for kvm-36 running windows xp 32 bit as guest is much higher. For kvm-35 this was around 2-4%, running kvm-36 it's 22% - 26%. Hmm. Is this using the ACPI HAL, or the Standard PC HAL, or what? The fix was targeted at ACPI MP HALs (reducing cpu usage from 100% to something sane). Looks like a vga regression introduced by support for large memory. Does the attached patch fix? -- error compiling committee.c: too many arguments to function diff --git a/qemu/hw/vga.c b/qemu/hw/vga.c index 55e2d4c..b55f6fd 100644 --- a/qemu/hw/vga.c +++ b/qemu/hw/vga.c @@ -1405,7 +1405,7 @@ static void vga_draw_graphic(VGAState *s, int full_update) int disp_width, multi_scan, multi_run; uint8_t *d; uint32_t v, addr1, addr; -ram_addr_t page0, page1; +int page0, page1; vga_draw_line_func *vga_draw_line; #ifdef USE_KVM - 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] Fix BIOS CPU enumeration
Li, Xin B wrote: Current BIOS delays 10ms for AP to boot up, but we found it may be too short : on some machine 10ms is OK, some other not. And if we look at the OS side, Linux waits for 5s for AP to boot up, so I would suggest to wait for a much longer time, like 2000ms, is that OK Two seconds is a bit long. But now that we have the bios in our source repo, we can go wild, and pass the cpu count in the cmos non volatile memory or through some port, and make it timing independent. -- error compiling committee.c: too many arguments to function - 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] Fix BIOS CPU enumeration
-Original Message- From: Avi Kivity [mailto:[EMAIL PROTECTED] Sent: Thursday, August 23, 2007 4:29 PM To: Li, Xin B Cc: kvm-devel@lists.sourceforge.net Subject: Re: [kvm-devel] [PATCH] Fix BIOS CPU enumeration Li, Xin B wrote: Current BIOS delays 10ms for AP to boot up, but we found it may be too short : on some machine 10ms is OK, some other not. And if we look at the OS side, Linux waits for 5s for AP to boot up, so I would suggest to wait for a much longer time, like 2000ms, is that OK Two seconds is a bit long. But now that we have the bios in our source repo, we can go wild, and pass the cpu count in the cmos non volatile memory or through some port, and make it timing independent. Hmmm, sounds good! -Xin - 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] Fix BIOS CPU enumeration
Li, Xin B wrote: -Original Message- From: Avi Kivity [mailto:[EMAIL PROTECTED] Sent: Thursday, August 23, 2007 4:29 PM To: Li, Xin B Cc: kvm-devel@lists.sourceforge.net Subject: Re: [kvm-devel] [PATCH] Fix BIOS CPU enumeration Li, Xin B wrote: Current BIOS delays 10ms for AP to boot up, but we found it may be too short : on some machine 10ms is OK, some other not. And if we look at the OS side, Linux waits for 5s for AP to boot up, so I would suggest to wait for a much longer time, like 2000ms, is that OK Two seconds is a bit long. But now that we have the bios in our source repo, we can go wild, and pass the cpu count in the cmos non volatile memory or through some port, and make it timing independent. Hmmm, sounds good! Okay, so I am dropping this patch (using the PIT) and waiting for a timing independent patch. -- error compiling committee.c: too many arguments to function - 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] [ANNOUNCE] kvm-36 release
2007/8/23, Avi Kivity [EMAIL PROTECTED]: Avi Kivity wrote: Gunther Persoons wrote: I noticed the idle cpu usage for kvm-36 running windows xp 32 bit as guest is much higher. For kvm-35 this was around 2-4%, running kvm-36 it's 22% - 26%. Hmm. Is this using the ACPI HAL, or the Standard PC HAL, or what? The fix was targeted at ACPI MP HALs (reducing cpu usage from 100% to something sane). Looks like a vga regression introduced by support for large memory. Does the attached patch fix? -- error compiling committee.c: too many arguments to function Yup, the patched fixed it. Cpu usage is now around 4%. - 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] [ kvm-Bugs-1780032 ] Cannot install 64bit vista into KVM guest
Bugs item #1780032, was opened at 2007-08-23 17:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1780032group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: yunfeng (yunfeng) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot install 64bit vista into KVM guest Initial Comment: I cannot install 64bit vista into KVM guest. The installtion failed with blue screen. Reproduce steps: use qemu-system-x86_64 to install 64bit vista image. Following is the cmd: qemu-system-x86_64 -hda kvm_vista_RTM_smp_acpi_32e.img -net nic,macaddr=00:16:3e:44:de:5e,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -m 1024 - cdrom /share/xvs/img/installation/Vistaamd64.iso -boot d -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1780032group_id=180599 - 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] [ANNOUNCE] kvm-36 release
On Thu, 2007-08-23 at 11:12 +0300, Avi Kivity wrote:
Avi Kivity wrote:
Gunther Persoons wrote:
I noticed the idle cpu usage for kvm-36 running windows xp 32 bit as
guest is much higher.
For kvm-35 this was around 2-4%, running kvm-36 it's 22% - 26%.
Hmm. Is this using the ACPI HAL, or the Standard PC HAL, or what?
The fix was targeted at ACPI MP HALs (reducing cpu usage from 100% to
something sane).
Looks like a vga regression introduced by support for large memory.
Does the attached patch fix?
avi, try this patch,
the problem was that page_max is set to -1 inside the code,
and when the code changed page0 and page1 to unsigned long, it never
entered to there.
the patch that i give now, is one way to fix it (ofcourse there is
another way to play with casting.)
--- oldvga.c 2007-08-23 03:22:30.0 +0300
+++ vga.c 2007-08-23 03:28:58.0 +0300
@@ -1400,12 +1400,12 @@ extern int kvm_allowed;
*/
static void vga_draw_graphic(VGAState *s, int full_update)
{
-int y1, y, update, page_min, page_max, linesize, y_start, double_scan, mask;
+int y1, y, update, linesize, y_start, double_scan, mask;
int width, height, shift_control, line_offset, bwidth;
int disp_width, multi_scan, multi_run;
uint8_t *d;
uint32_t v, addr1, addr;
-ram_addr_t page0, page1;
+long page0, page1, page_min, page_max;
vga_draw_line_func *vga_draw_line;
#ifdef USE_KVM
-
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] [ANNOUNCE] kvm-36 release
On Thu, 2007-08-23 at 03:36 +0300, Izik Eidus wrote: On Thu, 2007-08-23 at 11:12 +0300, Avi Kivity wrote: Avi Kivity wrote: Gunther Persoons wrote: I noticed the idle cpu usage for kvm-36 running windows xp 32 bit as guest is much higher. For kvm-35 this was around 2-4%, running kvm-36 it's 22% - 26%. Hmm. Is this using the ACPI HAL, or the Standard PC HAL, or what? The fix was targeted at ACPI MP HALs (reducing cpu usage from 100% to something sane). Looks like a vga regression introduced by support for large memory. Does the attached patch fix? avi, try this patch, the problem was that page_max is set to -1 inside the code, and when the code changed page0 and page1 to unsigned long, it never entered to there. by entered to there i mean: if (page1 page_max) page_max = page1; the patch that i give now, is one way to fix it (ofcourse there is another way to play with casting.) - 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] [ANNOUNCE] kvm-36 release
Izik Eidus wrote: On Thu, 2007-08-23 at 11:12 +0300, Avi Kivity wrote: Avi Kivity wrote: Gunther Persoons wrote: I noticed the idle cpu usage for kvm-36 running windows xp 32 bit as guest is much higher. For kvm-35 this was around 2-4%, running kvm-36 it's 22% - 26%. Hmm. Is this using the ACPI HAL, or the Standard PC HAL, or what? The fix was targeted at ACPI MP HALs (reducing cpu usage from 100% to something sane). Looks like a vga regression introduced by support for large memory. Does the attached patch fix? avi, try this patch, the problem was that page_max is set to -1 inside the code, and when the code changed page0 and page1 to unsigned long, it never entered to there. Thanks, applied. It isn't particularly pretty but I don't want to change qemu code too much. -- error compiling committee.c: too many arguments to function - 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-commits] KVM: VMX: Use shadow TPR/cr8 for 64-bits guests
On Thu, 2007-08-23 at 10:46 +0300, Avi Kivity wrote: repository: /home/avi/kvm/linux-2.6 branch: lapic5 commit 8ed05c33d82a394c90b5dd830513416e59ffcf68 Author: Yang, Sheng [EMAIL PROTECTED] Date: Wed Aug 22 15:03:15 2007 +0300 KVM: VMX: Use shadow TPR/cr8 for 64-bits guests This patch enables TPR shadow of VMX on CR8 access. 64bit Windows using CR8 access TPR frequently. The TPR shadow can improve the performance of access TPR by not causing vmexit. I remember when I added something similar to the lapic series that both of my C2D systems (Merom + Woodcrest) reported that they didn't support the feature in the HW. Since those were fairly new, which ones *do* support this (out of curiosity), or is there a microcode update floating around out there ;). -Greg - 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-commits] KVM: VMX: Use shadow TPR/cr8 for 64-bits guests
I remember when I added something similar to the lapic series that both of my C2D systems (Merom + Woodcrest) reported that they didn't support the feature in the HW. Since those were fairly new, which ones *do* support this (out of curiosity), or is there a microcode update floating around out there ;). It's only supported in Penryn (upcomming 45nm Core2 shrink) AFAIK Intel made a press release about this recently. -Andi - 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] [PATCH] Split segments reload in vmx_load_host_state()
It is from the TODO and I hope no one is already working on this.
'vmx_load_host_state() bundles fs, gs, ldt, and tss reloading into one in the
hope that it is infrequent. With smp guests, fs reloading is frequent and the
separate reloads should be unbundled.'
Signed-off-by: Laurent Vivier [EMAIL PROTECTED]
Index: kvm/drivers/kvm/vmx.c
===
--- kvm.orig/drivers/kvm/vmx.c 2007-08-23 11:26:34.0 +0200
+++ kvm/drivers/kvm/vmx.c 2007-08-23 13:45:10.0 +0200
@@ -54,7 +54,8 @@ struct vcpu_vmx {
struct {
int loaded;
u16 fs_sel, gs_sel, ldt_sel;
- int fs_gs_ldt_reload_needed;
+ int gs_ldt_reload_needed;
+ int fs_reload_needed;
}host_state;
};
@@ -353,20 +354,20 @@ static void vmx_save_host_state(struct v
* allow segment selectors with cpl 0 or ti == 1.
*/
vmx-host_state.ldt_sel = read_ldt();
- vmx-host_state.fs_gs_ldt_reload_needed = vmx-host_state.ldt_sel;
+ vmx-host_state.gs_ldt_reload_needed = vmx-host_state.ldt_sel;
vmx-host_state.fs_sel = read_fs();
if (!(vmx-host_state.fs_sel 7))
vmcs_write16(HOST_FS_SELECTOR, vmx-host_state.fs_sel);
else {
vmcs_write16(HOST_FS_SELECTOR, 0);
- vmx-host_state.fs_gs_ldt_reload_needed = 1;
+ vmx-host_state.fs_reload_needed = 1;
}
vmx-host_state.gs_sel = read_gs();
if (!(vmx-host_state.gs_sel 7))
vmcs_write16(HOST_GS_SELECTOR, vmx-host_state.gs_sel);
else {
vmcs_write16(HOST_GS_SELECTOR, 0);
- vmx-host_state.fs_gs_ldt_reload_needed = 1;
+ vmx-host_state.gs_ldt_reload_needed = 1;
}
#ifdef CONFIG_X86_64
@@ -396,9 +397,10 @@ static void vmx_load_host_state(struct v
return;
vmx-host_state.loaded = 0;
- if (vmx-host_state.fs_gs_ldt_reload_needed) {
- load_ldt(vmx-host_state.ldt_sel);
+ if (vmx-host_state.fs_reload_needed)
load_fs(vmx-host_state.fs_sel);
+ if (vmx-host_state.gs_ldt_reload_needed) {
+ load_ldt(vmx-host_state.ldt_sel);
/*
* If we have to reload gs, we must take care to
* preserve our gs base.
@@ -409,9 +411,9 @@ static void vmx_load_host_state(struct v
wrmsrl(MSR_GS_BASE, vmcs_readl(HOST_GS_BASE));
#endif
local_irq_restore(flags);
-
- reload_tss();
}
+ if (vmx-host_state.gs_ldt_reload_needed ||
vmx-host_state.fs_reload_needed)
+ reload_tss();
save_msrs(vmx-guest_msrs, vmx-save_nmsrs);
load_msrs(vmx-host_msrs, vmx-save_nmsrs);
if (msr_efer_need_save_restore(vmx))
-
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] Split segments reload in vmx_load_host_state()
Laurent Vivier wrote: It is from the TODO and I hope no one is already working on this. 'vmx_load_host_state() bundles fs, gs, ldt, and tss reloading into one in the hope that it is infrequent. With smp guests, fs reloading is frequent and the separate reloads should be unbundled.' }; @@ -353,20 +354,20 @@ static void vmx_save_host_state(struct v * allow segment selectors with cpl 0 or ti == 1. */ vmx-host_state.ldt_sel = read_ldt(); - vmx-host_state.fs_gs_ldt_reload_needed = vmx-host_state.ldt_sel; + vmx-host_state.gs_ldt_reload_needed = vmx-host_state.ldt_sel; Missing initialization for fs_reload_needed here. -- error compiling committee.c: too many arguments to function - 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] Split segments reload in vmx_load_host_state()
Avi Kivity wrote: Laurent Vivier wrote: It is from the TODO and I hope no one is already working on this. 'vmx_load_host_state() bundles fs, gs, ldt, and tss reloading into one in the hope that it is infrequent. With smp guests, fs reloading is frequent and the separate reloads should be unbundled.' }; @@ -353,20 +354,20 @@ static void vmx_save_host_state(struct v * allow segment selectors with cpl 0 or ti == 1. */ vmx-host_state.ldt_sel = read_ldt(); -vmx-host_state.fs_gs_ldt_reload_needed = vmx-host_state.ldt_sel; +vmx-host_state.gs_ldt_reload_needed = vmx-host_state.ldt_sel; Missing initialization for fs_reload_needed here. It is initialized on fs_sel, should it be initialized on ldt_sel too ? Laurent -- - [EMAIL PROTECTED] -- Software is hard - Donald Knuth signature.asc Description: OpenPGP digital signature - 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] Split segments reload in vmx_load_host_state()
Laurent Vivier wrote: Avi Kivity wrote: Laurent Vivier wrote: It is from the TODO and I hope no one is already working on this. 'vmx_load_host_state() bundles fs, gs, ldt, and tss reloading into one in the hope that it is infrequent. With smp guests, fs reloading is frequent and the separate reloads should be unbundled.' }; @@ -353,20 +354,20 @@ static void vmx_save_host_state(struct v * allow segment selectors with cpl 0 or ti == 1. */ vmx-host_state.ldt_sel = read_ldt(); - vmx-host_state.fs_gs_ldt_reload_needed = vmx-host_state.ldt_sel; + vmx-host_state.gs_ldt_reload_needed = vmx-host_state.ldt_sel; Missing initialization for fs_reload_needed here. It is initialized on fs_sel, should it be initialized on ldt_sel too ? It's only initialized to 1, but never cleared to zero. The original code means: if ((ldt_sel != 0) || ((fs_sel 7) != 0) || ((gs_sel 7) != 0)) then a reload is needed. In the new code, fs reload should depend only on ((fs_sel 7) != 0) and ldt/gs reload should depend on ldt_sel and gs_sel only. Regarding reload_tss(), it should probably be unconditional. -- error compiling committee.c: too many arguments to function - 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] Johann LAGRUE est absent(e).
Je serai absent(e) du 20/08/2007 au 31/08/2007. Je répondrai à votre message dès mon retour. En cas d'urgence, merci de contacter Mr LEPAGE ou Mr DUVAL au 01.34.94.37.80- 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] [PATCH][RESEND] Split segments reload in vmx_load_host_state()
From KVM/TODO:
vmx_load_host_state() bundles fs, gs, ldt, and tss reloading into
one in the hope that it is infrequent. With smp guests, fs reloading is
frequent and the separate reloads should be unbundled.
Signed-off-by: Laurent Vivier [EMAIL PROTECTED]
Index: kvm/drivers/kvm/vmx.c
===
--- kvm.orig/drivers/kvm/vmx.c 2007-08-23 14:41:48.0 +0200
+++ kvm/drivers/kvm/vmx.c 2007-08-23 16:20:23.0 +0200
@@ -54,7 +54,8 @@ struct vcpu_vmx {
struct {
int loaded;
u16 fs_sel, gs_sel, ldt_sel;
- int fs_gs_ldt_reload_needed;
+ int gs_ldt_reload_needed;
+ int fs_reload_needed;
}host_state;
};
@@ -353,20 +354,21 @@ static void vmx_save_host_state(struct v
* allow segment selectors with cpl 0 or ti == 1.
*/
vmx-host_state.ldt_sel = read_ldt();
- vmx-host_state.fs_gs_ldt_reload_needed = vmx-host_state.ldt_sel;
+ vmx-host_state.gs_ldt_reload_needed = vmx-host_state.ldt_sel;
vmx-host_state.fs_sel = read_fs();
- if (!(vmx-host_state.fs_sel 7))
+ if (!(vmx-host_state.fs_sel 7)) {
vmcs_write16(HOST_FS_SELECTOR, vmx-host_state.fs_sel);
- else {
+ vmx-host_state.fs_reload_needed = 0;
+ } else {
vmcs_write16(HOST_FS_SELECTOR, 0);
- vmx-host_state.fs_gs_ldt_reload_needed = 1;
+ vmx-host_state.fs_reload_needed = 1;
}
vmx-host_state.gs_sel = read_gs();
if (!(vmx-host_state.gs_sel 7))
vmcs_write16(HOST_GS_SELECTOR, vmx-host_state.gs_sel);
else {
vmcs_write16(HOST_GS_SELECTOR, 0);
- vmx-host_state.fs_gs_ldt_reload_needed = 1;
+ vmx-host_state.gs_ldt_reload_needed = 1;
}
#ifdef CONFIG_X86_64
@@ -396,9 +398,10 @@ static void vmx_load_host_state(struct v
return;
vmx-host_state.loaded = 0;
- if (vmx-host_state.fs_gs_ldt_reload_needed) {
- load_ldt(vmx-host_state.ldt_sel);
+ if (vmx-host_state.fs_reload_needed)
load_fs(vmx-host_state.fs_sel);
+ if (vmx-host_state.gs_ldt_reload_needed) {
+ load_ldt(vmx-host_state.ldt_sel);
/*
* If we have to reload gs, we must take care to
* preserve our gs base.
@@ -409,9 +412,8 @@ static void vmx_load_host_state(struct v
wrmsrl(MSR_GS_BASE, vmcs_readl(HOST_GS_BASE));
#endif
local_irq_restore(flags);
-
- reload_tss();
}
+ reload_tss();
save_msrs(vmx-guest_msrs, vmx-save_nmsrs);
load_msrs(vmx-host_msrs, vmx-save_nmsrs);
if (msr_efer_need_save_restore(vmx))
signature.asc
Description: OpenPGP digital signature
-
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][RESEND] Split segments reload in vmx_load_host_state()
Laurent Vivier wrote: From KVM/TODO: vmx_load_host_state() bundles fs, gs, ldt, and tss reloading into one in the hope that it is infrequent. With smp guests, fs reloading is frequent and the separate reloads should be unbundled. Applied, thanks. -- error compiling committee.c: too many arguments to function - 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] Another unhandled vm exit: 0x9
Avi Kivity wrote: Cam Macdonell wrote: Avi Kivity wrote: Hi, I had this same problem. I have an old XP image that would not run under kvm-35. It was installed with the kvm that is packaged with Ubuntu Feisty (kvm-27, I believe). After I upgraded, it crashes during boot. How can I check the HAL it uses? Windows device manager, under 'Computer'. I see MPS Uniprocessor PC. This image was installed with kvm. I still have it around if you would like me to do some debugging with it. Can you check which kvm version caused the regression? It works under KVM-16 (which is the version that ships with Feisty) and up to kvm-24 (I did a manual binary search so a few versions were skipped). versions 25, 26, 27 stall at boot (I wait several minutes but Windows never starts) and crashing with unhandled vm exit: 0x9 happens with KVM-33. I'm not on which precise version where the crashing begins (let me know if that would be useful). A possibly unimportant note, I noticed that the later versions (above 27) compile the executable as qemu-system-x86_64 where as earlier versions build it as qemu. My system is a Centrino Duo, so it's a i386. I'm not sure if this matters but I just thought I would mention it. Let me know if you have any more questions, Cam - 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] Another unhandled vm exit: 0x9
Cam Macdonell wrote: Avi Kivity wrote: Cam Macdonell wrote: Avi Kivity wrote: Hi, I had this same problem. I have an old XP image that would not run under kvm-35. It was installed with the kvm that is packaged with Ubuntu Feisty (kvm-27, I believe). After I upgraded, it crashes during boot. How can I check the HAL it uses? Windows device manager, under 'Computer'. I see MPS Uniprocessor PC. This image was installed with kvm. I still have it around if you would like me to do some debugging with it. Can you check which kvm version caused the regression? It works under KVM-16 (which is the version that ships with Feisty) and up to kvm-24 (I did a manual binary search so a few versions were skipped). versions 25, 26, 27 stall at boot (I wait several minutes but Windows never starts) and crashing with unhandled vm exit: 0x9 happens with KVM-33. I'm not on which precise version where the crashing begins (let me know if that would be useful). That should be enough to start debugging. However, with the kvm forum next week, I doubt it will happen soon. A possibly unimportant note, I noticed that the later versions (above 27) compile the executable as qemu-system-x86_64 where as earlier versions build it as qemu. My system is a Centrino Duo, so it's a i386. I'm not sure if this matters but I just thought I would mention it. It is likely related. You can check it by changing 'echo x86_64' to 'echo i386' in ./configure. -- error compiling committee.c: too many arguments to function - 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] Another unhandled vm exit: 0x9
Avi Kivity wrote: Cam Macdonell wrote: Avi Kivity wrote: Cam Macdonell wrote: Avi Kivity wrote: Hi, I had this same problem. I have an old XP image that would not run under kvm-35. It was installed with the kvm that is packaged with Ubuntu Feisty (kvm-27, I believe). After I upgraded, it crashes during boot. How can I check the HAL it uses? Windows device manager, under 'Computer'. I see MPS Uniprocessor PC. This image was installed with kvm. I still have it around if you would like me to do some debugging with it. Can you check which kvm version caused the regression? It works under KVM-16 (which is the version that ships with Feisty) and up to kvm-24 (I did a manual binary search so a few versions were skipped). versions 25, 26, 27 stall at boot (I wait several minutes but Windows never starts) and crashing with unhandled vm exit: 0x9 happens with KVM-33. I'm not on which precise version where the crashing begins (let me know if that would be useful). That should be enough to start debugging. However, with the kvm forum next week, I doubt it will happen soon. BTW, you can use -no-kvm (or an older kvm) to switch to the Standard PC HAL. But please keep a copy of the failing image for future testing. -- error compiling committee.c: too many arguments to function - 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] Vista 32 Premium 32 bit gets blue screen on boot
Haydn Solomon wrote: Yep.. sure enough, that did it. Please try out the bios images in http://people.qumranet.com/avi/bios-images/ and let us know which ones work and which don't. On 8/23/07, *Avi Kivity* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Haydn Solomon wrote: I've installed vista premium home 32 bit on previous versions of kvm, namely 24-1 which is packaged with fedora 7. Since then I've removed these packages and building kvm from releases from sourceforge provided qumranet website. When I try to install vista premium home 32 bit using kvm release 36 I'm getting blue screen. I'm running on a dell 1720 core 2 duo, 2 GB ram. I'm running fedora 7 64-bit. The previously installed windows xp ( installed using kvm release 35 ) is running fine under release 36. I'm starting kvm with the following: /usr/local/kvm/bin/qemu-system-x86_64 \ -hda vistahome.img \ -m 400 \ -no-rtc \ -localtime \ -boot d \ -cdrom /home/hsolomon/isos/VISTA_32_PREMIUM.iso The message from the blue screen is: ***STOP: 0X00A5 ( 0X0001000B, 0X50434146, 0XFFD0502C, 0X ) Any feedback would be appreciated. Thanks and great piece of work here guys. Can you check which version of kvm causes the regression? If kvm-35 works and kvm-36 doesn't, try copying kvm-35's bios.bin (from qemu/pc-bios) to the install location (/use/local/share/qemu/bios.bin by default) -- error compiling committee.c: too many arguments to function -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. - 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] A small problem
Hi Guys, Congratulations on creating something altogether more elegant and simple to use than Xen. However I am having a small problem. Every time I try to start qemu the machine hangs completely. Can you give me some pointers? My environment is:- Gentoo x86_64, Gcc-3.4.6-r2 + Gcc-4.1.2, kernel Gentoo-2.6.22-r2. I am not using the in kernel kvm module and have kvm-36. The modules appear to load with problem and I can create a disk image with qemu-img. Please let me know what other information you need. Thanks, John. - 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] A small problem
John Lewis wrote: Hi Guys, Congratulations on creating something altogether more elegant and simple to use than Xen. However I am having a small problem. Every time I try to start qemu the machine hangs completely. That's hardly simple to use. Can you give me some pointers? My environment is:- Gentoo x86_64, Gcc-3.4.6-r2 + Gcc-4.1.2, kernel Gentoo-2.6.22-r2. I am not using the in kernel kvm module and have kvm-36. The modules appear to load with problem and I can create a disk image with qemu-img. What's your cpu type? Please post /proc/cpuinfo and kernel .config. Do previous kvm versions work? Previous host kernels? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. - 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] Vista 32 Premium 32 bit gets blue screen on boot
Yep.. sure enough, that did it. On 8/23/07, Avi Kivity [EMAIL PROTECTED] wrote: Haydn Solomon wrote: I've installed vista premium home 32 bit on previous versions of kvm, namely 24-1 which is packaged with fedora 7. Since then I've removed these packages and building kvm from releases from sourceforge provided qumranet website. When I try to install vista premium home 32 bit using kvm release 36 I'm getting blue screen. I'm running on a dell 1720 core 2 duo, 2 GB ram. I'm running fedora 7 64-bit. The previously installed windows xp ( installed using kvm release 35 ) is running fine under release 36. I'm starting kvm with the following: /usr/local/kvm/bin/qemu-system-x86_64 \ -hda vistahome.img \ -m 400 \ -no-rtc \ -localtime \ -boot d \ -cdrom /home/hsolomon/isos/VISTA_32_PREMIUM.iso The message from the blue screen is: ***STOP: 0X00A5 ( 0X0001000B, 0X50434146, 0XFFD0502C, 0X ) Any feedback would be appreciated. Thanks and great piece of work here guys. Can you check which version of kvm causes the regression? If kvm-35 works and kvm-36 doesn't, try copying kvm-35's bios.bin (from qemu/pc-bios) to the install location (/use/local/share/qemu/bios.bin by default) -- error compiling committee.c: too many arguments to function - 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] serious-looking warning building kvm-36
Hi, I've just built kvm-36 and noticed what looks as if it may be a non-trivial warning: make[1]: Leaving directory `/home/chris/rpm/BUILD/kvm-36/kernel' make -C user make[1]: Entering directory `/home/chris/rpm/BUILD/kvm-36/user' cc -I /home/chris/rpm/BUILD/kvm-36/kernel/include -MMD -MF ./.kvmctl.d -g -fomit-frame-pointer -Wall -m32 -fno-stack-protector -c -o kvmctl.o kvmctl.c kvmctl.c: In function 'kvm_create': kvmctl.c:256: warning: integer constant is too large for 'long' type Please cc me to any reply - I'm not subscribed. Chris -- Beer is proof that God loves us and wants us to be happy - Benjamin Franklin - 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] Fix network boot whether KVM is enabled or disabled
On 8/22/07, Anthony Liguori [EMAIL PROTECTED] wrote: Hrm, it looks like it's the BIOS. Using the BIOS in qemu-0.9.0, -boot n works with x86_64 but the bios installed by KVM doesn't work. Yeah, it does seem to be the case. I ran a few experiments after reading your message: kvm-28 and kvm-36 successfully PXE-boots when using bios.bin from kvm-28, but both fails to PXE-boot when using bios.bin from kvm-36. Can you try a more recent KVM with -no-kvm? Using the patch I posted to the list, I can PXE-boot using the qemu-system-x86_64 executable from kvm-36 both with and without kvm kernel module acceleration (provided that I use the bios from kvm-28, that is). Regards, -- Chuan-kai Lin - 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] Fix network boot whether KVM is enabled or disabled
On Thu, 2007-08-23 at 12:08 -0700, Chuan-kai Lin wrote: On 8/22/07, Anthony Liguori [EMAIL PROTECTED] wrote: Hrm, it looks like it's the BIOS. Using the BIOS in qemu-0.9.0, -boot n works with x86_64 but the bios installed by KVM doesn't work. Yeah, it does seem to be the case. I ran a few experiments after reading your message: kvm-28 and kvm-36 successfully PXE-boots when using bios.bin from kvm-28, but both fails to PXE-boot when using bios.bin from kvm-36. Can you try a more recent KVM with -no-kvm? Using the patch I posted to the list, I can PXE-boot using the qemu-system-x86_64 executable from kvm-36 both with and without kvm kernel module acceleration (provided that I use the bios from kvm-28, that is). Only with the old BIOS right? The new BIOS provides very limited support for plug-and-play option ROMs. This needs to be indicated in CMOS memory. This morning I made a quick attempt to change the CMOS boot value to 0x04 which would indicate booting from an expansion ROM but that didn't work. There was a patch on qemu-devel recently that might be worth looking at. Regards, Anthony Liguori Regards, - 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] serious-looking warning building kvm-36
On 8/23/07, Chris Clayton [EMAIL PROTECTED] wrote: Hi, I've just built kvm-36 and noticed what looks as if it may be a non-trivial warning: make[1]: Leaving directory `/home/chris/rpm/BUILD/kvm-36/kernel' make -C user make[1]: Entering directory `/home/chris/rpm/BUILD/kvm-36/user' cc -I /home/chris/rpm/BUILD/kvm-36/kernel/include -MMD -MF ./.kvmctl.d -g -fomit-frame-pointer -Wall -m32 -fno-stack-protector -c -o kvmctl.o kvmctl.c kvmctl.c: In function 'kvm_create': kvmctl.c:256: warning: integer constant is too large for 'long' type Please cc me to any reply - I'm not subscribed. It's harmless. That branch is only taken when using more than 4GB of memory, which in turn is only possible on a 64bit host. In this case the 'unsigned long' would be a 64bit integer (and the shift would be acceptable). There are a couple more of warning related to this issue, a possible solution to silence the warning is to use always 64bit integers instead of the longs. Luca - 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] tun/tap kernel module
Hi, I'm trying to setup networking on FC6. Where can I find the tun/tap interface? I realize this is almost a RTFM question, but I just haven't been able to find it. If someone could point me to a RPM or yum repo that would be great. Thanks, Cam - 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] tun/tap kernel module
On 8/23/07, Cam Macdonell [EMAIL PROTECTED] wrote: I'm trying to setup networking on FC6. Where can I find the tun/tap interface? CONFIG_TUN But I'm pretty sure that default FC kernel has the module already built. Try: modprobe tun Luca - 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
