Re: [Fedora-xen] Peculiar errors with libvirt/virt-manager/xen in F18
by Marco Guazzone
Hello,
I followed this thread on the list archives.
I've just installed Fedora 18 and now I want to run the VM images I
previously run on Fedora 16 (xen 4.1 + libvirt).
So, I would like to know what is the current status of xen/libvirt
integration.
>From the xen wiki (http://wiki.xen.org/wiki/Fedora_Host_Installation), it
seems that it is still unsafe to use libvirt with the xl toolstack.
But the last update is on Febraury 2013. So some time is passed.
Is it still true?
Furthermore, do you know what changes one has to do to a libvirt VM
configuration XML file that was used to define VM for the xend toolstack?
Thank you very much for the help!
Best,
-- Marco
10 years, 5 months
Dom0 seems to be not running
by Mustafa Hassan
Hi all
I am a very newbie to XEN. I have managed to install it as described here "
http://wiki.xen.org/wiki/Fedora_Host_Installation"
However, now when I run "Virt_Manager"
1- It does not show a running Dom0
2- I am not able to create a guest. It says "Error polling connection
'xen:///': internal error client socket is closed"
I have no idea, however I think Dom0 is not running. I have booted into
"Fedora with XEN Hypervisor 2.2"
Here is the output from "xl list"
=================================================================
[root@localhost xen-tools-4.3.1]# xl list
Name ID Mem VCPUs State Time(s)
(null) 0 930 2
r----- 333.5
[root@localhost xen-tools-4.3.1]#
=================================================================
and output of "xl info"
================================================================
[root@localhost xen-tools-4.3.1]# xl info
host : localhost.localdomain
release : 3.6.10-4.fc18.i686.PAE
version : #1 SMP Tue Dec 11 18:15:08 UTC 2012
machine : i686
nr_cpus : 2
max_cpu_id : 3
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2333
hw_caps :
bfebfbff:20100000:00000000:00000940:0000e3fd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 1011
free_memory : 62
sharing_freed_memory : 0
sharing_used_memory : 0
free_cpus : 0
xen_major : 4
xen_minor : 2
xen_extra : .1
xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xf5800000
xen_changeset : unavailable
xen_commandline : placeholder
cc_compiler : gcc (GCC) 4.7.2 20121109 (Red Hat 4.7.2-8)
cc_compile_by : mockbuild
cc_compile_domain : [unknown]
cc_compile_date : Thu Apr 4 22:40:34 UTC 2013
xend_config_format : 4
[root@localhost xen-tools-4.3.1]#
================================================================
Please help!
--
With Best Regards
MusT
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
UNIX is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
10 years, 5 months
pci passthrough
by Mike Wright
Hi all,
I need help debugging this situation.
Running xen-4.2.1 with kernel 3.8.5-201.fc18.x86_64.
I have successfully passed an on-board audio adapter to a VM running f14
but it does not work.
When f14 runs on bare metal it has full audio capability.
"lspci" on VM-f14 correctly shows:
00:00.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) (rev 40)
"lsmod | grep snd" shows:
snd_hda_codec_realtek 322852 1
snd_hda_intel 23945 2
snd_hda_codec 83791 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 6288 1 snd_hda_codec
snd_seq 52985 0
snd_seq_device 5969 1 snd_seq
snd_pcm 79886 2 snd_hda_intel,snd_hda_codec
snd_timer 19363 2 snd_seq,snd_pcm
snd 63685 12
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
soundcore 6329 1 snd
snd_page_alloc 7359 2 snd_hda_intel,snd_pcm
All the pieces seem to be there.
However, "System->Preferences->Sound->Hardware" is empty and
"System->Preferences->Sound->Output" shows only "Dummy Output, Stereo".
Anybody know how to debug this?
Right now I have to use Domain0 for multimedia, which seems to pervert
the whole concept of keeping Domain0 away from general users.
Please, Thanks, All of the above :)
Mike Wright
10 years, 5 months
dependency problem with my (first) RPM
by Dario Faggioli
Hello Everyone,
I created an (my first!) RPM of this software
http://www.xen-tools.org/software/xen-tools/ but I'm having some issues
when trying to install it.
Before anyone ask, yes, the long term plan is to follow all the usual
step to get the package officially accepted in Fedora, but I'd like to
have it "working" before starting to do that. :-)
So, xen-tools is just a collection of perl scripts, but having the
package I'm making depend from perl is driving me nuts! :-O Spec file is
attached (I've run it through rpmlint, and I know it have some issues,
but still...) and here's what I get when I tr to install the result of
`rpmbuild -ba xen-tools.spec':
# yum install ../RPMS/noarch/xen-tools-4.3.1-1.fc18.noarch.rpm
Loaded plugins: langpacks, presto, refresh-packagekit
Examining ../RPMS/noarch/xen-tools-4.3.1-1.fc18.noarch.rpm: xen-tools-4.3.1-1.fc18.noarch
Marking ../RPMS/noarch/xen-tools-4.3.1-1.fc18.noarch.rpm to be installed
Resolving Dependencies
--> Running transaction check
...
---> Package xen-tools.noarch 0:4.3.1-1.fc18 will be installed
--> Processing Dependency: perl(any) for package: xen-tools-4.3.1-1.fc18.noarch
--> Processing Dependency: perl(any) for package: xen-tools-4.3.1-1.fc18.noarch
--> Finished Dependency Resolution
Error: Package: xen-tools-4.3.1-1.fc18.noarch (/xen-tools-4.3.1-1.fc18.noarch)
Requires: perl(any)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
I googled for this quite a bit, but I don't seem to be able to find
anything explaining how to make that "Requires: perl(any)" go
away... :-(
Any ideas?
Thanks a lot and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
10 years, 5 months
