similar to: More than one drive on HVM

Hi. I'm testing a centos 5.4 xen PV guest on top of a centos 5.4 host. for some reason, the disk performance from the guest is awful. when I do an import , the io is fine for a while then climbs to 100% and stays there most of the time. at first I tougth it was because I was using file-backed disks, so deleted those and changed to LVM, but the situation did't improve. Here's an

Yesterday, I had a PV OpenSolaris DomU stop responding. I looked on my xen machine and it was in a paused state. I ended up destroying it and then doing xm create to bring it back up. It won''t boot, and I think PyGrub is hanging. Not sure how to resolve this, there aren''t any errors being presented in xen/xm itself. If I try ''xm create config.conf'' it just

Package: xen Version: 4.0.1-5.5 Severity: critical --- Please enter the report below this line. --- Hi! Since the update last weekind in stable/squeeze I'm experiencing problems with running Xen on amd64 and multiple domUs losing their network connection/VIFs. From http://blog.windfluechter.net/content/blog/2013/02/26/1597-xen-problems-vms-2632-5-xen-amd64 Unfortunately this update

After a few days, one of my DomU becomes unresponsive. Here''s the output of my DomU''s. root@xenII:/var/log/xen# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 7126 2 r----- 723932.0 redhat-sdsweb 11 4091 2 -b---- 92633.1 w2k8-AD

Am 2015-09-17 09:29, schrieb Pasi K?rkk?inen: > > Are you using nfs over UDP or TCP ? > TCP, but Network cant be the bottleneck, have tested it with iperf between bare metal/domU's and the nfs domU and it was perfectly fast... > > I don't think. > > > If you used NFS over UDP, try running it over TCP. no I use it over TCP... > > What does

Dear all, I have a reproducible issue with centos54 dom0 and debian lenny domU using pygrub. As far as I enter "shutdown -r now" in the running Debian Lenny DomU the whole system hangs. Keyboard is dead, network is dead and no more logging. Ending up in a hardware reset of the box. I was able to reproduce this 3 times. Restarting with xm reboot debian50 works without problems. Is there

I apologize if this is a little off-topic, but it does relate to Xen and using NPIV on Xen, so I think this is an appropriate forum for the question. I''ve recently begun using NPIV for a couple of Xen PV domUs rather than traditional disk passthrough. My reasons are primarily for performance - I''m hoping that NPIV has lower overhead and lower reliance on the resources of dom0

On Fri, Apr 26, 2019 at 11:25:13AM +0200, Christoph wrote: > > Hi > > libvirt 5.2.0 should support maxGrantFrames setting for xen (changelog). > I get ever an error if I use it in the config: Hi > <domain type='xen'> > <name>satan.chao5.int</name> > <uuid>f1f96b1c-fb75-4707-afb7-604d696d29cc</uuid> > <memory

I have a kickstart file created that works great for installing CentOS on PVM''s and now I want to use it for HVM''s as well. The problem is that when I attempt to run the install, it seems to ignore the kickstart and starts prompting me for all the things I already have specified in the kickstart. Any idea what I could be doing wrong? Here is the command im using to get things

Hi libvirt 5.2.0 should support maxGrantFrames setting for xen (changelog). I get ever an error if I use it in the config: <domain type='xen'> <name>satan.chao5.int</name> <uuid>f1f96b1c-fb75-4707-afb7-604d696d29cc</uuid> <memory unit='KiB'>3145728</memory> <currentMemory unit='KiB'>3145728</currentMemory>

Hi, I double checked the configuration with xm and the "w!" option seems to be configured :-( I also upgraded to build 123, but also no change in behaviour. Thus is this a RAC 11.2 problem or is there a general problem using zvols as as shared disks for xVM domains ? (device (vbd (protocol x86_64-abi) (uuid 048d282d-da4c-2e0b-b9f4-f3f4cc0811c7)

Hi, i tried to make a RAID5 Software Raid with 3 HDDs Disk /dev/xvdb: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xe86f85d6 Device Boot Start End Blocks Id System /dev/xvdb1 1 30401 244196001 fd Linux raid autodetect Disk /dev/xvdc: 250.0 GB,

Hi, I am using xen 3.1.0 on opensuse 10.3, for more details see below. When I try to start the third domU, then this will not work, I get the error: Error: Boot loader didn''t return any data! When I shutdown an other one, I can successfully start the machine that failed, see my log below. The xen configuration files are all similar to this one: name="FTP"

On 11/08/2014 05:41 AM, Ian Campbell wrote: > Please can you try running xl under valgrind, something similar to what > I described earlier should work. I guess it didn't find much.. # valgrind --leak-check=full xl cr -F /etc/xen/auto/asterisk_deb80.cfg ==6736== Memcheck, a memory error detector ==6736== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==6736== Using

Greetings, I would like to know how one can identify if a DomU is PV or HVM? Any docs which may indicate a way to find out? I have a CentOS 5.5 64bit DomU which might be HVM - how can this DomU can be made PV? Just stop the DomU, and then delete it using Virtual Machine Manager and the create another config file for a PV DomU and use xm new and then xm start? Let''s say I have a config

Hi. I have problem with installation XCP and XenServer on DomU. Installation just stuck after a while from installation beginning. DomU just stop responding, even reconnect with vncviewer isn''t possible. I''m using iso images to install. Dom0 is kernel 3.6-rc7 with xen 4.2.1-pre. I''m having such log: -videoram option does not work with cirrus vga device model. Videoram

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: normal -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash

Hello, I'm wondering if anyone out there is doing tap:aio disk devices on a Xen HVM vm with any success. Please let me know if you are, and perhaps your version info and a config file snippet. I've posted this to the xen-users list, and what I'm trying to do seems to be correct, works on Ubuntu, Debian, and XenSource; but it doesn't work on CentOS. Here's the snippet from my

Mounting ISOs now works as designed when using "local SR"-storage of ISO's too. Example local SR created (from cli) : xe sr-create name-label=isostorage type=iso device-config:location=/home/isostorage device-config:legacy_mode=true content-type=iso shared=true xe sr-scan UUID=<UUID given from the above> ISO-files are now available and listed properly in xencenter and

There are a number of flaws in the blktap userspace daemon when dealing with I/O errors. - The backends which use AIO check the io_events.res member to determine if an I/O error occurred. Which is good. But when calling the callback to signal completion of the I/O, they pass the io_events.res2 member Now this seems fine at first glance[1] "res is the usual result of an I/O