similar to: reboot command lost?

Hi! I am trying to setup a guest using virt-install script: /usr/bin/virt-install -n fc18guest5 -r 1024 \ --disk path=/home/aik/virtimg/fc18guest,size=8 \ -c /home/aik/virtimg/Fedora-18-ppc64-DVD.iso \ --video vga --arch=ppc64 -d --machine=pseries And it fails. I could not find any relevant log in /var/log/libvirt/ so I simply hacked /usr/local/bin/qemu-system-ppc64 to print all the

Hi! I am trying libvirt on POWERPC64 with the default settings such as selinux enabled. It is all good till I move images out of /var/lib/libvirt/images/. http://libvirt.org/drvqemu.html#securityselinux is saying that "If attempting to use disk images in another location, the user/administrator must ensure the directory has be given this requisite label. Likewise physical block devices

Hi, When I use 'virConnectOpenAuth' function to connect to '192.168.1.102' libvirtd with ssh, Code below, the screen print the dialog "root at 192.168.1.102's password:" , and only After I type the password, the connection can be created. How can I connect to libvirtd with ssh automatically? No need to type the password manually. char *au[2] = {"root",

Thanks Wangkai but libvirt infact pre-configures network tap devices and pre-opens /dev/vhost-net file and passes these to qemu as open, ready to use file descriptors. My issue is that my qemu requires that /dev/vhost-net directory is removed and it's kernel module be unloaded. Then it creates a vhost -net device using its own configuration. On 24 July 2014 07:35, Wangkai (Kevin,C)

hi, contacting this mailing list is my last-ditch effort to somehow come to a working configuration where postfix "ends in" dovecot, IE for special LDAP-based users, featured in the virtual mailbox delivery, dovecot would act as LDA. here's the deal. i've set up dovecot's access to the LDAP server, and for the purposes of being an IMAP server and a SASL auth backend,

From: "Richard W.M. Jones" <rjones at redhat.com> This commit models libvirt authentication events through the API, adding one new event (GUESTFS_EVENT_LIBVIRT_AUTH) and several new APIs: guestfs_set_libvirt_supported_credentials guestfs_get_libvirt_requested_credentials guestfs_get_libvirt_requested_credential_prompt guestfs_get_libvirt_requested_credential_challenge

Well, I don't know about yuuuge security risk (not saying there isn't any...), but if this concerns you, you can also use LTMP instead, which is probably a better solution here. Aki On 31.07.2018 13:42, Andras Kemeny wrote: > > yeah, the only problem about that is it's a yuuuge security risk :), > and also, postfix simply won't let me: > > Jul 31 02:20:37 rhyno

https://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP Aki On 31.07.2018 14:35, Andras Kemeny wrote: > > can you point me to an url regarding LTMP between postfix and dovecot? > it might be an area worth exploring for me. > > thanks, > a > > > 2018. 07. 31. 12:46 keltez?ssel, Aki Tuomi ?rta: >> >> Well, I don't know about yuuuge security risk (not saying

hi (especially to you, Aki), so to solve the previous UID issue, i went the full LMTP route. however, i seem to be having problems with the prefetch userdb (i'm trying to minimize load on the LDAP server). namely, the log says: Aug? 2 00:15:35 rhyno postfix/submission/smtpd[21158]: 5EEF35C05C5: client=localhost[127.0.0.1], sasl_method=login, sasl_username=aik Aug? 2 00:15:40 rhyno

you mean i should define another, "fallback" userdb service if prefetch doesn't work for some reason? is it the problem that it's a chicken and egg scenario and with LMTP address verification (from postfix) there is no login beforehand so then dovecot needs to consult the userdb once again and having no fallback mechanism, it gives up? i can understand that, but then it

ah well, but i'm not using sql at all. here's doveconf -n: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-4-amd64 x86_64 Debian 9.4 auth_cache_negative_ttl = 0 auth_mechanisms = plain login hostname = rhyno.tech mail_debug = yes mail_location = maildir:~/mail namespace inbox { ? inbox = yes ? location = ? mailbox Drafts { ???

Hi forum, I'm trying to get peimg.exe running on wine for some time, now. Unfortunately I didn't succeed yet. It would be great to get some hints here. Peimg.exe is an application which is used to add hardware drivers in Windows PE "images" to be used during the installation Process of Vista and 2008 Servers. It is part of the windows AIK. While we are using a linux-based

Il 20/08/2013 11:59, Timon Wang ha scritto: > On Tue, Aug 20, 2013 at 4:33 PM, Paolo Bonzini <pbonzini@redhat.com> wrote: >> Il 20/08/2013 08:00, Timon Wang ha scritto: >>> <disk type='file' device='disk'> >>> <driver name='qemu' type='raw' cache='none'/> >>> <source

Hi, I was wondering whether it's possible to run libvirtd inside a chroot environment. The assumption is that only one instance of libvirtd would be running on the machine at a time, but still, inside chroot. Currently in my chroot env I have: - /dev/kvm added with mknod - /dev/vhost-net added with mknod - mounted:   - /dev/net   - /dev/shm   - /run/dbus When I run libvirtd in

Il 20/08/2013 12:42, Timon Wang ha scritto: > [root@localhost /]# ls -l /dev/VM-IMAGES-BACKUP-DO-NOT-REMOVE/q_disk > lrwxrwxrwx. 1 root root 8 8月 20 17:38 > /dev/VM-IMAGES-BACKUP-DO-NOT-REMOVE/q_disk -> ../dm-13 > [root@localhost /]# sg_inq /dev/VM-IMAGES-BACKUP-DO-NOT-REMOVE/q_disk > standard INQUIRY: > PQual=0 Device_type=0 RMB=0 version=0x05 [SPC-3] > [AERC=0]

On 17.05.2011, at 08:47, David Gibson wrote: > From: Alexey Kardashevskiy <aik at ozlabs.ru> > > The recently added pseries machine does not currently support PCI > emulation. For the (upcoming) kvm case, this is quite difficult to do > because the preferred HV mode for the host kernel does not allow MMIO > emulation (a hardware limitation). > > Therefore, to

On 17.05.2011, at 08:47, David Gibson wrote: > From: Alexey Kardashevskiy <aik at ozlabs.ru> > > The recently added pseries machine does not currently support PCI > emulation. For the (upcoming) kvm case, this is quite difficult to do > because the preferred HV mode for the host kernel does not allow MMIO > emulation (a hardware limitation). > > Therefore, to

--- src/guestfs-internal.h | 1 + src/libvirt-auth.c | 55 +++++++++++++++++++++++++++++++++++++++++--------- 2 files changed, 46 insertions(+), 10 deletions(-) diff --git a/src/guestfs-internal.h b/src/guestfs-internal.h index 5356920..d81fa6b 100644 --- a/src/guestfs-internal.h +++ b/src/guestfs-internal.h @@ -469,6 +469,7 @@ struct guestfs_h unsigned int nr_supported_credentials;

For qemu, the default vhost drive file is “/dev/vhost-net”, when you configured vhost on. Give the command “modprobe vhost-net” to add host kernel support for vhost. This is cannot controlled by libvirt I think. Wangkai From: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] On Behalf Of Asadullah Hussain Sent: Thursday, July 24, 2014 12:43 AM To:

On Thu, Jul 24, 2014 at 08:42:47AM +0500, Asadullah Hussain wrote: > Thanks Wangkai but libvirt infact pre-configures network tap devices and > pre-opens /dev/vhost-net file and passes these to qemu as open, ready to > use file descriptors. > > My issue is that my qemu requires that /dev/vhost-net directory is removed > and it's kernel module be unloaded. Then it creates a