On 01/09/2011 10:10 PM, Nikola Ciprich wrote:
Hi Avi,
sorry it took so long.
running chkdsk from windows is OK, runs pretty fast.
so there must be something different in this preboot environment.
Let's try to see what's the difference between the working machine and
the bad one.
Please
Avi,
I was forced to interrupt checkdisk on this machine, I tried it again
and it's reproducible (even on another (testing) W2K8 guests).
I transfered the image to testing machine where chkdsk runs OK and finished
it there.
So in case You'd like to continue debugging, I'm at Your disposal, we can
On 01/09/2011 02:36 PM, Nikola Ciprich wrote:
Avi,
I was forced to interrupt checkdisk on this machine, I tried it again
and it's reproducible (even on another (testing) W2K8 guests).
I transfered the image to testing machine where chkdsk runs OK and finished
it there.
So in case You'd like to
What are the differences between the host the completes chkdsk and the
host that fails? Hardware-wise and software-wise.
Software-wise, I'm not aware of any, both nodes use:
- kernel 2.6.36.2
- qemu-kvm-0.13.0
- seabios-0.6.0
hardware-wise, problematic machine is older 8core, 16GB RAM,
On Sun, Jan 09, 2011 at 02:36:55PM +0100, Nikola Ciprich wrote:
What are the differences between the host the completes chkdsk and the
host that fails? Hardware-wise and software-wise.
Software-wise, I'm not aware of any, both nodes use:
- kernel 2.6.36.2
- qemu-kvm-0.13.0
-
On 01/09/2011 03:36 PM, Nikola Ciprich wrote:
What are the differences between the host the completes chkdsk and the
host that fails? Hardware-wise and software-wise.
Software-wise, I'm not aware of any, both nodes use:
- kernel 2.6.36.2
- qemu-kvm-0.13.0
- seabios-0.6.0
hardware-wise,
On 01/09/2011 03:44 PM, Nikola Ciprich wrote:
On Sun, Jan 09, 2011 at 02:36:55PM +0100, Nikola Ciprich wrote:
What are the differences between the host the completes chkdsk and the
host that fails? Hardware-wise and software-wise.
Software-wise, I'm not aware of any, both nodes use:
Please try the newer machine, after rmmoding kvm-intel, and reloading it
with the module parameter ept=0.
seems to be OK even with parameter..
n.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line unsubscribe kvm in
the
On 01/09/2011 04:27 PM, Nikola Ciprich wrote:
Please try the newer machine, after rmmoding kvm-intel, and reloading it
with the module parameter ept=0.
seems to be OK even with parameter..
n.
Ok. Is chkdsk outside the preboot environment working okay on the bad host?
--
error compiling
Ok. Is chkdsk outside the preboot environment working okay on the bad host?
I'll check, give me some time, I'll have to add another large volume which I can
check while the system is up..
in the meantime, on hosts, I noticed following messages:
[322172.007569] kvm: 17743: cpu1 unhandled wrmsr:
Hi Avi,
sorry it took so long.
running chkdsk from windows is OK, runs pretty fast.
so there must be something different in this preboot environment.
n.
On Sun, Jan 09, 2011 at 04:15:19PM +0100, Nikola Ciprich wrote:
Ok. Is chkdsk outside the preboot environment working okay on the bad host?
Hi,
I'd like to ask for advice with following problem.
I have windows 2008 terminal server guest running on 2.6.36 x86_64
host (kvm 0.13.0).
guest has 4GB of RAM, 40GB storage on top of LVM volume and two cores.
So far everything was running fine, but during periodic maintenance
I wanted to
On Thu, Jan 6, 2011 at 7:48 AM, Nikola Ciprich extmaill...@linuxbox.cz wrote:
So windows started checking disk integrity, but the problem is, that
it's waaay too slow - after ~12 hours, it's still running and seeems
like it'll take ages to finish.
Please post your KVM command-line.
Have you
On 01/06/2011 09:48 AM, Nikola Ciprich wrote:
Hi,
I'd like to ask for advice with following problem.
I have windows 2008 terminal server guest running on 2.6.36 x86_64
host (kvm 0.13.0).
guest has 4GB of RAM, 40GB storage on top of LVM volume and two cores.
So far everything was running fine,
Hello Stefan!
Please post your KVM command-line.
/usr/bin/qemu-kvm -S -M pc-0.13 -enable-kvm -m 4096 -smp
2,sockets=2,cores=1,threads=1 -name vmwts02 -uuid
1e501300-dc48-11df-a690-00304834195b -nodefconfig -nodefaults -chardev
Hello Avi!
On Thu, Jan 06, 2011 at 11:08:32AM +0200, Avi Kivity wrote:
Let's start with a few 'kvm_stat -1' snapshots while this is going on.
here it is, but note that there are few more machines running on this host.
but they're almost idle in contrast to this windows one, so I hope it's not
On 01/06/2011 11:20 AM, Nikola Ciprich wrote:
Hello Avi!
On Thu, Jan 06, 2011 at 11:08:32AM +0200, Avi Kivity wrote:
Let's start with a few 'kvm_stat -1' snapshots while this is going on.
here it is, but note that there are few more machines running on this host.
but they're almost idle in
On 01/06/2011 11:27 AM, Avi Kivity wrote:
On 01/06/2011 11:20 AM, Nikola Ciprich wrote:
Hello Avi!
On Thu, Jan 06, 2011 at 11:08:32AM +0200, Avi Kivity wrote:
Let's start with a few 'kvm_stat -1' snapshots while this is going
on.
here it is, but note that there are few more machines
- run trace-cmd record -e kvm -b 10 -P pid1 -P pid2, ctrl-C after a
seems like it's not possible to specify multiple pids, so
I've run 4 commands in parallel. Also I can't get monitor information
since vm is started using libvirt, so I've just used all machine's qemu-kvm
pids..
hope it's OK
On 01/06/2011 11:42 AM, Nikola Ciprich wrote:
- run trace-cmd record -e kvm -b 10 -P pid1 -P pid2, ctrl-C after a
seems like it's not possible to specify multiple pids, so
Did you get 'overrun: something' reports from trace-cmd, where something
!= 0?
If you're not sure, please run the
Did you get 'overrun: something' reports from trace-cmd, where something
!= 0?
nope, all entries were 0.
Dan, is there a way to hijack the monitor so we can run some commands on
it? Things like 'info registers' and disassembly.
AFAIK that's intentionally not possible :(
pity..
Looks
On 01/06/2011 12:25 PM, Nikola Ciprich wrote:
Did you get 'overrun: something' reports from trace-cmd, where something
!= 0?
nope, all entries were 0.
Dan, is there a way to hijack the monitor so we can run some commands on
it? Things like 'info registers' and disassembly.
AFAIK that's
On Thu, Jan 06, 2011 at 12:19:21PM +0200, Avi Kivity wrote:
On 01/06/2011 11:42 AM, Nikola Ciprich wrote:
- run trace-cmd record -e kvm -b 10 -P pid1 -P pid2, ctrl-C after a
seems like it's not possible to specify multiple pids, so
Did you get 'overrun: something' reports from
OK, got test environment running, but it seems to be running much faster
there :(
but as dan suggested, I can type monitor commands using virsh, so I can
(carefully:)) continue debugging on this production machine..
here's info registers:
RAX=0007 RBX=00ac
If you have a new enough libvirt, then you can also send
commands directly using 'virsh qemu-monitor-command' (checking
whether you need JSON or HMP syntax first - in this case you
can see it needs HMP).
Thanks Dan!
didn't know this is possible, works pretty well!
n.
Regards,
Daniel
--
On 01/06/2011 02:18 PM, Nikola Ciprich wrote:
OK, got test environment running, but it seems to be running much faster
there :(
Same host kernel?
but as dan suggested, I can type monitor commands using virsh, so I can
(carefully:)) continue debugging on this production machine..
here's info
Same host kernel?
yes, I also disabled KSM now, se below.
(qemu) cpu 1
(qemu) info registers
RAX= RBX= RCX=0002
RDX=55a9
RSI=fa8003660450 RDI=0001 RBP=0080
RSP=f880009f7cc0
R8 = R9
On 01/06/2011 03:55 PM, Nikola Ciprich wrote:
Same host kernel?
yes, I also disabled KSM now, se below.
(qemu) cpu 1
(qemu) info registers
RAX= RBX= RCX=0002
RDX=55a9
RSI=fa8003660450 RDI=0001 RBP=0080
$ perf record -a -f -g
$ perf report -g
here we go:
here we go:
- 49.72% _raw_spin_lock
▒
- 32.32% kvm_mmu_pte_write
29 matches
Mail list logo
