** Changed in: u-boot-linaro (Ubuntu)
Assignee: Justin L Werner (justin-l-werner) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927781
Title:
PXELINUX implementation doesn't
The --no-log will be a kernel command line option.
If you're on x86 or amd64, you would stop the Grub boot, and manually
edit the kernel cmdline to add the --no-log. Then, once you're up and
running, you would edit /etc/default/grub changing GRUB_CMDLINE_LINUX,
to affect both normal and
Here's a patch for RFC 5071 support. I'd like to talk to Linaro guys
about this.
** Patch added: proposed RFC 5071 implementation
https://bugs.launchpad.net/ubuntu/+source/u-boot-linaro/+bug/927781/+attachment/2870936/+files/rfc5071-justinlw.patch
--
You received this bug notification
I have some changes I've made to implement RFC 5071 against u-boot-
linaro that I will attach shortly. I want to get Linaro guys to take a
look at this and maybe have a quick chat about it today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've got code well under way and my cursory testing shows I can handle
208,9,10 fine. Working on 211 (RebootTime)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927781
Title:
PXELINUX
Jason, good input and I'd like to get the Dave Walker's consideration of
it into this bug. Dave?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927781
Title:
PXELINUX implementation doesn't respect
** Changed in: u-boot-linaro (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927781
Title:
PXELINUX implementation doesn't respect dhcp ConfigFile or
I tried to build a 64-bit Precise desktop virt using libvirt manager,
itself running on a 64-bit AMD 4-core box with Precise. When
specifying the vmvga/vmware option, qemu keeled over and died as soon as
(in VNC) it looked like the card was going into graphics mode.
I then built the image
** Changed in: u-boot (Ubuntu)
Assignee: (unassigned) = Justin L Werner (justin-l-werner)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/820141
Title:
Kernel cmdline limited to 256 characters
** Changed in: u-boot-linaro (Ubuntu)
Assignee: (unassigned) = Justin L Werner (justin-l-werner)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927781
Title:
PXELINUX implementation doesn't
Some incremental findings:
In 'qemu-kvm' the DeviceState for the peer device of the
BlockDeviceState that gets created when a disk attached by 'virsh
attach-disk' references the 'QemuOpts' options structure that lists the
options and the device ID string (ex: as 'virtio-disk4') that will (on a
I've been looking at libvirt and qemu for other work, I'm doing, and
I've criceld back to take another look at this.
Since I first looked at this, my testbed has updated to use the
oneiric-proposed
qemu-kvm package '0.14.1+noroms-0ubuntu6.1'
while retaining the libvirt-bin package
Public bug reported:
Release: Ubuntu 11.10 (Oneiric)
libvirt-bin: 0.9.2-4ubuntu15.1
qemu-kvm: 0.14.1+noroms-0ubuntu6
Summary:With a running KVM virt, performing an 'attach-disk', then a
'detach-disk', then another 'attach-disk'
in an attempt to reattach the volume at the
But, I think that the 'Duplicate ID' messages is generated from within
qemu-kvm, so perhaps an interaction between libvirt/qemu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/897750
Title:
14 matches
Mail list logo
