Advertisement
Guest User

Untitled

a guest
Mar 24th, 2010
255
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.41 KB | None | 0 0
  1. 03:59 < prometheanfire > well, I do love getting crashes on disk activity
  2. 04:01 < prometheanfire > I'll ask about it tomorrow as everyone seems to be asleep
  3. 04:02 < mjt > wassup?
  4. 04:02 < prometheanfire > I'm getting crashes on high disk activity
  5. 04:03 < prometheanfire > kvm 0.11.1
  6. 04:03 < mjt > what sorts of crashes?
  7. 04:03 < prometheanfire > odd crashes
  8. 04:03 < prometheanfire > it's like the disk disapears
  9. 04:03 < agraf__ > prometheanfire: what disk backend? ide? scsi? virtio?
  10. 04:04 < prometheanfire > I can still get console but network dies
  11. 04:04 < prometheanfire > now that I think about it, it happened when I hit alot of net activity, I can do high disk load all day long
  12. 04:04 < prometheanfire > but it is with virtio
  13. 04:04 < prometheanfire > /usr/bin/kvm -monitor unix:/var/run/qemu-server/102.mon,server,nowait -vnc unix:/var/run/qemu-server/102.vnc,password -pidfile /var/run/qemu-server/102.pid -daemonize -usbdevice tablet -name library -smp
  14. sockets=1,cores=1 -boot menu=on,order=c -vga cirrus -tdf -localtime -k en-us -drive file=/dev/raid/vm-102-disk-2,if=virtio,index=1 -drive file=/dev/raid/vm-102-disk-1,if=virtio,index=0,boot=on -m 512 -net
  15. tap,vlan=3,ifname=vmtab102i3,script=/var/lib/qemu-server/bridge-vlan -net nic,vlan=3,model=virtio,macaddr=10:10:10:10:10:10
  16. 04:05 < prometheanfire > I'm gonna test it
  17. 04:05 < agraf__ > prometheanfire: what guest kernel?
  18. 04:05 < prometheanfire > 2.6.32-r3
  19. 04:05 < mjt > what's "r3" ?
  20. 04:06 < prometheanfire > release 3
  21. 04:06 < mjt > return -ENOSUCHRELEASE;
  22. 04:06 < prometheanfire > Linux library 2.6.32-hardened-r3 #3 SMP PREEMPT Thu Mar 4 16:16:52 EST 2010 x86_64 QEMU Virtual CPU version 0.11.1 GenuineIntel GNU/Linux
  23. 04:10 < prometheanfire > heh, I'm hitting 100% cpu on a 40MBps file transfer (which is about 20 times faster then the speed I was experiencing before
  24. 04:10 < prometheanfire > well, if I don't respond soon, you will know that I crashed
  25. 04:10 < mjt > there was a race in kvm
  26. 04:10 < prometheanfire > well, it's doing 45MBps
  27. 04:11 < prometheanfire > race?
  28. 04:11 < mjt > and a thread "network stops under high load" or somesuch
  29. 04:11 < mjt > race condition
  30. 04:11 < prometheanfire > I think it happens under bittorrent conditions, not single file transfer conditions
  31. 04:11 < mjt > " network shutdown under heavy load
  32. 04:11 < mjt > "
  33. 04:12 < prometheanfire > I'm gonna limit my connection to about half and see how it goes
  34. 04:12 < prometheanfire > so if I crash you know why lol
  35. 04:13 < prometheanfire > mjt: you know if this has been fixed in git (I tested the git kernel and had the same issue 0.12.50)
  36. 04:13 < mjt > http://www.mail-archive.com/kvm@vger.kernel.org/msg26033.html
  37. 04:13 < prometheanfire > lol, it's called vger
  38. 04:13 < mjt > http://marc.info/?l=kvm&m=126564542625725&w=2
  39. 04:13 < mjt > that's the patch
  40. 04:14 < prometheanfire > well, I tested with a git pull from a week ago and still had the issue
  41. 04:16 < mjt > in current kvm git that patch is not present
  42. 04:16 < prometheanfire > awesome, thanks
  43. 04:16 < mjt > err
  44. 04:16 < mjt > no, it is
  45. 04:16 < prometheanfire > even better lol
  46. 04:17 < prometheanfire > well, I reduced load to 900KBps
  47. 04:17 < mjt > 06b1297017415ae6a07a0e97ad7d8e90b2d95823
  48. 04:17 < mjt > Date: Mon Feb 8 10:10:01 2010 -0600
  49. 04:17 < prometheanfire > huh
  50. 04:18 < prometheanfire > ya, the kvm in proxmox is oldish
  51. 04:18 < prometheanfire > 0.11.1
  52. 04:19 < prometheanfire > I'm gonna poke them to update it because, to me at least, this is a big problem
  53. 04:20 < mjt > http://www.proxmox.com/forum/showthread.php?t=3117
  54. 04:21 < mjt > but apparently that's something different
  55. 04:21 < mjt > (crashing, not freezing)
  56. 04:21 < prometheanfire > ya, I'm posting in that thread
  57. 04:21 < prometheanfire > might make a thread of my own too
  58. 04:22 < prometheanfire > they are actually pretty good about communication
  59. 04:22 < prometheanfire > WAY better then asus
  60. 04:23 < prometheanfire > is 06b1297017415ae6a07a0e97ad7d8e90b2d95823 a git string or something
  61. 04:23 < prometheanfire > I don't know how to describe it to them
  62. 04:23 < prometheanfire > I think I may just pastebin this whole conversation for them
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement