similar to: There's no output when connecting to console of domain on PowerPC

Hi, I tried to use libvirt to run KVM/QEMU on Freescale PowerPC platforms. So far there's only one serial device (spapr-vty) defined in QEMU to work as console for IBM PSeries platform. There's no serial device support in QEMU for Freescale PowerPC (ePAPR). libvirt/src/qemu/qemu_command.c /* This function generates the correct '-device' string for character * devices of each

2015-03-02 23:41 GMT+03:00 Brian Rak <brak@gameservers.com>: > In IRC, I was directed to this patch: > https://www.redhat.com/archives/libvir-list/2015-February/msg01212.html ... > which does exactly what I was looking for. It doesn't build cleanly in that > state, but it's pretty trivial fix (needs actualType added to the function > definition for

Hi,everyone, there is a problem with libvirt support spice protocol. i use the following patch file,but it seems not success.anyone have an idea about that? thanks. patch file: This adds an element <graphics type='spice' port='5903' tlsPort='5904' listen='127.0.0.1'/> This is the bare minimum that should be exposed in the guest config for SPICE. Other

HI, all My daemon exists a libvirt API call: virEventRegisterDefaultImpl(); once I called the virEventRegisterDefaultImpl() ,must be core ,the bt stack is: (gdb) bt #0 free (ptr=0x1) at include/jemalloc/internal/arena.h:652 #1 0x00007f57690a488a in virFree () from /lib64/libvirt.so.0 #2 0x00007f57690c3562 in virResetError () from /lib64/libvirt.so.0 #3 0x00007f57690c49ad in

On Wed, Jun 04, 2014 at 03:29:11PM +0530, abhishek jain wrote: > supermin: kernel: SUPERMIN_KERNEL environment variable /boot/uImage > supermin: failed to find a suitable kernel (host_cpu=powerpc64). > > I looked for kernels in /boot and modules in /lib/modules. If you follow the code in src/kernel.ml you'll see that this means supermin was unable to get the kernel version from

On Wed, Jun 04, 2014 at 02:25:58PM +0530, abhishek jain wrote: > Hi RIch > > > Below are the details of the powerpc ubuntu system ... > > ls -l /boot/ > total 10200 > -rw-r--r-- 1 root root 5224765 Nov 22 2013 uImage > -rw-r--r-- 1 root root 5192861 Nov 22 2013 uImage.orig > > > ls -l /lib/modules/ > total 4 > drwxr-xr-x 3 ubuntu ubuntu 4096 Jun 3

On Wed, Jun 04, 2014 at 01:18:47PM +0530, abhishek jain wrote: > Hi RIch > > Below are the necessary details of the system.. > > > *ls -l /boot/total 10200-rw-r--r-- 1 root root 5224765 Nov 22 2013 > uImage-rw-r--r-- 1 root root 5192861 Nov 22 2013 uImage.origls -l > /lib/modules/total 4drwxr-xr-x 3 ubuntu ubuntu 4096 Jun 3 07:21 > 3.8.13-rt9-QorIQ-SDK-V1.4uname

Hi Rich I'm noe getting the below logs after running libguestfs-test-tool.. SUPERMIN_MODULES=/lib/modules/3.8.13-rt9-QorIQ-SDK-V1.4 SUPERMIN_KERNEL=/boot/vmlinuz-3.8.13-rt9-QorIQ-SDK-V1.4 PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/usr/local/bin SELinux: sh: getenforce: command not found guestfs_get_append: (null) guestfs_get_autosync: 1 guestfs_get_backend: direct

Hi, What's the difference between QEMU snapshot and libvirt snapshot? # qemu-img create -f qcow2 disk.img 512 Formatting 'disk.img', fmt=qcow2 size=512 encryption=off cluster_size=65536 lazy_refcounts=off # qemu-img info disk.img image: disk.img file format: qcow2 virtual size: 512 (512 bytes) disk size: 136K cluster_size: 65536 Format specific information: compat: 1.1 lazy

Here is v11. Fixed comments/bugs and updated against the latest libvirt.git. Changes v10->v11: - fixed comments on each patches - fixed cgroup handling in patch 3. - fixed MODIFY_CURRENT handling in patch 4. most of diff comes from refactoring qemu/qemu_driver.c -- conf/domain_conf.c | 40 ++ conf/domain_conf.h | 5 libvirt_private.syms | 3 qemu/qemu_driver.c | 727

Hi, Excuse me, I have a question when I reading the libvirt source codes. I have known the process of how libvirt start/manage qemu, since I need to write a driver based on libvirt. But one thing also confused, please give me some tips. 1. In qemu_command.c, there is a function call "cmd = virCommandNewArgList(emulator, "-S", NULL);", which

Hi everyone, I incidentally configured two IDE controller for my machine-1.2 VM(it might be virsh attach-disk to blame), and I got the error message "Only a single IDE controller is unsupported...". I can't understand this error message, I think it means I HAVE to configure two or more IDE controllers until I looked it up in the source. At libvirt-1.2.22/src/qemu/qemu_command.c:

[adding back the ML, you probably hit reply instead of reply-all, this way other people might help if they know more] On Fri, Jun 02, 2017 at 08:10:01AM -0400, Michael C. Cambria wrote: > >Hi, > >libvirtd never seems to get notified that there is work to do. journalct >-f indicated that nothing was logged when connections were attempted via >virsh. > >I also tried

On 06/03/2017 05:47 PM, Martin Kletzander wrote: > On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria wrote: >> I also tried stopping libvirtd, renaming both qemu-system-i386 and >> qemu-system-x86_64, start libvirtd. Things get further along; dnsmasq >> log messages show up. >> >> $ sudo systemctl status libvirtd.service >> ● libvirtd.service -

Hi, Now that the Arndale board is supported in upstream Xen I don''t get any output on the serial console. I followed the instructions on the wiki with no luck: The xen repository I''m using is: git://xenbits.xen.org/xen.git last commit: 61c6dfce3296da2643c4c4f90eaab6fa3c1cf8b3 The linux repository is: git://xenbits.xen.org/people/julieng/linux-arm.git last commit:

On 06/04/2017 05:46 AM, Martin Kletzander wrote: > On Sat, Jun 03, 2017 at 08:27:08PM -0400, Michael C Cambria wrote: >> >> >> On 06/03/2017 05:47 PM, Martin Kletzander wrote: >>> On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria wrote: >>>> I also tried stopping libvirtd, renaming both qemu-system-i386 and >>>> qemu-system-x86_64,

Hi, I'am just wondering why there's no support for vhost-net (qemu) in an ethernet domain (<interface type='ethernet'>) ? below code from qemu_command.c: if (actualType == VIR_DOMAIN_NET_TYPE_NETWORK || actualType == VIR_DOMAIN_NET_TYPE_BRIDGE || actualType == VIR_DOMAIN_NET_TYPE_DIRECT) { /* Attempt to use

On Fri, Dec 04, 2015 at 10:42:30AM +0800, Tashi Lu wrote: > Hi everyone, > > I incidentally configured two IDE controller for my machine-1.2 VM(it > might be virsh attach-disk to blame), and I got the error message > "Only a single IDE controller is unsupported...". I can't understand > this error message, I think it means I HAVE to configure two or more > IDE

As planned the new release is available at: ftp://libvirt.org/libvirt/ It is a rather large release with near 400 commits included. From an user point of view the main improvement is likely to be when using migration as various work has been done to extend the protocol and to avoid having the migration command stop other concurrent operations (like virsh list). See below for a number of

On Sat, Jun 03, 2017 at 08:27:08PM -0400, Michael C Cambria wrote: > > >On 06/03/2017 05:47 PM, Martin Kletzander wrote: >> On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria wrote: >>> I also tried stopping libvirtd, renaming both qemu-system-i386 and >>> qemu-system-x86_64, start libvirtd. Things get further along; dnsmasq >>> log messages show