On Tue, 23 Dec 2014 15:40:22 +0100 Paolo Bonzini pbonz...@redhat.com wrote:
A commercial application running on Windows (kvm guest) detects CPU as:
CPU_0: CPU0, Intel64 Family 6 Model 42 Stepping 1, 64, 64, 2200,
078BFBFD000206A1, 10753, CPU 0
After some time, without reboot, it detects
On Tue, 3 Feb 2015 18:07:57 +0400 Andrey Korolyov and...@xdel.ru wrote:
Have you tried to disable turbo mode (assuming you have new enough CPU
model) and fix frequency via frequency governor` settings? If it
helps, it can be an ugly hack with pre-up/post-up libvirt actions,
though you`d
Nerijus Baliunas nerijus at users.sourceforge.net writes:
Paolo Bonzini pbonzini at redhat.com writes:
In the case of Windows it's probably some timing loop that is executed
at startup, and the result depends on frequency scaling in the host.
Try adding this to the XML in the meanwhile
Hello,
A commercial application running on Windows (kvm guest) detects CPU as:
CPU_0: CPU0, Intel64 Family 6 Model 42 Stepping 1, 64, 64, 2200,
078BFBFD000206A1, 10753, CPU 0
After some time, without reboot, it detects as:
CPU_0: CPU0, Intel64 Family 6 Model 42 Stepping 1, 64, 64, 2298,
Paolo Bonzini pbonzini at redhat.com writes:
How are you running qemu-kvm? (Command line, or XML if you're using
libvirt, or similar).
XML - http://paste.fedoraproject.org/162378/14193357
command line - http://paste.fedoraproject.org/162379/93358231
--
To unsubscribe from this list: send the
Paolo Bonzini pbonzini at redhat.com writes:
Do you know how the application computes the frequency?
No.
In the case of Windows it's probably some timing loop that is executed
at startup, and the result depends on frequency scaling in the host.
Try adding this to the XML in the meanwhile,
Paolo Bonzini pbonzini at redhat.com writes:
It should work with disk type='block' device='lun', but you also need
to use
source dev='/dev/sr0'/
(i.e. dev instead of file).
Thanks, it worked! VM now sees the lightscribe drive, Just for the
information, the following works:
disk
Oliver Rath rath at mglug.de writes:
Normally kvm emulates the cdrom drive. If you want to use the native
functionality, you have to passthrough the drive (depending on the your
device usb or pci sata-hardware). If your drive is attached via usb, you
can try passthrough the usb-device, if it
Nerijus Baliunas nerijus at users.sourceforge.net writes:
It is connected via PCI IDE controller (Silicon Image, Inc. PCI0680 Ultra
ATA-133 Host Controller). Is it possible to passthrough it?
Tried it, but unsuccessfully:
Error starting domain: internal error: early end of file from monitor
Nerijus Baliunas nerijus at users.sourceforge.net writes:
pci-assign,configfd=26,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x8: No IOMMU
found. Unable to assign device hostdev0
I added intel_iommu=on' to the kernel cmdline, # dmesg|grep -i iommu
[0.00] Command line: ro root=/dev/md0
Brian Jackson iggy at theiggy.com writes:
You could try to use virtio-scsi and scsi passthru. I believe there's
been a post on this in the past (more than likely on the qemu-devel
mailing list.
I see I can choose VirtIO SCSI bus type in virt-manager. I added as a raw
cdrom, then changed
Nerijus Baliunas nerijus at users.sourceforge.net writes:
I see I can choose VirtIO SCSI bus type in virt-manager. I added as a raw
cdrom, then changed VM.xml like this:
disk type='file' device='cdrom'
driver name='qemu' type='raw'/
source file='/dev/sr0'/
target dev
Hello,
is it possible to support lightscribe in KVM? Now Windows VM sees QEMU
DVD-ROM ATA Device and labeling software shows No LightScribe Drives Found.
Regards,
Nerijus
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More
13 matches
Mail list logo
