-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `libattr.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libacl.so.1' -> `': No such file or directory
ln: creating symbolic link `libattr.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libacl.so.1' -> `': No such file or directory
ln: creating symbolic link `libattr.so.1' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `libdl.so.2' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libtinfo.so.5' -> `': No such file or directory
ln: creating symbolic link `libpcre.so.0' -> `': No such file or directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ln: creating symbolic link `libc.so.6' -> `': No such file or directory
ln: creating symbolic link `ld-linux-x86-64.so.2' -> `': No such file or
directory
ldconfig: Cannot mmap file /lib64/libdmraid-events-isw.so.
ldconfig: Cannot mmap file /lib64/libnss_files.so.2.
/sbin/dracut: line 307: : No such file or directory
E: dracut: creation of failed
mkinitrd failed
warning: %post(kernel-2.6.32.14-1.2.105.xendom0.fc12.x86_64) scriptlet failed,
exit status 1
Cheers
Virgil.
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
unpackaged) file(s) found:
/etc/hotplug/xen-backend.agent
RPM build errors:
Installed (but unpackaged) file(s) found:
/etc/hotplug/xen-backend.agent
The question is:
Does this matter?
Can I just ignore it and use the RPM anyway?
Cheers
Virgil.
--
xen mailing list
xen@lists.fedoraproject.org
On Thu, 3 Jun 2010 05:34:34 am M A Young wrote:
> On Wed, 2 Jun 2010, Virgil wrote:
> > Just doing an rpmbuild on:
> >
> > xen-4.0.0-0.7.fc12.x86_64
> >
> > and I get this error towards the end:
> >
> > Processing files: xen-debuginfo-4.0.0-0.7.f
Further testing (haven't done the extra recommended things yet).
xendom0-105/xen-3.9.3 Success. This works but hardware virtualization exhibits
the same issues with WinXP as the xendom0-97/xen-4.0.0 combo. The configs are
identical except that qemu-dm is in /usr/lib64/xen/bin whereas with xen-4.
8005003b cr4: 06d0
(XEN) cr3: 015a9000 cr2: b1b60000
(XEN) ds: 007b es: 007b fs: 00d8 gs: 00e0 ss: 0068 cs: 0060
On Thu, 3 Jun 2010 04:59:12 pm you wrote:
> On Thu, Jun 03, 2010 at 02:23:15PM +1000, Virgil wrote:
> > On Thu, 3 Jun 2010 05
memsize=maxmem and
target=memory. If these the same, the internal function will not use
PoD.
Trying this now.
Success!! The 32hv12 machine is alive and kicking!!!
Just set MAXMEM=MEMORY and PoD is disabled!!
Very happy here.
Now for WinXP.
Cheers
V
On Fri, 4 Jun 2010 10:53:40 am Virgil wrote
Success! xendom0-105/xen-3.4.3 combo. PoD memory disabled and WinXP Pro
installed and operational.
On Fri, 4 Jun 2010 02:03:26 pm Virgil wrote:
> Is this what is happening?:
>
> http://lists.xensource.com/archives/html/xen-devel/2008-12/msg01030.html
>
> i.e. the guest does not
On Sat, 29 May 2010 11:26:50 pm M A Young wrote:
> If anyone wants to test xen 3.4.3, I have put up a source RPM at
> http://myoung.fedorapeople.org/dom0/src/xen-3.4.3-0.91.fc13.src.rpm
>
> Michael Young
>
> --
> xen mailing list
> xen@lists.fedoraproject.org
> https://admin.fedoraproject.o
Just a quick update:
Just tried xen-4.0.0-2. Recompile from source on fc12.x86_64.
identical behaviour.
Cheers
V
On Fri, 18 Jun 2010 03:17:19 pm Virgil wrote:
> On Sat, 29 May 2010 11:26:50 pm M A Young wrote:
> > If anyone wants to test xen 3.4.3, I have put up a source RPM at
is to add an n-millisecond delay every time the output stream in
Xen sees a \n. This would delay the screen updates enough for the camera to
see them. The n should be configurable on the kernel boot command line. It's
set to 0 right now.
Cheers
V
On Mon, 21 Jun 2010 12:10:17 pm Virgil wrote
Hi Pasi,
On Mon, 21 Jun 2010 08:57:55 pm Pasi Kärkkäinen wrote:
> On Mon, Jun 21, 2010 at 01:56:36PM +0300, Pasi Kärkkäinen wrote:
> > On Mon, Jun 21, 2010 at 02:28:15PM +1000, Virgil wrote:
> > > Another quick update
> > >
> > > xen-4.0.1-0.1.rc3.fc13.s
xt this buffer
overflow causes the RTC to hangup somehow.
I pressed the reset button, but this time the 2 64PV machines are not logged
in. I'll just let it go and see if it keeps going.
Cheers
V
On Tue, 22 Jun 2010 04:29:06 pm Pasi Kärkkäinen wrote:
> On Tue, Jun 22, 2010 at
On Wed, 23 Jun 2010 03:30:52 pm Pasi Kärkkäinen wrote:
> On Wed, Jun 23, 2010 at 11:11:58AM +1000, Virgil wrote:
> > Hi Pasi,
> >
> > Had a hiccup overnite:
> >
> > The host became unresponsive in a weird way. The time stopped
> > incrementing.
> >
&
p.s. FYI Samba4-Alpha12 Active Directory controller is working well on
64PVFC12.
On Wed, 23 Jun 2010 05:18:56 pm Virgil wrote:
> On Wed, 23 Jun 2010 03:30:52 pm Pasi Kärkkäinen wrote:
> > On Wed, Jun 23, 2010 at 11:11:58AM +1000, Virgil wrote:
> > > Hi Pasi,
> &
Update:
Completely stable with 7 VMs. Hasn't missed a beat for several days now.
Will now run the pings again in 2 of 64PV from the virtual consoles (no
graphics - and disconnected) and see if the host clock tick dies again.
Cheers
V
On Thu, 24 Jun 2010 03:17:51 pm Virgil wrote:
&g
ched on for that long :-)
Cheers
V
On Thu, 1 Jul 2010 09:25:48 am Virgil wrote:
> Update:
>
> Completely stable with 7 VMs. Hasn't missed a beat for several days now.
>
> Will now run the pings again in 2 of 64PV from the virtual consoles (no
> graphics - and disconnected)
Host lockup.
Hi Guys, disaster after starting a WindowsXP Pro HVM. Came back this morning to
find a dead host.
Here's the output from the XEN serial port relating to the 3 domU's running. 2
are running Fedora 12 and 13. These had been running for 4 days prior to
starting the WinXP machine.
(X
FYI Stability with:
Linux seanl64. 2.6.32.17-157.xendom0.fc12.x86_64 #1 SMP Sat Aug 7
15:26:59 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
kernel-devel-2.6.32.17-157.xendom0.fc12.x86_64
kernel-2.6.32.17-157.xendom0.fc12.x86_64
kernel-firmware-2.6.32.17-157.xendom0.fc12.noarch
kernel-headers-2
Sep 20
19:32:37 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
Cheers
Virgil
On Sat, 25 Sep 2010 08:02:00 am M A Young wrote:
> I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12) at
> http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 or at the
> reposi
Further to the previous email regarding diskio stats:
It appears the ksysguardd is no longer able to gather stats either.
I'm suspecting a bug in the kernel and not libvirtd.
Cheers
V
On Sat, 25 Sep 2010 08:02:00 am M A Young wrote:
> I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12
xen-4.0.1-6.fc12 (recompiled under FC12) likewise seems to resolve all issues
here. Fingers crossed, so far so good.
Cheers
V
On Sun, 17 Oct 2010 10:32:12 pm Pasi Kärkkäinen wrote:
> On Thu, Oct 14, 2010 at 04:32:20PM +0100, M A Young wrote:
> > On Wed, 13 Oct 2010, M A Young wrote:
> > > On Wed
kernel-2.6.32.25-171.rc1.xendom0.fc12
RTC went mad. 1 sec = 1mS
Top was showing hours whizzing past in minutes. Windows VM went crazy doing
stuff. FC13 VM went crazy too doing all sorts of things really quickly.
Bizzare effect.
Went back to -168 kernel. Alls well again.
Cheers
V96
On Sun, 24
(Xen) Platform timer appears to have unexpectedly wrapped 10 or more times
Kaboom! Zz.
2.6.32.25-172.xendom0.fc12
FC14 everything else.
Cheers
V
On Mon, 8 Nov 2010 07:43:36 am M A Young wrote:
> I have built another 2.6.32.x based kernel (2.6.32.25-172.xendom0.fc12) at
> http://koji.fe
Host crashed. Running HVM fc14-32.
Skipping 86000 seconds.
Skipping 86000 seconds.
Skipping 86000 seconds.
Skipping 86000 seconds.
Skipping 86000 seconds.
Skipping 86000 seconds.
Skipping 86000 seconds.
...
...
...
...
Kaboom
Cheers
V
On Mon, 8 Nov 2010 07:43:36 am M A Young wrote:
> I have buil
Found this in /var/log/messages as the last thing prior to death.
Clocksource tsc unstable
Did some Googling and found some people changed the dom0 clocksource.
Added clocksource=jiffies to the kernel commandline.
Will see if it does anything.
V
On Wed, 17 Nov 2010 12:00:01 pm Virgil
gt; On Mon, Dec 13, 2010 at 11:30:35AM +1100, Virgil wrote:
> > Found this in /var/log/messages as the last thing prior to death.
> >
> > Clocksource tsc unstable
> >
> > Did some Googling and found some people changed the dom0 clocksource.
> >
> >
Just a quick pre-xmas report:
Since turning off all power saving in the BIOS, everything has worked
flawlessly
(now that I've emailed this I'm sure the entire system will blow up).
So far so good.
Cheers and merry Xmas
V.
On Wed, 15 Dec 2010 01:56:31 pm Virgil wrote:
> Hi
Feb 23rd here in Australia.
The system is still running flawlessly since turning off all power saving in
the BIOS. Looks like the power saving stuff in the BIOS for AMD processors
could be the issue with the clocksource.
Cheers
V
On Fri, 24 Dec 2010 02:10:54 pm Virgil wrote:
> Just a qu
Just did:
rpm -Uvh --oldpackage *
The upgrade deleted all previous kernels (/lib/modules and all) on the F14
test box.
It got the grub.conf wrong (we're booting off raid). Manually fixed the
grub.conf and life goes on.
Cheers
V.
On Fri, 25 Mar 2011 07:57:05 AM M A Young wrote:
> I have b
AAAhhhh
Noun: BALLOON!
Verb: BALLOONING!
V
On Fri, 30 Sep 2011 08:56:28 AM Konrad Rzeszutek Wilk wrote:
> On Wed, Sep 28, 2011 at 08:03:37PM -0300, Itamar Reis Peixoto wrote:
> > On Wed, Sep 28, 2011 at 7:59 PM, Konrad Rzeszutek Wilk
> >
> > wrote:
> > > On Wed, Sep 28, 2011 at 0
tat -ant'
Only nat'd tcp connections are effected. Connections to machines on the same
bridge work fine.
Does this sound familiar to anyone?
Thanks in advance
Virgil
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
I'm having a problem with mdraid running in a DomU. The issue is that mdraid
declares one leg of the raid to have failed (when there's actually nothing
wrong).
DomU is fc16 - 3.2.2-1.fc16.x86_64
Dom0 is fc14 - 2.6.32.26-174.2.xendom0.fc12.x86_64
The same DomU running on Dom0 fc16 - 3.2.7-1.fc16
make it easy to install via rpm (assuming it can compile).
On Mon, 26 Mar 2012 01:17:49 PM Konrad Rzeszutek Wilk wrote:
> On Mon, Mar 19, 2012 at 01:35:19PM +1100, Virgil wrote:
> > I'm having a problem with mdraid running in a DomU. The issue is that
> > mdraid declares one l
compatible controller: ATI Technologies Inc ES1000 (rev 02)
Thanks again.
V
On Thu, 29 Mar 2012 10:51:14 AM Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 29, 2012 at 01:38:38PM +1100, Virgil wrote:
> > Hi Konrad,
> >
> > Firstly, thanks for the reply.
> >
> > What I&#x
34 matches
Mail list logo
