similar to: virsh vs. xm, and questions about different distributions of Xen

HVM = fully virtualized. The question is, why are you using fully virtualized domUs? Why not paravirtualized (PV)? >>> On 2008/06/16 at 16:07, Rudi Ahlers <Rudi@SoftDux.com> wrote: Itamar - IspBrasil wrote: > why you''re using hvm ? its slow > > > > Rudi Ahlers wrote: >> Hi all >> >> I''m running CentOS 5.1 x64 + Xen 3.0 & I

I am getting the following error with "xm list" on a x86_64 SLES10 Beta system running changeset 9435:11fee62328cc. I am able to bring up DomUs and I am able to do "xm info" without issues. But I am seeing similar "OverflowError: int exceeds XML-RPC limits" with "xm shutdown" and "xm destroy". My python version is 2.4.2. Any way I can get around

My dom0 is uing Centos 5.2 x64. I have just upgraded Xen from 3.3.0 to 3.3.1. After upgraded, I find that I cannot hotplug additional vcpu anymore. I have a domU "linux1" which is a paravirtualized vm with centos 5.2. I try to "xm vcpu-set linux1 4", it does not have any error message, but those vcpu cannot be displayed. I also tried to add vcpu using "virsh setvcpus

On Tue, Dec 16, 2014 at 10:29:53PM +0200, Pasi K?rkk?inen wrote: > > > > * xend is now disabled by default. You can enable it by running > > chkconfig. xend has been removed from the tree entirely in Xen 4.5, > > so this should (hopefully) serve as a "wake-up-call" for people to > > begin the transition over to xend. > > > > * A lot have

I''m creating a new domU using ''virsh create <xmlfile>'' without specifying the MAC address within the XML file, under the assumption that the dom0 or hypervisor generates the MAC address for me. Next I''d like to get the MAC address that was assigned to this new domU, and I don''t see a way to get that information from the command line via virsh

Hello everybody! I´d like to know where "xm top" gets its information from. I want to get those informations (cpu-load, mem etc. from the domUs) and display them with php in a browser. So are the informations stored and updated in a textfile or something like that? Can anybody help me with this? Regards Alexandros _______________________________________________ Xen-users mailing

I installed xen on top of Cent OS 5.3 64bit OS with gitco rpm sources. Everything works fine except that I can''t run 64bit pv guest with virsh command. With xm commands I can load the same guest. 32bit pv guest, 32 bit and 64bit hvm works fine with both virsh and xm command. Has anyon have any idea? any help will be largely appreciated. **This is dumpxml for 64bit configuration* **

Hello everyone - I am stumped ... Does anyone have suggestions on how to proceed? Is there a way to get what I want? The environment: CentOS 7.0 with latest patches. The goal: I want logwatch to include a report on the status of kvm virtual computers. The problem: When run from anacron, SELinux denies permission for the virsh utility. Here is a portion of the logwatch output:

hi all, I can''t create domU with the virt-manager, but I''d like to use it anyway. If I start domUs from command line (xm create ~) I can see them in the virt-manager, but they''re gone after I pause them or stop them. I assume that the virt-manager has some place where it saves config files for domUs, on linux it is usually /etc/xen/vm. I went in some obvious places

I''m running Xen on Nexenta Core, and I haven''t yet figured out how to control which DomU''s are started with svcadm enable svc:/system/xvm/domains:default. virsh doesn''t seem to be available with Nexenta Core, so I''d rather edit the configuration files by hand. However, I''ve found neither OpenSolaris or Nexenta documentation on how this is

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for

Hi, I have some problems to configure the xen I''ve installed (3.3.1). The computer is a Intel Core 2 Duo, I''m using Ubuntu 8.10 and have linux in my dom0 and winxp pro in my domU. I have two cores and I''d like to set the affinity of dom0 to cpu0 and domU to cpu1 but I haven''t find the way of making this permanent. I''ve set cpus=1 in the domU config

Hi, i''m running a two dom0 nodes cluster for HA, and xen domUs running on top, currently it handles 5 domUs. The issue is that there''s a domU that can only run on one node, it''s not possible to start it on the other one. I get a ''b'' status and can''t access the console. Other domUs can start in either node and I can access their console without

I see that "xl list" shows a domain waiting idly for console input as "r", whereas "xm list" shows the same domain as "b". I also see that the State field for "xl list" contains only three characters (e.g. "r--"), whereas "xm list" shows six (e.g. "-b----"). Is this expected/intended (e.g. "r" in xm list

Hello I have a production server, on which I had to install a new OS. Unfortunately, xen is not willing to run any domUs! Any help would be most highly appreciated. My problem is essentially that described in this post, to which there was no answer at the time: <http://lists.xensource.com/archives/html/xen-devel/2009-06/msg01147.html> Symptoms: When trying to xm create a previously

On some production servers with dom0 kernel 2.6.32 pvops and xen 4.0 and domus mainly windows with gplpv I noticed a strange cpu usage by the dom0 mainly with the use of a single cpu, for example this take from one server: xm vcpu-list Name ID VCPU CPU State Time(s) CPU Affinity ... Domain-0 0 0 3 -b- 1043377.5 any cpu

I have followed a combination of instructions from this post and have been able to get an Ubuntu paravirtualized instance running under snv_96. Is there a way to "list" the fact that it is paravirtualized? For example, xm list, virsh list, etc. thanks -- This message posted from opensolaris.org

Hello everybody, I can successfully boot up my dom0, but I can''t create domUs. If I try to create one I get the following output from xm: root@revo:~# xm create /etc/xen/debian.cfg Using config file "/etc/xen/debian.cfg". Error: (22, ''Invalid argument'') There''s no more interesting information in syslog. Any ideas what is the problem? -- Regards,

Hi all, I can''t find any good talk about this subject and would like some insights and advices on the cache side in xen. I discovered that a domO power outage can lead to a severe filesystem corruption of the domUs. The domO is a dual disk dell server with a PERC controler in writethrough cache mode, the disk cache is disabled, the scheduler in the domO/domU is NOOP, the domO is holding