Public bug reported:
cempedak:~$ euca-run-instances -k mykey emi-DFE41074 -t c1.medium -n 8--group
more8
Traceback (most recent call last):
File "/usr/bin/euca-run-instances", line 198, in
main()
File "/usr/bin/euca-run-instances", line 139, in main
max_count = int(counts[1])
ValueEr
I am not sure either. But we do have some options:
1. if rejecting all requests, it should print out a reason, and end immediately;
2. if accepting up to (VNET_ADDRSPERNET - 3), then it should print out messages
for the refusals (and not even try to start them) (but I guess there is a
timing iss
** Summary changed:
- No instances started if euca-run-instance is run with bug -n
+ No instances started if euca-run-instance is run with a large -n
--
No instances started if euca-run-instance is run with a large -n
https://bugs.launchpad.net/bugs/546293
You received this bug notification beca
Hi Etyenne,
Yes, the basic symptom is the same. The difference is that *no*
instances succeed when I run with a -n > 30. This is rather unexpected.
BTW, thank you, adjusted the bug title.
** Summary changed:
- Cannot start more than 29 instances
+ No instances started if euca-run-instance is ru
Public bug reported:
Using the tamarind-based test rig, and ISO images from cdimage
(20100323.2).
I tried to run the maximum number of instances on the setup (using
lucid-amd64-topol, 66 sessions) from a idling cloud. All failed.
Looking at the configuration, I found VNET_ADDRSPERNET="32". I th
Indeed, and sorry for that. Anyway, the rest is still valid: ntpdate
will be run when the NIC is brought up, and will adjust the time on your
system.
Now. I was on my way to close this bug as working as designed, but I am
not as sure of that anymore. If you set the Time/Date to *manual*, then
you
Thank you for opening this bug and helping make Ubuntu better. I am
setting this package Confirmed/Low: this is a -- at the moment -- known
issue, see http://www.mail-archive.com/libvir-
l...@redhat.com/msg15612.html for details.
Apart from the messages in the log (which should happen every time
l
Thank you for opening this bug and helping make Ubuntu better. This
seems to have occurred because dbconfig-common expects to find a
previous-version 'bacula' database under MySQL, and could not find it.
Have you deleted it?
** Changed in: bacula (Ubuntu)
Importance: Undecided => Medium
** Cha
Thank you for opening this bug and helping make Ubuntu better. Can you
give us a sample ntp(date) config where this happens? Also, please be
aware that ntpdate is set to run when an interface is brought up (see
/etc/network/if-up.d/ntpdate).
** Changed in: ntp (Ubuntu)
Importance: Undecided =>
Looking at the dpkg log, I see that all update requests (since the
beginning of the log, at 2010-03-01) failed for MySQL. I also see the
following lines:
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'debian-sys-maint'@'localhost' (using password:
YES
Thank you for opening this bug and helping make Ubuntu better. Did you
also uninstall samba-common before trying to reinstall? I cannot see a
reference to samba-common being uninstalled (purged) on the dpkg log you
provided.
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
packa
Thank you for opening this bug and helping make Ubuntu better. Can you
please give us the version for your libdns64 package? It seems
/usr/lib/libdns.so.64.1.0 is empty (/usr/lib/libdns.so.64) is a soft
link to it), and this is why ldconfig is complaining.
Please note that this does not impact you
Public bug reported:
I was following the test scenario at
http://testcases.qa.ubuntu.com/Install/ServerEConfig, specifically the
"Test Case: Greedy scheduling policy".
Followed the instructions, expecting to find one NC running two images.
Instead I got this:
euca-describe-instances
Fri Mar 19 1
Indeed. Mathias and I just ran by the same error, and I went on and
increased the disk size for m1.small from 2 to 3 G. I was then able to
start the image.
This was done on Lucid Eucalyptus, running the Karmic image from the
store.
--
default karmic image from image-store doesn't run on default
*** This bug is a duplicate of bug 529056 ***
https://bugs.launchpad.net/bugs/529056
It is indeed a dup of bug 529056. Marking as such.
** This bug has been marked a duplicate of bug 529056
default karmic image from image-store doesn't run on default m1.small
--
Downloaded image from Ima
Public bug reported:
While executing the Image Store images download; this *can* be a dup of
bug 529056, but I do not see any disk error on the log.
ProblemType: Bug
Architecture: amd64
Date: Wed Mar 17 18:35:46 2010
DistroRelease: Ubuntu 10.04
Package: eucalyptus-cc 1.6.2-0ubuntu14
ProcEnviron:
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41178988/Dependencies.txt
--
Downloaded image from Image store fails to start up
https://bugs.launchpad.net/bugs/540577
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
works on a testdrive call:
kvm -vga std -m 512 -cdrom /srv/vBox/iso/lucid-server-amd64.iso -drive
file=/srv/vBox/img/testdrive-disk-BoYURX.img,if=virtio,index=0,boot=on
-usb -usbdevice tablet -net nic,model=virtio -net user -soundhw es1370
--
kvm with -vga std is broken since karmic
https://bug
OK. Just installed it. Please be aware that there is a conflict with
current vgabios seabios, which have to be uninstalled (which cause qemu
to be uninstalled also). But a bit of a dance around apt-get and dpkg
gets it done.
Will test tomorrow, gotta go now.
--
kvm with -vga std is broken since
Will test it, as soon as the package is built.
--
kvm with -vga std is broken since karmic
https://bugs.launchpad.net/bugs/513273
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubun
No right now, no, but I should be able to next week, when I return to
service one of my machines. I do think this is somehow related to my
hardware, also.
--
daily server ISO install fails with a kernel OOPS in KVM
https://bugs.launchpad.net/bugs/531455
You received this bug notification because
Sigh. Had it again, after a reboot. Rebooted clean to 2.6.32-15, tried
again, failed. Rebooted clean to 2.6.32-13, tried again, worked. So...
reopening.
Current status: working on 2.6.32-13, libvirt* at 0.7.5-5ubuntu9, qemu*
at 0.12.3-0ubuntu4
** Changed in: qemu-kvm (Ubuntu)
Status: Inva
Closing Invalid -- today's update to libvirt seems to have done the
trick.
** Changed in: qemu-kvm (Ubuntu)
Status: New => Invalid
--
daily server ISO install fails with a kernel OOPS in KVM
https://bugs.launchpad.net/bugs/531455
You received this bug notification because you are a member
I have just downgraded qemu* to 0.12.3-0ubuntu3; although it still fails
on the 2.6.32-15 kernel, I am able to successfully boot the ISO on
2.6.32-13.
I will try the permutations and zero in the version change that brought
it in.
--
daily server ISO install fails with a kernel OOPS in KVM
https:
I actually found it about two days ago while running the automated ISO
testing from Soren (https://wiki.ubuntu.com/AutomatedISOTesting). After
a reboot on the new kernel (32-15), the autotest would fail
continuously, with the same OOPS in the VM.
I have not been able to bypass it, and -- just in c
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/40092285/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/40092286/CurrentDmesg.txt
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/40092287/Lspci.txt
** Attachment adde
Public bug reported:
Binary package hint: qemu-kvm
I started having this after the latest updates to Lucid -- at least both
the kernel and qemu.
ProblemType: Bug
Architecture: amd64
CheckboxSubmission: 73b44a828b993e7076441e3a0979ddbb
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Wed Ma
27 matches
Mail list logo
