Well this is damn annoying ... should the bug be against python-imaging
for not magically providing python2.4-imaging as well as
python2.5-imaging, python2.6-imaging ? Or against zope2.10 for being
"behind the times" by depending on python2.4 ?
Is there a backport of python2.4-imaging for Jaunty?
In linux-image-2.6.24-16-xen (2.6.24-16.30) I am back to the old
problem:
[EMAIL PROTECTED]:~$ sudo xm create -c /etc/xen/gutsy.cfg
Using config file "/etc/xen/gutsy.cfg".
Error: Device 51713 (vbd) could not be connected. losetup /dev/loop4
/xen/domains/gutsy/swap.img failed
[EMAIL PROTECTED]:~$
Now it seems with the latest Xen kernel package (linux-
image-2.6.24-16-xen) the xen modules are missing altogether. So with
release 2.6.24-16.30 it is not possible to load the modules to work
around this problem...?
[EMAIL PROTECTED]:/var/lib/dpkg/info$ grep /lib/modules
linux-image-2.6.24-15-x
I beg your pardon, I didn't read the first line of your bug report!
But yes I can confirm the same problems with losetup ... or rather with
the xen block daemon, which called losetup and then broke.
--
losetup fails when using the 'file:/', preventing the DomU from being created
https://bugs.lau
It's annoying and poorly documented but it now seems necessary to use
"tap:aio" instead of "file".
i.e. for your example:
disk = [ 'tap:aio:/images/win2k3disk.img,ioemu:hda,w',
'tap:aio:/images/win2k3iso.img,ioemu:hdc:cdrom,r']
This should work.
--
losetup fails when using the 'file:/', preve
ubuntu4) has slipped in quietly to fix the
xvda problem and to add support for hardy guests. It hasn't fixed the
tap:aio: instead of file: yet.
> So, the bug as filed has basically been fixed and has workarounds for
> things that are broken otherwise
Agreed, I suppose.
Andrew.
--
deti said:
> The new kernel package 2.6.24-14 fixed this problem for me. Can anyone
> confirm this?
> The networking bug #204010 seems not to be fixed by now.
Not fixed for me by this package, no. =/
Andrew.
--
Andrew Shugg <[EMAIL PROTECTED]> http://www.neep
Public bug reported:
I have been having troubles with Xen simply being unable to run paravirt
domUs since I built a gutsy server a while ago. When booting a domU it
would bomb out to the initrd busybox shell because it could not find its
root device. (The same config works fine on an Ubuntu 7.04
Never mind, the .debs did show up a day later.
I still can't boot my server with them because (a) the (EVMS) dm_bbr
patch isn't included in the xen-source-2.6.19 package, and (b) when
added, the dm_bbr module won't build under 2.6.19 anyway ... but that's
an EVMS problem, not a Xen problem. =)
A
This may or may not be related to why I can't use EVMS under the feisty
xen kernel. I'll look into it ...
In Feisty the evms package version is 2.5.5-18ubuntu3, and in Edgy the
evms package version is 2.5.5-15
In Feisty, I have the following local-top scripts:
/usr/share/initramfs-tools/scrip
Hi Chuck,
I can see in http://archive.ubuntu.com/ubuntu/pool/universe/x/xen-
source/ that a xen-source_2.6.19-2ubuntu7.diff.gz and xen-
source_2.6.19-2ubuntu7.dsc have appeared, but no .debs?
Are we waiting on an autobuilder, or is approval needed from the release
team? Is there a copy of the .d
Will gladly test once my iBook G4 is returned to me from the service
shop, grr.
Andrew S.
--
BCM4306 do not work on powerbook
https://bugs.launchpad.net/bugs/76685
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
Hi Chuck,
The feisty xen image (2.6.19-4-server and 2.6.19-4-generic) sadly do not
work for me, as they lack the CONFIG_BLK_DEV_DM_BBR kernel option - this
means that EVMS won't run under these kernels, and I can't start up my
domU's as they live on various EVMS volumes.
With the feisty freeze ju
Confirmed. This is the same issue raised in part (b) of bug 96123
(rejected).
The issue just happened with me when trying to install from
ubuntu-7.04-beta- server-amd64.iso under Xen. The qemu cdrom device is
not detected.
I have a 6.10-server-amd64 installation alongside in another Xen domain
While still on the Live CD, I did:
apt-get install xorg-driver-fglrx
(which installed gcc-3.3-base, libc6-i386, libstdc++5 and xorg-driver-
fglrx)
I then changed the driver from 'vesa' to 'fglrx' in /etc/X11/xorg.conf
and did Ctrl+Alt+Bckspc ... and it worked, I'm in 1680x1050. Only at
60Hz and
** Tags added: 6.10 edgy
--
[edgy] Live CD improperly detects widescreen monitor.
https://launchpad.net/bugs/59841
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Tags added: edgy
--
Edgy Live CD - internal disk's partitions do not appear on desktop
https://launchpad.net/bugs/68822
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm not sure what the process is that "discovers" disk partitions and
automagically adds them to /etc/fstab with /etc/media mountpoints - if
someone can point me to it I'll see if I can debug what's happening
here.
I've confirmed that gnome-volume-manager is running, and that the
filesystems /dev/
Public bug reported:
In Dapper my internal hard disk's NTFS partitions were visible on the
desktop, had /etc/fstab entries, and /media/sda{1,4} mountpoints.
Booting with the Edgy amd64 install CD, I don't see them. A 320GB USB
drive is seen as /dev/sdd and a mountpoint created for it under /media
It's happening to me with the (release) Ubuntu 6.10 amd64 live CD. =)
(Mind you it's been the same for me in Dapper as well.) I'm not stuck
in 800x600 though, I get 1280x1024 at 75Hz.
I don't know if I'm prepared to go to the lengths Matt Philmon took to
it working. However I have attached my x
This is possibly the same issue as bug #58503.
Andrew S.
--
Edgy Eft not properly shutting down/rebooting
https://launchpad.net/bugs/68599
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Me three ...
Additionally as I have a widescreen monitor (ViewSonic vx2025wm) I not
only get the black and white colour scheme, it's all whacked out across
the screen too. =/
This is with the released Ubuntu 6.10 amd64 Desktop live CD.
System is AMD64 X2 on nForce4. I've attached my lspci -vv
How can users encourage this to happen? The backport of the Debian fix
to Ubuntu Dapper, I mean.
Andrew S.
--
libnm-util0 for network-manager on ppc does not work with wpa passphrases
https://launchpad.net/bugs/52922
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
23 matches
Mail list logo
