Bugs item #2001452, was opened at 2008-06-24 08:27
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2001452&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: intel
Group: None
>Status: Pending
Resolution: None
Priority: 7
Private: No
Submitted By: gwachs (gerdwachs)
Assigned to: Nobody/Anonymous (nobody)
Summary: Restarted Windows 2003 Server guests have disk corruption
Initial Comment:
I have a number of Windows 2003 32Bit guests.
I use them to perform installation and configuration
tests of a large software product.
During these tests, the guests are restarted.
Randomly, the guests produce disk corruption messages
after a restart.
The following are two examples :
-------------------------------------------------------
Windows Registry Hive Recovered
Registry hive (file): SOFTWARE was corrupted and it has
been recovered. Some data might have been lost.
-------------------------------------------------------
The system cannot log on due to the following error:
Unable to complete the requested operation because of
either a catastrophic media failure or a data structure
corruption on the disk.
-------------------------------------------------------
OS : Ubuntu 8.04 x86_64
Kernel : 2.6.24-18-server #1 SMP x86_64 GNU/Linux
KVM : kvm-70
CPU : Intel(R) Core(TM)2 Quad CPU @ 2.40GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2
ssse3 cx16 xt
Start Command : sudo /usr/local/kvm/bin/qemu-system-x86_64 -hda asit51ascs.img \
-m 1024 -std-vga -boot c -k sv -usb -usbdevice tablet -snapshot
-vnc :51 \
-net nic,vlan=0,macaddr=00:16:3e:00:51:00 -net
tap,vlan=0,script=/etc/qemu-ifup-br0 \
-net nic,vlan=1,macaddr=00:16:3e:00:51:01 -net
tap,vlan=1,script=/etc/qemu-ifup-br1
no-kvm : Cannot do due to the loss of performance.
Tests execute time is 7 hours with kvm.
----------------------------------------------------------------------
>Comment By: Avi Kivity (avik)
Date: 2008-07-16 17:23
Message:
Logged In: YES
user_id=539971
Originator: NO
What disk format are you using?
Does switching to raw format help?
----------------------------------------------------------------------
Comment By: gwachs (gerdwachs)
Date: 2008-07-10 08:10
Message:
Logged In: YES
user_id=2122332
Originator: YES
Regarding using daily builds.
>From Build 20080707, my existing guests would not start.
Have rebuilt one guest using 20080708. Seems OK but need
to be running more guests for longer time to be sure.
I will not have access to the environment from July 12 to Aug 10
----------------------------------------------------------------------
Comment By: gwachs (gerdwachs)
Date: 2008-06-30 14:27
Message:
Logged In: YES
user_id=2122332
Originator: YES
Sorry, I am not that advanced on the usage of git.
If you would care to send instructions, I will try.
I am currently using the latest snapshots.
It appears to be working enough to for my requirements, but I have still
been getting the odd corruption message.
P.S. I believe that kvm is an absolute winning concept.
----------------------------------------------------------------------
Comment By: Brian Jackson (iggy_cav)
Date: 2008-06-27 17:09
Message:
Logged In: YES
user_id=611130
Originator: NO
For some reason, I thought a virtio patch would help you, when you
obviously aren't using that with windows guests. It could still be
something with the i/o thread though. Is there any way you can do a git
bisect to figure out where exactly it breaks? I know it's hard to do
something like that when it takes so long to trigger the issue. It may be
our only option though.
kvm-69 doesn't have the i/o thread (I think), so it should be safe to use
if you just need something that works.
----------------------------------------------------------------------
Comment By: gwachs (gerdwachs)
Date: 2008-06-27 13:44
Message:
Logged In: YES
user_id=2122332
Originator: YES
Patch did not fix problem.
Had one XP guest hang with build 20080626
Are currently running with build 20080626 on both hosts
to assess disk corruption occurances.
----------------------------------------------------------------------
Comment By: gwachs (gerdwachs)
Date: 2008-06-27 11:25
Message:
Logged In: YES
user_id=2122332
Originator: YES
Regarding the patch. This seemed to fix the problem,
but will keep re-running for a week before being certain.
Regarding the computer freezing, tried snapshot 20080626,
whilst one guest SEEMED to hang for seconds/minutes, it kept running.
Thank you very much iggy_cav
----------------------------------------------------------------------
Comment By: gwachs (gerdwachs)
Date: 2008-06-26 13:18
Message:
Logged In: YES
user_id=2122332
Originator: YES
I have applied the patch and begun testing.
I will update after testing.
----------------------------------------------------------------------
Comment By: Brian Jackson (iggy_cav)
Date: 2008-06-25 15:59
Message:
Logged In: YES
user_id=611130
Originator: NO
Can you try to revert (patch -R) the virtio async feature? Someone else in
the irc channel that was having fs corruption had luck doing that.
http://people.redhat.com/~mtosatti/virtioblk-async.patch
Otherwise, just stick with the kvm-69 userspace until it's fixed.
----------------------------------------------------------------------
Comment By: gwachs (gerdwachs)
Date: 2008-06-25 10:26
Message:
Logged In: YES
user_id=2122332
Originator: YES
Windows 2003 Guests also have random BSOD
The problems in this bug report put a stop to running Windows 2003 Server
on kvm
at this point in time.
----------------------------------------------------------------------
Comment By: gwachs (gerdwachs)
Date: 2008-06-24 11:33
Message:
Logged In: YES
user_id=2122332
Originator: YES
The message : apic write: bad size=1 fee00030
does not occur when using the option : -no-kvm-irqchip
Will continue testing.
----------------------------------------------------------------------
Comment By: gwachs (gerdwachs)
Date: 2008-06-24 11:15
Message:
Logged In: YES
user_id=2122332
Originator: YES
The message : apic write: bad size=1 fee00030
only occurs when the guest is started using kvm.
i.e does not occur with the -no-kvm option.
When using the -no-acpi option, the guest does not start kvm or no kvm
----------------------------------------------------------------------
Comment By: gwachs (gerdwachs)
Date: 2008-06-24 10:32
Message:
Logged In: YES
user_id=2122332
Originator: YES
Noted that I get the following in the linux console :
apic write: bad size=1 fee00030
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2001452&group_id=180599
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
