Best way to exchange data between host and guest?
Hi, What is the fastest way to exchange data between host and guest? Thanks Anjali -- 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
SMBIOS support in Qemu?
Hi, Which version of Qemu contains the Smbios code? If I have to get the code in my repo, is there any place I can get the complete set of patches? Thanks Anjali -- 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
Passing in additional info to guest OS and e1000 test suite?
Hi, - If I want to pass in additional arguments to the guest OS while booting(in particular which slot I want to map a nic to) - is there any way to do it? Some kind of configuration file that I can pass in would also be ok for me. - Is there a KVM/Qemu/e1000 test suite that is already available and I can us? Thanks Anjali -- 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
Re: [Qemu-devel] Hitting 29 NIC limit
Can you send me pointers to the qdev documentation? How can I use it? Will
it allow us to scale above the 32 PCI limit?
Anjali
On 10/14/10 2:57 PM, Anthony Liguori anth...@codemonkey.ws wrote:
On 10/14/2010 04:42 PM, Richard W.M. Jones wrote:
On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel P. Berrange wrote:
Or a PCI bridge to wire up more PCI buses, so we raise the max limit for
any type of device we emulate.
Break the 29/30/31 virtio-blk limit ... please!
It was broken ages ago:
anth...@howler:~$ wc -l /proc/partitions; tail /proc/partitions
422 /proc/partitions
251 1618 1 vdcx2
251 1621 489951 vdcx5
251 1632 10485760 vdcy
251 16339992398 vdcy1
251 1634 1 vdcy2
251 1637 489951 vdcy5
251 1648 10485760 vdcz
251 16499992398 vdcz1
251 1650 1 vdcz2
251 1653 489951 vdcz5
This is what makes qdev so useful.
args=
for slot in 5 6 7 8 9 10 11 12 13 14 15 16 17; do
for fn in 0 1 2 3 4 5 6 7; do
args=$args -drive
file=/home/anthony/images/linux.img,if=none,snapshot=on,id=disk${slot}_${fn}
args=$args -device
virtio-blk-pci,addr=${slot}.${fn},drive=disk${slot}_${fn},multifunction=on
done
done
x86_64-softmmu/qemu-system-x86_64 -hda ~/images/linux.img ${args}
-enable-kvm -serial stdio
Regards,
Anthony Liguori
Rich.
--
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
--
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
Re: [Qemu-devel] Hitting 29 NIC limit
Thanks. Does this work for e1000 as well?
Also, does it support pci hotplug?
Anjali
On 10/14/10 3:09 PM, Anthony Liguori anth...@codemonkey.ws wrote:
On 10/14/2010 05:00 PM, Anjali Kulkarni wrote:
Can you send me pointers to the qdev documentation? How can I use it? Will
it allow us to scale above the 32 PCI limit?
It's all below. You just have to create a PCI device and mark the
multifunction flag to on and then assign it a PCI address that includes
a function number. Then you can pack 8 virtio PCI devices into a single
slot.
Regards,
Anthony Liguori
Anjali
On 10/14/10 2:57 PM, Anthony Liguorianth...@codemonkey.ws wrote:
On 10/14/2010 04:42 PM, Richard W.M. Jones wrote:
On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel P. Berrange wrote:
Or a PCI bridge to wire up more PCI buses, so we raise the max limit for
any type of device we emulate.
Break the 29/30/31 virtio-blk limit ... please!
It was broken ages ago:
anth...@howler:~$ wc -l /proc/partitions; tail /proc/partitions
422 /proc/partitions
251 1618 1 vdcx2
251 1621 489951 vdcx5
251 1632 10485760 vdcy
251 16339992398 vdcy1
251 1634 1 vdcy2
251 1637 489951 vdcy5
251 1648 10485760 vdcz
251 16499992398 vdcz1
251 1650 1 vdcz2
251 1653 489951 vdcz5
This is what makes qdev so useful.
args=
for slot in 5 6 7 8 9 10 11 12 13 14 15 16 17; do
for fn in 0 1 2 3 4 5 6 7; do
args=$args -drive
file=/home/anthony/images/linux.img,if=none,snapshot=on,id=disk${slot}_${fn}
args=$args -device
virtio-blk-pci,addr=${slot}.${fn},drive=disk${slot}_${fn},multifunction=on
done
done
x86_64-softmmu/qemu-system-x86_64 -hda ~/images/linux.img ${args}
-enable-kvm -serial stdio
Regards,
Anthony Liguori
Rich.
--
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
--
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
Hitting 29 NIC limit
Hi, Using the legacy way of starting up NICs, I am hitting a limitation after 29 NICs ie no more than 29 are detected (that's because of the 32 PCI slot limit on a single bus- 3 are already taken up) I had initially increased the MAX_NICS to 48, just on my tree, to get to more, but ofcource that wont work. Is there any way to go beyond 29 NICs the legacy way? What is the maximum that can be supported by the qdev mothod? Thanks Anjali -- 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
Question about using multiple Qemu emulation devices/NICs at one time
Hi, Has anyone tried to use many Qemu devices/NICs at one time with the same guest? Ie let the guest think it has say 3 or 4 virtual NICs? I see that after about 2, it seems to be a little unstable - I got a em0 watchdog timeout once. So, I wanted to know is there any known issue with having more than 2 emulated devices at one time? Has anyone used many, and what's the max that anyone has used with stability? Anjali -- 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
Question about e1000 NIC emulation in Qemu - chipset used
Hi, I am using Qemu for emulation of my virtual e1000 NIC, and my driver for the e1000 is a modified version of 82547EI. (Modified because it is userspace and plugs into other modules - but the device access specific parts are not modified). I wanted to know which chipset exactly does Qemu emulate? Does it make a difference if it is different from the 82547? I see that 82547 is in the e1000 family, so should my driver work for a variant of the e1000 family which Qemu or vmware supports, for eg, vmware supports 82545EM, so can I use my driver for 82547(maybe I will need some modifications) and will it work with the emulated e1000 nic in vmware? Which chipset does Qemu's e1000 emulate? Thanks! Anjali -- 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
Re: Freebsd image from Qemu hangs on booting in KVM
Thanks Avi, I am trying to reproduce this on another setup, and do not see the issue. My understanding is to run KVM + Qemu, I only need to install KVM modules, and Qemu does not need to be modified. Is that correct? I see [r...@ipg-virt01 anjali]# lsmod | grep kvm kvm_intel 87016 0 kvm 211496 1 kvm_intel [r...@ipg-virt01 anjali]# modprobe -l 'kvm*' /lib/modules/2.6.18-164.el5/kernel/extra/kvm.ko /lib/modules/2.6.18-164.el5/kernel/extra/kvm-amd.ko /lib/modules/2.6.18-164.el5/kernel/extra/kvm-intel.ko And then I run Qemu, as I did, before installing KVM. It should just use KVM? Is there any way I can check? Btw, when it hangs, I cannot even press any key, so not sure how I can get those commands you suggest below.. Anjali On 8/5/10 1:46 AM, Avi Kivity a...@redhat.com wrote: On 08/05/2010 05:20 AM, Anjali Kulkarni wrote: Hi, I have a problem similar to the one seen on this list before - when I boot my freebsd based(but modified) image in Qemu with KVM on CentOS, then after almost booting completely, the image hangs - just before the login prompt is seen. If I do not have KVM ie plain CenOS with Qemu, then this issue does not occur. Has anyone seen this before and any ideas how to debug this? First step is to issue 'info registers' and 'x/30i $eip-20' from the monitor when it hangs (qemu -monitor stdio makes cut'n'paste easier). -- 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
Re: Freebsd image from Qemu hangs on booting in KVM
Ok, I could reproduce the problem, and also get the info you asked for: (qemu) info registers EAX= EBX=c27166c0 ECX=0013 EDX=c0bf85e0 ESI=c057cea0 EDI= EBP=d35a5ce4 ESP=d35a5ce4 EIP=c09e48ba EFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0028 00c09300 CS =0020 00c09b00 SS =0028 00c09300 DS =0028 00c09300 FS =0008 c0c6c900 00c09300 GS =003b 00c0f300 LDT=0050 c0c6c720 0087 e200 TR =0048 c0c6c940 0067 8b00 GDT= c0c6c680 0097 IDT= c0c6db40 07ff CR0=e005003b CR2=4808e000 CR3=1f54e000 CR4=0090 DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 FCW=127f FSW= [ST=0] FTW=00 MXCSR= FPR0= FPR1= FPR2= FPR3= FPR4= FPR5= FPR6= FPR7= XMM00= XMM01= XMM02= XMM03= XMM04= XMM05= XMM06= XMM07= (qemu) x/30i $eip-20 0xc09e48a6: add%al,(%eax) 0xc09e48a8: leave 0xc09e48a9: ret 0xc09e48aa: push %ebp 0xc09e48ab: mov%esp,%ebp 0xc09e48ad: leave 0xc09e48ae: ret 0xc09e48af: push %ebp 0xc09e48b0: mov%esp,%ebp 0xc09e48b2: hlt 0xc09e48b3: jmp0xc09e48b2 0xc09e48b5: push %ebp 0xc09e48b6: mov%esp,%ebp 0xc09e48b8: sti 0xc09e48b9: hlt 0xc09e48ba: leave 0xc09e48bb: ret 0xc09e48bc: push %ebp 0xc09e48bd: mov%esp,%ebp 0xc09e48bf: mov%cr0,%eax 0xc09e48c2: or $0x5002a,%eax 0xc09e48c7: mov%eax,%cr0 0xc09e48ca: movl 0xc0c6c888,%gs 0xc09e48d0: leave 0xc09e48d1: ret 0xc09e48d2: push %ebp 0xc09e48d3: mov%esp,%ebp 0xc09e48d5: sub$0x8,%esp 0xc09e48d8: mov%ebx,(%esp,1) 0xc09e48db: mov%esi,0x4(%esp,1) (qemu) On 8/5/10 1:51 PM, Anjali Kulkarni anj...@juniper.net wrote: Thanks Avi, I am trying to reproduce this on another setup, and do not see the issue. My understanding is to run KVM + Qemu, I only need to install KVM modules, and Qemu does not need to be modified. Is that correct? I see [r...@ipg-virt01 anjali]# lsmod | grep kvm kvm_intel 87016 0 kvm 211496 1 kvm_intel [r...@ipg-virt01 anjali]# modprobe -l 'kvm*' /lib/modules/2.6.18-164.el5/kernel/extra/kvm.ko /lib/modules/2.6.18-164.el5/kernel/extra/kvm-amd.ko /lib/modules/2.6.18-164.el5/kernel/extra/kvm-intel.ko And then I run Qemu, as I did, before installing KVM. It should just use KVM? Is there any way I can check? Btw, when it hangs, I cannot even press any key, so not sure how I can get those commands you suggest below.. Anjali On 8/5/10 1:46 AM, Avi Kivity a...@redhat.com wrote: On 08/05/2010 05:20 AM, Anjali Kulkarni wrote: Hi, I have a problem similar to the one seen on this list before - when I boot my freebsd based(but modified) image in Qemu with KVM on CentOS, then after almost booting completely, the image hangs - just before the login prompt is seen. If I do not have KVM ie plain CenOS with Qemu, then this issue does not occur. Has anyone seen this before and any ideas how to debug this? First step is to issue 'info registers' and 'x/30i $eip-20' from the monitor when it hangs (qemu -monitor stdio makes cut'n'paste easier). -- 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
Virtualization technology conferences/tutorials/courses to attend?
Hi, I am new to Virtualization, so can someone point me to conferences/tutorials/courses that I can attend related to Linux KVM, para-virtualization, device driver virtualization, hardware assisted virtualization etc.? Even documents pointers will be much useful. Thanks! Anjali -- 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
Virtualization technology conferences/tutorials/courses to attend?Wednesday, August 4, 2010 6:59 PM
Hi, I am new to Virtualization, so can someone point me to conferences/tutorials/courses that I can attend related to Linux KVM, para-virtualization, device driver virtualization, hardware assisted virtualization etc.? Even documents pointers will be much useful. Thanks! Anjali -- 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
Freebsd image from Qemu hangs on booting in KVM
Hi, I have a problem similar to the one seen on this list before - when I boot my freebsd based(but modified) image in Qemu with KVM on CentOS, then after almost booting completely, the image hangs - just before the login prompt is seen. If I do not have KVM ie plain CenOS with Qemu, then this issue does not occur. Has anyone seen this before and any ideas how to debug this? Thanks Anjali-- 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
Re: Looking at using KVM for embedded product
Hi, I am not sure if this is the right forum for my questions - I am using Qemu+KVM on centOS to run my freebsd based virtual OS. The Qemu emulates one of my nics - yukon -II 88E8022 chip. Now, my yukon driver exists in kernel as well as user space(and I will use the one which I want based on some configs). The kernel driver is able to read the bar0 from PCI config and also read contents correctly. The user space driver gets the bar0 correctly, and mmaps it into it's process space, but when it reads contents of bar0, it gets all 0s. This same code when written on a real device works. Is it due to the fact Qemu is running my freebsd based OS in userland, so does mmap require some tweaks? Are there any documents which I could regarding how the Qemu/KVM traps the read write to bar0 so that it can emulate the device reads/writes? If this is not the right forum, can you point me to the right one? Thanks Anjali -- 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
Question about mmap from user space and accessing emulated device bar0 contents
Changing subject, Hi, I am not sure if this is the right forum for my questions - I am using Qemu+KVM on centOS to run my freebsd based virtual OS. The Qemu emulates one of my nics - yukon -II 88E8022 chip. Now, my yukon driver exists in kernel as well as user space(and I will use the one which I want based on some configs). The kernel driver is able to read the bar0 from PCI config and also read contents correctly. The user space driver gets the bar0 correctly, and mmaps it into it's process space, but when it reads contents of bar0, it gets all 0s. This same code when written on a real device works. Is it due to the fact Qemu is running my freebsd based OS in userland, so does mmap require some tweaks? Are there any documents which I could regarding how the Qemu/KVM traps the read write to bar0 so that it can emulate the device reads/writes? If this is not the right forum, can you point me to the right one? Thanks Anjali -- 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
