** Tags added: yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi xfs unsupported filesystem
To manage notifications about this bug go to:
bummer workaround:
for xml in /etc/libvirt/qemu/*.xml; do VM=$(basename $xml|cut -d. -f1);
rm /var/lib/libvirt/qemu/channel/target/${VM}.org.qemu.guest_agent.0;
virsh dumpxml $VM | /usr/lib/libvirt/virt-aa-helper -c -u libvirt-`virsh
domuuid $VM`; virsh start $VM; done
--
You received this bug
Confirmed. Update in proposed works as mpanella says
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393842
Title:
libvirt does not grant qemu-guest-agent channel perms
To manage notifications
Will there be a fix for Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103389
Title:
makedumpfile --dump-dmesg fails on 3.5 kernels and later
To manage notifications about this bug go to:
As a related comment, the serial port is *always* ttyS0, even when it's
not there, and even when both GRUB2 itself and the kernel are all
configured to go to, say ttyS1 or something completely else.
I propose to modify /etc/grub.d/20_memtest86+
* Look at /sys/class/tty/ ; if there's nothing in
I set the user to 'Always Ask' for password, yet I had to give a
(nonsensical) password for the p12 file, otherwise it wouldn't ungrey.
Upon connecting, it still asked me for both passwords.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Bug watch added: freedesktop.org Bugzilla #50403
https://bugs.freedesktop.org/show_bug.cgi?id=50403
** Also affects: nouveau via
https://bugs.freedesktop.org/show_bug.cgi?id=50403
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 570542 ***
https://bugs.launchpad.net/bugs/570542
It's largely semantics (it should be 'related'), but the issue is largely the
same. For some reason the build farms don't pick up on ahci's dependency on
libahci (it's also not registered in modules.dep)
The ahci.ko needs libahci to work, which is included in
linux-image-extra-virtual (along with everything but the kitchen sink). It
*SHOULD* be included in linux-image-virtual IMHO, because ahci.ko is next to
worthless without it, and installing an additional 120MB of drivers, modules
and cruft
On a side note, something appears not right there anyways;
modules.dep doesn't list libahci.ko as a dependency for ahci.ko, while modinfo
does
so either depmod -a silently fails the dependency and doesn't list it, or
something strange is going on with the dependency resolution.
--
You received
*** This bug is a duplicate of bug 570542 ***
https://bugs.launchpad.net/bugs/570542
The ahci.ko needs libahci to work, which is included in linux-image-
extra-virtual (along with everything but the kitchen sink). It *SHOULD*
be included in linux-image-virtual IMHO, because ahci.ko is next to
Natty still doesn't include it. Please reopen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/570542
Title:
linux-image-virtual does not include ahci module, prevents virtualbox
from booting an
*** This bug is a duplicate of bug 570542 ***
https://bugs.launchpad.net/bugs/570542
** This bug has been marked a duplicate of bug 570542
linux-image-virtual does not include ahci module, prevents virtualbox from
booting an Ubuntu guest
--
You received this bug notification because you
Neither does Oneiric. Please reopen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/570542
Title:
linux-image-virtual does not include ahci module, prevents virtualbox
from booting an Ubuntu guest
Well, looks like it, yes.
I ended up completely nulling out the HD's because dmraid kept refusing
deleting both the RAID set (can't be done for DDF1) and the metadata
(gave errors no matter what) and completely rebuilding the array again.
Problem is resolved now.
Although it continues to elude
Right. That was 'smart' :D Here's the tar now.
mdadm is as before:
root@ubuntu:/tmp# mdadm -E /dev/sdc /dev/sdc1
/dev/sdc:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ef584e09:52f1d802:3d7ec530:e2926701
Name : ubuntu:SATAs (local to host
hm. Since that is not the case, I'm rather suspicious of messing with my
metadata ;-) I'll try that tonight, after backing up everything on the
disks.
And/or perhaps I'll try reproducing this in a VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The mobo is a SuperMicro one with a very very weird option to choose (I
kid you not) between Intel MSM or Adaptec BIOS for the SATA ports.
However, neither have been active to my knowledge, certainly not in a
RAID6 config, as neither support this.
It is unlikely but possible I once configured a
Judging from your tar comment, you're expecting way more output than
this from dmraid -rD:
root@ubuntu:~# dmraid -rD
/dev/sdh: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdg: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdf: ddf1, .ddf1_disks, GROUP, ok,
Philip,
Thanks for responding. Of course I meant 'Upgrade from Maverick to Natty
(problem didn't occur on Maverick)' :)
The array in question was created under Maverick ~~ like this:
mdadm --create /dev/md20 --level=6 --raid-devices=6 -c 128 -e 1.2 --name=SATAs
/dev/sd[cdefgh]
root@ubuntu:~#
Phillip,
It seems Magic : a92b4efc is consistent with native mdadm format, so it
seems it's not DDF1. My hypothesis would therefore seem to be that
dmraid incorrectly picks up native mdadm RAID sets as DDF1 sets?
Also, I assumed the Debian bug was related, because the people over
there mention
Public bug reported:
Binary package hint: dmraid
Setup:
* Upgrade from Lucid to Natty (problem didn't occur on Lucid)
* /dev/sd[ab] in fakeRAID setup w/rootFS on it
* /dev/sd[cdefgh] in an md RAID6
Upon upgrade, system will fail to assemble the RAID6, saying the block devices
are busy:
mdadm:
root@ubuntu:/lib/udev# dmraid -r
/dev/sdh: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdg: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdf: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sde: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors,
Also, note that the attached Debian bug 534274 reports the same issue,
but fails to consider my scenario as a valid setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
dmraid
** Tags added: mdadm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
dmraid interferes with mdadm
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
For me, the workaround works.
The related bug has already been filed under #644669
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/577264
Title:
libvirt started after cgred -
** Bug watch added: Red Hat Bugzilla #660402
https://bugzilla.redhat.com/show_bug.cgi?id=660402
** Also affects: libcgroup (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=660402
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
For me, the workaround works.
The related bug has already been filed under #644669
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/577264
Title:
libvirt started after cgred - cgroup not working
And there you go.
+1 for fix on my up-to-date 64-bit Maverick Server :)
I'm loving it. Been rebuilding my 6*2TB RAID6 for three days now,
figuring something went wrong a couple of times.
Then I found out the detection issue and then this bug is easily found.
FWIW, I've got an array created
Got hit by #570542 at the same time.
The two issues seem to have some similarities between them in that they're both
broken kernel modules in the -virtual that should've been available and seem to
have been compiled in, or the build at least should've tried.
I've noticed that the -headers
I second that.
Both upgrade and clean install result in same error as Andy.
Got hit by #659084 at the same time.
The two issues seem to have some similarities between them in that they're both
broken kernel modules in the -virtual that should've been available and seem to
have been compiled in,
Linux ubuntu 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC
2010 x86_64 GNU/Linux
kerneltop: /boot/System.map-2.6.32-22-generic(27435): wrong map line
FWIW, the line is:
8174ce30 r
__pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_ESB_10quirk_disable_intel_boot_interrupt
--
I see there's a lot of discussion going on about this bug, I'll just
drop in my 5c:
I cleanly installed/updated a x64 Karmic w/ext4 filesystems on my MacBook 5,1
(no other OSes installed).
Due to the nature of my work I downloaded over a dozen ISO's of different
HTTP/FTPs, none of which failed
I was having the exact same issue, but then with a Macbook 79 model
keyboard (Macbook/Pro Intl) and the US International with AltGr dead
keys.
One of the commenters in the FreeDesktop bug correctly notes that there
might actually be little use for these symbols anymore, but since I'm
not exactly
34 matches
Mail list logo
