xen 4.2 and libvirt
by M A Young
I would like to update the xen version on rawhide and probably also Fedora
18 to xen 4.2.0 , however libvirt links against some xen libraries whose
versions have changed in xen 4.2 and when I looked a few months ago it
seemed that libvirt didn't support the newer library versions.
Does anyone know what the current support status of libvirt for xen 4.2
is, and what work might be going on (if necessary) to add it?
Michael Young
10 years, 10 months
Fedora 18 Virt Test Day is Thurs Nov 1, we need you!
by Cole Robinson
Hey all,
The Fedora 18 Virt Test Day is this Thursday, November 1st. That's two days
away! The test day landing page is here:
https://fedoraproject.org/wiki/Test_Day:2012-11-01_Virtualization
If you're interested in trying out some new virt functionality, we've got
step by step instructions for:
* Using snapshots to backup disk images of a live VM with no VM downtime
* Assigning a physical USB3 device to your VM
* Assign a local USB device to your VM, even if the VM is on a remote machine!
* Setting disk IO bandwidth limits on your VM
* Suspend and Hibernate your VMs
* Enabling the PV EOI performance optimization for your VMs
* Using kernel syscall filters (seccomp) to further secure your host
against VM exploits (currently busted but we are working on a fix)
Of course, maybe you don't care about new features. We still need you! The
test day is the perfect time to make sure your virt workflow is working fine
on Fedora 18, as there will be several developers on hand to answer any
questions, help with debugging, provide patches, etc. No requirement to run
through test cases on the wiki, just show up and let us know what works (or
breaks).
And to be clear, while it is greatly preferred that you have a physical
machine running Fedora 18, participating in the test day does NOT require
it: you can test the latest virt bits on Fedora 17 courtesy of the
virt-preview repo. For more details, as well as easy instructions on updating
to Fedora 18, see:
https://fedoraproject.org/wiki/Test_Day:2012-11-01_Virtualization#What.27...
If you plan on showing up to the test day, add your name to the participant
list on the wiki, and on thursday, pop into #fedora-test-day on freenode
and give us a shout!
Thanks,
Cole
10 years, 10 months
[Fwd: Re: xen 4.2 and libvirt]
by Dario Faggioli
Cc-ing the correct Fedora Xen mailing list...
-------- Forwarded Message --------
From: Dario Faggioli <>
To: M A Young <>
Cc: Cole Robinson <>, ...
Subject: Re: [fedora-virt] xen 4.2 and libvirt
Date: Tue, 30 Oct 2012 12:14:09 +0100
On Thu, 2012-10-25 at 23:47 +0100, M A Young wrote:
> On Thu, 25 Oct 2012, Cole Robinson wrote:
> > Thanks Michael, I've pushed a new libvirt build to rawhide.
>
> Thanks for that. I think I will leave it a few days in case any problems
> emerge, then update F18 to 4.2 early next week, if that is okay for you.
>
Ok, so here's what I'm getting this morning, when 'yum update' tries to
update Xen on my Fedora 18 beta to 4.2:
# sudo yum update
Loaded plugins: langpacks, presto, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package xen.x86_64 0:4.1.3-4.fc18 will be updated
---> Package xen.x86_64 0:4.2.0-3.fc18 will be an update
---> Package xen-hypervisor.x86_64 0:4.1.3-4.fc18 will be updated
---> Package xen-hypervisor.x86_64 0:4.2.0-3.fc18 will be an update
---> Package xen-libs.x86_64 0:4.1.3-4.fc18 will be updated
--> Processing Dependency: libxenctrl.so.4.0()(64bit) for package: libvirt-daemon-driver-libxl-0.10.2.1-1.fc18.x86_64
--> Processing Dependency: libxenguest.so.4.0()(64bit) for package: libvirt-daemon-driver-libxl-0.10.2.1-1.fc18.x86_64
--> Processing Dependency: libxenlight.so.1.0()(64bit) for package: libvirt-daemon-driver-libxl-0.10.2.1-1.fc18.x86_64
---> Package xen-libs.x86_64 0:4.2.0-3.fc18 will be an update
---> Package xen-licenses.x86_64 0:4.1.3-4.fc18 will be updated
---> Package xen-licenses.x86_64 0:4.2.0-3.fc18 will be an update
---> Package xen-runtime.x86_64 0:4.1.3-4.fc18 will be updated
---> Package xen-runtime.x86_64 0:4.2.0-3.fc18 will be an update
--> Finished Dependency Resolution
Error: Package: libvirt-daemon-driver-libxl-0.10.2.1-1.fc18.x86_64 (@updates-testing)
Requires: libxenlight.so.1.0()(64bit)
Removing: xen-libs-4.1.3-4.fc18.x86_64 (@fedora)
libxenlight.so.1.0()(64bit)
Updated By: xen-libs-4.2.0-3.fc18.x86_64 (updates-testing)
Not found
Error: Package: libvirt-daemon-driver-libxl-0.10.2.1-1.fc18.x86_64 (@updates-testing)
Requires: libxenctrl.so.4.0()(64bit)
Removing: xen-libs-4.1.3-4.fc18.x86_64 (@fedora)
libxenctrl.so.4.0()(64bit)
Updated By: xen-libs-4.2.0-3.fc18.x86_64 (updates-testing)
Not found
Error: Package: libvirt-daemon-driver-libxl-0.10.2.1-1.fc18.x86_64 (@updates-testing)
Requires: libxenguest.so.4.0()(64bit)
Removing: xen-libs-4.1.3-4.fc18.x86_64 (@fedora)
libxenguest.so.4.0()(64bit)
Updated By: xen-libs-4.2.0-3.fc18.x86_64 (updates-testing)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
I installed this yesterday, and I installed Xen and libvirt via the
following:
# yum install xen libvirt-daemon-xen
Also, I noticed that the libvirt-daemon-driver-libxl got installed
(although I thought it shouldn't and wasn't :-O):
# rpm -qa | grep libxl
libvirt-daemon-driver-libxl-0.10.2.1-1.fc18.x86_64
Is that correct and aligned with the discussion we were having since now
(i.e., going for Xen 4.2 but _without_ the libxl driver in libvirt)? Am
I missing something or doing something wrong?
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)
--
<<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)
10 years, 10 months
QCOW2 vs QROW2 Disks
by Jorge Fábregas
Hi there,
I'm just curious: Where does the "Copy on Write" (from QCOW) comes
from? Everything I've been reading regarding how snapshots work with
QEMU points to a "redirect on write" approach. Or is the COW part
related to some other internal mechanism (not related to snapshots)?
Thanks in advance,
Jorge
10 years, 10 months
General Virtualization Questions
by Jorge Fábregas
Hi,
I'm new to KVM (just got a CPU with VT-x support) so now I can finally
use QEMU/KVM properly. I'm using Fedora 14. Yes I know it's not
supported; I promise I won't ask for issues I'll encounter until I
upgrade to F18 when it comes out :) (and then I'll face GNOME 3...)
Right now I've been playing with a Windows XP VM and so far so good; I
love the performance. Since my previous experience was with VMware
Workstation/Player & VirtualBox I've got some general questions
regarding virtualization (from the point of view of a desktop user):
1) Is there an equivalent of "VMware Tools"/"Guest Additions"? I noticed
there's an ISO with the paravirtualized drivers (VirtIO) but I'm
wondering: If you're not using any of those paravirtualized drivers: is
there anything to be installed on the guest in order to integrate it
more with the host?
2) What's the standard method you guys use to transfer files between the
guest & the host? Is drag & drop supported with Spice these days? Do
you recreate the "Shared Folder" thing (like VirtualBox) using Samba on
the host? or do you loop mount the VM disk image when the guest is down?
3) Is sound working "out of the box" these days (F17 & F18 beta?). I
got it working following a website (I had to put SElinux in permissive
mode, had to change the uid of the qemu process to be that of my user
and enabled vnc_allow_host_audio in qemu.conf).
4) Is SPICE the default remote-display system used these days (F17 and
forward)? Since I'll be using QEMU/KVM on my desktop system (I'll run
all my VMs locally), is there a noticeable difference between VNC and
SPICE when you run these VMs locally?
Thanks in advance!
Jorge
10 years, 11 months
No networking?
by Tom Horsley
I'm on fedora 17 and I just started trying to install a
fedora 17 virtual machine where I can screw around with
stuff without blowing up my actual machine.
I get to step 5 of 5 in the New VM wizard of virt
manager and it tells me "No networking" and has
a little warning triangle icon.
Whyfor? All my existing virtual machines use one
of the two bridge devices I have, but it doesn't
seem to see the bridges?
It used to see them in earlier versions of virt-manager.
Is this a bug or some kind of new feature that
requires me to go to infinite pains to make
virt-manager aware of the bridges for my
convenience?
I'll try to do the install and manually tweak the
xml later to see if I can add the bridge...
10 years, 11 months
No network with Guests F17_Host fully updated, No F18 preview.
by Frank Murphy
NM_Controlled=0 for host-box eth0, eth1.
# service network restart
Restarting network (via systemctl): [ OK ]
[root@testvm ~]# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.525400211c46 yes virbr0-nic
vnet0
vnet1
default.xml
<network>
<name>default</name>
<uuid>6fc62803-d768-4f28-9aaf-6c1798d97dff</uuid>
<bridge name="virbr0" />
<forward/>
<ip address="192.168.1.1" netmask="255.255.255.0">
<dhcp>
<range start="192.168.1.10" end="192.168.1.20" />
</dhcp>
</ip>
</network>
There seemt to be no connection between,
the virt-network and the physical though:
nat --> eth1
is in virt-manager.
The two running guests F17+testing,
are set up with NIC: default nat to eth1
--
Regards,
Frank
"Jack of all, fubars"
10 years, 11 months
remote-viewer and resize of window
by Gianluca Cecchi
Hello,
in my F17 system with virt-viewer-0.5.3-1.fc17.x86_64 I notice that at
a certain point in updates I began to get the option
Automatically resize
enabled by default so that, as I don't like it, I have to disable each time.
Is there any option or config file to set disable by default?
Thanks,
Gianluca
10 years, 11 months
F17 Host, FedoraX guests no network
by Frank Murphy
F17 host full updated + updatess-testing.
No F18-Preview.
The only work I had to do was disable eth0 on the host(bios)
and bump everything to eth1
Host:
ifconfig
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.6 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::222:3fff:fef1:f2d8 prefixlen 64 scopeid 0x20<link>
ether 00:22:3f:f1:f2:d8 txqueuelen 1000 (Ethernet)
RX packets 371493 bytes 513854679 (490.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 189705 bytes 23501474 (22.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 5268 bytes 17202695 (16.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5268 bytes 17202695 (16.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255
ether 52:54:00:62:f8:20 txqueuelen 0 (Ethernet)
RX packets 117 bytes 11815 (11.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20 bytes 2613 (2.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0-nic: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:62:f8:20 txqueuelen 500 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Default.xml :
<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made
using:
virsh net-edit default
or other application using the libvirt API.
-->
<network>
<name>default</name>
<uuid>b3db8312-5eb8-fd3e-80bb-f560c08a4e16</uuid>
<forward dev='eth1' mode='nat'>
<interface dev='eth1'/>
</forward>
<bridge name='virbr0' stp='on' delay='0' />
<mac address='52:54:00:62:F8:20'/>
<ip address='192.168.1.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.1.200' end='192.168.1.220' />
</dhcp>
</ip>
</network>
Attachment is screencap of F17-Guest ifconfig
--
Regards,
Frank
"Jack of all, fubars"
10 years, 11 months
