similar to: VMs failing to restart

It seems it's not possible to monitor kvm virtual image network interfaces via SNMP. MRTG's cfgmaker says ### The following interface is commented out because: ### * has no ifSpeed property and other monitors are consistently reporting that vm's interfaces are exceeding traffic thresholds (even on lo ...). Which is no surprise if the threshold is zero. I found a hint on some

On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 5/5/2017 1:42 ??, Nikolaos Milas wrote: > > Hmm, it seems that the boot flag should be removed from /dev/vda2 >> partition? >> > > Actually, I tried this and left the boot flag only to /dev/vda1. I > rebooted and I am still getting the same error. :-( > > I was hoping we were

Hi, I have a virtual machine which fails to boot linux-4.1.8 while mounting file systems: > * Mounting local filesystem ... > ------------[ cut here ]------------ > kernel BUG at drivers/block/virtio_blk.c:172! > invalid opcode: 000 [#1] SMP > Modules linked in: pcspkr psmouse dm_log_userspace virtio_net e1000 fuse nfs lockd grace sunrpc fscache dm_snapshot dm_bufio dm_mirror

Hi, I have a virtual machine which fails to boot linux-4.1.8 while mounting file systems: > * Mounting local filesystem ... > ------------[ cut here ]------------ > kernel BUG at drivers/block/virtio_blk.c:172! > invalid opcode: 000 [#1] SMP > Modules linked in: pcspkr psmouse dm_log_userspace virtio_net e1000 fuse nfs lockd grace sunrpc fscache dm_snapshot dm_bufio dm_mirror

? 2020/1/9 ??9:48, David Hildenbrand ??: > Ping, > > I'd love to get some feedback on > > a) The remaining MM bits from MM folks (especially, patch #6 and #8). > b) The general virtio infrastructure (esp. uapi in patch #2) from virtio > folks. > > I'm planning to send a proper v1 (!RFC) once I have all necessary MM > acks. In the meanwhile, I will do more

? 2020/1/9 ??9:48, David Hildenbrand ??: > Ping, > > I'd love to get some feedback on > > a) The remaining MM bits from MM folks (especially, patch #6 and #8). > b) The general virtio infrastructure (esp. uapi in patch #2) from virtio > folks. > > I'm planning to send a proper v1 (!RFC) once I have all necessary MM > acks. In the meanwhile, I will do more

Hello, I am running into problems with virt-builder on my Ubuntu-14.04 install. Please find the checklist below: 1. What are you trying to achieve? I'm trying to build a standard Ubuntu 14.04 disk image. 2. What exact commands did you run? I ran "virt-builder ubuntu-14.04" 3. What was the precise error/output of these commands? The process gets stuck indefinitely at

Folks I know that support for the network adaptors supported by the 'e1000' driver have been removed from the base distribution. However, I have exactly that controller (Broadcom Gigabit Ethernet PCI, not PCIe). Is there a way for me to add support for that on Centos 8.1? Perhaps a driver in an RPM package? Thanks David

At the risk of angering the crash Gods, my sustem has NOT crashed again since I downgraded the kernel from 2.6.18-1.2239.fc5 to 2.6.18-1.2200.fc5. Given that newfound stability, and my lack of time, I'm going to put on hold any further diagnostics, until the next kernel revision is released. I have submitted a report at bugzilla.redhat.com (bug 218128). (Ah, nuts; accidentally created a

On 5/5/2017 1:19 ??, Gianluca Cecchi wrote: > Could you verify, if /dev/sda is your boot disk, with the command > > fdisk -l /dev/sda > ? It's /dev/vda in my case: # fdisk -l /dev/vda Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512

On Thu, Jul 26, 2018 at 11:29 AM, syzbot <syzbot+604f8271211546f5b3c7 at syzkaller.appspotmail.com> wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit: dc66fe43b7eb rds: send: Fix dead code in rds_sendmsg > git tree: net-next > console output: https://syzkaller.appspot.com/x/log.txt?x=127874c8400000 > kernel config:

On Thu, Jul 26, 2018 at 11:29 AM, syzbot <syzbot+604f8271211546f5b3c7 at syzkaller.appspotmail.com> wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit: dc66fe43b7eb rds: send: Fix dead code in rds_sendmsg > git tree: net-next > console output: https://syzkaller.appspot.com/x/log.txt?x=127874c8400000 > kernel config:

Hi list, I've recently managed to install CentOS 4.4 on an Apple Mac Pro. Functionality-wise everything works great, but when trying to benchmark the system, I don't get stable runtimes, they differ by more than 30%. For example a benchmark run with our PDE solving code takes between 500 and 800 s on the completely unloaded machine. Suspicious kernel output (complete output attached):

Hi, I am looking for dual or quad fast ethernet NICs that work with CentOS. There is no need for high performance so regular fast/pci is ok. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20101228/1f5e2944/attachment-0001.html>

On Thu, Oct 01, 2015 at 03:10:14AM +0200, Thomas D. wrote: > Hi, > > I have a virtual machine which fails to boot linux-4.1.8 while mounting > file systems: > > > * Mounting local filesystem ... > > ------------[ cut here ]------------ > > kernel BUG at drivers/block/virtio_blk.c:172! > > invalid opcode: 000 [#1] SMP > > Modules linked in: pcspkr

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

>>> ... Bottom line; There are timing issues with TFTP transfers on VM machines emulating BIOS hardware. Probably the interrupt based timer is not the culprit; now I'm working on /core/fs/pxe/core.c trying to see if there's something wrong there. Best, Patrick <<< I've been working on this issue, I have tested the timers, and as you guys mentioned before they

Have you experienced this? What's going on when this occurs? What do I need to do to keep it from occurring? Please advise. Thanks. Dec 4 10:18:17 localhost kernel: e1000: eth1 NIC Link is Down Dec 4 10:18:19 localhost kernel: e1000: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX Dec 4 10:18:21 localhost kernel: e1000: eth1 NIC Link is Down Dec 4 10:18:23 localhost kernel:

I have Centro 5.4 it named starts at bootup but fails to restart when I give command service named restart and it there is no any error in syslog messages. With reload command I get the following message in syslog :- Nov 25 14:03:30 unitedinfotechs named[2201]: using default UDP/IPv4 port range: [1024, 65535] Nov 25 14:03:30 unitedinfotechs named[2201]: using default UDP/IPv6 port range: [1024,