Fedora X86/64bit :: Libvirtd And Lxcstartup Errors After Reboot - No Such Device Or Address
Jan 7, 2011
Unfortunately accidentaly I disconnected my usb drive my computer and my VMs run from so I just rebooted for a quick fix Now I can't open virt-manager locally and the VM's can't get network connections I see this in the logs after the last two reboots
Code:
grep lxc /var/log/messages |tail -n 2
Jan 7 00:45:04 F820 libvirtd: 00:45:04.524: warning : lxcStartup:1895 : Unable to create cgroup for driver: No such device or address
Jan 7 11:52:53 F820 libvirtd: 11:52:53.325: warning : lxcStartup:1895 : Unable to create cgroup for driver: No such device or address
[code]...
I tried restarting libvirtd after with no love so I rebooted and cgroup was gone this was a clean install of F14, after this started I brought the system current, I can provide the packages installed but they errors didnt change
Error occurred while booting from QEMU. I am building a minimalistic linux kernel using virtual hard disk. GRUB was loaded successfully. But while booting kernel, I got the following errors :
"can't open /dev/tty2 : No such device or address " "can't open /dev/tty3 : No such device or address " "can't open /dev/tty4 : No such device or address "
I, then created these files using mknod. Still the same errors occur.
I've got a problem, the interfaces are shutted by the system, so after the reboot I have no network conectivity even if I used the setup command to configure the interfaces.
Recently I installed Fedora 12 64bit in my HP Compaq 6720s. Among many other problems that I had and I solved with your help, I have the following problem:When I restart or shut-down Fedora 12 it crushes and hangs and only thing that I can do is to stop and restart my laptop by means of ON/OFF button.My question is:Is there any way to see this error (maybe some log file or something) so I can send this message or log file here in this forum and get some help?
This has been happening for over a week and is preventing me from installing updates, They all download OK then as they start to install I get this error message. Test Transaction Errors: package nss-softokn-3.12.4-19.fc13.x86_64 (which is newer than nss-softokn-3.12.4-17.fc13.i686) is already installed Then the update fails and I am unable to continue.
I am a complete noob with this OS, I left for a week in the hope it would sort it's self out.
I'm not sure if this helps and I'm not sure how to tell anyone what I found, but was a problem in Fedora 10 and 11 were VM's running in KVM would lockup due to (disk or network) IO activity. The problem silently vanished as soon as I installed Fedora 12 as my VM. I upgraded my VM to Fedora 13 and the problem re-surfaced. Oddly, no other distributions seem to have this problem any more judging from Google. My configuration:Host = x86_64, 4 cores, Fedora 11VM = i686, 2 virtual cores, Fedora 10, 11, or 13 (Fedora 12 works)What worked for me was using only one core in my VM. Things have been stable for a few days now
i was trying to crate a script to show the last time iptables had seen a given IP address (contained in the ipt_recent kernel hook -- my user-defined table name is 'iplist'). The ipt_recent table yields the following information (IPv4 addresses masked for paranoid reasons):
Such command yields the following (I'm willing to live with the trailing zero):
Code:
Wed Jun 20 05:48:46 EDT 2266 src=www.xxx.yyy.zzz 0
[code]....
I presume the ipt_recent table uses the standard UNIX epoch timestamp. Am I using the date command syntax incorrectly, is this a 32-bit vs 64-bit break, or it is something else? Please note that I am using FC10, and I have double-checked my system clock settings (both BIOS and OS). The system has only been running during 2009 (no reboot yet).
I'm using fedora12 with KVM. I'm also using iptables for filtering and nat. Problem is when I start libvirtd, it overwrites my current iptables and iptables config file (/etc/sysconfig/iptables).
Ok it leaves an old copy in /etc/sysconfig/iptables.old, but the main problem is that it removes also all my custom settings from filter and my full nat. I would like the keep control on my iptables and like to manage them on my own. But I cant find an option in the libvirtd config files and/or the libvirtd startup scripts to prevent libvirt from changing my iptables. how I can make libvirtd stop tempering with my iptables?
I have a fedora 13 rc3. The problem is that boot the system stops here Starting libvirtd daemon Prior to that, stop at this point registering binary handler for windows application. I got up to enter the tty2 to remove Wine This time to stop here Starting libvirtd daemon
I tried to install F12 on my new IDE-HDD. The installation completed without any errors. But, when rebooting my PC I got a dark screen with error message: reboot and select proper boot device.
No BIOS boot up issue, since booting up using other hard disk running windows has no problem at all. I have set the hardisk jumper to master/primary, tried to re-install F12 a couples of time, but didn't make any difference.
I'm running 9.10 on a Dell IM1012-6780BK netbook (very nice and snappy, btw). I was in the process of installing the ubuntu-restricted packages (apt-get was halfway into setting-up libtwolame0) when the machine locked up and I was forced to do a hard reboot. Now, at the CLI, I try to remove the corrupted package before re-installing, but I get the following errors: (they seem to be persistent, no matter what I'm trying to install/uninstall via apt-get...$ sudo apt-get --purge remove ubuntu-restricted-extras
Reading package lists... Done Building dependency tree Reading state information... Done
I'm installing Fedora 11 x86_64 from the DVD iso. The SHA256 checksum was fine, and the media checked out fine just prior to install. The F11 install seems to go perfectly and I get all the way through the installation. However, on reboot, I get this message, "No bootable device -- insert boot disk and press any key"!!!!I'm installing to an old Intel 975XBX2 motherboard with 4GB of memory, which I have used successfully, flawlessly for every single Fedora install since F6. I've only been using one hard drive with a FAT32 partition, and an NTFS partition for Windows XP, the remainder of the disk is Fedora.I've probably tried this F11 install about 8 or 9 times already with no success; actually, the installation seems to go perfectly, but I just cannot boot the PC. I think there's something wrong with GRUB being written into the MBR of the hard drive, because I cannot boot DOS on that FAT32 partition, I can't boot into the NTFS partition which contains XP, nor can I boot into F11.Anyone else having problems with the boot? I've been a long time Fedora user and was counting on the reliability of F11: Wondering if that Anaconda re-write had anything to do with all of these problems?
Reboot and select proper boot device or insert boot media in selected boot device and press a key. I got this error after: Reducing my Windows 7 partition by about 100gb. Creating a new partition (100gb) and copying my Ubuntu partition (10gb) to the new partition. After it was copied, and pasted, the original partition was deleted. I now had two partitions a new 100gb Ubuntu partition and a 600gb (or so) Windows 7 partition.
All of this was done using a bootable USB with Ubuntu 10.10 and GParted partition editor. Now when I boot I get the "Reboot and select proper boot device or insert boot media in selected boot device and press a key." error.
After installing Opensuse 11.3 i get massive graphical errors after reboot. Those errors directly start after the first resolution change after grub. So i used nomodeset from now on and installed the drivers from nvidia.
After this X11 only flasht up very shortly and i got this logs:
I have a problem w/ the LAN connection: the MAC address appears to be different after every reboot. I checked it w/ the ifconf command and looked for the eth0 hardware address. I am using Ubuntu 10.10 on ASUS K51AE laptop. The Fax/Modem/LAN/WLAN interface is integrated 802.11 b/g/n (I only have problem with the LAN connection).
Currently I cannot use my modem internet connection, it is really annoying. I would like to keep on using Ubuntu, but if I cannot find a solution I will have to return to windows...
I am having this problem on my old 64-bit Debian box (stable's Jessie) box, but nothing seems to fix it from what I saw online like in [URL] ... and other forums. Maybe I missed something?
I'm trying to troubleshoot some strange networking problems. The pattern seems to be that only newer distributions are affected. CentOS 5.4 and Ubuntu 8.04 work fine out-of-the-box. But Arch, Sidux, AntiX, Fedora, etc. show the same pattern of errors.Certain websites cannot be found unless I disable ipv6 in Firefox. And certain addresses cannot be resolved using various terminal commands (wget, apt-get, yum, etc.). What I would ideally like is a permanent solution, perhaps changing some settings on my router, so that I don't have to deal with this each time I test-drive a new distro. I have a hunch the issue has something to do with my DSL provider (Fairpoint) filing for bankruptcy.
One more piece of information that may or may not be relevant: I recently switched a website from one hosting company to another. I noticed there was a delay of several days where I saw the old version at the old host, but viewing the site at a friend's house or the coffee shop showed the new site on the new host. This leads me to suspect DNS issues perhaps, but this is not an area of expertise.
I recently upgraded from Lucid to Maverick, which went fairly smooth. Then I upped my RAM with some new memory sticks (4Gb to 8Gb). Since about then, I'm seeing these errors in syslog:
Code: Jun 6 22:23:52 howler console-kit-daemon[1224]: WARNING: Failed to add monitor on '/dev/tty2': No space left on device Jun 6 22:23:59 howler console-kit-daemon[1224]: WARNING: Failed to add monitor on '/dev/pts/0': No space left on device I also get errors when running "tail -f" as root:
Code: tail: cannot watch `/var/log/syslog': No space left on device
I searched around and I found some other reports of the tail -f error, with the suggestion of increasing fs.inotify.max_user_watches. I set it to 16384, and that at first resolved the tail -f problem, but now I'm getting that error again even after upping max_user_watches.
I know swap is suggested to be approx. the same size as RAM, but with this upgrade RAM is now bigger than the 5.7G of swap.
I am having trouble with connecting my Sony Ericsson phone with my Ubuntu 9.10 using USB. It doesn't matter how I choose to connect it - "File Transfer" and "Phone Mode" - both does not work. The phone IS charching, when it is connected, but it doesn't shows anywhere. When I type "lsusb" in terminal, it does not show me my phone. When I look in "/var/log/messages" there is NO error. It does not even show the procedure of connecting and disconnecting the phone. What could be the problem?
For the record, I'm having the same issue as the OP with Lucid with a backported 2.6.35-28 kernel and a Samsung scx-4623fw printer hooked up via USB. Same symptoms - lsusb hangs until the printer is unplugged, devices aren't recognized, etc. Dmesg output includes a bunch of device descriptor errors:
[603.091961] usb 7-1: new full speed USB device using ohci_hcd and address 9 [618.241335] usb 7-1: device descriptor read/64, error -110 [633.521986] usb 7-1: device descriptor read/64, error -110
I suddenly started having a bunch of USB issues (including complete system locks whenever I plugged in a logitech USB mic) around early march with the stock lucid kernel. Everything was fine before that.
I'm designing an embedded USB device. When I connect the device to the computer, I get the following messages:
usb 1-3: device descriptor read/64, error 2 usb 1-3: device descriptor read/64, error 2 usb 1-3: device descriptor read/64, error 2 usb 1-3: device descriptor read/8, error -71 usb 1-3: device descriptor read/8, error -71 usb 1-3: device descriptor read/8, error -71
Note that other USB devices work fine. I am fairly certain that the problem is with my hardware. I'd like info on what these error messages mean to help my debug. Searching Google I wasn't able to find any explanations about what these errors mean exactly.
I'm running Cent OS 5.4 with kernel 2.6.18-164.el5 on an i686
i'm having some issues trying to get the oSUSE 11.3 x64 hypervisor working, these are the errors im getting when i've opened the virtual machine manager, and clicked on one of the 2 options.
verify that 'libvirtd' daemon has been started:
Unable to open connection to hypervisor URI 'qemu:///system': unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 971, in _try_open None], flags)
