https://bugzilla.kernel.org/show_bug.cgi?id=38672
Summary: KVM guest boot crashed
Product: Virtualization
Version: unspecified
Kernel Version: 3.0.0-rc5+
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
On 2011-07-02 08:56, bugzilla-dae...@bugzilla.kernel.org wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=38672
Summary: KVM guest boot crashed
Product: Virtualization
Version: unspecified
Kernel Version: 3.0.0-rc5+
Platform: All
https://bugzilla.kernel.org/show_bug.cgi?id=38672
--- Comment #1 from Anonymous Emailer anonym...@kernel-bugs.osdl.org
2011-07-02 08:24:18 ---
Reply-To: jan.kis...@web.de
On 2011-07-02 08:56, bugzilla-dae...@bugzilla.kernel.org wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=38672
* Asias He asias.he...@gmail.com wrote:
I don't care too much what we use as the namespace prefix but as
a directory name tools/kvm/uip is pretty meaningless. I'd just
move the code under tools/kvm/net to mirror what the kernel
already has.
I have thought about putting user mode
https://bugzilla.kernel.org/show_bug.cgi?id=38672
--- Comment #2 from Steve stefan.bo...@gmail.com 2011-07-02 09:04:56 ---
(In reply to comment #1)
Reply-To: jan.kis...@web.de
On 2011-07-02 08:56, bugzilla-dae...@bugzilla.kernel.org wrote:
On Fri, 2011-07-01 at 13:53 +0200, Ingo Molnar wrote:
* Asias He asias.he...@gmail.com wrote:
Usermode TCP/IP can be quite cumbersome for users as things like
ping and ip6 won't work properly.
Yes, usermode TCP/IP do have limits. But it's more cumbersome for
user to setup
On Fri, 2011-07-01 at 15:46 +0200, Alexander Graf wrote:
That's pretty impressive (if it does not come at the expensive of
features that Qemu's slirp code has) - and the thing is that we don't
actually have to implement the vast majority of TCP-IP features,
because the transport between
On Fri, 1 Jul 2011, Aneesh Kumar K.V wrote:
don't do a copy of the kernel header
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
I see this error with your patch applied:
cc1: warnings being treated as errors
In file included from virtio/9p.c:20:
* Pekka Enberg penb...@kernel.org wrote:
On Fri, 1 Jul 2011, Aneesh Kumar K.V wrote:
don't do a copy of the kernel header
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
I see this error with your patch applied:
cc1: warnings being treated as errors
In file included
On Fri, 2011-07-01 at 17:22 -0400, Glauber Costa wrote:
@@ -1971,8 +1974,14 @@ static inline u64 steal_ticks(u64 steal)
static void update_rq_clock_task(struct rq *rq, s64 delta)
{
- s64 irq_delta;
-
+/*
+ * In theory, the compile should just see 0 here, and optimize out the call
* Pekka Enberg penb...@kernel.org wrote:
On Fri, 2011-07-01 at 15:46 +0200, Alexander Graf wrote:
That's pretty impressive (if it does not come at the expensive of
features that Qemu's slirp code has) - and the thing is that we don't
actually have to implement the vast majority of
On Fri, 2011-07-01 at 17:22 -0400, Glauber Costa wrote:
@@ -3929,6 +3945,23 @@ void account_process_tick(struct task_struct *p, int
user_tick)
return;
}
+#ifdef CONFIG_PARAVIRT
+ if (static_branch(paravirt_steal_enabled)) {
+ u64 steal, st =
On Fri, 2011-07-01 at 17:22 -0400, Glauber Costa wrote:
This patch makes update_rq_clock() aware of steal time.
The mechanism of operation is not different from irq_time,
and follows the same principles. This lives in a CONFIG
option itself, and can be compiled out independently of
the rest
On 02.07.2011, at 11:45, Pekka Enberg penb...@kernel.org wrote:
On Fri, 2011-07-01 at 15:46 +0200, Alexander Graf wrote:
That's pretty impressive (if it does not come at the expensive of
features that Qemu's slirp code has) - and the thing is that we don't
actually have to implement the
I think there are no way to tell the kernel didn't dump guest os memory.
for current kernel, /proc/pid/coredump_filter only support the
following 7 memory types.
- (bit 0) anonymous private memory
- (bit 1) anonymous shared memory
- (bit 2) file-backed private memory
- (bit 3) file-backed
On 02.07.2011, at 11:45, Pekka Enberg penb...@kernel.org wrote:
On Fri, 2011-07-01 at 15:46 +0200, Alexander Graf wrote:
That's pretty impressive (if it does not come at the expensive of
features that Qemu's slirp code has) - and the thing is that we don't
actually have to implement the vast
On 07/01/2011 06:42 PM, Alexander Graf wrote:
On 01.07.2011, at 17:35, Hannes Reinecke wrote:
This patch adds an emulation for the LSI Megaraid SAS 8708EM2 HBA.
Have you tried to execute the current version of megasas and actually
do something with it? I just booted up openSUSE 11.4
Am 02.07.2011 um 15:50 schrieb Hannes Reinecke h...@suse.de:
On 07/01/2011 06:42 PM, Alexander Graf wrote:
On 01.07.2011, at 17:35, Hannes Reinecke wrote:
This patch adds an emulation for the LSI Megaraid SAS 8708EM2 HBA.
Have you tried to execute the current version of megasas and
Am 02.07.2011 um 13:27 schrieb Pekka Enberg penb...@kernel.org:
On 02.07.2011, at 11:45, Pekka Enberg penb...@kernel.org wrote:
On Fri, 2011-07-01 at 15:46 +0200, Alexander Graf wrote:
That's pretty impressive (if it does not come at the expensive of
features that Qemu's slirp code has) -
On Fri, Jul 1, 2011 at 4:35 PM, Hannes Reinecke h...@suse.de wrote:
+static void megasas_mmio_writel(void *opaque, target_phys_addr_t addr,
+ uint32_t val)
+{
+ MPTState *s = opaque;
+ target_phys_addr_t frame_addr;
+ uint32_t frame_count;
+ int i;
https://bugzilla.kernel.org/show_bug.cgi?id=38672
--- Comment #3 from Steve stefan.bo...@gmail.com 2011-07-03 00:48:13 ---
Here is result:
6506e4f995967b1a48cc34418c77b318df92ce35 is the first bad commit
commit 6506e4f995967b1a48cc34418c77b318df92ce35
Author: Stefano Stabellini
https://bugzilla.kernel.org/show_bug.cgi?id=38672
--- Comment #4 from Steve stefan.bo...@gmail.com 2011-07-03 01:00:44 ---
You should have KVM guest with more than 4 GB memory.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail
22 matches
Mail list logo
