This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] burn in program

On Jul 13, 2004, at 10:37 PM, James Harper wrote:

Has anyone tried out any burn-in program under xen? I think a neat test would be something that:
. runs the cpu load up
. pages lots
. ups and downs the network interfaces
. sends and receives lots of packets
running that under, say, 5 domains at once would give a basic test of functionality

That's exactly what I plan to do with CTCS when I finally figure out how to get -unstable up and running. :)

Other than the network stuff, CTCS severely stresses a machine/OS, and writing a script to mess with the iface and do some stuff (with iptraf perhaps) and hook to the CTCS framework isn't that difficult. It's not really a regression test, more a burn-in test, but if a machine passes CTCS for 24 hours, in my experience, it's working just fine, and it's a lot easier to set up and run than a real regression test.

"I think that's what they mean by   |
"nickels a day can feed a child."   |       http://www.eff.org/
I thought, "How can food be so      | http://www.anti-dmca.org/
cheap over there?"  It's not, they  |--------------------------
just eat the nickels." -- Peter Nguyen

"We all enter this world in the    | Support Electronic Freedom
same way: naked; screaming; soaked |        http://www.eff.org/
in blood. But if you live your     |  http://www.anti-dmca.org/
life right, that kind of thing     |---------------------------
doesn't have to stop there." -- Dana Gould

This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>