Hi Avi,
Avi Kivity wrote:
Erik Rull wrote:
The file system is the guest's business. Instead of '-hda /dev/hda2', try
-drive file=/dev/hda2,cache=none
great!
cache=off worked - none caused an error.
The Timing problem is still present but the XP system is now much more
interactive during
Hi Avi,
Avi Kivity wrote:
Erik Rull wrote:
The file system is the guest's business. Instead of '-hda /dev/hda2', try
-drive file=/dev/hda2,cache=none
great!
cache=off worked - none caused an error.
The Timing problem is still present but the XP system is now much more
interactive during
Erik Rull wrote:
Hi Avi,
Avi Kivity wrote:
interface: virtio
cache: none
format: raw, using a partition or logical volume
What are you using?
uhm, I'm not sure, I call qemu with:
qemu-system-x86_64 -usb -hda /dev/hda2 -m 1536 -net
nic,macaddr=$MACADDR -net tap,script=/etc/qemu-ifup
Erik Rull wrote:
Are you using qcow2? In some cases qcow2 will stall the guest cpu.
Note that defragmenting the guest drive may cause the qcow2 file to
fragment even more, and will certainly increase its size. I
recommend only defragmenting when using raw storage.
I don't think so. I
Hi Avi,
Avi Kivity wrote:
interface: virtio
cache: none
format: raw, using a partition or logical volume
What are you using?
uhm, I'm not sure, I call qemu with:
qemu-system-x86_64 -usb -hda /dev/hda2 -m 1536 -net nic,macaddr=$MACADDR
-net tap,script=/etc/qemu-ifup -no-acpi -monitor stdio
Erik Rull wrote:
Hi all,
I'm running kvm-77 and windows xp as guest. When I start the
defragmentation of the virtualized drive within the windows guest
(well this is not a fine way, but it should work :-)), the real time
clock starts hanging - I recognized that because some underlying
Hi Avi,
Avi Kivity wrote:
Are you using qcow2? In some cases qcow2 will stall the guest cpu.
Note that defragmenting the guest drive may cause the qcow2 file to
fragment even more, and will certainly increase its size. I recommend
only defragmenting when using raw storage.
I don't think
