Re: kvm 76 - open /dev/kvm: No such device or address
It's unlikely that the CPU is broken, but intel has vmx turned off by default, though if that were off, then kvm-intel shouldn't have loaded. Check your (main hardware) bios settings and try again. Matias Aguirre wrote: $ groups audio floppy video cdrom plugdev web kvm The user have the kvm group. Can be the CPU broke? Michael Malone wrote: Also, you might want to make sure that the user you're using to run KVM has been added to the kvm group and make sure that your X-session has been restarted since this change, or it will not have taken effect. Matias Aguirre wrote: Hi all, Im using 2.6.26.5 kernel and slackware-current distribution. I was compiled the latest 76 version of kvm and when i run kvm i return this error: open /dev/kvm: No such device or address Could not initialize KVM, will disable KVM support The module is already loaded: # lsmod Module Size Used by kvm_intel 33984 0 kvm 116156 1 kvm_intel nvidia 6886800 26 And my CPU have VM support. # cat /proc/cpuinfo | grep vmx flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm And the file permission: # dir /dev/kvm crw-rwxr-- 1 root kvm 250, 0 2008-10-07 18:22 /dev/kvm Any help? Thanks -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: kvm 76 - open /dev/kvm: No such device or address
Also, you might want to make sure that the user you're using to run KVM has been added to the kvm group and make sure that your X-session has been restarted since this change, or it will not have taken effect. Matias Aguirre wrote: Hi all, Im using 2.6.26.5 kernel and slackware-current distribution. I was compiled the latest 76 version of kvm and when i run kvm i return this error: open /dev/kvm: No such device or address Could not initialize KVM, will disable KVM support The module is already loaded: # lsmod Module Size Used by kvm_intel 33984 0 kvm 116156 1 kvm_intel nvidia 6886800 26 And my CPU have VM support. # cat /proc/cpuinfo | grep vmx flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm And the file permission: # dir /dev/kvm crw-rwxr-- 1 root kvm 250, 0 2008-10-07 18:22 /dev/kvm Any help? Thanks -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: kvm-76 --std-vga problem
Avi Kivity wrote: Michael Malone wrote: 1) what is the difference between running qemu-system-x86_64 and kvm directly? Because, when I run kvm directly, I get this error: The kvm script was mostly a development tool. I don't actually use it anymore. The main drawback is that you have to teach it about all qemu options, and there are many; the only value it provides is reloading the module (useful when you make changes), and not requiring the bios to be installed. 2) (this has been around for quite some time, I just haven't done anything about it) Even though I start up with -smp 2, windows only reads 1 cpu What HAL does Windows use? (Device Manager, properties on the Computer object) Yes, Glauber Costa pointed that one out to me. It is using the Uniprocessor HAL and I am about to re-install Windows to get around that one. Thanks though! Michael === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
kvm-76 --std-vga problem
Hi Everyone,
I just downloaded and ran the new kvm-76 (upgrading from kvm-74) and I
have a few issues.
I am running Ubuntu 8.04 (Hardy) as my host and Windows XP as my guest.
I am using VT-d and the kernel modules loaded correctly.
Here is the command I use to start kvm:
kvm-bridge -hda windows2.img -boot c -m 1000 -serial /dev/ttyUSB0
-serial file:serial.out -smp 2 -usb -usbdevice tablet -full-screen
-cdrom /dev/cdrom
kvm-bridge is a script that configures my network and passes the other
options straight through to qemu-system-x86_64
1) what is the difference between running qemu-system-x86_64 and kvm
directly?
Because, when I run kvm directly, I get this error:
Traceback (most recent call last):
File /home/malonem/kvm-76/kvm, line 20, in module
external_module = config.get('shell', 'want_module')
File /usr/lib/python2.5/ConfigParser.py, line 511, in get
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'shell'
2) (this has been around for quite some time, I just haven't done
anything about it)
Even though I start up with -smp 2, windows only reads 1 cpu
3) When I run it using the --std-vga parameter, windows boots to just
before it gets to the welcome screen and hangs. The output shows a
multitude of kvm: get_dirty_pages returned -2 Is this something to do
with the kernel version I am using? I am using the standard Ubuntu
Hardy Kernel 2.6.24-19-generic. I read the release notes about the
kernel version with kvm-76 but didn't really understand them and
presumed that I am using the kernel modules supplied with kvm. (I
rmmod'd kvm-intel and kvm before I compiled and installed, then
modprobe'd the modules afterwards and everything seemed to go ok)
Any help or insight would be much appreciated,
Michael
===
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
===
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: serial problems cont..
Avi Kivity wrote: Michael Malone wrote: Hi everyone, I've written a couple of questions regarding the serial device in KVM. After slightly more investigation I think I have found what's going awry. Correct me if I'm wrong, but I believe that KVM generates an interrupt for every single character it sends through the serial port. This throws CPU usage through the roof and I suspect this means that the timers aren't being handled correctly and it failed on a string of 0's for me due to the timing slips. GNU/Linux and Windows don't have anywhere near the processor usage for their serial ports. Now, I know nothing of serial programming and don't have any time to investigate it too heavily just now, but I have pulled down the source and had a look through that, but it looks to be doing the right thing (I suppose?). I was mainly wondering how GNU/Linux and windows handle serial interrupts or if some of the serial character events could be buffered, rather than overload the processor? I guess this is a low priority for you, but any help would be greatly appreciated (And when I have some more time, I will spend some of it helping to develop KVM! Quid pro quo, Clarice...) What version of kvm are you testing? There were some changes to the serial emulation recently. See for example 02f0b4c0cc26f3a2578d515d96781f5a625d in kvm-73. I have tried with kvm 62, 69, 72 and 74. All of them gave the same result. What do you mean by See for example 02f0b4c0cc26f3a2578d515d96781f5a625d? - I am running Ubuntu 8.04 (Hardy) as host and Windows XP as guest on an Intel Core 2 duo processor. === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
serial problems cont..
Hi everyone, I've written a couple of questions regarding the serial device in KVM. After slightly more investigation I think I have found what's going awry. Correct me if I'm wrong, but I believe that KVM generates an interrupt for every single character it sends through the serial port. This throws CPU usage through the roof and I suspect this means that the timers aren't being handled correctly and it failed on a string of 0's for me due to the timing slips. GNU/Linux and Windows don't have anywhere near the processor usage for their serial ports. Now, I know nothing of serial programming and don't have any time to investigate it too heavily just now, but I have pulled down the source and had a look through that, but it looks to be doing the right thing (I suppose?). I was mainly wondering how GNU/Linux and windows handle serial interrupts or if some of the serial character events could be buffered, rather than overload the processor? I guess this is a low priority for you, but any help would be greatly appreciated (And when I have some more time, I will spend some of it helping to develop KVM! Quid pro quo, Clarice...) Thanks, Michael === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: serial/ rs232 and qemu /kvm?
I have been trying to use kvm to do some microcontroller programming, mostly with success - until I want to send an ascii NULL down the port. (I don't know what's going on there, but if you have any ideas, that would be fantastic)Our communication protocol is very touchy about speeds, so the baud rate was being passed on correctly when I used qemu/kvm like this: kvm irrelevant options -serial /dev/ttyUSB0 (I'm using a usb-serial converter). You can have up to 4 COM ports by repeating the -serial device option. See the qemu man page for more details (yes, it works just the same when you're invoking it with kvm). If you're trying to use virt-manager, then don't. Virt-manager stops you from having access to a bunch of the underlying features of kvm/qemu such as serial ports. I'm told they're working on it, but it's only useful for a basic setup at the moment. Michael Glauber Costa wrote: On Tue, Aug 19, 2008 at 11:24 AM, Marc Weber [EMAIL PROTECTED] wrote: First of all, is this the mailinglist to ask this question? Or should I ask it on the qemu lists? I'd like to run WinXP/ Vista within kvm and do microcontroller programming. My host is linux of course. I had some success using the qemu pre 0.8 way using slsnif. Setting baud rate to 115200 made some of the operations work, but most don't. So is there a way to connect COM1 within the guest to /dev/ttyS0 so that baud rate settings within the guest will be forwarded to /dev/ttyS0 on the host? check out for qemu's -serial option Marc Weber -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: serial/ rs232 and qemu /kvm?
Charles Duffy wrote: Michael Malone wrote: If you're trying to use virt-manager, then don't. Virt-manager stops you from having access to a bunch of the underlying features of kvm/qemu such as serial ports. I'm told they're working on it, but it's only useful for a basic setup at the moment. Serial ports *are* available through libvirt, and have been since late April. Using a recent git build of libvirt, I've yet to find anything I'm interested in but incapable of (except perhaps USB storage hot-unplug, but that's very much just a nice-to-have). My apologies. It's more than likely that I'm using Ubuntu and using their package (where feature updates are only included every 6months), rather than a recent download. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Serial problems
Hi all, Here at my work we develop our code for an embedded system in linux, but the application we use to put firmware onto the physical device runs only under windows. I am investigating the feasibility of running windows as a virtual machine, rather than our current situation where every developer has two boxes at their desk. The new boxes at work don't come with a serial port, so I am trying with a USB to serial converter and running kvm like: kvm -hda windows2.img -boot c -m 1000 -serial /dev/ttyUSB0 -smp 2 -usb -usbdevice tablet -full-screen -cdrom /dev/cdrom I can do low-cpu tasks with the embedded device like reading the current configuration, but I can't do cpu-intensive tasks like loading a new firmware onto the device. I have sniffed the line to see what is being sent down the physical wires and I have logged inside windows what the application was sending and the two are almost the same, until we meet an ascii null. We log an ascii null (0x00) as being sent, but on the other side of the virtual machine 0xFF is coming out. We can run the application with Wine and download firmware but can't read the current configuration, so it's not the linux usb to serial converter drivers. So my question is, do you have any idea what's going wrong? I have tried kvm72 and the 2008-08-12 nightly snapshot. I am running an Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz with 2048MB RAM on Ubuntu Linux 8.04 (Hardy Heron). if anyone can help, it would be greatly appreciated! Thanks in advance, Michael Malone === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. === -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
