Displaying 20 results from an estimated 70000 matches similar to: "Has anyone packaged 3.1.0 for Debian yet?"
2007 May 24
3
[HOWTO] Xen 3.1.0 on Debian etch amd64
Hello,
attached is a little guide (in mediawiki notation) how to cleanly
install xen 3.1.0 on debian etch amd64.
Suggestions welcome!
Regards,
Bjoern
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2007 Nov 25
4
behaviour of ''xm block-attach'' changed with 3.1.2?
''xm block-attach'' doesn''t let me assign the same backend device anymore,
even if I use ''r!'' or ''w!''.
I think this has changed since 3.1.1 (or maybe since 3.1.0).
Is this the way it is supposed to work?
Thanks
James
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
2009 Jan 17
25
GPLPV network performance
Just reporting some iperf results. In each case, Dom0 is iperf server,
DomU is iperf client:
(1) Dom0: Intel Core2 3.16 GHz, CentOS 5.2, xen 3.0.3.
DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based.
Iperf: 1.17 Gbits/sec
(2) Dom0: Intel Core2 2.33 GHz, CentOS 5.2, xen 3.0.3.
DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based.
Iperf: 725 Mbits/sec
(3) Dom0: Intel Core2 2.33 GHz,
2007 May 27
9
Windows HVM - orderly shutdown
Is there a way to get Windows to do an orderly shutdown (eg simulate a
power button press) using the ''xm shutdown'' command?
Thanks
James
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2011 Jul 18
2
Forcing domU''s to never hibernate
Hey, list --
Recently we had to reboot some of our dom0''s. We were confused after doing
so to discover that some of the resident domU''s had not actually rebooted.
Some of the domU''s still had very long uptimes (weeks/months), despite the
dom0 having an uptime of just minutes.
Apparently, when the "shutdown -r now" command was issued, the dom0 was able
to
2008 Dec 26
17
Multiple IRQ''s in HVM for Windows
I really need to have the ability to tie event channel port''s to
interrupts for my gplpv drivers under Windows. Is anyone working on
anything like this? Does MSI allow more than one interrupt per PCI
device?
Thanks
James
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2008 Jul 16
7
Please help: domU becomes unresponsive
Hi all, sorry to intrude on xen-devel, but I think I need direction
from the expertise here. I''ve admin''d Xen servers of various flavors
for a couple years, but never seen this before. After a period ranging
from several hours to several days, my primary database and
development DomU completely locks up. Net disconnects, but CPU(sec)
continues to tick in xentop. No errors, and
2009 Nov 02
4
vps file lost after server crash
Hello, All,
Today one of our servers was crashed, after I rebooted the server, one
vps can not boot up, and it needs fsck, after I run fsck command, a
lot of files lost, and also some file content was changed. Not sure
how could it happen, do you have any advice that can avoid this or
recover the data?
Thanks.
_______________________________________________
Xen-users mailing list
2008 Aug 18
5
HVM windows - PCI IRQ firing on both CPU''s
I''m just doing some testing on the gplpv drivers with different ways of
handling interrupts, and I''m trying a scheme where each xen device (eg
vbd/vif) driver attaches to the same IRQ as the pci driver, and each
handles it in sequence.
In testing though, I noticed the following when logging what each ISR is
doing:
60.32381439 - evtchn event on port 5
60.32384109 - port 5
2010 Jan 30
20
"Iomem mapping not permitted" during windows crash dump under GPLPV
I''ve recently noticed that my windows crash dumps fail at around 40-50%
under GPLPV. ''xm dmesg'' shows the following:
(XEN) grant_table.c:350:d0 Iomem mapping not permitted ffffffffffffffff
(domain 865)
At first I thought that the cause was just a bug in my grant ref code
but it just occurred to me that this could be happening when Windows
tries to write out the
2009 Feb 10
7
hang on restore in 3.3.1
I am having problems with save/restore under 3.3.1 in the GPLPV drivers.
I call hvm_shutdown(xpdd, SHUTDOWN_suspend), but as soon as I lower IRQL
(enabling interrupts), qemu goes to 100% CPU and the DomU load goes
right up too.
Xentrace is showing a whole lot of this going on:
CPU0 200130258143212 (+ 770) hypercall [ rip =
0x000000008020632a, eax = 0xffffffff ]
CPU0 200130258151107 (+
2011 Dec 30
12
set_phys_to_machine not exported?
I''m trying to compile pvscsi out-of-tree, and I''m getting an error that set_phys_to_machine is not defined when I try to load the module (with the warning to that effect at compile time too). This used to work fine in pvops.
It seems that netfront uses that symbol in a module so I''m confused as to why pvscsi can''t... any suggestions? Is it one of the virtues of
2010 Jun 08
32
Problems with GPLPV network latency
Hi,
DomU is a Win2008 R2 64
When i install the GPLPV drivers the network latency goes from 15ms to
random numbers up to 1200ms and eventually dies. If you run a ping from
the DomU to another host the network stays alive but the high latency is
still there.
Further more if i try and uninstall the network driver i am unable to
use the old one (realtek) as it cannot detect the device.
2008 Jun 01
65
Release 0.9.5 of GPL PV Drivers for Windows
I''ve just made my first ever attempt at an Nullsoft installer, so if you
want to try it download "Xen PV Drivers 0.9.5.exe" from
http://www.meadowcourt.org/downloads/
The installer should detect the version of windows you are running and
install the drivers. At the moment you''ll need to install the shutdown
monitor service manually, but you can do that from the start
2008 Jun 01
65
Release 0.9.5 of GPL PV Drivers for Windows
I''ve just made my first ever attempt at an Nullsoft installer, so if you
want to try it download "Xen PV Drivers 0.9.5.exe" from
http://www.meadowcourt.org/downloads/
The installer should detect the version of windows you are running and
install the drivers. At the moment you''ll need to install the shutdown
monitor service manually, but you can do that from the start
2009 May 16
13
GPLPV uninstaller
I''ve just uploaded a couple of .bat files to
http://www.meadowcourt.org/downloads/gplpv_uninstall_bat.zip that will
manually (and forcibly) uninstall GPLPV from your computer, which seems
to be necessary before doing upgrades from some versions. Run the
uninstaller, reboot, then install. There is a 0.9.x and a 0.10.x
uninstaller, which differ slightly, but the basic steps performed are:
2009 May 16
13
GPLPV uninstaller
I''ve just uploaded a couple of .bat files to
http://www.meadowcourt.org/downloads/gplpv_uninstall_bat.zip that will
manually (and forcibly) uninstall GPLPV from your computer, which seems
to be necessary before doing upgrades from some versions. Run the
uninstaller, reboot, then install. There is a 0.9.x and a 0.10.x
uninstaller, which differ slightly, but the basic steps performed are:
2009 Feb 26
8
GPL PV TAP cow incompatible?
Hi
Is it true that the GPLPV drivers is incompatible with QCOW images?
The Windows DomU works fine with raw standard "file:/" images, and
paravirtualized Linux DomU works fine with QCOW and raw images.
If i use QCOW images with my Windows DomU''s i get a stop error:
0x00000007b (inaccessible boot device).
It looks like the blkback.3.hda process, that normally starts with
2010 Nov 02
4
Windows 2008 SBS suddenly disappearing on Xen 4.0.0
Hi all,
when running Windows 2008 SBS on Xen 4.0.0, it disappears after some time (longest time I had it running was 20 minutes). In /var/log/xen/qemu-dm-win1.log I find:
xc_map_foreign_batch: mmap failed: Cannot allocate memory
xc_map_foreign_bulk error 12
Anyone any idea how to troubleshoot this? The Hypervisor has 16 GB of RAM, currently 2 GB are allocated to Dom0. This specific DomU has 8
2008 Nov 10
14
GPL PV Intermitent Network Problems
Well, I seem to have developed a strange issue with the GPL PV drivers
in Windows. I''m running Xen 3.2 on SLES 10 SP2 and running some Windows
XP HVM domUs. Most (12-15) of my Windows machines work just fine. Two
of them, though, have started exhibiting a strange behavior with
intermittent network connectivity. Basically, the network starts up and
connects initially. After some