Re: [Qemu-devel] Why I advise against using ivshmem
Nahanni's poor current development coupled with virtIO's promising expansion was what encouraged us to explore virtIO-serial [1] for inter-virtual machine communication. Though virtIO-serial as it is isn't helpful for inter-VM communication, some work is needed for this purpose and this is exactly what we (I and two of my fellow classmates) accomplished. We haven't published it yet since we do need to polish yet for upstreaming it and are planning do it in near future. [1]: http://fedoraproject.org/wiki/Features/VirtioSerial On Fri, Jun 13, 2014 at 2:56 PM, Vincent JARDIN wrote: > > (+merging with Paolo's email because of overlaps) > > >>> see inline (I am not on all mailing list, please, keep the cc list). >>> > 1. ivshmem code needs work, but has no maintainer >>> >>> See David's contributions: >>>http://patchwork.ozlabs.org/patch/358750/ >> >> >> We're grateful for David's patch for qemu-char.c, but this isn't ivshmem >> maintenance, yet. > > > others can come (doc), see below. > > 2. There is no libvirt support >>> >>> >>> One can use qemu without libvivrt. >> >> >> You asked me for my reasons for disliking ivshmem. This is one. >> >> Sure, I can drink my water through a straw while standing on one foot, >> but that doesn't mean I have to like it. And me not liking it doesn't >> mean the next guy shouldn't like it. To each their own. > > > I like using qemu without libvirt, libvirt is not part of qemu. > Let's avoid trolling about it ;) > > >> Back when we accepted ivshmem, the out-of-tree parts it needs were well >> below the "community & packaged" bar. But folks interested in it talked >> to us, and the fact that it's in shows that QEMU maintainers decided >> what they had then was enough. >> >> Unfortunately, we now have considerably less: Nahanni appears to be >> dead. > > > agree and to bad it is dead. We should let Nahanni dead since ivshmem is a > QEMU topic now, see below. Does it make sense? > > >> >> An apparently dead git repository you can study is not enough. The fact >> that you hold an improved reimplementation privately is immaterial. So >> is the (plausible) claim that others could also create a >> reimplementation. > > > Got the point. What's about a patch to docs/specs/ivshmem_device_spec.txt > that improves it? > > I can make qemu's ivshmem better: > - keep explaining memnic for instance, > - explain how to write other ivshmem. > > does it help? > > 4. Out-of-tree kernel uio driver required >>> >>> >>> No, it is optional. >> >> >> Good to know. Would you be willing to send a patch to >> ivshmem_device_spec.txt clarifying that? > > > got the point, yes, > > * Get all the required parts outside QEMU packaged in major distros, or absorbed into QEMU >>> >>> >>> Redhat did disable it. why? it is there in QEMU. >> >> >> Up to now, I've been wearing my QEMU hat. Let me exchange it for my Red >> one for a bit. >> >> We (Red Hat) don't just package & ship metric tons of random free >> software. We package & ship useful free software we can support for >> many, many years. >> >> Sometimes, we find that we have to focus serious development resources >> on making something useful supportable (Paolo mentioned qcow2). We >> obviously can't focus on everything, though. > > > Good open technology should rule. ivshmem has use cases. And I go agree with > you, it is like the phoenix, it has to be re-explained/documented to be back > to life. I was not aware that the QEMU community was missing ivshmem > contributors (my bad I did not check MAINTAINERS). > > >> Anyway, ivshmem didn't make the cut for RHEL-7.0. Sorry if that >> inconveniences you. To get it into RHEL, you need to show it's both >> useful and supportable. Building a community around it would go a long >> way towards that. > > > understood. > > >> If you want to discuss this in more detail with us, you may want to try >> communication channels provided by your RHEL subscription in addition to >> the QEMU development mailing list. Don't be shy, you're paying for it! > > > done. I was focusing on DPDK.org and ignorant of QEMU's status, thinking > Redhat was covering it. How to know which part of an opensource software are > and are not included into Redhat. Sales are ignorant about it ;). Redhat > randomly disables some files at compilation (for some good reasons I guess, > but not public rationals or I am missing something). > > Feel free to open this PR to anyone: > https://bugzilla.redhat.com/show_bug.cgi?id=1088332 > > In short, create a viable community around ivshmem, either within the QEMU community, or separately but cooperating. >>> >>> >>> At least, DPDK.org community is a community using it. >> >> >> Using something isn't the same as maintaining something. But it's a >> necessary first step. > > > understood, after David's patch, documentation will come. > > (now Paolo's email since there were some overlaps) > > > Markus especially referred to parts *ou
Add armhf support for qemu-kvm
Hey, all! I want to run a virtual machine on virt-manager using qemu as the emulator and armhf as the architecture. However, I see that virt-manager only lists x86_64 and i686 as the supported architectures. For this, I tried referring to https://wiki.debian.org/QemuUserEmulation which asked me to do the following: sudo dpkg --add-architecture armhf sudo apt-get update sudo apt-get install libc6:armhf However, since I am on dpkg version 1.16.1.2, I had to add a new architecture using the method given here: http://askubuntu.com/a/423089/72576 However, even after doing this, I get 404's for armhf packages on doing sudo apt-get update and sudo apt-get install libc6:armhf returns the following error: Package libc6:armhf is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: tzdata libc-bin initscripts libdb1-compat locales E: Package 'libc6:armhf' has no installation candidate So, how do I add armhs support for qemu? -- Thanks and regards, Jobin Raju George Final Year, Information Technology College of Engineering Pune Alternate e-mail: georgejr10...@coep.ac.in -- 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: ssh from host to guest using qemu to boot VM
Adding "-net nic" to the end of the booting command, I am able to connect to the internet now and have 10.0.2.15 as the IP address, but still ssh username@10.0.2.15 returns ssh: connect to host 10.0.2.15 port 22: Connection timed out On Tue, Apr 15, 2014 at 2:25 PM, Fam Zheng wrote: > On Tue, 04/15 14:03, Jobin Raju George wrote: >> Yes, you were right, the port was already being used when I was doing: >> >> >> -chardev socket,host=localhost,port=,server,nowait,id=port1-char \ >> >> However, even after using a unix socket for this socket as: >> >> -chardev socket,path=/tmp/g2g,server,nowait,id=port1-char >> >> the VM has booted giving a warning at the host console: Warning: vlan 0 >> with no nics but when I do ifconfig on the guest I see only lo and I still >> get ssh: connect to host 10.0.2.15 port 22: Connection timed out when I try >> to ssh; the IP I used to ssh is 10.0.2.15, which according to man >> qemu-system-x86_64 is the IP assigned to the first VM booted if static IP >> is not assigned. And now there is no internet connection on the guest. > > That means you have to create a device. Add an "-net nic". > > Fam > >> >> >> On Mon, Apr 14, 2014 at 6:15 PM, Fam Zheng wrote: >> >> > On Mon, 04/14 17:36, Jobin Raju George wrote: >> > > I retried using: >> > > >> > > /usr/bin/qemu-system-x86_64 \ >> > > -m 1024 \ >> > > -name vserialtest \ >> > > -cdrom ubuntu-12.04-desktop-amd64.iso -hda ubuntu1204-virtio-serial \ >> > > -chardev socket,host=localhost,port=,server,nowait,id=port1-char \ >> > > -device virtio-serial \ >> > > -device >> > virtserialport,id=port1,chardev=port1-char,name=org.fedoraproject.port.0 >> > > \ >> > > -net user,hostfwd=tcp:127.0.0.1:-:8001 >> > > >> > > but get the following: >> > > >> > > qemu-system-x86_64: -net user,hostfwd=tcp:127.0.0.1:-:8001: could >> > > not set up host forwarding rule 'tcp:127.0.0.1:-:8001' >> > > qemu-system-x86_64: -net user,hostfwd=tcp:127.0.0.1:-:8001: Device >> > > 'user' could not be initialized >> > > >> > > >> > > Also tried: >> > > >> > > -net user,hostfwd=tcp::-:8001 >> > > >> > > but get the following error: >> > > >> > > qemu-system-x86_64: -net user,hostfwd=tcp::-:8001: could not set >> > > up host forwarding rule 'tcp::-:8001' >> > > qemu-system-x86_64: -net user,hostfwd=tcp::-:8001: Device 'user' >> > > could not be initialized >> > >> > Is the port busy? What does "netstat -ltn" say? >> > >> > Fam >> > >> > > >> > > >> > > On Mon, Apr 14, 2014 at 5:31 PM, Fam Zheng wrote: >> > > > On Mon, 04/14 17:14, Jobin Raju George wrote: >> > > >> Hey! >> > > >> >> > > >> How do I setup ssh from the host to the guest using qemu? >> > > >> >> > > >> 1) I am able to use port redirection when I boot the VM without any >> > > >> special parameter(explained in point 2) as follows: >> > > >> >> > > >> /usr/bin/qemu-system-x86_64 -hda ubuntu1204 -m 512 -redir >> > tcp:::8001 >> > > >> >> > > >> 2) But when I try to boot using the following >> > > >> >> > > >> /usr/bin/qemu-system-x86_64 \ >> > > >> -m 1024 \ >> > > >> -name vserialtest \ >> > > >> -cdrom ubuntu-12.04-desktop-amd64.iso \ >> > > >> -hda ubuntu1204-virtio-serial \ >> > > >> -chardev socket,host=localhost,port=,server,nowait,id=port1-char \ >> > > >> -device virtio-serial \ >> > > >> -device >> > virtserialport,id=port1,chardev=port1-char,name=org.fedoraproject.port.0 >> > > >> \ >> > > >> -net user,hostfwd=tcp:::8001 >> > > >> >> > > >> I get the following error and the VM does not boot: >> > > >> >> > > >> qemu-system-x86_64: -net user,hostfwd=tcp:::8001: invalid host >> > > >> forwarding rule 'tcp:::8001' >> > > >> qemu-system-x86_64: -net user,hostfwd=tcp:::8001: Device 'user' >> > > >> could not be initialize
Re: ssh from host to guest using qemu to boot VM
Yes, you were right, the port was already being used when I was doing: -chardev socket,host=localhost,port=,server,nowait,id=port1-char \ However, even after using a unix socket for this socket as: -chardev socket,path=/tmp/g2g,server,nowait,id=port1-char the VM has booted giving a warning at the host console: Warning: vlan 0 with no nics but when I do ifconfig on the guest I see only lo and I still get ssh: connect to host 10.0.2.15 port 22: Connection timed out when I try to ssh; the IP I used to ssh is 10.0.2.15, which according to man qemu-system-x86_64 is the IP assigned to the first VM booted if static IP is not assigned. And now there is no internet connection on the guest. On Mon, Apr 14, 2014 at 6:15 PM, Fam Zheng wrote: > On Mon, 04/14 17:36, Jobin Raju George wrote: >> I retried using: >> >> /usr/bin/qemu-system-x86_64 \ >> -m 1024 \ >> -name vserialtest \ >> -cdrom ubuntu-12.04-desktop-amd64.iso -hda ubuntu1204-virtio-serial \ >> -chardev socket,host=localhost,port=,server,nowait,id=port1-char \ >> -device virtio-serial \ >> -device >> virtserialport,id=port1,chardev=port1-char,name=org.fedoraproject.port.0 >> \ >> -net user,hostfwd=tcp:127.0.0.1:-:8001 >> >> but get the following: >> >> qemu-system-x86_64: -net user,hostfwd=tcp:127.0.0.1:-:8001: could >> not set up host forwarding rule 'tcp:127.0.0.1:-:8001' >> qemu-system-x86_64: -net user,hostfwd=tcp:127.0.0.1:-:8001: Device >> 'user' could not be initialized >> >> >> Also tried: >> >> -net user,hostfwd=tcp::-:8001 >> >> but get the following error: >> >> qemu-system-x86_64: -net user,hostfwd=tcp::-:8001: could not set >> up host forwarding rule 'tcp::-:8001' >> qemu-system-x86_64: -net user,hostfwd=tcp::-:8001: Device 'user' >> could not be initialized > > Is the port busy? What does "netstat -ltn" say? > > Fam > >> >> >> On Mon, Apr 14, 2014 at 5:31 PM, Fam Zheng wrote: >> > On Mon, 04/14 17:14, Jobin Raju George wrote: >> >> Hey! >> >> >> >> How do I setup ssh from the host to the guest using qemu? >> >> >> >> 1) I am able to use port redirection when I boot the VM without any >> >> special parameter(explained in point 2) as follows: >> >> >> >> /usr/bin/qemu-system-x86_64 -hda ubuntu1204 -m 512 -redir tcp:::8001 >> >> >> >> 2) But when I try to boot using the following >> >> >> >> /usr/bin/qemu-system-x86_64 \ >> >> -m 1024 \ >> >> -name vserialtest \ >> >> -cdrom ubuntu-12.04-desktop-amd64.iso \ >> >> -hda ubuntu1204-virtio-serial \ >> >> -chardev socket,host=localhost,port=,server,nowait,id=port1-char \ >> >> -device virtio-serial \ >> >> -device >> >> virtserialport,id=port1,chardev=port1-char,name=org.fedoraproject.port.0 >> >> \ >> >> -net user,hostfwd=tcp:::8001 >> >> >> >> I get the following error and the VM does not boot: >> >> >> >> qemu-system-x86_64: -net user,hostfwd=tcp:::8001: invalid host >> >> forwarding rule 'tcp:::8001' >> >> qemu-system-x86_64: -net user,hostfwd=tcp:::8001: Device 'user' >> >> could not be initialized >> > >> > Format: >> > hostfwd=[tcp|udp]:[hostaddr]:hostport-[guestaddr]:guestport >> > >> > Try: >> > >> > -net user,hostfwd=tcp::7777-:8001 >> > >> > Fam >> > >> >> >> >> Please note that I am able to boot the VM without the -net parameter >> >> without any issues, however, I want to setup ssh from the host to the >> >> guest. ssh from guest to host works fine as expected. >> >> >> >> -- >> >> >> >> Thanks and regards, >> >> Jobin Raju George >> >> Final Year, Information Technology >> >> College of Engineering Pune >> >> Alternate e-mail: georgejr10...@coep.ac.in >> >> -- >> >> 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 >> >> >> >> -- >> Thanks and regards, >> >> Jobin Raju George >> >> Final Year, Information Technology >> >> College of Engineering Pune >> >> Alternate e-mail: georgejr10...@coep.ac.in >> -- >> 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 -- Thanks and regards, Jobin Raju George Final Year, Information Technology College of Engineering Pune Alternate e-mail: georgejr10...@coep.ac.in -- 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: ssh from host to guest using qemu to boot VM
I retried using: /usr/bin/qemu-system-x86_64 \ -m 1024 \ -name vserialtest \ -cdrom ubuntu-12.04-desktop-amd64.iso -hda ubuntu1204-virtio-serial \ -chardev socket,host=localhost,port=,server,nowait,id=port1-char \ -device virtio-serial \ -device virtserialport,id=port1,chardev=port1-char,name=org.fedoraproject.port.0 \ -net user,hostfwd=tcp:127.0.0.1:-:8001 but get the following: qemu-system-x86_64: -net user,hostfwd=tcp:127.0.0.1:-:8001: could not set up host forwarding rule 'tcp:127.0.0.1:-:8001' qemu-system-x86_64: -net user,hostfwd=tcp:127.0.0.1:-:8001: Device 'user' could not be initialized Also tried: -net user,hostfwd=tcp::-:8001 but get the following error: qemu-system-x86_64: -net user,hostfwd=tcp::-:8001: could not set up host forwarding rule 'tcp::-:8001' qemu-system-x86_64: -net user,hostfwd=tcp::-:8001: Device 'user' could not be initialized On Mon, Apr 14, 2014 at 5:31 PM, Fam Zheng wrote: > On Mon, 04/14 17:14, Jobin Raju George wrote: >> Hey! >> >> How do I setup ssh from the host to the guest using qemu? >> >> 1) I am able to use port redirection when I boot the VM without any >> special parameter(explained in point 2) as follows: >> >> /usr/bin/qemu-system-x86_64 -hda ubuntu1204 -m 512 -redir tcp:::8001 >> >> 2) But when I try to boot using the following >> >> /usr/bin/qemu-system-x86_64 \ >> -m 1024 \ >> -name vserialtest \ >> -cdrom ubuntu-12.04-desktop-amd64.iso \ >> -hda ubuntu1204-virtio-serial \ >> -chardev socket,host=localhost,port=,server,nowait,id=port1-char \ >> -device virtio-serial \ >> -device >> virtserialport,id=port1,chardev=port1-char,name=org.fedoraproject.port.0 >> \ >> -net user,hostfwd=tcp:::8001 >> >> I get the following error and the VM does not boot: >> >> qemu-system-x86_64: -net user,hostfwd=tcp:::8001: invalid host >> forwarding rule 'tcp:::8001' >> qemu-system-x86_64: -net user,hostfwd=tcp:::8001: Device 'user' >> could not be initialized > > Format: > hostfwd=[tcp|udp]:[hostaddr]:hostport-[guestaddr]:guestport > > Try: > > -net user,hostfwd=tcp::-:8001 > > Fam > >> >> Please note that I am able to boot the VM without the -net parameter >> without any issues, however, I want to setup ssh from the host to the >> guest. ssh from guest to host works fine as expected. >> >> -- >> >> Thanks and regards, >> Jobin Raju George >> Final Year, Information Technology >> College of Engineering Pune >> Alternate e-mail: georgejr10...@coep.ac.in >> -- >> 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 -- Thanks and regards, Jobin Raju George Final Year, Information Technology College of Engineering Pune Alternate e-mail: georgejr10...@coep.ac.in -- 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
ssh from host to guest using qemu to boot VM
Hey! How do I setup ssh from the host to the guest using qemu? 1) I am able to use port redirection when I boot the VM without any special parameter(explained in point 2) as follows: /usr/bin/qemu-system-x86_64 -hda ubuntu1204 -m 512 -redir tcp:::8001 2) But when I try to boot using the following /usr/bin/qemu-system-x86_64 \ -m 1024 \ -name vserialtest \ -cdrom ubuntu-12.04-desktop-amd64.iso \ -hda ubuntu1204-virtio-serial \ -chardev socket,host=localhost,port=,server,nowait,id=port1-char \ -device virtio-serial \ -device virtserialport,id=port1,chardev=port1-char,name=org.fedoraproject.port.0 \ -net user,hostfwd=tcp:::8001 I get the following error and the VM does not boot: qemu-system-x86_64: -net user,hostfwd=tcp:::8001: invalid host forwarding rule 'tcp:::8001' qemu-system-x86_64: -net user,hostfwd=tcp:::8001: Device 'user' could not be initialized Please note that I am able to boot the VM without the -net parameter without any issues, however, I want to setup ssh from the host to the guest. ssh from guest to host works fine as expected. -- Thanks and regards, Jobin Raju George Final Year, Information Technology College of Engineering Pune Alternate e-mail: georgejr10...@coep.ac.in -- 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: Using block device instead of character device for virtio-serial
On Fri, Feb 14, 2014 at 4:05 PM, Stefan Hajnoczi wrote: > > On Sun, Feb 09, 2014 at 11:39:19PM +0530, Jobin Raju George wrote: > > On Sun, Feb 9, 2014 at 2:42 PM, Stefan Hajnoczi wrote: > > > > > On Thu, Feb 06, 2014 at 12:22:36PM +0530, Jobin Raju George wrote: > > > > I am trying to establish a communication mechanism between the guest > > > > and its host using virtio-serial. For this I am using the following to > > > > boot the VM: > > > > > > > > qemu-system-x86_64 -m 1024 \ > > > > -name ubuntu_vm \ > > > > -hda ubuntu \ > > > > -device virtio-serial \ > > > > -chardev socket,path=/tmp/virt_socket,server,nowait,id=virt_socket \ > > > > -device virtconsole,name=v_soc,chardev=virt_socket,name=ubuntu_vm_soc > > > > > > > > This creates a character device on the guest machine and a UNIX socket > > > > on the host machine. > > > > > > > > 1) Is there a way I can create sockets on the host as well as the guest? > > > > > > The syntax is documented on the QEMU man page. Try: > > > > > > -chardev socket,port=1234,server,nowait,id=virt_socket > > > > > > > I did not try this out, but would this create a "socket" instead of a > > character device(/dev/hvc0) on the guest? > > Things should be unchanged inside the guest. This just creates a TCP > socket on the host. My main concern is creating a socket in the guest. > > > > > > > > 2) Is there a way I can create a block device for communication? > > > > > > > > I required a block device since the data that is to be transferred is > > > > huge and the frequency of the data transfer is quite high. > > > > > > Have you benchmarked virtio-serial or is this just a guess? > > > > > > > I have not benchmarked virtio-serial but it seems to be intuitive that a > > block device would perform data transfer at a faster rate than a character > > device. I may be wrong, would be happy to be corrected. And yes, I would > > like to know how can I benchmark virtio-serial using a character device vs > > a TCP/IP socket data transfer vs virtio-serial using a block device. > > Write a program that transfers data and measures the speed :-). It seems like netperf: www.netperf.org/netperf/training/Netperf.html is pretty useful for this purpose. -- Thanks and regards, Jobin Raju George Final Year, Information Technology College of Engineering Pune Alternate e-mail: georgejr10...@coep.ac.in -- 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
Fwd: Using block device instead of character device for virtio-serial
-- Forwarded message -- From: Jobin Raju George Date: Sun, Feb 9, 2014 at 11:39 PM Subject: Re: Using block device instead of character device for virtio-serial To: Stefan Hajnoczi Cc: kvm@vger.kernel.org On Sun, Feb 9, 2014 at 2:42 PM, Stefan Hajnoczi wrote: > > On Thu, Feb 06, 2014 at 12:22:36PM +0530, Jobin Raju George wrote: > > I am trying to establish a communication mechanism between the guest > > and its host using virtio-serial. For this I am using the following to > > boot the VM: > > > > qemu-system-x86_64 -m 1024 \ > > -name ubuntu_vm \ > > -hda ubuntu \ > > -device virtio-serial \ > > -chardev socket,path=/tmp/virt_socket,server,nowait,id=virt_socket \ > > -device virtconsole,name=v_soc,chardev=virt_socket,name=ubuntu_vm_soc > > > > This creates a character device on the guest machine and a UNIX socket > > on the host machine. > > > > 1) Is there a way I can create sockets on the host as well as the guest? > > The syntax is documented on the QEMU man page. Try: > > -chardev socket,port=1234,server,nowait,id=virt_socket I did not try this out, but would this create a "socket" instead of a character device(/dev/hvc0) on the guest? > > > > 2) Is there a way I can create a block device for communication? > > > > I required a block device since the data that is to be transferred is > > huge and the frequency of the data transfer is quite high. > > Have you benchmarked virtio-serial or is this just a guess? I have not benchmarked virtio-serial but it seems to be intuitive that a block device would perform data transfer at a faster rate than a character device. I may be wrong, would be happy to be corrected. And yes, I would like to know how can I benchmark virtio-serial using a character device vs a TCP/IP socket data transfer vs virtio-serial using a block device. > > > Stefan -- Thanks and regards, Jobin Raju George Final Year, Information Technology College of Engineering Pune Alternate e-mail: georgejr10...@coep.ac.in -- Thanks and regards, Jobin Raju George Final Year, Information Technology College of Engineering Pune Alternate e-mail: georgejr10...@coep.ac.in -- 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
Using block device instead of character device for virtio-serial
I am trying to establish a communication mechanism between the guest and its host using virtio-serial. For this I am using the following to boot the VM: qemu-system-x86_64 -m 1024 \ -name ubuntu_vm \ -hda ubuntu \ -device virtio-serial \ -chardev socket,path=/tmp/virt_socket,server,nowait,id=virt_socket \ -device virtconsole,name=v_soc,chardev=virt_socket,name=ubuntu_vm_soc This creates a character device on the guest machine and a UNIX socket on the host machine. 1) Is there a way I can create sockets on the host as well as the guest? 2) Is there a way I can create a block device for communication? I required a block device since the data that is to be transferred is huge and the frequency of the data transfer is quite high. Thanks in advance! -- Thanks and regards, Jobin Raju George Final Year, Information Technology College of Engineering Pune Alternate e-mail: georgejr10...@coep.ac.in -- 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
Fwd: Delete index created using kvm -boot
Hey, all! I am new to KVM and IVSHMEM. I am trying to create a virtual machine which would use IVSHMEM to communicate with other VM's when they are located on the same host machine. For this, I am trying the instructions given in this blog: http://www.abhijeet-dev.net/content/ivshmem-qemu-kvm-interrupts. However, when I try to create a VM using the following command: kvm -boot d -hda ~/Fedora-Live-Desktop-x86_64-19-1.iso -cpu core2duo -m 1G chardev socket,path=/tmp/nahanni,id=nahanni2 -device ivshmem,chardev=nahanni,size=512m,ioeventfd=on,vectors=8,index=2 I get the following error: kvm: -m 1G: drive with bus=0, unit=0 (index=0) exists I would like you to know that I had already created a VM using the same command, but a different image kvm -boot d -hda lupu-528.005.iso -cpu core2duo -m 1G chardev socket,path=/tmp/nahanni,id=nahanni2 -device ivshmem,chardev=nahanni,size=512m,ioeventfd=on,vectors=8,index=2 Please let me know how to resolve this error. Also, it would be nice if someone could give me some good tutorials on using IVSHMEM or other inter-VM communication mechanisms. -- Thanks and regards, Jobin Raju George Final Year, Information Technology College of Engineering Pune Alternate e-mail: georgejr10...@coep.ac.in -- 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
