[Bug 210495] Re: qemu man page incorrectly specifies default emulated nic

2008-12-08 Thread pturing
However, the initial report about the documentation is accurate as of 8.10 ... Both kvm and qemu use an rtl8139 as the default NIC now, but the qemu man page does not reflect this while the kvm-qemu man page does -- qemu man page incorrectly specifies default emulated nic https://bugs.launchpad.

[Bug 210495] Re: qemu man page incorrectly specifies default emulated nic

2008-12-08 Thread pturing
This problem is no longer reproducible for me in 8.10 -- qemu man page incorrectly specifies default emulated nic https://bugs.launchpad.net/bugs/210495 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-

[Bug 210495] Re: qemu man page incorrectly specifies default emulated nic

2008-07-27 Thread pturing
As far as I can tell, the default NIC hasn't been changed yet in qemu. hw/pc.c still says: if (!nd->model) { if (pci_enabled) { nd->model = "ne2k_pci"; } else { nd->model = "ne2k_isa"; } However, it has been changed in k

[Bug 223501] Re: qemu-img can't create a 27 terabyte qcow2 image

2008-07-27 Thread pturing
Narrowed it down a little further.. 2049 * 1024 = 2098176M works fine.. $ qemu-img create -f qcow2 foo.qemu 2098176M Formatting 'foo.qemu', fmt=qcow2, size=2148532224 kB but (2049 * 1024) +1 = 2098177M breaks it $ qemu-img create -f qcow2 foo.qemu 2098177M Formatting 'foo.qemu', fmt=qcow2, siz

[Bug 241014] Re: update-grub breaks root on loop

2008-06-25 Thread pturing
I no longer think this patch is necessary ** Changed in: grub (Ubuntu) Status: New => Invalid -- update-grub breaks root on loop https://bugs.launchpad.net/bugs/241014 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-b

[Bug 241014] Re: update-grub breaks root on loop

2008-06-23 Thread pturing
** Attachment added: "same patch as originally posted in-line" http://launchpadlibrarian.net/15544335/no_uuid_for_loops_update-grub.patch -- update-grub breaks root on loop https://bugs.launchpad.net/bugs/241014 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 241053] Re: loop-aes module is not available when update-initramfs is run

2008-06-23 Thread pturing
** Attachment added: "same patch as originally posted in-line" http://launchpadlibrarian.net/15544348/loop-aes-utils_use_module-assistant.patch -- loop-aes module is not available when update-initramfs is run https://bugs.launchpad.net/bugs/241053 You received this bug notification because y

Re: [Bug 241053] Re: loop-aes module is not available when update-initramfs is run

2008-06-20 Thread pturing
Cool :) Building the module works for me too, which is very cool. But... it doesn't do it automatically when building the initrd for a new kernel, which would be much better. On Fri, Jun 20, 2008 at 6:41 PM, Eymen Alyaz <[EMAIL PROTECTED]> wrote: > Hi, > I'm using the same setup. Loop-aes-source

[Bug 241053] [NEW] loop-aes module is not available when update-initramfs is run

2008-06-18 Thread pturing
Public bug reported: Binary package hint: loop-aes-utils Currently when a new kernel is installed, the loop-aes-utils hooks for initramfs-tools will always fail because the loop-aes version of loop.ko has not been installed for the new kernel. This patch modifies the loopaes hook script such th

[Bug 241014] [NEW] update-grub breaks root on loop

2008-06-18 Thread pturing
Public bug reported: Binary package hint: grub I am running grub 0.97-29ubuntu21 on Hardy My root device is /dev/loop1, and I am setting this in the kopt= line in menu.lst but update-grub tries to resolve this to a UUID, which means I can't boot This patch will disable converting /dev/loop entr