virt January 2013

virt@lists.fedoraproject.org

13 participants
13 discussions

Postfix + Courier-IMAP Error
by Sava Teodor 30 Jan '13

30 Jan '13

Hello, I am trying to set up a mail server using Postfix And Courier-IMAP with virtual users on a KVM-QEMU virtual machine. So far I managed to set up the server to send emails and receive emails but when trying to read the received messages I get the following error in /var/log/maillog: *mail pop3d: rename(./new/1359445367.V20I2c4000dM270929.mail.craiovadrilling,./cur/1359445367.V20I2c4000dM270929.mail.craiovadrilling:2,) failed: Invalid cross-device link * KVM host is Fedora 17 kernel 3.7.3 KVM guest is Fedora 17 kernel 3.7.3 Virtual users folder is set to a shared folder between KVM host and KVM guest. The same settings are working well if not using the virtual users folder on a shared folder between the two machines. Any hint for fixing this error? Best regards, Teodor Sava -- www.tedallcorp.com

2 4

What the heck are the guestfs-yaddayadda... virtual machines?
by Tom Horsley 28 Jan '13

28 Jan '13

If I run virt-manager on fedora 18, I see random instances of virtual machines named guestfs-something pop up for a second, then go away. Where the heck do they come from and why is it happening?

3 13

Has something happened to virtio cache modes?
by Tom Horsley 28 Jan '13

28 Jan '13

Back around fedora 16 I tried all the different virtio cache modes and experimentally discovered that cache=none was nearly infinitely faster than cache=default and cache=writeback was even a little faster than cache=none. So I set all my VMs to cache=writeback. I've been copying my virtual machine defs to each new fedora since then, but now it seems to be dog slow with disk IO again. I'm planning to experiment with different settings again, but I have to wait for my Windows XP virtual machine to finish doing a windows update which may take all night at the rate it is writing to disk :-(. Just thought I'd ask if there is some known difference in the virtio modes in fedora 18?

6 6

virt preview for F18?
by James Cassell 27 Jan '13

27 Jan '13

Hello, Are there plans to have a fedora-virt-preview repo for Fedora 18? I recently upgraded to F18, and my libvirt packages are version 1.0.1-2.fc17 from F17 virt-preview. The version in F18 is 0.10.2.2-3.fc18. Would it be best for me to just distro-sync the libvirt packages? Thanks! -- James Cassell

2 2

virtio-scsi with libvirt
by Ian Pilcher 25 Jan '13

25 Jan '13

Can anyone point me to an example of using libvirt XML to create a virtio-scsi disk? I haven't been able to find anything anywhere. Thanks! -- ======================================================================== Ian Pilcher arequipeno(a)gmail.com Sometimes there's nothing left to do but crash and burn...or die trying. ========================================================================

3 4

Re: [fedora-virt] libxl and libvirt in Fedora (rawhide)
by M A Young 23 Jan '13

23 Jan '13

On Tue, 22 Jan 2013, Jim Fehlig wrote: > For those not following in the bug, the libxl driver executes > '/usr/sbin/xend status' and refuses to load it xend is running. The > problem here is that the status check causes xend to start! I can't > reproduce the issue, so perhaps it is specific to the fedora packages. It is specific to the Fedora package. I traced it to the xen-initscript.patch file in the Fedora source. From xen-3.1.0-2.fc8 onwards Fedora xend ignores the option passed to it and just does a start. It was from before I started doing things on the package, but idea seems to have been to strip out functions like stop, reload etc. and do them directly in the init script. I don't think it is worth changing this much, but I think I will put back the status option to keep libvirt happy. Michael Young

2 1

Re: [fedora-virt] libxl and libvirt in Fedora (rawhide)
by Dario Faggioli 22 Jan '13

22 Jan '13

On Mon, 2013-01-21 at 17:55 -0700, Jim Fehlig wrote: > > I'm not even sure whether xend is running or not! :-( As I wrote there, > > even when I only see the xend status check, I have xm working, which > > shouldn't happen without a proper xend running, right? > > > > For those not following in the bug, the libxl driver executes > '/usr/sbin/xend status' and refuses to load it xend is running. The > problem here is that the status check causes xend to start! > Ok, that sounds strange, but it is also the only reasonable explanation. I'll try to have a look and confirm this > I can't > reproduce the issue, so perhaps it is specific to the fedora packages. > I guess it can well be. I'll investigate this and report back to both the list and the bug. > > Moreover, independently from whether I install the package or not, or > > whether I kill/start xend manually, it looks indeed like the libxl > > driver is not able to load itself. > > > > Since checking xend status starts the service and returns that it is > running, the driver won't load :). > Yep, now it makes sense. :-) Thanks a lot for your time and Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

1 0

No mouse?
by Tom Horsley 19 Jan '13

19 Jan '13

I just tried to start a Windows XP kvm under fedora 18 and have no mouse. I could swear I saw something about spice and mouse problems recently, but I can't find it. This VM works fine under fedora 17. I have it configured to use spice. Do I need newer drivers inside the VM or something? I just copied the xml file and pointed to the same image that f17 is running. Here's the log, don't know what all the internal buf is not available messages are about, I don't have anything like that in the log on fedora 17. 2013-01-18 23:05:56.662+0000: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name hog1 -S -M pc-0.14 -enable-kvm -m 1024 -smp 2,sockets=2,cores=1,threads=1 -uuid 72c25613-ec08-08a4-de48-a4432404fd91 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/hog1.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x8 -drive file=/zooty/images/hog1.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/zooty/images/swap-hog1.img,if=none,id=drive-virtio-disk1,format=raw,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk1,id=virtio-disk1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device id e-cd,bus =ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=54:52:00:66:58:ed,bus=pci.0,addr=0x5 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 char device redirected to /dev/pts/1 main_channel_link: add main channel client main_channel_handle_parsed: net test: latency 0.346000 ms, bitrate 21113402061 bps (20135.309278 Mbps) red_dispatcher_set_cursor_peer: inputs_connect: inputs channel client create main_channel_handle_parsed: agent start __spice_char_device_write_buffer_get: internal buf is not available __spice_char_device_write_buffer_get: internal buf is not available __spice_char_device_write_buffer_get: internal buf is not available __spice_char_device_write_buffer_get: internal buf is not available __spice_char_device_write_buffer_get: internal buf is not available __spice_char_device_write_buffer_get: internal buf is not available __spice_char_device_write_buffer_get: internal buf is not available __spice_char_device_write_buffer_get: internal buf is not available __spice_char_device_write_buffer_get: internal buf is not available __spice_char_device_write_buffer_get: internal buf is not available qemu: terminating on signal 15 from pid 5012 2013-01-18 23:09:21.508+0000: shutting down

2 2

Re: [fedora-virt] libxl and libvirt in Fedora (rawhide)
by Dario Faggioli 18 Jan '13

18 Jan '13

On Thu, 2013-01-17 at 09:00 -0700, Jim Fehlig wrote: > Dario Faggioli wrote: > > Hi Jim, > > > > I'm having some problems with the libvirt libxl driver you're working > > on. More specifically, it does not seem to be working for me, at least > > not in the form in which it comes out of the related Fedora package. > > > > If/When you have a minute, would it be possible to you to have a look > > here: > > https://bugzilla.redhat.com/show_bug.cgi?id=893699 > > https://bugzilla.redhat.com/show_bug.cgi?id=893699#c10 ? > > > > Thanks for the bug ref, I've made a comment there. > Thanks. I replied myself, trying to provide some more information about what's going on... > As mentioned in the bug, the libxl driver will not load if xend is > running. It appears xend is not running on your system, so hopefully > there is something in your libvirtd logs telling why the driver did not > load. > I'm not even sure whether xend is running or not! :-( As I wrote there, even when I only see the xend status check, I have xm working, which shouldn't happen without a proper xend running, right? Moreover, independently from whether I install the package or not, or whether I kill/start xend manually, it looks indeed like the libxl driver is not able to load itself. Where should I look for the libvirtd logs you're mentioning? I've checked in /var/log/libvirt/* and in /var/log/messages, without finding anything interesting. Should I look somewhere else? Should I pass additional parameter to any of the involved components? Thanks again and Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

1 0

libxl and libvirt in Fedora (rawhide)
by Dario Faggioli 17 Jan '13

17 Jan '13

Hi Jim, I'm having some problems with the libvirt libxl driver you're working on. More specifically, it does not seem to be working for me, at least not in the form in which it comes out of the related Fedora package. If/When you have a minute, would it be possible to you to have a look here: https://bugzilla.redhat.com/show_bug.cgi?id=893699 https://bugzilla.redhat.com/show_bug.cgi?id=893699#c10 ? Even just knowing whether it is me that am doing something wrong, or from where to start looking for the issue would be a great help. :-) Any further information you (or anyone) need, or any other setup you (or anyone) think it would be worthwhile to test, just tell me, I'll do my best to comply. Thanks and Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt January 2013