I have this problem with 14.04.1
I partition a USB stick with a 1GB partition (fat32) and 31GB partition (ext4)
I create the live system with the Startup Disk Creator
I name the other partition casper-rw
I edit txt.cfg and syslinux.cfg, adding `persistant`
After booting, I perform a dist-upgrade.
I'm hunting around hoping to find a way to get the initial scan files updated
before 12.04 is released.
I'm running 11.10 and they are still out of date.
This was posted 2 years ago so I'm guessing it's dead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
OK, I've tried the following:
1) Recompile kernel with all the same options except enabling DMAR.
2) Edit the apparmour profile to match suggested by flashydave
3) Installed latest qemu-kvm from kvm edgers ppa:
https://launchpad.net/~ubuntu-server-edgers/+archive/server-edgers-qemu-kvm
Attached
Here is the test.log
** Attachment added: test.log
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/639712/+attachment/1820712/+files/test.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
These commands:
echo 1106 3038 /sys/bus/pci/drivers/pci-stub/new_id
echo :08:06.0 /sys/bus/pci/devices/:08:06.0/driver/unbind
echo :08:06.0 /sys/bus/pci/drivers/pci-stub/bind
From here:
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
Did nothing.
However
Reboot did nothing, game over for now.
The driver 'pci-stub' is occupying your device
I thought pci-stub taking the device is what it was supposed to do?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
OK, I've tried the following:
1) Recompile kernel with all the same options except enabling DMAR.
2) Edit the apparmour profile to match suggested by flashydave
3) Installed latest qemu-kvm from kvm edgers ppa:
https://launchpad.net/~ubuntu-server-edgers/+archive/server-edgers-qemu-kvm
Attached
Here is the test.log
** Attachment added: test.log
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/639712/+attachment/1820712/+files/test.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
These commands:
echo 1106 3038 /sys/bus/pci/drivers/pci-stub/new_id
echo :08:06.0 /sys/bus/pci/devices/:08:06.0/driver/unbind
echo :08:06.0 /sys/bus/pci/drivers/pci-stub/bind
From here:
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
Did nothing.
However
Reboot did nothing, game over for now.
The driver 'pci-stub' is occupying your device
I thought pci-stub taking the device is what it was supposed to do?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Looks like this is also affecting me. :(
I'm trying to pass a PCI tuner through to a virtual machine, I have an AMD
890FX based board with IOMMU and it's switched on in the BIOS.
Running Ubuntu server 10.10 x64.
Flashydave: It sounds like you've actually got this working, have you
written
Hi,
Looks like this is also affecting me. :(
I'm trying to pass a PCI tuner through to a virtual machine, I have an AMD
890FX based board with IOMMU and it's switched on in the BIOS.
Running Ubuntu server 10.10 x64.
Flashydave: It sounds like you've actually got this working, have you
written
I have no idea, I learnt to not set the bootable flags manually, I just
let the installer handle it.
Oh, and I just put my /boot partition on a usb stick. Much simpler.
Personally I think this is long dead, but I don't see any sort of
close button.
J.
--
Alternate installer fails to install a
Hi,
I think I may also be having this problem, I'm trying to pass through a PCI
WinTV NOVA T 500.
It's actually a pair of USB DVB-T tuners on a PCI card so it needed the 'three
stars' in the /sys path in the apparmour profile.
I appended the improved solution:
/sys/bus/usb/devices/ r,
Rebooting the PC fixed that problem so I guess something hadn't been reloaded.
I've also added /dev/** rwk, to the apparmour profile. Taking it away doesn't
stop it from working again, although I've not tried rebooting the host yet.
It still doesn't quite work however, as now (on the guest) I
Hmm, it seems thats actually because usb2 is not supported in KVM?
I tried passing through the PCI card itself, but I'm back to permission
denied :(
device: 03:06.0: driver=pci-assign host=03:06.0
device: 03:06.1: driver=pci-assign host=03:06.1
device: 03:06.2: driver=pci-assign host=03:06.2
Found the apparmour errors in syslog, related to virt-aa helper.
I added /sys/devices/** r, to usr.lib.virt-aa-helper and got a bit further.
Still getting this:
May 10 23:14:25 hal kernel: [ 179.037233] type=1503
audit(1273529665.107:22): operation=open pid=1601 parent=1 profile
Hi,
I think I may also be having this problem, I'm trying to pass through a PCI
WinTV NOVA T 500.
It's actually a pair of USB DVB-T tuners on a PCI card so it needed the 'three
stars' in the /sys path in the apparmour profile.
I appended the improved solution:
/sys/bus/usb/devices/ r,
Rebooting the PC fixed that problem so I guess something hadn't been reloaded.
I've also added /dev/** rwk, to the apparmour profile. Taking it away doesn't
stop it from working again, although I've not tried rebooting the host yet.
It still doesn't quite work however, as now (on the guest) I
Hmm, it seems thats actually because usb2 is not supported in KVM?
I tried passing through the PCI card itself, but I'm back to permission
denied :(
device: 03:06.0: driver=pci-assign host=03:06.0
device: 03:06.1: driver=pci-assign host=03:06.1
device: 03:06.2: driver=pci-assign host=03:06.2
Found the apparmour errors in syslog, related to virt-aa helper.
I added /sys/devices/** r, to usr.lib.virt-aa-helper and got a bit further.
Still getting this:
May 10 23:14:25 hal kernel: [ 179.037233] type=1503
audit(1273529665.107:22): operation=open pid=1601 parent=1 profile
Hi,
I've been trying to install Lucid Server 64bit Beta 1 with the following
config:
8Gb usb flash -- ext4 on /boot
3 x 500gb SATA -- RAID5 -- lvm -- ext4 on / 8G swap.
The install would lock the machine completely after finishing creating
the ext4 filesystem on vg_main, lv_root.
I can
Hi,
I'm running Ubuntu 7.10 and I'm also afflicted by this problem.
I've got a nice workaround though, to tide you over before a proper fix becomes
available.
Firefox -- Edit -- Preferences -- Content -- Manage -- Double click PLS
Select Open With and set it to /usr/bin/totem
Now clicking on
Hi,
I'm running Ubuntu 7.10 and I'm also afflicted by this problem.
I've got a nice workaround though, to tide you over before a proper fix becomes
available.
Firefox -- Edit -- Preferences -- Content -- Manage -- Double click PLS
Select Open With and set it to /usr/bin/totem
Now clicking on
Hi,
Fixed it.
Followed this guide:
http://dev.jerryweb.org/raid/
4 things were different to what I tried:
1) /dev/sda,b,c1 *not* set to bootable
2) /dev/sda,b,c1 512MB
3) didn't label any of the partitions
4) left 2% of the HDDs as free space (10GB per drive!! 8@)
If I had to guess, I'd say
25 matches
Mail list logo