May 7 23:30:35 test kernel: ata2: lost interrupt (Status 0x48) There was only one error message in the guest kernel log: The machine has been running fine for about an hour of heavy disk I/O on the host and guest. I removed the disks from the SATA controller of my test machine and instead attached them to the IDE controller. Running single-core is not a long-term option for these machines. I am going to set up a test machine to try out different solutions to this problem. I simply reduced the number of virtual CPUs to 1 and it has been running fine since. Also, the system behaved quite normally as long as I didn't do anything that involved disk access.īecause this particular system is already in production use, I did not play around for long. My clock was advancing with what looked like normal speed. I tried that for a few (about 15) seconds. If you can still get into the console and run basic commands, try running 'date' a few times and see if the clock is incrementing and not looping (see my post above). Replying to Your symptoms sound identical to mine. I have had this issue with many different guests, including Ubuntu 8.04 and 10.10 and the SystemRescueCD from.
No, I am using ext3 and Ubuntu 10.04 as host. Is everybody in this discussion using ext4 file systems ? Maybe everybody is using ubuntu 10.10 ? I have put this machine in a saved state in case anyone want me to run any other commands before it crashes completely. So there definitely does appear to be something time related going on here. Then I did a little date date date date date date goes on - time "looping" between 3:08:59.xxxx and 3:09:03.xxxx. I had left a console open on the guest, so I checked the time at the command line and it reported 3:09am (while in reality it was 10:48am). When I got up this morning, I saw that the latest time on the graph was 3:09am. I had a one of my guests start exhibiting problems last night (it was graphing netflow traffic).
0 kommentar(er)
