On Mon, Jun 20, 2011 at 03:20:16PM +0200, Joel Uckelman wrote:
On Fri, Jun 10, 2011 at 2:16 PM, Joel Uckelman <joel@lightboxtechnologies.com> wrote:
Aha! I hadn't realized that udev depends on having /sys and /proc mounted first. Once I do that, I can start udev and my pipe is created as /dev/vport0p1.
Thanks for you help!
I've run into one further problem here: It seems that the socket attached to the pipe is already bound when the appliance comes up, because I get an "Address already in use error" when I call bind(2) on /dev/vport0p1 from the appliance side.
You're better off looking at the source and/or asking the qemu developers. As you can see, we just open the device file. Whether that is the correct thing to do is another matter: http://git.annexia.org/?p=libguestfs.git;a=blob;f=daemon/guestfsd.c;h=eb1e82...
I'd been planing to listen on the appiance end of the pipe, and have clients connect from the host end. Is that not possible?
virtio-serial is like a serial port, and AFAIK there is no connection control (or there didn't used to be). Anyway I strongly recommend you ask the qemu developers or experiment yourself. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v