Am 18.05.2010 um 15:51 schrieb Alexander Graf:
Peter Lieven wrote:
Alexander Graf wrote:
Peter Lieven wrote:
we are running on intel xeons here:
That might be the reason. Does it break when passing -no-kvm?
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model
On 18.05.2010, at 11:14, Peter Lieven wrote:
Hi,
we try to migrate some Suse Linux Enterprise 10 64-bit guests from abandoned
Virtual Iron by Iron Port to qemu-kvm 0.12.4. Unfortunately the guests are not
very stable by now. With ACPI they end up in a kernel panic at boot time and
Alexander Graf wrote:
On 18.05.2010, at 11:14, Peter Lieven wrote:
Hi,
we try to migrate some Suse Linux Enterprise 10 64-bit guests from abandoned
Virtual Iron by Iron Port to qemu-kvm 0.12.4. Unfortunately the guests are not
very stable by now. With ACPI they end up in a kernel panic at
On 18.05.2010, at 11:57, Peter Lieven wrote:
Alexander Graf wrote:
On 18.05.2010, at 11:14, Peter Lieven wrote:
Hi,
we try to migrate some Suse Linux Enterprise 10 64-bit guests from abandoned
Virtual Iron by Iron Port to qemu-kvm 0.12.4. Unfortunately the guests are
not
very
hi alex,
what 64-bit -cpu types do you suggest?
when i boot the kernel with nohpet it simply hangs shortly after
powersaved...
br,
peter
Alexander Graf wrote:
On 18.05.2010, at 11:57, Peter Lieven wrote:
Alexander Graf wrote:
On 18.05.2010, at 11:14, Peter Lieven wrote:
Sorry, ommitted your questions. This particular system
is still runnung on
/kernel: /2.6.31-14-server, /bin: /qemu-kvm-0.12.2, /mod: /kvm-kmod-2.6.32.7
If there where any fixes improvements I can try on:
/kernel: /2.6.33.3, /bin: /qemu-kvm-0.12.4, /mod: /2.6.33.3
BR,
Peter
Alexander Graf
Hi Peter,
On 18.05.2010, at 12:18, Peter Lieven wrote:
Sorry, ommitted your questions. This particular system
is still runnung on
Please don't top post.
/kernel: /2.6.31-14-server, /bin: /qemu-kvm-0.12.2, /mod: /kvm-kmod-2.6.32.7
This looks reasonable.
Alex
--
To unsubscribe from
On 18.05.2010, at 12:12, Peter Lieven wrote:
hi alex,
what 64-bit -cpu types do you suggest?
For starters I'd say try -cpu host.
Alex
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at
hi alex,
unfortunately -cpu host, -cpu qemu64, -cpu core2duo, -cpu kvm64 (which
should be default) doesn't help
all other cpus available are 32-bit afaik.
as i said if i boot with with kernel parameter nohpet, but acpi on the
guest just hangs at 100% cpu.
would a backtrace help?
br,
peter
On 18.05.2010, at 13:01, Peter Lieven wrote:
hi alex,
unfortunately -cpu host, -cpu qemu64, -cpu core2duo, -cpu kvm64 (which should
be default) doesn't help
all other cpus available are 32-bit afaik.
as i said if i boot with with kernel parameter nohpet, but acpi on the
guest just
Alexander Graf wrote:
On 18.05.2010, at 13:01, Peter Lieven wrote:
hi alex,
unfortunately -cpu host, -cpu qemu64, -cpu core2duo, -cpu kvm64 (which should
be default) doesn't help
all other cpus available are 32-bit afaik.
as i said if i boot with with kernel parameter nohpet, but acpi on
hi alex,
here is a backtrace of the sles 10 sp1 vm running on qemu-kvm 0.12.4.
hanging at boot.
a colleguage is meanwhile upgraded a cloned system to sp3 to see if it
is also
not working.
^C
Program received signal SIGINT, Interrupt.
[Switching to Thread 0x7f0b753c76f0 (LWP 25532)]
Peter,
Peter Lieven wrote:
hi alex,
here is a backtrace of the sles 10 sp1 vm running on qemu-kvm 0.12.4.
hanging at boot.
Please do not top post! Seriously. One more time and I'll stop responding.
I tried to reproduce this locally on an openSUSE 11.1 system using
latest
Alexander Graf wrote:
Peter,
Peter Lieven wrote:
hi alex,
here is a backtrace of the sles 10 sp1 vm running on qemu-kvm 0.12.4.
hanging at boot.
Please do not top post! Seriously. One more time and I'll stop responding.
I tried to reproduce this locally on an openSUSE 11.1 system
Peter Lieven wrote:
we are running on intel xeons here:
That might be the reason. Does it break when passing -no-kvm?
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 26
model name: Intel(R) Xeon(R) CPU L5530 @ 2.40GHz
stepping: 5
cpu MHz
Alexander Graf wrote:
Peter Lieven wrote:
we are running on intel xeons here:
That might be the reason. Does it break when passing -no-kvm?
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 26
model name: Intel(R) Xeon(R) CPU L5530 @
Peter Lieven p...@dlh.net writes:
Starting mail service (Postfix)
NMI Watchdog detected LOCKUP on CPU 0
You could simply turn off the NMI watchdog (nmi_watchdog=0 at the kernel
command line)
Perhaps the PMU emulation is not complete and nmi watchdog
needs PMU. It's not really needed
Peter Lieven wrote:
Alexander Graf wrote:
Peter Lieven wrote:
we are running on intel xeons here:
That might be the reason. Does it break when passing -no-kvm?
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 26
model name: Intel(R) Xeon(R)
Alexander Graf wrote:
Peter Lieven wrote:
Alexander Graf wrote:
Peter Lieven wrote:
we are running on intel xeons here:
That might be the reason. Does it break when passing -no-kvm?
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model
19 matches
Mail list logo
