similar to: debian binaries using qemu

Hello, I have installed libguestfs on RHEL 5.5 64 bit. 3 packages i have installed. libguestfs-tools-c-1.9.10-1.1 libguestfs-tools-1.9.10-1.1 libguestfs-1.9.10-1.1 When i am trying to run virt-resize it gives me error: virt-resize -expand /dev/sda1 vm01.scilab vm01.scilab-15GB -d libguestfs: trace: add_drive_opts "vm01.scilab" "readonly:true" libguestfs: trace:

Hi, whenever I perform 'launch' operation to launch a disk, guestfs looks for KVM support and prints this message "Could not initialize KVM, will disable KVM support" . Is there a way to turn it off.. I dont want guestfs to look for KVM . Thanks in advance -- Cheers, Yeswanth -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Sun, Aug 08, 2010 at 12:05:58PM +0800, Kirby Zhou wrote: > guestfish takes legacy qemu instead of kvm? > ]# rpm -q libguestfs --requires | fgrep qemu > qemu-system-x86 >= 0.10.5 To make it clear, this is EPEL-5. There was some still unresolved problem with adding a dependency on KVM: https://fedorahosted.org/rel-eng/ticket/2982 As a result, we have to depend on qemu (software

When we hot unplug a virtserialport and then try to hot plug again, it fails: (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\

When we hot unplug a virtserialport and then try to hot plug again, it fails: (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\

On 06/11/2019 14:56, Michael S. Tsirkin wrote: > On Fri, Oct 18, 2019 at 06:47:18PM +0200, Laurent Vivier wrote: >> When we hot unplug a virtserialport and then try to hot plug again, >> it fails: >> >> (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait >> (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >>

On 06/11/2019 14:56, Michael S. Tsirkin wrote: > On Fri, Oct 18, 2019 at 06:47:18PM +0200, Laurent Vivier wrote: >> When we hot unplug a virtserialport and then try to hot plug again, >> it fails: >> >> (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait >> (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >>

On Wed, Nov 13, 2019 at 10:21:11AM -0500, Michael S. Tsirkin wrote: > On Wed, Nov 13, 2019 at 04:00:56PM +0100, Laurent Vivier wrote: > > When we hot unplug a virtserialport and then try to hot plug again, > > it fails: > > > > (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait > > (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >

On Wed, Nov 13, 2019 at 10:21:11AM -0500, Michael S. Tsirkin wrote: > On Wed, Nov 13, 2019 at 04:00:56PM +0100, Laurent Vivier wrote: > > When we hot unplug a virtserialport and then try to hot plug again, > > it fails: > > > > (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait > > (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >

When we hot unplug a virtserialport and then try to hot plug again, it fails: (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\

When we hot unplug a virtserialport and then try to hot plug again, it fails: (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\

On Wed, Mar 31, 2010 at 09:26:24PM +0300, Active Systems O? wrote: > Hi, > > As I couldnt find any appropriate bugzilla - so I'll post directly to you. There seems to be a problem with EPEL repo libguestfs-1.0.85-1.el5.5 rpm (x86_64) - for example it is very slow with VM filesystem copy as it does not make use of KVM acceleration (running plain qemu). > Running

When we hot unplug a virtserialport and then try to hot plug again, it fails: (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\

When we hot unplug a virtserialport and then try to hot plug again, it fails: (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\

XEN of RHEL5.x DOM0 provides a qemu-dm command at /usr/lib64/xen/bin/qemu-dm, Can I run libguestfs with it? I have tried run libguestfs with kqemu, but it always cause system hang. Regards Kirby Zhou -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libguestfs/attachments/20100518/50c18dd7/attachment.htm>

On Tue, Dec 03, 2019 at 03:46:50PM +0100, Amit Shah wrote: > On Thu, 2019-11-14 at 13:25 +0100, Laurent Vivier wrote: > > When we hot unplug a virtserialport and then try to hot plug again, > > it fails: > > > > (qemu) chardev-add socket,id=serial0,path=/tmp/serial0,server,nowait > > (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ > >

Ubuntu are now supplying a libguestfs package (or to be more accurate, they are just copying the Debian package) but it doesn't work out of the box. There is a bug in apt which we worked around in febootstrap 3.14, but the supplied version of febootstap is only 3.12. Hence you will get errors like this during installation: febootstrap: aptitude: error: no file was downloaded corresponding

Notes: (1) Tis doesn't completely remove legacy serial ports yet. I couldn't work out how to make the Linux kernel see the virtconsole, so that is still using a serial port. (2) The guest network is completely unavailable if you apply this patch. We will need to add this back, possibly as an optional feature. Rich. -- Richard Jones, Virtualization Group, Red Hat

Hello, This is the patch that I have for adding support for multiple ports to virtio_console. It's pretty stable in my testing so far and the memory corruption that I had earlier has been resolved in linux-next so I'm proposing this for inclusion. This currently uses device major number 60 from the experimental range; Alan could you please reserve a new major number for virtio_console?

Hello, This is the patch that I have for adding support for multiple ports to virtio_console. It's pretty stable in my testing so far and the memory corruption that I had earlier has been resolved in linux-next so I'm proposing this for inclusion. This currently uses device major number 60 from the experimental range; Alan could you please reserve a new major number for virtio_console?