similar to: My Windows7 VM stopped at loading screen.

Bug report follows. Please CC me if you want me to read the reply, as I'm not subscribed to ext3-users. [1.] One line summary of the problem: Ext3 has just causing filesystem corruption which required fsck to fix. [2.] Full description of the problem/report: I just had my machine lock up with an ext3 oops, preceeded by a bunch of error messages in the logs. On rebooting, after replaying the

After a bit of searching through these archives I haven't found quite my problem described yet, so let me bounce this off you guys: Red Hat 7.2, I run up2date whenever patches come out; right now I'm using kernel 2.4.9-21. Things have been quite pleasant for several months, but in the last week I have begun receiving the following error messages: Feb 22 08:06:27 medmeta kernel:

Hi! Today I switched over to devfs. I'm on Debian unstable, installed devfsd, installed a kernel with devfs support and "devfs mount on boot". Reboot, devfs is being used. All over a sudden, dmesg reports: Linux version 2.4.21-ac1 (root@hummus) (gcc version 3.3 (Debian)) #1 Sun Jun 15 19:06:13 CEST 2003 ... kjournald starting. Commit interval 5 seconds EXT3-fs: mounted

Wondering if anyone here might better be able to diagnose an issue we're seeing, or point me to some guidelines for this sort of thing. There are two machines with identical hardware, both running Red Hat 7.3's stock SMP kernel (required due to third party software). Both have come down with the same symptoms after having run fine for a number of months. The initial errors were these:

A brand new system setup with RH 7.3 is still Oopsing after every X hours. The problem started after about 1 week without errors. Sometimes everything is locked, sometimes still messages are written to /var/log/messages. Sometimes other processes keep running (can still ping the machine) I upgraded the kernel to 2.4.18-19.7.x, changed the memory, but still got problems. When I read all sort of

While compiling two kernels and untarring a third, my root fs was remounted r/w and I got the following in dmesg (kernel 2.4.19-pre9): EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28 Aborting journal on device ide0(3,2). ext3_abort called EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal. Remounting filesystem read-only Remounting filesystem read-only

Hi All, I am running on CentOS Released 6.1 final. Been using and running Linux KVM quite well for quite some time, something goes wrong after I perform yum upgrade. I created new VM yesterday without any problem, same exact installation procedure, installed FreeBSD 8.2. I tried to create a new VM today after yum upgrade, it's able to detect the hard disk, when I start commit FreeBSD 8.2

Is there any way to get virsh / libvirt to create a domain such that I can later connect to it via QMP (without hacking the code)? The command line that libvirt creates for my current setup looks like this: /usr/local/bin/qemu-system-x86_64 -S -M pc-0.12 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name winxpsp2 -uuid ab244939-c804-1aff-68b6-9324f174c3c8 -nodefconfig -nodefaults

I am trying to connect a KVM-QEMU VM to OVS-DPDK vhostuser port. But, I am encountering a few errors. Since I am very new to libvrt and Linux I am not able to sort them out. Any guidance in this regard would be a great help. These are my System Logs: Mar 28 18:03:04 dpdk-OptiPlex-5040 libvirtd.service: 1529: debug : virCommandRunAsync:2429 : About to run LIBVIRT_LOG_OUTPUTS=3:stderr

Hi All, I m a novice developer of Linux applications. Recently I faced a file system corruption. (I guess) I have a Kernel 2.4.7-10 with ext3 file system in compact flash. The system was up for 3 months and was running with average load conditions. One fine day, it just started sending kernel messages on the serial console. The message was like this. EXT3-fs error (device ide0(3,2)):

Hello list, In short: I am experiencing a problem where trying to start a VM which is allready running on a different libvirt host. Starting it fails, thanks to sanlock, but the disk dies on the original hypervisor and the vms filesystem is rendered read-only. Long version: i have the following setup: Two machines (H1 and H2) using CentOS 6.2 with the packages:

Hello Everyone, My pc run in CentOS 7.4 and install libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10 ALL-in-One. I use python-sdk with libvirt and run [self.domain.updateDeviceFlags(xml, libvirt.VIR_DOMAIN_AFFECT_LIVE)] on CDROM (I want to change media path). However, I enable libvirt debug log , the log as below: "2018-02-26 13:09:13.638+0000: 50524: debug :

Dear list, I have moved my HVMs from xen to kvm and it worked well except some problems using virsh. First, one OpenSolaris HVM does boot with warnings: WARNING: /pci at 0,0/pci1af4,1100 at 1,2 (uhci1): No SOF interrupts have been received, this USB UHCI host controller is unusable* *The corresponding process: /usr/bin/qemu-system-x86_64 -S -M pc-0.12 -enable-kvm -m 1024 -smp

I am running libvirt 0.9.8, virsh -V Virsh command line tool of libvirt 0.9.8 See web site at http://libvirt.org/ Compiled with support for: Hypervisors: Xen QEmu/KVM UML OpenVZ LXC Test Networking: Remote Daemon Network Bridging Nwfilter VirtualPort Storage: Dir Disk Filesystem SCSI Multipath iSCSI LVM Miscellaneous: AppArmor Secrets Debug Readline in an ubuntu 12.04.1 install. I created a

On 10.07.2013 11:37, Lentes, Bernd wrote: > Hi, > > i have a SLES 11 SP2 64bit host with three guests: > - Windows XP 32 > - Ubuntu 12.04 LTS 64bit > - SLES 11 SP2 64bit > > The SLES guest shuts down with the host shutdown. The others not. When i shutdown these two guests with the virt-manager, they shutdown fine. > ACPI is activated in virt-manager for both of them.

On 10/03/2017 04:40 PM, Nick Gilmour wrote: > I have set root in both for user and group in the qemu.conf and changed the > file permissions to root like it was before. Now I'm getting this error: > > *# Error 1#* > *Unable to complete install: 'internal error: process exited while > connecting to monitor: us=pci.0,addr=0x5.0x7 -device >

Dear all, I install centos 6.3-64bit in a new server and also installed KVM using yum. Then I create a new virtual machine(i686) to install windows xp, but it's very slow, do you know why? Server: CPU: i7 3370, Memory: 16GB. Virtual machine: 1 cpu and 1GB ram. type: i686 KVM information: qemu 4223 1 9 15:10 ? 00:00:41 /usr/libexec/qemu-kvm -S -M rhel6.3.0 -cpu

I've "ported" an old VMware VM containing Windows NT 4 SP6 into libvirt/kvm/qemu and got it running (more or less). However, the CPU graph next to the VM in virt-manager shows it starts using 100% of the allocated CPU as soon as it reaches the "OS Loader" screen, and stays there even after Windows has booted and I've logged in. (There's a dip now and then,

WinXP ignores a USB passthrough! Hello, I need a persistent passthrough of a USB-device: Bus 001 Device 020: ID 04e6:5311 SCM Microsystems, Inc. I added <hostdev mode='subsy.... </hostdev> like this to xml file: [...] <on_crash>restart</on_crash> <devices> <hostdev mode='subsystem' type='usb' managed='no'>

On 03/05/2018 03:47 AM, Peter Krempa wrote: > On Fri, Mar 02, 2018 at 15:32:44 -0500, John Ferlan wrote: >> >> >> On 03/02/2018 08:28 AM, Peter Krempa wrote: >>> On Tue, Feb 27, 2018 at 09:53:00 +0100, Michal Privoznik wrote: >>>> On 02/27/2018 03:06 AM, Star Guo wrote: >>>>> Hello Everyone, >>>>> >>>>>