Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Mon, Sep 29, 2014 at 04:00:38PM +0800, Zhi Yong Wu wrote: > On Mon, Sep 29, 2014 at 1:41 AM, Richard W.M. Jones wrote: > > On Mon, Sep 29, 2014 at 01:35:08AM +0800, Zhi Yong Wu wrote: > >> On Mon, Sep 29, 2014 at 1:27 AM, Richard W.M. Jones > >> wrote: > >> > User-Mode Linux is also a possibility. Slow but consistent > >> Slow is a big concern... > > > > There are some measurements here: > > > > http://rwmj.wordpress.com/2013/08/14/performance-of-user-mode-linux-as-a-libguestfs-backend/ > What do you think that it is good to backport UML support to 1.20? Difficult. I think it would be easier to forward-port the 'oldlinux' branch to libguestfs 1.24 or 1.26. However that is still not trivial, as in particular this patch touches a lot of code: https://github.com/libguestfs/libguestfs/commit/2d836027a0a273dbcafa4216f8ab554063d71bf3 A third alternative would be to use an upstream qemu & kernel on top of RHEL 5: http://libguestfs.org/guestfs-faq.1.html#how-can-i-compile-and-install-libguestfs-if-my-distro-doesnt-have-new-enough-qemu-supermin-kernel I think this third approach may be easiest of all, but will still require you to carefully fix any porting problems in libguestfs where we use newer (eg) glibc features than are found in RHEL 5. (Even easier is to move to RHEL 6 or 7) Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Mon, Sep 29, 2014 at 1:41 AM, Richard W.M. Jones wrote: > On Mon, Sep 29, 2014 at 01:35:08AM +0800, Zhi Yong Wu wrote: >> On Mon, Sep 29, 2014 at 1:27 AM, Richard W.M. Jones >> wrote: >> > User-Mode Linux is also a possibility. Slow but consistent >> Slow is a big concern... > > There are some measurements here: > > http://rwmj.wordpress.com/2013/08/14/performance-of-user-mode-linux-as-a-libguestfs-backend/ What do you think that it is good to backport UML support to 1.20? > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > libguestfs lets you edit virtual machines. Supports shell scripting, > bindings from many languages. http://libguestfs.org -- Regards, Zhi Yong Wu ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Mon, Sep 29, 2014 at 01:35:08AM +0800, Zhi Yong Wu wrote: > On Mon, Sep 29, 2014 at 1:27 AM, Richard W.M. Jones wrote: > > User-Mode Linux is also a possibility. Slow but consistent > Slow is a big concern... There are some measurements here: http://rwmj.wordpress.com/2013/08/14/performance-of-user-mode-linux-as-a-libguestfs-backend/ Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Mon, Sep 29, 2014 at 1:27 AM, Richard W.M. Jones wrote: > On Mon, Sep 29, 2014 at 01:22:19AM +0800, Zhi Yong Wu wrote: >> Yes, I am trying to run it in Xen Domain0. I thought that we can use >> Domain0 as a public libguestfs VM, This will avoid starting a new >> guest for virt-xxx every time, But Domain0 has no corresponding qemu >> task. So this way isn't available. >> Now, i am considering if we can run private VM for libguestfs which >> will keep running forever and if it will bring more trouble. > > User-Mode Linux is also a possibility. Slow but consistent Slow is a big concern... > performance. Unfortunately it lacks several important features > (notably qcow2 support). The other unfortunate thing is that we No matter, our image all use vhd or raw, not qcow2.:) > didn't support UML in 1.20 -- it was added in 1.24. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-builder quickly builds VMs from scratch > http://libguestfs.org/virt-builder.1.html -- Regards, Zhi Yong Wu ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Mon, Sep 29, 2014 at 01:22:19AM +0800, Zhi Yong Wu wrote: > Yes, I am trying to run it in Xen Domain0. I thought that we can use > Domain0 as a public libguestfs VM, This will avoid starting a new > guest for virt-xxx every time, But Domain0 has no corresponding qemu > task. So this way isn't available. > Now, i am considering if we can run private VM for libguestfs which > will keep running forever and if it will bring more trouble. User-Mode Linux is also a possibility. Slow but consistent performance. Unfortunately it lacks several important features (notably qcow2 support). The other unfortunate thing is that we didn't support UML in 1.20 -- it was added in 1.24. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Mon, Sep 29, 2014 at 1:14 AM, Richard W.M. Jones wrote: > On Mon, Sep 29, 2014 at 12:55:04AM +0800, Zhi Yong Wu wrote: >> On Mon, Sep 29, 2014 at 12:36 AM, Richard W.M. Jones >> wrote: >> > On Sun, Sep 28, 2014 at 11:43:17PM +0800, Zhi Yong Wu wrote: >> >> Yeah, but why did it happen when i directly issue guest VM via above >> >> command? >> > >> > OK I see. When libguestfs runs qemu-kvm, it sets up a TCP socket >> > first [on RHEL 5 -- it works differently upstream]. Without the >> > socket existing (and sending commands etc), the qemu-kvm command on >> > its own won't work. >> I got it, thanks. >> >> By the way, i found that virt-xxx usually has very poor performance on >> my box. e.g. virt-filesystems will return the result in 30s, >> virt-resize will need 30 minutes to complete resizing one disk. Every >> virt-xxx need to start one QEMU guest at first every time it is >> issued, so this takes too long time to run. I am trying to find out >> some ways to improve its perf. > > A good place to start is: > > http://libguestfs.org/guestfs-performance.1.html > > Are you running this inside a VM? Yes, I am trying to run it in Xen Domain0. I thought that we can use Domain0 as a public libguestfs VM, This will avoid starting a new guest for virt-xxx every time, But Domain0 has no corresponding qemu task. So this way isn't available. Now, i am considering if we can run private VM for libguestfs which will keep running forever and if it will bring more trouble. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-df lists disk usage of guests without needing to install any > software inside the virtual machine. Supports Linux and Windows. > http://people.redhat.com/~rjones/virt-df/ -- Regards, Zhi Yong Wu ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Mon, Sep 29, 2014 at 12:55:04AM +0800, Zhi Yong Wu wrote: > On Mon, Sep 29, 2014 at 12:36 AM, Richard W.M. Jones > wrote: > > On Sun, Sep 28, 2014 at 11:43:17PM +0800, Zhi Yong Wu wrote: > >> Yeah, but why did it happen when i directly issue guest VM via above > >> command? > > > > OK I see. When libguestfs runs qemu-kvm, it sets up a TCP socket > > first [on RHEL 5 -- it works differently upstream]. Without the > > socket existing (and sending commands etc), the qemu-kvm command on > > its own won't work. > I got it, thanks. > > By the way, i found that virt-xxx usually has very poor performance on > my box. e.g. virt-filesystems will return the result in 30s, > virt-resize will need 30 minutes to complete resizing one disk. Every > virt-xxx need to start one QEMU guest at first every time it is > issued, so this takes too long time to run. I am trying to find out > some ways to improve its perf. A good place to start is: http://libguestfs.org/guestfs-performance.1.html Are you running this inside a VM? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Mon, Sep 29, 2014 at 12:36 AM, Richard W.M. Jones wrote: > On Sun, Sep 28, 2014 at 11:43:17PM +0800, Zhi Yong Wu wrote: >> Yeah, but why did it happen when i directly issue guest VM via above command? > > OK I see. When libguestfs runs qemu-kvm, it sets up a TCP socket > first [on RHEL 5 -- it works differently upstream]. Without the > socket existing (and sending commands etc), the qemu-kvm command on > its own won't work. I got it, thanks. By the way, i found that virt-xxx usually has very poor performance on my box. e.g. virt-filesystems will return the result in 30s, virt-resize will need 30 minutes to complete resizing one disk. Every virt-xxx need to start one QEMU guest at first every time it is issued, so this takes too long time to run. I am trying to find out some ways to improve its perf. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-p2v converts physical machines to virtual machines. Boot with a > live CD or over the network (PXE) and turn machines into KVM guests. > http://libguestfs.org/virt-v2v -- Regards, Zhi Yong Wu ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Sun, Sep 28, 2014 at 11:43:17PM +0800, Zhi Yong Wu wrote: > Yeah, but why did it happen when i directly issue guest VM via above command? OK I see. When libguestfs runs qemu-kvm, it sets up a TCP socket first [on RHEL 5 -- it works differently upstream]. Without the socket existing (and sending commands etc), the qemu-kvm command on its own won't work. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v ___ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Sun, Sep 28, 2014 at 11:31 PM, Richard W.M. Jones wrote:
> On Sun, Sep 28, 2014 at 11:04:11PM +0800, Zhi Yong Wu wrote:
>> On Sun, Sep 28, 2014 at 6:48 PM, Richard W.M. Jones
>> wrote:
>> > On Sun, Sep 28, 2014 at 06:33:53PM +0800, Zhi Yong Wu wrote:
>> >> On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones
>> >> wrote:
>> >> > Which version of libguestfs is this? I think you'll have no hope of
>> >> #rpm -qa | grep libguestfs
>> >> libguestfs-1.20.8-1
>> >> libguestfs-tools-c-1.20.8-1
>> >> > getting upstream libguestfs to run on RHEL 5. There is a branch
>> >> Yes. The upstream maybe be involving in libvirtd, you know, there is
>> >> no libvirtd on RHEL5
>> >> > ('oldlinux') which may still work:
>> >> >
>> >> > https://github.com/libguestfs/libguestfs/commits/oldlinux
>> >> I will try it.
>> >
>> > I think the EPEL 5 package is the same as this branch. In particular
>> > the EPEL 5 package has the
>> > "Add-null-vmchannel-back-for-qemu-without-virt" patch which should
>> > make it work on RHEL 5, although for some reason it doesn't.
>> >
>> > Can you post the full, unedited output from 'libguestfs-test-tool'.
>> #libguestfs-test-tool
>>
>> *IMPORTANT NOTICE
>> *
>> * When reporting bugs, include the COMPLETE, UNEDITED
>> * output below in your bug report.
>> *
>>
>> PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/ali/bin/:/usr/ali/sbin/:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/zhiyong.wzy/bin
>> SELinux: Disabled
>> library version: 1.20.8
>> guestfs_get_append: (null)
>> guestfs_get_attach_method: appliance
>> guestfs_get_autosync: 1
>> guestfs_get_cachedir: /var/tmp
>> guestfs_get_direct: 0
>> guestfs_get_memsize: 500
>> guestfs_get_network: 0
>> guestfs_get_path: /usr/lib64/guestfs
>> guestfs_get_pgroup: 0
>> guestfs_get_qemu: /usr/bin/qemu-kvm
>> guestfs_get_recovery_proc: 1
>> guestfs_get_selinux: 0
>> guestfs_get_smp: 1
>> guestfs_get_tmpdir: /tmp
>> guestfs_get_trace: 0
>> guestfs_get_verbose: 1
>> host_cpu: x86_64
>> Launching appliance, timeout set to 600 seconds.
>> libguestfs: launch: attach-method=appliance
>> libguestfs: launch: tmpdir=/tmp/libguestfspcFf1K
>> libguestfs: launch: umask=0022
>> libguestfs: launch: euid=0
>> libguestfs: command: run: febootstrap-supermin-helper
>> libguestfs: command: run: \ --verbose
>> libguestfs: command: run: \ -f checksum
>> libguestfs: command: run: \ /usr/lib64/guestfs/supermin.d
>> libguestfs: command: run: \ x86_64
>> supermin helper [0ms] whitelist = (not specified), host_cpu =
>> x86_64, kernel = (null), initrd = (null), appliance = (null)
>> supermin helper [0ms] inputs[0] = /usr/lib64/guestfs/supermin.d
>> checking modpath /lib/modules/2.6.18-274.el5 is a directory
>> picked vmlinuz-2.6.18-274.el5 because modpath /lib/modules/2.6.18-274.el5
>> exists
>> supermin helper [0ms] finished creating kernel
>> supermin helper [0ms] visiting /usr/lib64/guestfs/supermin.d
>> supermin helper [0ms] visiting /usr/lib64/guestfs/supermin.d/base.img
>> supermin helper [1ms] visiting /usr/lib64/guestfs/supermin.d/daemon.img
>> supermin helper [1ms] visiting /usr/lib64/guestfs/supermin.d/hostfiles
>> supermin helper [00036ms] visiting /usr/lib64/guestfs/supermin.d/init.img
>> supermin helper [00036ms] visiting
>> /usr/lib64/guestfs/supermin.d/udev-rules.img
>> supermin helper [00036ms] adding kernel modules
>> supermin helper [00071ms] finished creating appliance
>> libguestfs: checksum of existing appliance:
>> 324cdbfc0cad1d0765d7648b529c39f0bd665c66a69ad941ae2c93ccaee20323
>> libguestfs: [00113ms] begin testing qemu features
>> libguestfs: command: run: /usr/bin/qemu-kvm
>> libguestfs: command: run: \ -nographic
>> libguestfs: command: run: \ -help
>> libguestfs: parse_qemu_version: failed to parse qemu version string ''
>> libguestfs: null_vmchannel_port = 33186
>> libguestfs: [00157ms] finished testing qemu features
>> libguestfs: accept_from_daemon: 0x6082b0 g->state = 1
>> [00158ms] /usr/bin/qemu-kvm \
>> -global virtio-blk-pci.scsi=off \
>> -nodefconfig \
>> -nodefaults \
>> -nographic \
>> -drive
>> file=/tmp/libguestfs-test-tool-sda-5XmXiw,cache=none,format=raw,if=virtio
>> \
>> -drive
>> file=/var/tmp/.guestfs-0/root.27302,snapshot=on,if=virtio,cache=unsafe
>> \
>> -machine accel=kvm:tcg \
>> -m 500 \
>> -no-reboot \
>> -no-hpet \
>> -serial stdio \
>> -net user,vlan=0,net=10.0.2.0/24 \
>> -net nic,model=virtio,vlan=0 \
>> -kernel /var/tmp/.guestfs-0/kernel.27302 \
>> -initrd /var/tmp/.guestfs-0/initrd.27302 \
>> -append 'panic=1 noapic console=ttyS0 udevtimeout=600
>> no_timer_check acpi=off printk.time=1 cgroup_disable=memory
>> root=/dev/vdb selinux=0 guestfs_vmchannel=tcp:10.0.2.2:33186
>> guestfs_verbose=1 TERM=vt100'Could not acc
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Sun, Sep 28, 2014 at 11:04:11PM +0800, Zhi Yong Wu wrote:
> On Sun, Sep 28, 2014 at 6:48 PM, Richard W.M. Jones wrote:
> > On Sun, Sep 28, 2014 at 06:33:53PM +0800, Zhi Yong Wu wrote:
> >> On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones
> >> wrote:
> >> > Which version of libguestfs is this? I think you'll have no hope of
> >> #rpm -qa | grep libguestfs
> >> libguestfs-1.20.8-1
> >> libguestfs-tools-c-1.20.8-1
> >> > getting upstream libguestfs to run on RHEL 5. There is a branch
> >> Yes. The upstream maybe be involving in libvirtd, you know, there is
> >> no libvirtd on RHEL5
> >> > ('oldlinux') which may still work:
> >> >
> >> > https://github.com/libguestfs/libguestfs/commits/oldlinux
> >> I will try it.
> >
> > I think the EPEL 5 package is the same as this branch. In particular
> > the EPEL 5 package has the
> > "Add-null-vmchannel-back-for-qemu-without-virt" patch which should
> > make it work on RHEL 5, although for some reason it doesn't.
> >
> > Can you post the full, unedited output from 'libguestfs-test-tool'.
> #libguestfs-test-tool
>
> *IMPORTANT NOTICE
> *
> * When reporting bugs, include the COMPLETE, UNEDITED
> * output below in your bug report.
> *
>
> PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/ali/bin/:/usr/ali/sbin/:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/zhiyong.wzy/bin
> SELinux: Disabled
> library version: 1.20.8
> guestfs_get_append: (null)
> guestfs_get_attach_method: appliance
> guestfs_get_autosync: 1
> guestfs_get_cachedir: /var/tmp
> guestfs_get_direct: 0
> guestfs_get_memsize: 500
> guestfs_get_network: 0
> guestfs_get_path: /usr/lib64/guestfs
> guestfs_get_pgroup: 0
> guestfs_get_qemu: /usr/bin/qemu-kvm
> guestfs_get_recovery_proc: 1
> guestfs_get_selinux: 0
> guestfs_get_smp: 1
> guestfs_get_tmpdir: /tmp
> guestfs_get_trace: 0
> guestfs_get_verbose: 1
> host_cpu: x86_64
> Launching appliance, timeout set to 600 seconds.
> libguestfs: launch: attach-method=appliance
> libguestfs: launch: tmpdir=/tmp/libguestfspcFf1K
> libguestfs: launch: umask=0022
> libguestfs: launch: euid=0
> libguestfs: command: run: febootstrap-supermin-helper
> libguestfs: command: run: \ --verbose
> libguestfs: command: run: \ -f checksum
> libguestfs: command: run: \ /usr/lib64/guestfs/supermin.d
> libguestfs: command: run: \ x86_64
> supermin helper [0ms] whitelist = (not specified), host_cpu =
> x86_64, kernel = (null), initrd = (null), appliance = (null)
> supermin helper [0ms] inputs[0] = /usr/lib64/guestfs/supermin.d
> checking modpath /lib/modules/2.6.18-274.el5 is a directory
> picked vmlinuz-2.6.18-274.el5 because modpath /lib/modules/2.6.18-274.el5
> exists
> supermin helper [0ms] finished creating kernel
> supermin helper [0ms] visiting /usr/lib64/guestfs/supermin.d
> supermin helper [0ms] visiting /usr/lib64/guestfs/supermin.d/base.img
> supermin helper [1ms] visiting /usr/lib64/guestfs/supermin.d/daemon.img
> supermin helper [1ms] visiting /usr/lib64/guestfs/supermin.d/hostfiles
> supermin helper [00036ms] visiting /usr/lib64/guestfs/supermin.d/init.img
> supermin helper [00036ms] visiting
> /usr/lib64/guestfs/supermin.d/udev-rules.img
> supermin helper [00036ms] adding kernel modules
> supermin helper [00071ms] finished creating appliance
> libguestfs: checksum of existing appliance:
> 324cdbfc0cad1d0765d7648b529c39f0bd665c66a69ad941ae2c93ccaee20323
> libguestfs: [00113ms] begin testing qemu features
> libguestfs: command: run: /usr/bin/qemu-kvm
> libguestfs: command: run: \ -nographic
> libguestfs: command: run: \ -help
> libguestfs: parse_qemu_version: failed to parse qemu version string ''
> libguestfs: null_vmchannel_port = 33186
> libguestfs: [00157ms] finished testing qemu features
> libguestfs: accept_from_daemon: 0x6082b0 g->state = 1
> [00158ms] /usr/bin/qemu-kvm \
> -global virtio-blk-pci.scsi=off \
> -nodefconfig \
> -nodefaults \
> -nographic \
> -drive
> file=/tmp/libguestfs-test-tool-sda-5XmXiw,cache=none,format=raw,if=virtio
> \
> -drive
> file=/var/tmp/.guestfs-0/root.27302,snapshot=on,if=virtio,cache=unsafe
> \
> -machine accel=kvm:tcg \
> -m 500 \
> -no-reboot \
> -no-hpet \
> -serial stdio \
> -net user,vlan=0,net=10.0.2.0/24 \
> -net nic,model=virtio,vlan=0 \
> -kernel /var/tmp/.guestfs-0/kernel.27302 \
> -initrd /var/tmp/.guestfs-0/initrd.27302 \
> -append 'panic=1 noapic console=ttyS0 udevtimeout=600
> no_timer_check acpi=off printk.time=1 cgroup_disable=memory
> root=/dev/vdb selinux=0 guestfs_vmchannel=tcp:10.0.2.2:33186
> guestfs_verbose=1 TERM=vt100'Could not access KVM kernel module: No
> such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Linux version 2.6.18-274.el5 (mockbu...@x86
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Sun, Sep 28, 2014 at 6:48 PM, Richard W.M. Jones wrote:
> On Sun, Sep 28, 2014 at 06:33:53PM +0800, Zhi Yong Wu wrote:
>> On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones
>> wrote:
>> > Which version of libguestfs is this? I think you'll have no hope of
>> #rpm -qa | grep libguestfs
>> libguestfs-1.20.8-1
>> libguestfs-tools-c-1.20.8-1
>> > getting upstream libguestfs to run on RHEL 5. There is a branch
>> Yes. The upstream maybe be involving in libvirtd, you know, there is
>> no libvirtd on RHEL5
>> > ('oldlinux') which may still work:
>> >
>> > https://github.com/libguestfs/libguestfs/commits/oldlinux
>> I will try it.
>
> I think the EPEL 5 package is the same as this branch. In particular
> the EPEL 5 package has the
> "Add-null-vmchannel-back-for-qemu-without-virt" patch which should
> make it work on RHEL 5, although for some reason it doesn't.
>
> Can you post the full, unedited output from 'libguestfs-test-tool'.
#libguestfs-test-tool
*IMPORTANT NOTICE
*
* When reporting bugs, include the COMPLETE, UNEDITED
* output below in your bug report.
*
PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/ali/bin/:/usr/ali/sbin/:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/zhiyong.wzy/bin
SELinux: Disabled
library version: 1.20.8
guestfs_get_append: (null)
guestfs_get_attach_method: appliance
guestfs_get_autosync: 1
guestfs_get_cachedir: /var/tmp
guestfs_get_direct: 0
guestfs_get_memsize: 500
guestfs_get_network: 0
guestfs_get_path: /usr/lib64/guestfs
guestfs_get_pgroup: 0
guestfs_get_qemu: /usr/bin/qemu-kvm
guestfs_get_recovery_proc: 1
guestfs_get_selinux: 0
guestfs_get_smp: 1
guestfs_get_tmpdir: /tmp
guestfs_get_trace: 0
guestfs_get_verbose: 1
host_cpu: x86_64
Launching appliance, timeout set to 600 seconds.
libguestfs: launch: attach-method=appliance
libguestfs: launch: tmpdir=/tmp/libguestfspcFf1K
libguestfs: launch: umask=0022
libguestfs: launch: euid=0
libguestfs: command: run: febootstrap-supermin-helper
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ -f checksum
libguestfs: command: run: \ /usr/lib64/guestfs/supermin.d
libguestfs: command: run: \ x86_64
supermin helper [0ms] whitelist = (not specified), host_cpu =
x86_64, kernel = (null), initrd = (null), appliance = (null)
supermin helper [0ms] inputs[0] = /usr/lib64/guestfs/supermin.d
checking modpath /lib/modules/2.6.18-274.el5 is a directory
picked vmlinuz-2.6.18-274.el5 because modpath /lib/modules/2.6.18-274.el5 exists
supermin helper [0ms] finished creating kernel
supermin helper [0ms] visiting /usr/lib64/guestfs/supermin.d
supermin helper [0ms] visiting /usr/lib64/guestfs/supermin.d/base.img
supermin helper [1ms] visiting /usr/lib64/guestfs/supermin.d/daemon.img
supermin helper [1ms] visiting /usr/lib64/guestfs/supermin.d/hostfiles
supermin helper [00036ms] visiting /usr/lib64/guestfs/supermin.d/init.img
supermin helper [00036ms] visiting /usr/lib64/guestfs/supermin.d/udev-rules.img
supermin helper [00036ms] adding kernel modules
supermin helper [00071ms] finished creating appliance
libguestfs: checksum of existing appliance:
324cdbfc0cad1d0765d7648b529c39f0bd665c66a69ad941ae2c93ccaee20323
libguestfs: [00113ms] begin testing qemu features
libguestfs: command: run: /usr/bin/qemu-kvm
libguestfs: command: run: \ -nographic
libguestfs: command: run: \ -help
libguestfs: parse_qemu_version: failed to parse qemu version string ''
libguestfs: null_vmchannel_port = 33186
libguestfs: [00157ms] finished testing qemu features
libguestfs: accept_from_daemon: 0x6082b0 g->state = 1
[00158ms] /usr/bin/qemu-kvm \
-global virtio-blk-pci.scsi=off \
-nodefconfig \
-nodefaults \
-nographic \
-drive
file=/tmp/libguestfs-test-tool-sda-5XmXiw,cache=none,format=raw,if=virtio
\
-drive
file=/var/tmp/.guestfs-0/root.27302,snapshot=on,if=virtio,cache=unsafe
\
-machine accel=kvm:tcg \
-m 500 \
-no-reboot \
-no-hpet \
-serial stdio \
-net user,vlan=0,net=10.0.2.0/24 \
-net nic,model=virtio,vlan=0 \
-kernel /var/tmp/.guestfs-0/kernel.27302 \
-initrd /var/tmp/.guestfs-0/initrd.27302 \
-append 'panic=1 noapic console=ttyS0 udevtimeout=600
no_timer_check acpi=off printk.time=1 cgroup_disable=memory
root=/dev/vdb selinux=0 guestfs_vmchannel=tcp:10.0.2.2:33186
guestfs_verbose=1 TERM=vt100'Could not access KVM kernel module: No
such file or directory
failed to initialize KVM: No such file or directory
Back to tcg accelerator.
Linux version 2.6.18-274.el5 (mockbu...@x86-002.build.bos.redhat.com)
(gcc version 4.1.2 20080704 (Red Hat 4.1.2-51)) #1 SMP Fri Jul 8
17:36:59 EDT 2011
Command line: panic=1 noapic console=ttyS0 udevtimeout=600
no_timer_check acpi=off printk.time=1 cgroup_disable=memory
root=/dev/vdb selinux=0 guestfs_vmchannel=tcp:10.0.2.2:33186
g
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Sun, Sep 28, 2014 at 06:33:53PM +0800, Zhi Yong Wu wrote:
> On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones wrote:
> > Which version of libguestfs is this? I think you'll have no hope of
> #rpm -qa | grep libguestfs
> libguestfs-1.20.8-1
> libguestfs-tools-c-1.20.8-1
> > getting upstream libguestfs to run on RHEL 5. There is a branch
> Yes. The upstream maybe be involving in libvirtd, you know, there is
> no libvirtd on RHEL5
> > ('oldlinux') which may still work:
> >
> > https://github.com/libguestfs/libguestfs/commits/oldlinux
> I will try it.
I think the EPEL 5 package is the same as this branch. In particular
the EPEL 5 package has the
"Add-null-vmchannel-back-for-qemu-without-virt" patch which should
make it work on RHEL 5, although for some reason it doesn't.
Can you post the full, unedited output from 'libguestfs-test-tool'.
> By the way, the libguestfs src can't build one available base.img and
> daemon.img.
>
> #ll /usr/lib64/guestfs/supermin.d/
> total 1752
> -rw-r--r-- 1 root root1536 Sep 27 14:39 base.img<- it can't work.
Not sure what you mean. Why wouldn't it work?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
___
Libguestfs mailing list
Libguestfs@redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones wrote:
> On Sun, Sep 28, 2014 at 04:30:37PM +0800, Zhi Yong Wu wrote:
>> HI,
>>
>> On a RHEL5 box, i tried to directly run guest which was issued by
>> libguestfs virt-xxx commands as below. But after some minutes, it
>> exited exceptionally.
>>
>> Does anyone also hit the issue or know the reason?
>
> As it says in the error message itself:
>
>> Failed to connect to virtio-serial channel.
>>
>> This is a fatal error and the appliance will now exit.
>>
>> Usually this error is caused by either QEMU or the appliance
>> kernel not supporting the vmchannel method that the
>> libguestfs library chose to use. Please run
>> 'libguestfs-test-tool' and provide the complete, unedited
>> output to the libguestfs developers, either in a bug report
>> or on the libguestfs redhat com mailing list.
>
> Which version of libguestfs is this? I think you'll have no hope of
#rpm -qa | grep libguestfs
libguestfs-1.20.8-1
libguestfs-tools-c-1.20.8-1
> getting upstream libguestfs to run on RHEL 5. There is a branch
Yes. The upstream maybe be involving in libvirtd, you know, there is
no libvirtd on RHEL5
> ('oldlinux') which may still work:
>
> https://github.com/libguestfs/libguestfs/commits/oldlinux
I will try it.
By the way, the libguestfs src can't build one available base.img and
daemon.img.
#ll /usr/lib64/guestfs/supermin.d/
total 1752
-rw-r--r-- 1 root root1536 Sep 27 14:39 base.img<- it can't work.
-rw-r--r-- 1 root root 1760768 Sep 27 14:39 daemon.img
-rw-r--r-- 1 root root 10772 Sep 27 14:39 hostfiles
-rw-r--r-- 1 root root4608 Sep 27 14:39 init.img
-rw-r--r-- 1 root root2048 Sep 27 14:39 udev-rules.img
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-builder quickly builds VMs from scratch
> http://libguestfs.org/virt-builder.1.html
--
Regards,
Zhi Yong Wu
___
Libguestfs mailing list
Libguestfs@redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
Re: [Libguestfs] Why libguestfs guest exist exceptionally?
On Sun, Sep 28, 2014 at 04:30:37PM +0800, Zhi Yong Wu wrote:
> HI,
>
> On a RHEL5 box, i tried to directly run guest which was issued by
> libguestfs virt-xxx commands as below. But after some minutes, it
> exited exceptionally.
>
> Does anyone also hit the issue or know the reason?
As it says in the error message itself:
> Failed to connect to virtio-serial channel.
>
> This is a fatal error and the appliance will now exit.
>
> Usually this error is caused by either QEMU or the appliance
> kernel not supporting the vmchannel method that the
> libguestfs library chose to use. Please run
> 'libguestfs-test-tool' and provide the complete, unedited
> output to the libguestfs developers, either in a bug report
> or on the libguestfs redhat com mailing list.
Which version of libguestfs is this? I think you'll have no hope of
getting upstream libguestfs to run on RHEL 5. There is a branch
('oldlinux') which may still work:
https://github.com/libguestfs/libguestfs/commits/oldlinux
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
Libguestfs mailing list
Libguestfs@redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
[Libguestfs] Why libguestfs guest exist exceptionally?
HI, On a RHEL5 box, i tried to directly run guest which was issued by libguestfs virt-xxx commands as below. But after some minutes, it exited exceptionally. Does anyone also hit the issue or know the reason? #/usr/bin/qemu-kvm -global virtio-blk-pci.scsi=off -nodefconfig -nodefaults -nographic -drive file=ubuntu1204_64_20G_aliaegis_20140811.vhd,snapshot=on,if=virtio -drive file=ubuntu-test.vhd,cache=none,if=virtio -drive file=/var/tmp/.guestfs-0/root.28754,snapshot=on,if=virtio,cache=unsafe -machine accel=kvm:tcg -m 500 -no-reboot -no-hpet -serial stdio -net user,vlan=0,net=10.0.2.0/24 -net nic,model=virtio,vlan=0 -kernel /var/tmp/.guestfs-0/kernel.28754 -initrd /var/tmp/.guestfs-0/initrd.28754 -append 'panic=1 noapic console=ttyS0 udevtimeout=600 no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/vdc selinux=0 guestfs_vmchannel=tcp:10.0.2.2:45041 guestfs_verbose=1 TERM=vt100' Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory Back to tcg accelerator. Linux version 2.6.18-274.el5 (mockbu...@x86-002.build.bos.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-51)) #1 SMP Fri Jul 8 17:36:59 EDT 2011 Command line: panic=1 noapic console=ttyS0 udevtimeout=600 no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/vdc selinux=0 guestfs_vmchannel=tcp:10.0.2.2:45041 guestfs_verbose=1 TERM=vt100 BIOS-provided physical RAM map: BIOS-e820: 0001 - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 1f3fe000 (usable) BIOS-e820: 1f3fe000 - 1f40 (reserved) BIOS-e820: fffc - 0001 (reserved) DMI 2.4 present. No NUMA configuration found Faking a node at -1f3fe000 Bootmem setup node 0 -1f3fe000 Memory for crash kernel (0x0 to 0x0) notwithin permissible range disabling kdump Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: BOCHSCPU Product ID: 0.1 APIC at: 0xFEE0 Processor #0 6:13 APIC version 17 I/O APIC #0 Version 17 at 0xFEC0. Setting APIC routing to flat Processors: 1 Nosave address range: 0009f000 - 000a Nosave address range: 000a - 000f Nosave address range: 000f - 0010 Allocating PCI resources starting at 2000 (gap: 1f40:e0bc) SMP: Allowing 1 CPUs, 0 hotplug CPUs Built 1 zonelists. Total pages: 124645 Kernel command line: panic=1 noapic console=ttyS0 udevtimeout=600 no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/vdc selinux=0 guestfs_vmchannel=tcp:10.0.2.2:45041 guestfs_verbose=1 TERM=vt100 Unknown boot option `printk.time=1': ignoring Initializing CPU#0 PID hash table entries: 2048 (order: 11, 16384 bytes) Console: colour *CGA 80x25 Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Checking aperture... ACPI: DMAR not present Memory: 494496k/511992k available (2603k kernel code, 17044k reserved, 1660k data, 224k init) Calibrating delay loop (skipped), value calculated using timer frequency.. 4806.63 BogoMIPS (lpj=2403317) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU 0/0 -> Node 0 SMP alternatives: switching to UP code Freeing SMP alternatives: 32k freed Using local APIC timer interrupts. Detected 62.582 MHz APIC timer. Brought up 1 CPUs WARNING: CPU#0: NMI appears to be stuck (0->0)! time.c: Using 1.193182 MHz WALL PIT GTOD PIT/TSC timer. time.c: Detected 2403.317 MHz processor. checking if image is initramfs... it is Freeing initrd memory: 2800k freed NET: Registered protocol family 16 PCI: Using configuration type 1 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Probing PCI hardware ACPI Error (tbget-0168): Invalid address flags 8 [20060707] ACPI Error (tbget-0168): Invalid address flags 8 [20060707] ACPI Error (tbget-0168): Invalid address flags 8 [20060707] ACPI Error (tbget-0168): Invalid address flags 8 [20060707] PCI quirk: region b000-b03f claimed by PIIX4 ACPI PCI quirk: region b100-b10f claimed by PIIX4 SMB ACPI Error (tbget-0168): Invalid address flags 8 [20060707] ACPI Error (tbget-0168): Invalid address flags 8 [20060707] ACPI Error (tbget-0168): Invalid address flags 8 [20060707] ACPI Error (tbget-0168): Invalid address flags 8 [20060707] PCI: Using IRQ router PIIX/ICH [8086/7000] at :00:01.0 NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protoc
