Hi Michael,
On Mon, 22.03.2010 at 10:59:06 +0100, Toni Mueller wrote:
> and then I tried again, but nothing changed (and no logs, too).
just to clarify, since I may have reported against the wrong bug:
The virtual machines do not boot with the 2.6.32* kernel, but hang with
an 'unstable clocks
Hi Michael,
On Fri, 12.03.2010 at 21:58:44 +0300, Michael Tokarev wrote:
> Toni, please verify if this bug is present in the current
> version of qemu-kvm in unstable (0.12.3+dfsg-4). If you
> don't like using unstable, try out qemu-kvm from my page
> (http://www.corpit.ru/debian/tls/kvm/ - gra
Toni Mueller wrote:
> Hi Michael,
Hello!
> On Fri, 12.03.2010 at 21:58:44 +0300, Michael Tokarev wrote:
>> Toni, please verify if this bug is present in the current
>> version of qemu-kvm in unstable (0.12.3+dfsg-4). If you
>> don't like using unstable, try out qemu-kvm from my page
>> (http://
Hi Michael,
On Mon, 22.03.2010 at 14:00:30 +0300, Michael Tokarev wrote:
> Toni, yet again, please, pretty please, read what I wrote. I refer to
> _virtual_ disk error, not to _physical_ disk error.
I read what you wrote, and I only wanted to say that I'm confident that
the physical disks are
Toni Mueller wrote at Wed, 03 Feb 2010 18:17:51 +0100:
> Package: qemu-kvm
> Version: 0.11.0+dfsg-1~bpo50+1
> Severity: important
>
> Hello,
>
> my virtual machine(s) become unresponsive every few days and need to be
> killed then. While being unresponsive, the machine consumes 100% CPU,
> fortun
Hi Michael,
On Fri, 12.03.2010 at 21:58:44 +0300, Michael Tokarev wrote:
> From what you provided above it sounds like some sort of i/o
> problem, but without much more details (exact kvm command line,
> kinds of disk devices you use, and some sorts of traces it is
> impossible to say what's goi
Toni Mueller wrote:
> Hi Michael,
>
> On Fri, 12.03.2010 at 21:58:44 +0300, Michael Tokarev wrote:
>> From what you provided above it sounds like some sort of i/o
>> problem, but without much more details (exact kvm command line,
>> kinds of disk devices you use, and some sorts of traces it is
>>
On Tue, 16.03.2010 at 17:44:05 +0300, Michael Tokarev wrote:
> Toni Mueller wrote:
> > and Sid machines. I've done both with the old qemu-kvm package, though,
> > and have to note that the Sid kvm does not start with the
> > 2.6.32-3 kernel (but hangs at the tsc clocksource unstable message that
Toni Mueller wrote:
[]
>>> kvm -localtime -no-acpi -m 512 \
>>> -net nic,model=rtl8139,macaddr=52:54:00:12:34:56,vlan=0 \
>>> -daemonize \
>>> -net tap,vlan=0 /mounts/vmachines/kvm/d-sid/sid1.img &
>>> --- cut
>> Ugh, can you retry without -no-acpi? -no-acpi
Hi,
On Tue, 16.03.2010 at 20:01:20 +0300, Michael Tokarev wrote:
> Toni Mueller wrote:
> > Umm... I thought acpi was asking for trouble. But what you said - I
> > retried without the -noacpi, and it still hangs with the 2.6.32-3 from
> > unstable (I just dist-upgraded the whole vm today before t
Package: qemu-kvm
Version: 0.11.0+dfsg-1~bpo50+1
Severity: important
Hello,
my virtual machine(s) become unresponsive every few days and need to be
killed then. While being unresponsive, the machine consumes 100% CPU,
fortunately only on one of my cores. Usually, some benign action
triggers the
11 matches
Mail list logo
