similar to: Slow boot when no serial pty connected

On Tue, Dec 15, 2015 at 09:47:41PM +0100, David Caro wrote: > >Hi everyone! > >It's the first time I send a message to this list, I hope it's not the last :) > >So my issue is that when booting a disk image generated with virt-builder [1] >it takes more than 5 minutes, waiting in the boot screen that says: > >" >Booting from disk... >press any key to

Hi, I am trying to set my VMs for redirecting their consoles to a file but its important to keep the virsh console access to solve any problem I can find while they are running. I tried several settings through libvirt (serial and console tags) but I can not get the key. Any suggestion? Any help? Many thanks in advance. Carlos G.

Hey all! Just a reminder, the CentOS Virt SIG meeting is tomorrow, 2pm, on #centos-devel (freenode IRC). Agenda items I've got: * Xen 4.4.1 for C6 update (finally) - Got xen 4.4.1 w/ updated XenServer blktap working, + libvirt - Other changes to consider: xend off by default, revert "favor qdisk" change * oVirt joining SIG? * Meetings over Christmas - proposal: Cancel phone

I didn't see what are the main differences in http://libguestfs.org/guestfs.3.html#backend Specifically, I'm interested in what is faster (direct sounds faster to me), and if there are any major restrictions (networking?) Here's an example command we are running (sorry, Python'ish, but you'll get it): ['virt-sysprep', '--connect', 'qemu:///system',

Il 19/03/2015 15:46, George Dunlap ha scritto: > On Thu, Mar 19, 2015 at 2:39 PM, Karanbir Singh <mail-lists at karan.org> wrote: >> On 03/19/2015 12:23 PM, George Dunlap wrote: >>> On Thu, Mar 19, 2015 at 12:20 PM, Sandro Bonazzola <sbonazzo at redhat.com> wrote: >>>> Hi, >>>> following Cloud SIG example[1] I would like to start defining the

Hello I have error virt-v2v: error: unable to rebuild initrd (/boot/initramfs-4.2.3-300.fc23.x86_64.img) because mkinitrd or dracut was not found in the guest My physical machine run on fedora23 Boot on usb made from virt-p2v-livecd-1.32.0.fc23.iso <http://oirase.annexia.org/virt-p2v/virt-p2v-livecd-1.32.0.fc23.iso> Log joined to this mail Do you have this problem ?

Hi folks I use libvirt to programmatically spawn lxc containers I am facing an issue when migrating from fedora23 to fedora24 I use the stock kernel and libvirt version on both deployments, i.e.: f23: libvirt-1.2.18.3-2.fc23.x86_64 - kernel 4.5.7-202.fc23.x86_64 f24: libvirt-1.3.3.1-4.fc24.x86_64 - kernel 4.6.3-300.fc24.x86_64 First off, I need to outline that the host installation is done

Hi, I wonder if someone can provide pointers on what might be wrong with my setup. I'm running a kvm host Fedora23 with rawhide kernel on top of a skylake cpu - Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz (family: 0x6, model: 0x4e, stepping: 0x3) As part of an experiment, I have enabled Nested virt support on the host and created a fedora23 guest with virt-manager using host-passthrough as the

Hello, I have first a question (and then may be a problem), that I have difficulties to understand and eventually to investigate. On each of my guests VM, I see constantly a RX dropped number increasing , Even if the VM does nothing ! ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.100.15 netmask 255.255.255.0 broadcast 192.168.100.255

hasm> Every few minutes windbindd posts an error message like: hasm> winbindd: ../source3/libads/ldap.c:552(ads_find_dc) hasm> winbindd: ads_find_dc: name resolution for realm 'XXX.CO' hasm> (domain 'XXX_01') failed: NT_STATUS_NO_LOGON_SERVERS hasm> How can I shut this thing up? I've also seen, not sure hasm> whether related, winbindd shooting up to

On 29.06.2015 17:06, Matthew Miller via Syslinux wrote: > > It actuallly looks from Adam's investigation that this isn't different > for this package. So, less than certainly. It looks like maybe more a > gcc 5 difference. > > > Regardless of whatever is actually causing this, here is the isolinux-debug.bin output: Booting from DVD/CD... ISOLINUX 6.03

On 30.06.2015 04:27, Gene Cumm wrote: > On Mon, Jun 29, 2015 at 6:20 PM, poma via Syslinux <syslinux at zytor.com> wrote: >> On 29.06.2015 17:06, Matthew Miller via Syslinux wrote: >> >>> >>> It actuallly looks from Adam's investigation that this isn't different >>> for this package. So, less than certainly. It looks like maybe more a

I run quad heads 2 graphic cards..They are NVidia chipset cards. Everything worked perfectly. Then I upgraded to FC23 and eveything goes wrong. Only 1 monitor comes up at half the resolution of the monitor. I tried a fresh install of FC23 with the same effect. I wish I could tell you more, but I have quite a bit going on right now and had to get my station running agin. The cards are GF 8600

https://bugs.freedesktop.org/show_bug.cgi?id=92922 Bug ID: 92922 Summary: Xorg random freeze Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau at

On 03/20, Sandro Bonazzola wrote: > Il 19/03/2015 15:46, George Dunlap ha scritto: > > On Thu, Mar 19, 2015 at 2:39 PM, Karanbir Singh <mail-lists at karan.org> wrote: > >> On 03/19/2015 12:23 PM, George Dunlap wrote: > >>> On Thu, Mar 19, 2015 at 12:20 PM, Sandro Bonazzola <sbonazzo at redhat.com> wrote: > >>>> Hi, > >>>>

I think I've hit the same problem that Predrag reported in http://comments.gmane.org/gmane.comp.emulators.libvirt.user/8825. With libvirt-1.3.2-1.fc23.x86_64 on Fedora 23, when I try uploading an image with vol-upload to a user libvirtd (qemu:///session): virsh vol-upload --pool default volume.qcow /path/to/file.qcow2 I am getting: error: Disconnected from qemu:///session due to

Hello, I use fedora-virt-preview repo and it recently updated to qemu-2.6.0-0.1.rc1.fc23.x86_64 and libvirt-1.3.3-1.fc23.x86_64. Now my arm VM does not start: Error starting domain: internal error: process exited while connecting to monitor: qemu-system-arm: -device pci-bridge,chassis_nr=2,id=pci,bus=pci,addr=0x1: Duplicate ID 'pci' for device I uploaded VM xml file to

I have an automatic process setup. It's still pretty new and obviously in need of better error handling because now I find myself in a bad state. I run snapshot-create-as across all my vms, then do zfs replication to the target backup system, then blockcommit everything. virsh snapshot-create-as --domain $vm snap --diskspec $DISK,file=$VMPREFIX/"$vm"-snap.qcow2 --disk-only --atomic

what is wasting that much RAM if vfs_fruit is enabled? had 4 OOM-killers today after not face a single one in the last 7 years and on a different machine i swa a smbd process eating up 6500 MB on a HP Microserver with 8 GB RAM due copy a 300 GB folder with a Apple client and even not release the memory after the operation was finished root 24301 1.9 22.3 1323692 903600 ? SN 12:29

"Richard W.M. Jones" <rjones@redhat.com> writes: > On Wed, Nov 16, 2016 at 09:06:29AM +0200, Michal Skrivanek wrote: >> >> > On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote: >> > >> > Hi, >> > >> > My last VM imported in 2 minutes. This one has been sitting for three >> > hours. I think this is