Re: [libvirt-users] CPU Model detection with virsh capabilities
by Jiri Denemark
On Mon, Sep 12, 2011 at 16:33:53 +0200, Olivier BONHOMME wrote:
> Hello,
>
> Thanks for your answer. My virsh capabilities is the following :
>
> <cpu>
> <arch>x86_64</arch>
> <model>pentium3</model>
> <vendor>Intel</vendor>
> <topology sockets='1' cores='4' threads='1'/>
> <feature name='lahf_lm'/>
> <feature name='lm'/>
> <feature name='syscall'/>
> <feature name='sse4.1'/>
> <feature name='dca'/>
> <feature name='xtpr'/>
> <feature name='cx16'/>
> <feature name='ssse3'/>
> <feature name='tm2'/>
> <feature name='est'/>
> <feature name='vmx'/>
> <feature name='ds_cpl'/>
> <feature name='monitor'/>
> <feature name='pni'/>
> <feature name='pbe'/>
> <feature name='tm'/>
> <feature name='ht'/>
> <feature name='ss'/>
> <feature name='sse2'/>
> <feature name='acpi'/>
> <feature name='ds'/>
> <feature name='clflush'/>
> <feature name='apic'/>
> </cpu>
>
> About what you say, I totally agree. It's just I am very surprised that
> an Intel Xeon E5430 is detected just as a pentium3
That's because your CPU doesn't support nx feature, which is included in all
models better than pentium3.
Jirka
13 years, 2 months
Re: [libvirt-users] [libvirt] how did libvirt manage Virtual Network?
by Laine Stump
(This seems more appropriate for the libvirt-users mailing list)
On 09/08/2011 10:16 PM, Wayne Xia wrote:
> Working at the network management, I am a bit confused about the
> VLAN model in libvirt.
>
> in the xml definition, there is a section as following:
>
> <devices>
> <interface type='network'>
> <source network='default'/>
> </interface>
> ...
> <interface type='network'>
> <source network='default' portgroup='engineering'/>
> <target dev='vnet7'/>
> <mac address="00:11:22:33:44:55"/>
> <virtualport type='802.1Qbg'>
> <parameters managerid='11' typeid='1193047' typeidversion='2'
> instanceid='09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'/>
> </virtualport>
>
> </interface>
> </devices>
>
>
> What is the really meaning of its related parameters of
> "virtualport"? I want to discover informations such as VLAN id,
> the switch type( software switch or hardware switch), connecting
> relationship, but from the xml I can only found "managerid". I am not
> sure how to map these xml information to those I needed, could I
> consider managerid as VLAN id, and a portgroup as a specified VLAN group?
> By the way to use virtualport, what components should I install on
> Linux?
<virtualport> is used only when configuring guests that connect directly
to a VEPA or VNLINK (i.e. 802.1Q) capable switch. Unless you have one of
these switches, you will not use it. If you do have one of these
switches, you will also have information included with them that
explains the meaning of the virtualport parameters and how they are used
(they're opaque to libvirt - it just passes them on to the switch
without assigning any meaning to them).
portgroup is a tag used to select certain bits of config out of
<portgroup> sections in the <network> definition being used for the
interface. Currently the things that can be configured in the
<portgroup> sections are 1) <bandwidth> info, and 2) <virtualport>
parameters. Again, it has nothing to do with VLAN groups. <portgroup> is
very new, btw - it has only been in libvirt since 0.9.4, so if you're
using an older version don't expect it to do anything.
Down to the real basic question of which VLAN a particular guest is
using - that can either be determined by the guest itself, or if the
guest has no VLAN id setting, it could be determined by the
switch/bridge the guest is connected to; in other words, wherever it is
done, it's outside of libvirt (well, I guess if your platform has
support for the iface-* commands, you could define a bridge that uses a
vlan interface as its connection to the physical network - then traffic
from any guest connected to that bridge would end up going onto the
physical network with the given vlan id).
13 years, 2 months
Re: [libvirt-users] Graphical framebuffers confuse, XML format about spice
by Laine Stump
(please reply to the list rather than personal mail)
On 09/08/2011 11:23 PM, huachao yao wrote:
>
>
> 2011/9/9 Laine Stump <laine(a)laine.org <mailto:laine@laine.org>>
>
> On 09/07/2011 11:03 PM, huachao yao wrote:
>
> Hello, i want to start a guest OS in the server, and use spice
> to achieve graphical interaction with the guest OS. But when
> i config the XML file, i was confuse by spice .
> The graphic node is :
> <graphics type='spice' port='5990' ><listen type='address'
> address='127.0.0.1'/></graphics>
>
> but is has such error as below :
> libvir: QEMU error : internal error process exited while
> connecting to monitor: qemu-spice: -spice
> port=5990,addr=127.0.0.1,disable-ticketing: Invalid parameter
> 'addr'
> parse error: port=5990,addr=127.0.0.1,disable-ticketing
>
>
> Apparently your "qemu-spice" binary supports the -spice option,
> but doesn't support the addr option. That seems very strange. What
> is the origin of "qemu-spice", and what version does it display?
>
> The qemu-spice version is :
> version 0.13.50 (qemu-kvm-devel), copy-right 2003-2008
> and the host OS is Fedora 13 , x86_64
> I think that "qemu-spice" binary supports the -spice option, but
> doesn't support the addr option." is a good reason to explain to
> problem. But how can i get the latest qemu-spice ?
> It is suit fedora 13?
Where did the original "qemu-spice" come from? That's not an official
Fedora13 package, and in later versions of Fedora, spice support is
included in the standard qemu-kvm package. It sounds like you either
built qemu + a spice patch from source, or found a prebuilt package like
that somewhere.
I've only used the spice support that is integrated into the qemu-kvm
package of Fedora 14 and RHEL (the qemu-kvm in Fedora 13 is too old to
have spice support, and Fedora 13 is now officially out of support mode)
I would do one of these things:
1) try getting a source tarball for a more recent qemu-kvm release and
build/install that on your F13 machine.
2) upgrade to F14 or F15 (if you upgrade to F14, add the virt-preview
repo to your yum configuration (just copy
http://repos.fedorapeople.org/repos/jforbes/virt-preview/fedora-virt-prev...
into /etc/yum.repos.d)
3) Decide that you maybe don't *really* need spice support, but that the
VNC-based guest displays are adequate for your needs - this will work
with the stock qemu-kvm on F13 and is just fine for most uses.
13 years, 2 months
[libvirt-users] IPs of VMs on KVM
by PREETHI RAMESH
How can I find the IPs of the VMs using libvirt function? As of now, I'm
thinking of using Nmap to get the MAC address and the ARP it to get the IP.
Can someone please help me out?
13 years, 2 months
[libvirt-users] CPU Model detection with virsh capabilities
by Olivier BONHOMME
Hello everybody,
I am a new user discovering libvirt with KVM software. During my first
VM creation, I saw an issue with virsh that I can't understand.
I wanted to emulate another CPU than the classical qemu32 using virsh.
So I used the virsh capabilites command to detect how is detected my CPU
host which is an Intel Xeon E5410 and my problem is that this CPU is
detected only with the cpumodel "pentium3".
But if use the kvm -cpu ? command, it returns me the following
capabilities :
$ kvm -cpu ?
x86 qemu64
x86 phenom
x86 core2duo
x86 kvm64
x86 qemu32
x86 coreduo
x86 486
x86 pentium
x86 pentium2
x86 pentium3
x86 athlon
x86 n270
Moreover, if i decide to use the pentium3 cpumodel for my KVM VM, the
CentOS freeze during its loading.
My libvirt and kvm are the following on a Debian Squeeeze :
$ virsh version
Compiled against library: libvir 0.8.3
Using library: libvir 0.8.3
Using API: QEMU 0.8.3
Running hypervisor: QEMU 0.12.5
Does anybody already had the same issue or am I doing anything wrong ?
Thanks for your answers
Regards,
Olivier BONHOMME
13 years, 2 months
[libvirt-users] Graphical framebuffers confuse, XML format about spice
by huachao yao
Hello, i want to start a guest OS in the server, and use spice to achieve
graphical interaction with the guest OS. But when i config the XML file, i
was confuse by spice .
The graphic node is :
<graphics type='spice' port='5990' ><listen type='address'
address='127.0.0.1'/></graphics>
but is has such error as below :
libvir: QEMU error : internal error process exited while connecting to
monitor: qemu-spice: -spice port=5990,addr=127.0.0.1,disable-ticketing:
Invalid parameter 'addr'
parse error: port=5990,addr=127.0.0.1,disable-ticketing
What is the meaning of <listen type='address' address='*****'/>, If the
localhost IP is A and the spice-server IP is B. what should i set the listen
type ? to start the Domain and to achieve graphical interaction with the
guest OS.
13 years, 2 months
[libvirt-users] Libvirt xen snapshot support?
by Joshua Harlow
Hi all,
I was wondering if there was support for xen (not xenserver/xcp) for snapshotting.
I have seen various sites that say it doesn't (using domainsnapshot) but I wanted to verify with the source.
Thanks.
Josh
13 years, 2 months
[libvirt-users] Libvirt vm migration with xen 4.1.1
by Rogério Vinhal Nunes
Hello,
I am trying to migrate a virtual machine between two xen 4.1.1 hosts using
libvirt, but as I use this command:
virsh migrate --live vm102 xen+ssh://10.0.254.8
The following error happens:
error: POST operation failed: xend_post: error from xen daemon: (xend.err
"can't connect: [Errno -2] Name or service not known")
The live migration works fine using "xm --live migrate vm102 10.0.254.8", so
everything is correctly set up. Am I doing something wrong?
Xen = 4.1.1
Ubuntu = 10.04
virsh version =
Using library: libvir 0.8.8
Using API: Xen 3.0.1
Running hypervisor: Xen 4.1.0
13 years, 2 months
[libvirt-users] How to dedicate a NIC for VM traffic without assigning it an IP
by Albert Chin
I am testing out a new server with RHEL6 running KVM. We have a few
NICs on the server, one of which we would like to dedicate to network
traffic to/from the virtual guests. Is it possible to do this without
assigning an IP address to the NIC? We're currently doing something
like this with Vmware Server, HP's HPVM for HP-UX/IA, and IBM's
PowerVM for AIX.
--
albert chin (china(a)thewrittenword.com)
13 years, 2 months
[libvirt-users] Libvirt migration with Xen 4.1.1
by Rogério Vinhal Nunes
Hello,
I am trying to migrate a virtual machine between two xen 4.1.1 hosts using
libvirt, but as I use this command:
virsh migrate --live vm102 xen+ssh://10.0.254.8
The following error happens:
error: POST operation failed: xend_post: error from xen daemon: (xend.err
"can't connect: [Errno -2] Name or service not known")
The live migration works fine using "xm --live migrate vm102 10.0.254.8", so
everything is correctly set up. Am I doing something wrong?
Xen = 4.1.1
Ubuntu = 10.04
virsh version =
Using library: libvir 0.8.8
Using API: Xen 3.0.1
Running hypervisor: Xen 4.1.0
13 years, 2 months
