Thank you Dan Streetman and all for your work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867375
Title:
systemd-networkd: UseRoutes behavior change with introduction of
UseGateway param
To ma
I can confirm, with "systemd 237-3ubuntu10.41 amd64" this bug is fixed for me.
To clarify: "use-routes=false" in netplan ignores the default gateway given by
DHCP.
I'm using Ubuntu Server 18.04.4 with wired network interfaces.
--
You received this bug notification because you are a member of Ubu
I can confirm, with "systemd 245.4-4ubuntu3.1 amd64" this bug is fixed for me.
To clarify: "use-routes=false" in netplan ignores the default gateway given by
DHCP.
I'm using Ubuntu Server 20.04 with wired network interfaces.
I don't know how to perform more tests, but don't see any problems so fa
I can confirm, with your build from
"https://launchpad.net/~ddstreet/+archive/ubuntu/systemd";, networkd is
behaving like before in Ubuntu 18.04. With this patch "use-routes=false"
in netplan ignores the default gateway given by DHCP.
Please, forgive my ignorance, but how do I return to normal off
Thank you very much for the rapid info!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867375
Title:
systemd-networkd: UseRoutes behavior change with introduction of
UseGateway param
To manage no
Hi,
this bug is affecting me as well on Focal (Ubuntu 20.04).
I used the option use-routes=false in netplan to ignore the default gateway and
now it doesn't work.
As you have explained, now the right way is to use the UseGateway option of
systemd.
But there is no option in the current version o
This is not ANNOYING. This is work BLOCKING! Please, realize it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243806
Title:
The names column has its width dictated by other columns
To manage noti
*** This bug is a duplicate of bug 1243806 ***
https://bugs.launchpad.net/bugs/1243806
I'm on Ubuntu 14.04 and cannot resize columns, only Name column gets resized
smaller and bigger, but never bigger from the initial size.
This bug is a MAJOR annoyance. It makes your computer 50% unusable! W
I could test my KINGSTON SV300S37A120G with firmware 521ABBF0.
I used Martin's test:
sudo dd if=/dev/sda of=/dev/zero &
sudo find / >/dev/null 2>&1 &
sudo grep -r . / >/dev/null &
and manual "fstrim -v /" several times.
I did this for about 5 minutes.
No problems and "fsck.ext4 /dev/sda" sa
I don't see an option to edit here, so will write it on a new post:
My chip is BCM 4318 and it has the same issues on my laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313221
Title:
modprob
Same here!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313221
Title:
modprobe wl crashes with broadcom 4306
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
*** This bug is a duplicate of bug 1025244 ***
https://bugs.launchpad.net/bugs/1025244
Well, I don't think that this is a desired behavior. I don't think it should be
put in the wishlist neither.
Since the machine dies, pauses and whatever, I think this is not a
desired/predicted way of man
*** This bug is a duplicate of bug 1025244 ***
https://bugs.launchpad.net/bugs/1025244
I can confirm that the machine doesn't die or pause when there is no "space"
problem. All of the problems were caused by the space issue!
Although now I have another problem - qcow2 image is broken after 6
I'm sorry, I meant 21. not 20.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025244
Title:
qcow2 image increasing disk size above the virtual limit
To manage notifications about this bug go to:
ht
@Serge, thank you for answering.
Well, I think this is not entirely true. I think that from my above post, 13.
and 20. should be with the same results, if it were true. The truth is that
when a snapshot is present, sometimes it uses the available space, sometimes it
doesn't. (!???)
I think there
I did some testing with a WindowsXP guest, that I have and could test on.
It seems that this behavior is not present at the beginning. But at the moment
we create a snapshot it is starting to write on top of the current size. So, it
is like this:
1. Image is:
Code:
qemu-img info WindowsXP.img
May be here will be more convenient for reading:
http://www.linuxquestions.org/questions/linux-virtualization-90/disk-physical-size-more-than-virtual-size-qcow2-image-4175416848/#post4730524
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Yes, I have created one snapshot and did fallocate in the beginning. The
other image, which I have problems with, also has snapshots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025244
Title:
qco
OK, I have created another bug report for the increasing size of image file:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1025244
I'm monitoring now, after creating a new image (with no fallocate) and having
enough space on the host, if the machine will die again. I suppose it will,
be
Public bug reported:
Using qemu/kvm, qcow2 images, ext4 file systems on both guest and host
Host and Guest: Ubuntu server 12.04 64bit
To create an image I did this:
qemu-img create -f qcow2 -o preallocation=metadata ubuntu-pdc-vda.img
10737418240 (not sure about the exact bytes, but around this
I have copied all of the content of the guest machine, deleted the image
ubuntu-pdc-vdb.img and created a new one without "fallocate", but only
with preallocation=metadata. The problem is that the image is growing
progressively and has obviously no limit, although I gave it one. The
root filesystem
I can confirm that the "Paused" case with IO_ERROR is happening when a user
(samba client) starts to copy files (70GB of pictures with 10MB/s). It crashes
almost immediately!
@Serge, the Ubuntu machine is with 1GB allocated and the Windows machine is
with 2GB allocated. The host is 4GB. I had a
Now it did it again - at 11:07. Same errors and symptoms (Paused).
Well, I see a pattern here. Every max. 15 min. before a round hour (for example
11.00) and every max. 10min. after this hour there are IO_ERRORs in the log and
therefore pausing the machine.
I saw that other dyings are also 15 min
Now it did it again - at 10:47. Same errors and symptoms (Paused).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
Title:
Ubuntu 12.04 64bit Guest (qemu/kvm) dies randomly
To manage notificat
There are no errors in the guest's syslog. Well I now saw the log and it seems
it has IO errors on "device": "drive-virtio-disk1". How could I determine which
of the two is this virtual disk - is there drive-virtio-disk0 or this is the
first?
Also, now it was obviously in Paused state, but the m
Now it happened again. By the way, I have made a script to autostart it 10
seconds after ping lose. This time the virt-manager was not connected at the
time it died. Also, the script couldn't start it again, because of some error.
When I connected with virt-manager to see what is the status - it
I have set the log_level and have virt_manager disconnected. Thank you
for your cooperation! Now I'm waiting, when it happens will write
immideately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10229
Of course. It has shut off at these hours (directly from host's
/var/log/libvirt/qemu/ubuntu-pdc.log):
2012-07-10 09:56:23.767+: shutting down
and
2012-07-10 11:50:09.191+: shutting down
** Attachment added: "Kern.log at the times of diying"
https://bugs.launchpad.net/ubuntu/+source/
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218623/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
Title:
Ub
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218624/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
Title:
apport information
** Attachment added: "RelatedPackageVersions.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218622/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218621/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218620/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/102
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218619/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218618/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
Title:
Ubun
apport information
** Attachment added: "KvmCmdLine.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218617/+files/KvmCmdLine.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
Ti
apport information
** Attachment added: "KernLog.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218616/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218615/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1022901/+attachment/3218614/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
apport information
** Tags added: apport-collected precise
** Description changed:
Using qemu/kvm
Host and Guest: Ubuntu server 12.04 64bit
The thing is that the guest randomly dies and it is s frustrating. There
is PDC on the guest and people cannot work. It happens almost every d
Maybe listing, because virt-manager is going on constantly. I'll stop it and
see what happens. I'm not sure what are these apport things about, but will do,
immediately!
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
I think it is the qemu-kvm package responsible...
** Package changed: ubuntu => qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022901
Title:
Ubuntu 12.04 64bit Guest (qemu/kvm) di
Public bug reported:
Using qemu/kvm
Host and Guest: Ubuntu server 12.04 64bit
The thing is that the guest randomly dies and it is s frustrating. There is
PDC on the guest and people cannot work. It happens almost every day.
There are no logs in the syslogs of host and guest in the time of c
Public bug reported:
Binary package hint: ebox
I've entered 2 gateways - "def" (default) and "sec" (secondary). When I
disconnect the default gateway it switches to the secondary according to the
rule given. But when I turn it back, it doesn't bring the default gateway back.
In fact it disable
Same to me: The user corner is not functioning: logging in at https://name:
will give you: Internal Server Error...
Also the WAN Failover does not bring up the default gateway after it has failed
and then succeeded back.
--
ebox webinterface not working properly
https://bugs.launchpad.net/b
45 matches
Mail list logo
