September 2010 - virt - Fedora Mailing-Lists

libvirt-0.8.3-2.fc14 - nwfilterxml2xmltest fails on Fedora/s390x

by Dan Horák

Hi, I have a problem with nwfilterxml2xmltest failing on Fedora/s390x ... TEST: nwfilterxml2xmltest !!!!!........................! 30 FAIL FAIL: nwfilterxml2xmltest ... Details from the build of an older libvirt-0.8.2-3.fc14 are available at http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=204650 but the build from f14 branch in dist-git have the same problem. Where should I look for the cause? Or let me know if you need an access on the s390x machine. Thanks, Dan

13 years, 7 months

1
1
0 / 0

Bad messages coming via XEN serial port

by Virgil

Does this mean anything? The system is still running. There is only one single domU running (Fedora13 32 bit HVM). multi.c:3470:d2 write to pagetable during event injection: cr2=0xf5f1efbf9cb many many more lines like this. Linux seanl64.xxxx 2.6.32.21-167.xendom0.fc12.x86_64 #1 SMP Fri Sep 3 21:46:55 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux xen-hypervisor-4.0.1-0.2.fc12.x86_64 kernel-devel-2.6.32.21-167.xendom0.fc12.x86_64 xen-debuginfo-4.0.1-0.2.fc12.x86_64 xen-4.0.1-0.2.fc12.x86_64 kernel-firmware-2.6.32.21-167.xendom0.fc12.noarch xen-runtime-4.0.1-0.2.fc12.x86_64 xen-doc-4.0.1-0.2.fc12.x86_64 kernel-headers-2.6.32.21-167.xendom0.fc12.x86_64 xen-devel-4.0.1-0.2.fc12.x86_64 xen-libs-4.0.1-0.2.fc12.x86_64 kernel-2.6.32.21-167.xendom0.fc12.x86_64 Cheers V

13 years, 7 months

1
0
0 / 0

Problen with VNC connection to HVM via Virtual Machine Manager

by Virgil

Hi List, Having an issue with HVM xen domU where I can see the screen whenever the virtual machine starts up by click Open from the popup menu. After disconnecting from its screen, a reconnect (via Open) always shows a bank black screen. I'm able to connect with the real VNC app (because that's how it's setup to overcome this) issue. However Virtual Machine Manager always sees a blank black screen via the inbuilt VNC no matter what I do (apart from restarting the domU). Anyone know about this? Same for WinXP, F10 etc. etc virtuals. Cheers V.

13 years, 7 months

1
0
0 / 0

Step-by-step tutorial: Installing Xen 4.0.1 rpms on Fedora 13 with pvops Linux 2.6.32.x dom0 kernel

by Pasi Kärkkäinen

Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS Hopefully this is helpful to someone! :) -- Pasi

13 years, 7 months

4
6
0 / 0

FYI: Major version rebase of libvirt in F12, F13 in updates-testing

by Daniel P. Berrange

Normally our policy is to avoid any major version rebases of libvirt in released Fedora products, and only cherry-pick patches. The exception to this policy is when we have security updates which are not practical to backport. This is such a time. Thus we are updating the libvirt in in Fedora 12 from 0.7.1 to 0.8.2 and Fedora 13 from 0.7.7 to 0.8.2, both matching rawhide. In general we expect the quality of 0.8.2 to be fairly high, since 0.8.2 was primarily accumulated bug fixes resulting from RHEL6 testing of the 0.8.1 release. None the less, if you are able to, please take time to test these two updates and report any regressions[1]: https://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc12 https://admin.fedoraproject.org/updates/libvirt-0.8.2-1.fc13 Regards, Daniel [1] There is an expected regression with certain uses of qcow2 disks as per the update notes. -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

13 years, 7 months

4
7
0 / 0

Anyone successfully run spice on fedora 14 alpha?

by Tom Horsley

I just submitted this bug (which may simply be due to me not knowing something I need to know and not a real bug :-). https://bugzilla.redhat.com/show_bug.cgi?id=630361 I just get an error when I try to run the spice client. To get the benefits of libvirt, I replaced the <emulator> name with a wrapper program that swaps the normal -vnc and -vga args for the spice args instead, but otherwise runs in a normal libvirt environment with all the voodoo libvirt provides for networking, etc. Is there maybe some additional libvirt supplied args that are incompatible with spice?

13 years, 7 months

2
1
0 / 0

F14: XP install fails on KVM

by sean darcy

I'm trying to install XP with virt-manager-0.8.5-1.fc14.noarch. XP setup gets to the point of copying the files to the .img. Then I get a quick flash that I think says something like VNC lost connection with hypervisor. If I reboot from the disk, I get "Error loading operating system". If I reboot from the CD, it tells me the .img file is corrupt and needs to be reformatted. Then I'm back to my original problem. Is this the right list for this problem? If not, where do I go? sean

13 years, 7 months

6
5
0 / 0

Re: [fedora-virt] F14: XP install fails on KVM

by sean darcy

On Thu, Sep 2, 2010 at 12:26 AM, sean darcy <seandarcy2(a)gmail.com> wrote: > On Wed, Sep 1, 2010 at 11:09 PM, sean darcy <seandarcy2(a)gmail.com> wrote: >> On Tue, Aug 31, 2010 at 8:41 AM, Cole Robinson <crobinso(a)redhat.com> wrote: >>> On 08/30/2010 10:53 PM, sean darcy wrote: >>>> I'm trying to install XP with virt-manager-0.8.5-1.fc14.noarch. XP >>>> setup gets to the point of copying the files to the .img. Then I get a >>>> quick flash that I think says something like VNC lost connection with >>>> hypervisor. >>>> >>>> If I reboot from the disk, I get "Error loading operating system". If >>>> I reboot from the CD, it tells me the .img file is corrupt and needs >>>> to be reformatted. Then I'm back to my original problem. >>>> >>> >>> If the VM spontaneously shuts down, something is crashing. Any error >>> messages in /var/log/libvirt/qemu/$VMNAME.log? >>> >> >> The only messages in /var/log/libvirt/qemu/XP.log that look like errors to me: >> >> grep failed XP.log >> qemu-kvm: block/raw.c:130: raw_aio_writev: Assertion >> `qiov->iov[i].iov_len >= 512' failed. >> qemu-kvm: block/raw.c:130: raw_aio_writev: Assertion >> `qiov->iov[i].iov_len >= 512' failed. >> qemu-kvm: block/raw.c:130: raw_aio_writev: Assertion >> `qiov->iov[i].iov_len >= 512' failed. >> qemu-kvm: block/raw.c:130: raw_aio_writev: Assertion >> `qiov->iov[i].iov_len >= 512' failed. >> qemu-kvm: block/raw.c:130: raw_aio_writev: Assertion >> `qiov->iov[i].iov_len >= 512' failed. >> qemu-kvm: block/raw.c:130: raw_aio_writev: Assertion >> `qiov->iov[i].iov_len >= 512' failed. >> qemu-kvm: block/raw.c:130: raw_aio_writev: Assertion >> `qiov->iov[i].iov_len >= 512' failed. >> qemu-kvm: block/raw.c:130: raw_aio_writev: Assertion >> `qiov->iov[i].iov_len >= 512' failed. >> >> sean >> > > Changed format of XP.img to qcow2. Now it works. Looks like a problem > with raw images. > > sean > This isn't a virt-manager issue. Should I report the failure with a raw image to some other list? sean

13 years, 7 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt September 2010