Hi,
I have gotten Windows 7 to install and boot on KVM now, but now I'm having
another problem: The qemu process that the Windows guest is running in is
constantly using about 27% of one cpu core when idle (more when not,
obviously).
This is a fresh install of Windows 7 Professional with SP1
On Wednesday 08 January 2014 19:40:10 Marcelo Tosatti wrote:
On Tue, Jan 07, 2014 at 07:48:41PM +0100, Guido Winkelmann wrote:
Hi,
When trying to boot a Windows 7 install from a local virtual disks, qemu
stops with the messages:
KVM internal error. Suberror: 1
emulation failure
Can you
Hi,
When trying to boot a Windows 7 install from a local virtual disks, qemu stops
with the messages:
KVM internal error. Suberror: 1
emulation failure
I've started qemu with libvirt. This is the output from libvirt's logfile:
2014-01-07 18:22:10.988+: starting up
LC_ALL=C
... It didn't show an error message that would
tell me what is actually wrong, though.
Guido
On Tuesday 07 January 2014 19:48:41 Guido Winkelmann wrote:
Hi,
When trying to boot a Windows 7 install from a local virtual disks, qemu
stops with the messages:
KVM internal error. Suberror: 1
Am Montag, 29. Oktober 2012, 12:29:01 schrieb Stefan Hajnoczi:
On Fri, Oct 19, 2012 at 2:55 PM, Guido Winkelmann
guido-k...@thisisnotatest.de wrote:
Am Donnerstag, 18. Oktober 2012, 18:05:39 schrieb Avi Kivity:
On 10/18/2012 05:50 PM, Guido Winkelmann wrote:
Am Mittwoch, 17. Oktober 2012
Am Donnerstag, 18. Oktober 2012, 18:05:39 schrieb Avi Kivity:
On 10/18/2012 05:50 PM, Guido Winkelmann wrote:
Am Mittwoch, 17. Oktober 2012, 13:25:45 schrieb Brian Jackson:
On Wednesday, October 17, 2012 10:45:14 AM Guido Winkelmann wrote:
vda1, logical block 1858771
Oct 17 17:12:04
Am Mittwoch, 17. Oktober 2012, 13:25:45 schrieb Brian Jackson:
On Wednesday, October 17, 2012 10:45:14 AM Guido Winkelmann wrote:
vda1, logical block 1858771
Oct 17 17:12:04 localhost kernel: [ 212.070600] Buffer I/O error on
device
vda1, logical block 1858772
Oct 17 17:12:04 localhost
Am Dienstag, 16. Oktober 2012, 12:44:27 schrieb Brian Jackson:
On Tuesday, October 16, 2012 11:33:44 AM Guido Winkelmann wrote:
[...]
The commandline, as generated by libvirtd, looks like this:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=none /usr/bin
Am Dienstag, 16. Oktober 2012, 12:44:27 schrieb Brian Jackson:
On Tuesday, October 16, 2012 11:33:44 AM Guido Winkelmann wrote:
The commandline, as generated by libvirtd, looks like this:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=none /usr/bin/qemu
Hi,
I'm experiencing I/O errors in a guest machine after migrating it from one
host to another, and then back to the original host. After doing this, I find
the following in the dmesg output of the guest machine:
[ 345.390543] end_request: I/O error, dev vda, sector 273871
[ 345.391125]
Am Mittwoch, 11. April 2012, 20:37:56 schrieb Guido Winkelmann:
Am Mittwoch, 11. April 2012, 17:25:12 schrieb Orit Wasserman:
On 04/11/2012 04:43 PM, Guido Winkelmann wrote:
Am Mittwoch, 11. April 2012, 16:29:55 schrieben Sie:
I'm not sure if this is the problem but I noticed
Hi,
Nested virtualization on Intel does not work for me with qemu-kvm. As soon as
the third layer OS (second virtualised) is starting the Linux kernel, the
entire second layer freezes up. The last thing I can see console of the third
layer system before it freezes is Decompressing Linux... .
Am Mittwoch, 11. April 2012, 16:29:55 schrieben Sie:
I'm not sure if this is the problem but I noticed that the second layer and
the third layer have the same memory size (8G), how about trying to reduce
the memory for the third layer ?
I tried reducing the third layer to 1G. That didn't
Am Mittwoch, 11. April 2012, 17:38:14 schrieb Nadav Har'El:
On Wed, Apr 11, 2012, Guido Winkelmann wrote about Nested virtualization on
Intel does not work - second level freezes when third level is starting:
Nested virtualization on Intel does not work for me with qemu-kvm. As soon
Am Mittwoch, 11. April 2012, 17:25:12 schrieben Sie:
On 04/11/2012 04:43 PM, Guido Winkelmann wrote:
Am Mittwoch, 11. April 2012, 16:29:55 schrieben Sie:
I'm not sure if this is the problem but I noticed that the second layer
and
the third layer have the same memory size (8G), how about
Am Mittwoch, 11. April 2012, 23:14:07 schrieb Kashyap Chamarthy:
On Wed, Apr 11, 2012 at 6:14 PM, Guido Winkelmann
guido-k...@thisisnotatest.de wrote:
[...]
Here is my complete notes on nested virtualization w/ Intel --
http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm
Am Mittwoch, 11. April 2012, 17:25:12 schrieb Orit Wasserman:
On 04/11/2012 04:43 PM, Guido Winkelmann wrote:
Am Mittwoch, 11. April 2012, 16:29:55 schrieben Sie:
I'm not sure if this is the problem but I noticed that the second layer
and
the third layer have the same memory size (8G
Hi,
Is there a spec-file somewhere for creating RPMs from the newest qemu-kvm
release?
Regards,
Guido
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Am Monday 28 March 2011 schrieb David Martin:
- Original Message -
On 3/28/11 2:46 PM, Avi Kivity wrote:
On 03/25/2011 10:26 PM, Marcin M. Jessa wrote:
[...]
One LUN per image allows you to implement failover, LVM doesn't (but
cluster-LVM does). I recommend using one LUN
Am Thursday 31 March 2011 schrieben Sie:
That's what CLVM is for, it propagates the volume changes to every member
of the 'cluster'.
Oh, right. I didn't know about clvm until now.
It sounds very promising though, certainly better than working with the
proprietary API of whoever your
Am Wednesday 16 March 2011 schrieb Stefan Hajnoczi:
On Tue, Mar 15, 2011 at 1:20 PM, Guido Winkelmann
guido-k...@thisisnotatest.de wrote:
Am Tuesday 15 March 2011 schrieben Sie:
On Mon, Mar 14, 2011 at 10:57 PM, Guido Winkelmann
guido-k...@thisisnotatest.de wrote:
On Monday 14
Am Tuesday 15 March 2011 schrieben Sie:
On Mon, Mar 14, 2011 at 10:57 PM, Guido Winkelmann
guido-k...@thisisnotatest.de wrote:
On Monday 14 March 2011 20:32:23 Stefan Hajnoczi wrote:
On Mon, Mar 14, 2011 at 6:05 PM, Guido Winkelmann
guido-k...@thisisnotatest.de wrote:
Does anybody
Hi,
I am experiencing hangs in disk IO in systems hosted inside a virtual KVM
machine. When the virtual system disk is SCSI and when I am doing a lot of I/O
on it, I will eventually get error messages on the console and in dmesg like
these:
sd 0:0:0:0: [sda] ABORT operation started
sd
On Monday 14 March 2011 20:32:23 Stefan Hajnoczi wrote:
On Mon, Mar 14, 2011 at 6:05 PM, Guido Winkelmann
guido-k...@thisisnotatest.de wrote:
Does anybody have an idea what might cause this or what might be done
about it?
The lsi_scsi emulation code is incomplete. It does not handle
Hi,
I've got a problem where I cannot start any new VMs with KVM if the host
machine is under high CPU load. The problem is not 100% reproducible (it works
sometimes), but under load conditions, it happens most of the time - roughly
95%.
I'm usually using libvirt to start and stop KVM VMs.
I just noticed that if I leave off the -nodefaults from the qemu command line,
the guest will reliably start up again.
I don't know what reasons the libvirt developers had for putting it there,
though...
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
Am Dienstag, 1. Juni 2010 schrieben Sie:
On 06/01/2010 06:59 PM, Guido Winkelmann wrote:
The host OS is Fedora Core 12, with qemu-kvm 0.11.0
Please try with at least qemu-kvm-0.11.1, preferably qemu-kvm-0.12.4.
Also use Linux 2.6.32.latest in the guest.
Okay, I've upgraded the userspace
Hi,
When using KVM machines with virtual disks that are hooked up to the guest via
either virtio or SCSI, the virtual disk will often hang completely after a
short time of operation. When this happens, the network connectivity of the
machine will usually go down, too. (I.e. it stops responding
28 matches
Mail list logo
