search for: virtioserial

...ager plugin for QEMU driver qemu-kvm.x86_64 : Userspace component of KVM qemu-kvm-tools.x86_64 : KVM debugging and diagnostics tools sheepdog.x86_64 : The Sheepdog Distributed Storage System for KVM/QEMU vios-proxy.x86_64 : Network proxy between a QEMU host and QEMU guests using : virtioserial channels vios-proxy-guest.x86_64 : Network proxy using virtioserial for QEMU guest vios-proxy-host.x86_64 : Network proxy using virtioserial for QEMU host But i do not need KVM or anything. I just need a stand alone qemu. I then enabled optional repos like EPEL, RPMFUSION, RPMFORGE etc. Although...

Hello, This series fixes a few issues pointed out by Avi and Juan. Avi pointed out we should do full scatter/gather processing of guest data even if current (well-behaved) guests don't send multiple iovs per element. Juan pointed out a few migration-related bugs. In handling the migration fixes, I noticed hot-plug/unplug isn't handled perfectly for the migration case: ports are

Hello, This series fixes a few issues pointed out by Avi and Juan. Avi pointed out we should do full scatter/gather processing of guest data even if current (well-behaved) guests don't send multiple iovs per element. Juan pointed out a few migration-related bugs. In handling the migration fixes, I noticed hot-plug/unplug isn't handled perfectly for the migration case: ports are

> > This patch set is the QEMU side implementation. > > > > The virtio-balloon is extended so that QEMU can get the free pages > > information from the guest through virtio. > > > > After getting the free pages information (a bitmap), QEMU can use it > > to filter out the guest's free pages in the ram bulk stage. This make > > the live migration

> > This patch set is the QEMU side implementation. > > > > The virtio-balloon is extended so that QEMU can get the free pages > > information from the guest through virtio. > > > > After getting the free pages information (a bitmap), QEMU can use it > > to filter out the guest's free pages in the ram bulk stage. This make > > the live migration

...case to add one for! For many other (userspace) use-cases, see the qemu-guest-agent in the qemu sources. The API is documented in the wiki: http://www.linux-kvm.org/page/Virtio-serial_API and the feature pages have some information that may help as well: https://fedoraproject.org/wiki/Features/VirtioSerial There are some links in here too: http://log.amitshah.net/2010/09/communication-between-guests-and-hosts/ Hope this helps. Amit

...return features; } diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c index 0d843fe..07a7a6f 100644 --- a/hw/char/virtio-serial-bus.c +++ b/hw/char/virtio-serial-bus.c @@ -472,6 +472,9 @@ static uint32_t get_features(VirtIODevice *vdev, unsigned int index, { VirtIOSerial *vser; + if (index == 1) { + features &= ~(1 << (VIRTIO_F_VERSION_1 - 32)); + } if (index > 0) { return features; } diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c index 67f91c0..4b75105 100644 --- a/hw/net/virtio-net.c +++ b/hw/net/virtio-net.c...

...return features; } diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c index 0d843fe..07a7a6f 100644 --- a/hw/char/virtio-serial-bus.c +++ b/hw/char/virtio-serial-bus.c @@ -472,6 +472,9 @@ static uint32_t get_features(VirtIODevice *vdev, unsigned int index, { VirtIOSerial *vser; + if (index == 1) { + features &= ~(1 << (VIRTIO_F_VERSION_1 - 32)); + } if (index > 0) { return features; } diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c index 67f91c0..4b75105 100644 --- a/hw/net/virtio-net.c +++ b/hw/net/virtio-net.c...

...gt; diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c > index 0d843fe..07a7a6f 100644 > --- a/hw/char/virtio-serial-bus.c > +++ b/hw/char/virtio-serial-bus.c > @@ -472,6 +472,9 @@ static uint32_t get_features(VirtIODevice *vdev, unsigned int index, > { > VirtIOSerial *vser; > > + if (index == 1) { > + features &= ~(1 << (VIRTIO_F_VERSION_1 - 32)); > + } > if (index > 0) { > return features; > } > diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c > index 67f91c0..4b75105 100644 > -...

...CE must be able to send * cache flushes. Thus, the "auto writethrough" behavior is never diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c index 3931085..0d843fe 100644 --- a/hw/char/virtio-serial-bus.c +++ b/hw/char/virtio-serial-bus.c @@ -75,7 +75,7 @@ static VirtIOSerialPort *find_port_by_name(char *name) static bool use_multiport(VirtIOSerial *vser) { VirtIODevice *vdev = VIRTIO_DEVICE(vser); - return vdev->guest_features & (1 << VIRTIO_CONSOLE_F_MULTIPORT); + return vdev->guest_features[0] & (1 << VIRTIO_CONSOLE_F_MULTIPORT)...

...CE must be able to send * cache flushes. Thus, the "auto writethrough" behavior is never diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c index 3931085..0d843fe 100644 --- a/hw/char/virtio-serial-bus.c +++ b/hw/char/virtio-serial-bus.c @@ -75,7 +75,7 @@ static VirtIOSerialPort *find_port_by_name(char *name) static bool use_multiport(VirtIOSerial *vser) { VirtIODevice *vdev = VIRTIO_DEVICE(vser); - return vdev->guest_features & (1 << VIRTIO_CONSOLE_F_MULTIPORT); + return vdev->guest_features[0] & (1 << VIRTIO_CONSOLE_F_MULTIPORT)...

...CE must be able to send * cache flushes. Thus, the "auto writethrough" behavior is never diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c index a7b1b68..55de504 100644 --- a/hw/char/virtio-serial-bus.c +++ b/hw/char/virtio-serial-bus.c @@ -75,7 +75,7 @@ static VirtIOSerialPort *find_port_by_name(char *name) static bool use_multiport(VirtIOSerial *vser) { VirtIODevice *vdev = VIRTIO_DEVICE(vser); - return vdev->guest_features & (1 << VIRTIO_CONSOLE_F_MULTIPORT); + return vdev->guest_features[0] & (1 << VIRTIO_CONSOLE_F_MULTIPORT)...

...CE must be able to send * cache flushes. Thus, the "auto writethrough" behavior is never diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c index a7b1b68..55de504 100644 --- a/hw/char/virtio-serial-bus.c +++ b/hw/char/virtio-serial-bus.c @@ -75,7 +75,7 @@ static VirtIOSerialPort *find_port_by_name(char *name) static bool use_multiport(VirtIOSerial *vser) { VirtIODevice *vdev = VIRTIO_DEVICE(vser); - return vdev->guest_features & (1 << VIRTIO_CONSOLE_F_MULTIPORT); + return vdev->guest_features[0] & (1 << VIRTIO_CONSOLE_F_MULTIPORT)...

...ce) use-cases, see the qemu-guest-agent in the > qemu sources. > > The API is documented in the wiki: > > http://www.linux-kvm.org/page/Virtio-serial_API > > and the feature pages have some information that may help as well: > > https://fedoraproject.org/wiki/Features/VirtioSerial > > There are some links in here too: > > http://log.amitshah.net/2010/09/communication-between-guests-and- > hosts/ > > Hope this helps. > > > Amit Thanks a lot !! Liang

...ce) use-cases, see the qemu-guest-agent in the > qemu sources. > > The API is documented in the wiki: > > http://www.linux-kvm.org/page/Virtio-serial_API > > and the feature pages have some information that may help as well: > > https://fedoraproject.org/wiki/Features/VirtioSerial > > There are some links in here too: > > http://log.amitshah.net/2010/09/communication-between-guests-and- > hosts/ > > Hope this helps. > > > Amit Thanks a lot !! Liang

...feature(vdev, VIRTIO_BLK_F_WCE)); aio_context_release(blk_get_aio_context(s->blk)); } } diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c index 0f637db..d49883f 100644 --- a/hw/char/virtio-serial-bus.c +++ b/hw/char/virtio-serial-bus.c @@ -75,7 +75,7 @@ static VirtIOSerialPort *find_port_by_name(char *name) static bool use_multiport(VirtIOSerial *vser) { VirtIODevice *vdev = VIRTIO_DEVICE(vser); - return vdev->guest_features & (1 << VIRTIO_CONSOLE_F_MULTIPORT); + return virtio_has_feature(vdev, VIRTIO_CONSOLE_F_MULTIPORT); } static size_...

...feature(vdev, VIRTIO_BLK_F_WCE)); aio_context_release(blk_get_aio_context(s->blk)); } } diff --git a/hw/char/virtio-serial-bus.c b/hw/char/virtio-serial-bus.c index 0f637db..d49883f 100644 --- a/hw/char/virtio-serial-bus.c +++ b/hw/char/virtio-serial-bus.c @@ -75,7 +75,7 @@ static VirtIOSerialPort *find_port_by_name(char *name) static bool use_multiport(VirtIOSerial *vser) { VirtIODevice *vdev = VIRTIO_DEVICE(vser); - return vdev->guest_features & (1 << VIRTIO_CONSOLE_F_MULTIPORT); + return virtio_has_feature(vdev, VIRTIO_CONSOLE_F_MULTIPORT); } static size_...

Some dropped quoted text restored. Vincent JARDIN <vincent.jardin at 6wind.com> writes: > Markus, > > see inline (I am not on all mailing list, please, keep the cc list). > >> Sure! The reasons for my dislike range from practical to >> philosophical. >> >> My practical concerns include: >> >> 1. ivshmem code needs work, but has no maintainer

Some dropped quoted text restored. Vincent JARDIN <vincent.jardin at 6wind.com> writes: > Markus, > > see inline (I am not on all mailing list, please, keep the cc list). > >> Sure! The reasons for my dislike range from practical to >> philosophical. >> >> My practical concerns include: >> >> 1. ivshmem code needs work, but has no maintainer

...evice virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,\ id=channel1,name=trace-path-cpu0\ ##9pfs path## -device virtio-serial \ -chardev socket,path=/tmp/virtio-trace/trace-9pfs,server,nowait, \ id=trace-9pfs \ -device virtserialport,chardev=trace-9pfs,name=virtioserial If you manage guests with libvirt, add the following tags to domain XML files. Then, libvirt passes the same command option to qemu. <channel type='pipe'> <source path='/tmp/virtio-trace/agent-ctl-path'/> <target type='virtio' n...