[Fwd: Re: serial problems cont..]
Avi Kivity wrote: Michael Malone wrote: 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. I meant http://git.kernel.org/?p=linux/kernel/git/avi/kvm-userspace.git;a=commit;h=02f0b4c0cc26f3a2578d515d96781f5a625d . But since it doesn't seem to solve your problems (it is part of kvm-74), more work is needed. I did some more testing yesterday with kvm-74 and the NULL problem is fixed. I still have the same symptom, however, when the characters sent in one go hit ~512. Maybe a character gets dropped? My cpu is maxed at that point. I'm officially lost. Thanks for your help though! === 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..
Michael Malone wrote: 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. I meant http://git.kernel.org/?p=linux/kernel/git/avi/kvm-userspace.git;a=commit;h=02f0b4c0cc26f3a2578d515d96781f5a625d . But since it doesn't seem to solve your problems (it is part of kvm-74), more work is needed. -- error compiling committee.c: too many arguments to function -- 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
Re: serial problems cont..
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. -- error compiling committee.c: too many arguments to function -- 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
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
