So we've finally confirmed, that on cleanly installed guest, (or previously
created image of w2k8) we can't reproduce the problem, only with this one
particular image.
I'd not worry about it anymore, I'll just have this one reinstalled.
thanks for Your time and sorry for delays
nik
On Wed, Jun
Hello Avi,
sorry, I've been off for vacation for few days now. I think even clean
preinstalled guest worked properly, only the one particular production machine
didn't.
I'll confirm during this week.
n.
Does installing the same guest software into a new image work?
--
error compiling
On 05/27/2011 12:05 PM, Nikola Ciprich wrote:
Hello Avi,
Try appending ,cache=none to the -drive parameter?
nope, unfortunately same result :(
n.
Does installing the same guest software into a new image work?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe
On 05/26/2011 03:56 PM, Nikola Ciprich wrote:
Should be more like that one with correct image path:
huh, now I got a bit lost :)
I tried running both:
/usr/bin/qemu-kvm -M pc-0.13 -enable-kvm -m 4096 -smp
1,sockets=1,cores=1,threads=1 -name vmtst04 -uuid
1f8328b8-8849-11e0-91e9-00259009d78c
Hello Avi,
Try appending ,cache=none to the -drive parameter?
nope, unfortunately same result :(
n.
Maybe we have a regression with writethrough block devices (a bad idea
anyway).
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
On Thu, May 26, 2011 at 11:59:10AM +0200, Nikola Ciprich wrote:
Hello,
after I tried updating our production host to 0.14.0 or 0.14.1, our windows
terminal server stopped booting.
Here's BSOD screen:
http://nik.lbox.cz/public/wincrash.png
reverting to 0.13.5 fixes the problem.
I can't
Hello Gleb!
What is you command line?
currently it's:
/usr/bin/qemu-kvm -S -M pc-0.13 -enable-kvm -m 4096 -smp
1,sockets=1,cores=1,threads=1 -name vmwts02 -uuid
1e501300-dc48-11df-a690-00304834195b -nodefconfig -nodefaults -chardev
On Thu, May 26, 2011 at 12:20:56PM +0200, Nikola Ciprich wrote:
You can make a copy from your production image, install 0.14 version in
different place from 0.13 and experiment.
yup, I think I've tried it also with exact copy and wasn't able to reproduce
it, but I'll try it again and report
OK, I tried copying the whole image to my test box running 0.14.0 again and it
crashes with exactly the same BSOD!
So now I have the test environment to play with...
What should I check/try now?
n.
PS: I'm not sure what You mean by permissions, but I'm using LVM partitions and
qemu-kvm is
On Thu, May 26, 2011 at 01:50:35PM +0200, Nikola Ciprich wrote:
OK, I tried copying the whole image to my test box running 0.14.0 again and
it crashes with exactly the same BSOD!
So now I have the test environment to play with...
What should I check/try now?
n.
PS: I'm not sure what You
This BSOD usually indicates that Windows can't write to the boot disk.
This is usually happens if qemu has no permission to write to the image
file. But if you are starting qemu as a root this is probably is not the
OK, I see.
case. So what is your 0.14 command line?
here it goes:
On Thu, May 26, 2011 at 02:03:57PM +0200, Nikola Ciprich wrote:
This BSOD usually indicates that Windows can't write to the boot disk.
This is usually happens if qemu has no permission to write to the image
file. But if you are starting qemu as a root this is probably is not the
OK, I see.
May be libvirt does something funny with selinux.
it shouldn't, I don't have selinux enabled in host kernel at all..
Try to run with -M pc-0.13.
tried now, same result...
--
Gleb.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a
On Thu, May 26, 2011 at 02:30:00PM +0200, Nikola Ciprich wrote:
May be libvirt does something funny with selinux.
it shouldn't, I don't have selinux enabled in host kernel at all..
Try to run with -M pc-0.13.
tried now, same result...
Hmm. And what if you start qemu directly (without
Hmm. And what if you start qemu directly (without using libvirt) with 0.13
command line?
/usr/bin/qemu-kvm -M pc-0.13 -enable-kvm -m 4096 -boot c -drive
file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device
ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -vnc
On Thu, May 26, 2011 at 02:46:30PM +0200, Nikola Ciprich wrote:
Hmm. And what if you start qemu directly (without using libvirt) with 0.13
command line?
/usr/bin/qemu-kvm -M pc-0.13 -enable-kvm -m 4096 -boot c -drive
file=/dev/vgshared/vmtst04-1,if=none,id=drive-ide0-0-0,format=raw -device
Should be more like that one with correct image path:
huh, now I got a bit lost :)
I tried running both:
/usr/bin/qemu-kvm -M pc-0.13 -enable-kvm -m 4096 -smp
1,sockets=1,cores=1,threads=1 -name vmtst04 -uuid
1f8328b8-8849-11e0-91e9-00259009d78c -nodefconfig -nodefaults -chardev
socket,id=char
On Thu, May 26, 2011 at 02:56:40PM +0200, Nikola Ciprich wrote:
Should be more like that one with correct image path:
huh, now I got a bit lost :)
I tried running both:
/usr/bin/qemu-kvm -M pc-0.13 -enable-kvm -m 4096 -smp
1,sockets=1,cores=1,threads=1 -name vmtst04 -uuid
No, try to run the one I gave you. Just replace the image file path. I
do no have much hope it will work though, but worth trying.
OK, I tried, I just had to remove the monitor device. Still, it fails the same
way...
n.
--
Gleb.
--
To unsubscribe from this list:
On Thu, May 26, 2011 at 03:15:19PM +0200, Nikola Ciprich wrote:
No, try to run the one I gave you. Just replace the image file path. I
do no have much hope it will work though, but worth trying.
OK, I tried, I just had to remove the monitor device. Still, it fails the
same way...
According
According to this:
http://social.msdn.microsoft.com/Forums/en-US/embeddedwindowscomponents/thread/09aae527-ff6d-4003-9e59-962d73d409ed
such bsod happens because Windows can't access boot device. Your boot
device is IDE. Nothing changed in this area from 13 to 14. Are you sure
your image was
On Thu, May 26, 2011 at 03:32:43PM +0200, Nikola Ciprich wrote:
According to this:
http://social.msdn.microsoft.com/Forums/en-US/embeddedwindowscomponents/thread/09aae527-ff6d-4003-9e59-962d73d409ed
such bsod happens because Windows can't access boot device. Your boot
device is IDE.
In this case I am very puzzled :)
well, so am I :)
but at least, I now know there seems to be problem with disk access. I'll ask
some of our windows guys to try some failsave mode or something and find out
what is going on...
I'll report when I know something.
thanks for Your help!
n.
--
23 matches
Mail list logo
