It appears that writeback caching was turned off in qemu for qcow2 in June 2009
because qcow2 was "fast". Then a new patch was applied in July 2010 that made
qcow2 slow again! I was able to solve my problems by turning on writeback
cache.
However, this creates a huge migration issue for any
>, and thread showed high cpu use.
>
>then I tried your next suggestion...
>qemu-img create win1.img 20G
>kvm -hda win1.img -cdrom win2003*.iso -m 1G -boot d
>
>my actual line was:
>sudo kvm -hda win1.img -cdrom win2k3.iso -m 1G -boot d
>and the returned the error "Could not initialize
I tried to do another win2k3 install, this time via libvirt xml file. I
used a minimal config. The install was immediately running very slow,
possibly due to using a qcow disk file and/or not having used any virtio
config. It ran so slow though with the disk io wait, that it brought the
load averag
Okay, so it appears to be a problem with something that is saved in the
image. I can use the full cmd and it runs...
sudo /usr/bin/kvm -M pc-0.12 -enable-kvm -m 1024 -smp 1 -name newtuna
-uuid 21a3c860-05b0-5dcf-cc8c-9243604f8e9b -localtime -boot c -drive
file=win1.img -drive
file=/mnt/isos/win200
Serge,
The version of windows I am using is, Microsoft Windows Server 2003 R2 with SP2
Enterprise Edition.
The kvm command I tested was:
kvm -drive file=/mnt/slices/newtuna.qcow2,if=virtio,index=0,boot=on -m 1G
-vnc :1
and that gave me the same result, blank screen, high cpu usage.
I just
Steven,
so when you ran kvm from the command line without using libvirt, as described
in comment #8, did you still have the failure? What exactly did your command
look like?
The simplest command which should definately work would be:
qemu-img create win1.img 20G
kvm -hda win1.img -cdrom w
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => Medium
** Changed in: qemu-kvm (Ubuntu)
Status: New => In Progress
--
win2k3 guest has blank screen and high cpu on first boot
https://bugs.launchpad.net/bugs/671163
You received this bug notification because you are a member of
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => New
--
win2k3 guest has blank screen and high cpu on first boot
https://bugs.launchpad.net/bugs/671163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Serge -
Ill jump to the point and tell you that Ive tried without virtio as well, and
the problem remains that same. Thanks for your continued help on this issue. Im
blocked on migrating any windows hosts for now. The only other time ive seen
something like this was when my server has Cpu frequ
Could not reproduce on 10.04 (amd64) host either.
Please start up the VM with libvirt, and do 'ps -ef | grep kvm' to find the
command being used to start the VM. Then trim things like vnc, serial,
parallel and monitor options, add 'monitor stdio', and start the command
by hand. Try it once with
Actually, I just noticed that your .xml specifies virtio for the block device.
Win 2003 by default does not support that. Did you do anything special
during install? Did you install the virtio drivers, and if so, where did you
get them?
--
win2k3 guest has blank screen and high cpu on first boo
Couldn't reproduce with a win2003 32-bit R2 SP2 on 10.10 host. I'll try on
10.04 when I have a chance to reboot.
--
win2k3 guest has blank screen and high cpu on first boot
https://bugs.launchpad.net/bugs/671163
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am trying to reproduce this locally - can you tell me exactly which version
you are
using? I am planning to try windows server 2003 Standard edition, SP2.
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
--
win2k3 guest has blank screen and high cpu
Serge - I did as you requested. When running the guest using that kvm
command, and then accessing it with vncviewer, I still get the same
black screen. 'top' on the server shows the process using 99% cpu.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => New
--
win2k3 guest has blan
Could you try running the VM without libvirt, using vnc?
Something like
kvm -drive file=/mnt/slices/newtuna.qcow2,if=virtio,index=0,boot=on -m
1G -vnc :1
should suffice. Then connect to it using 'vcnviewer :1'.
--
win2k3 guest has blank screen and high cpu on first boot
https://bugs.launchpad
(Note, I'm not asking you to make this your regular procedure, just trying
to figure out where the problem is)
** Changed in: qemu-kvm (Ubuntu)
Status: New => Incomplete
--
win2k3 guest has blank screen and high cpu on first boot
https://bugs.launchpad.net/bugs/671163
You received this bu
** Attachment added: "Attaching the libvirt guest conf I am using."
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/671163/+attachment/1723306/+files/win2k3guest.xml
--
win2k3 guest has blank screen and high cpu on first boot
https://bugs.launchpad.net/bugs/671163
You received this b
--
win2k3 guest has blank screen and high cpu on first boot
https://bugs.launchpad.net/bugs/671163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
18 matches
Mail list logo
