similar to: Linux PV udom stays in state r after migration

It is a pleasure to see what it has become, but - it scrambles the vnc-sessions (start virt-manager, open a win console, close all, start virt-manager again try open vnc-console => fail, fixed by xm vncviewer <name> => fail, again => works, also next time in virt-manager => same problem again) - Is it currently possible to connect to other xvms running next to the machine and may

Last night I upgraded from b127 to b130 and now I can''t mark autostart domains: # virsh autostart lunar-1 error: Failed to mark domain lunar-1 as autostarted error: failed to serialize S-Expr: (domain (on_crash restart) (uuid 91c21040-2098-bc0d-b401-3908f3a21667) (bootloader_args) (vcpus 1) (name lunar-1) (on_poweroff destroy) (on_reboot restart) (cpus ( Searching the archives

https://bugzilla.redhat.com/show_bug.cgi?id=466681 just to be sure that some one in xvm-team notices that before any bits from xvm-gate are putback ;) Florian

Hi, I can''t seem to get libvirtd to accept remote connections. Both systems are built using genunix''s b130. It seems that connections originating from the xvm0 server itself are fine but as soon as I go on to the other box and run the same python script (or simply virsh) the connection gets dropped immediately. Telnetting to port 16509 confirms that it drops the connection

I have installed the 210 gplpv (debug), when I try to update them with current gplpv I get a BSOD even so when I try to uninstall them. Now I have made a bootentry that specifies NOGPLPV, what gives me a bootable system after such a crash, I found (uninstalling the leftover driver packages after getting bsod during uninstall of the main package) that uninstalling the net driver leads to bsod. Now

I have tried to define a domain or using virt-install both failed. Could some one give me the correct command to do this? I used: virt-install --nographics --paravirt --os-type=solaris --os-variant=opensolaris --ram 1024 --name cam-host --disk path=/dev/dsk/c0t600A0B800049E902000008EB4A9CE744d0p0,driver=phy -l /export/media_images/sol-nv-b121-x86-dvd.iso thx, florian

Adding apic_verbosity=debug gives me that (hope nothing miss-typed as I have no serial console on this box). I found a lot of suggested workarounds: - noapic as suggested in output gives an noapic isn''t support - acpi_skip_timer_override has no effect at all Thx, Florian (XEN) Initing memory sharing. (XEN) AMD-Vi: IOMMU not found! (XEN) I/O virtualisation disabled (XEN) Getting

Adding apic_verbosity=debug gives me that (hope nothing miss-typed as I have no serial console on this box). I found a lot of suggested workarounds: - noapic as suggested in output gives an noapic isn''t support - acpi_skip_timer_override has no effect at all Thx, Florian (XEN) Initing memory sharing. (XEN) AMD-Vi: IOMMU not found! (XEN) I/O virtualisation disabled (XEN) Getting

I'm new to using Wine. I'm running UBUNTU 8.04 on a Dell B130/1300 laptop. Ubuntu seems to running fine. I uploaded Motorola Phone tools with no problem using the Wine installer. The program launched ok and even went to the internet an downloaded and installed the updates. The problem is it doesn't see my usb port. How do I get Wine to use the usb port? Also I get no sound out when I

I am in the middle of converting a FreeBSD 8.0-Release system to OpenSolaris b130 In order to import my stuff, the only way i knew to make it work (from testing in virtualbox) was to do this: label a bunch of drives with an EFI label by using the opensolaris live cd, then use those drives in FreeBSD to create a zpool. This worked fine. (though i did get a warning in freebsd about GPT

Hi, I have problem installing or running domU OS (Windows XP or Redhat 7.3). The machine runs CentOS 4.4 X86_64, Xen-3.0.3. Paravirtual domU works without problem. The problem is that when I run command "xm create <config>", nothing would happen. hvmloader does not seem get started at all. I''ve tried installing both 64bit and 32bit vnc, sdl but did not see any

There seems to be no list of needed packages, when starting with a fresh opensolaris dev (b121 today). hg gmake I guessed by now. Additionally the stuff mentioned here: http://opensolaris.org/os/project/indiana/building_on/ But are there further packages needed? Maybe some one should add a verified list to the building howtos... Florian

I've recently installed wine on my laptop (Dell B130) to play War3 (which works flawlessly on my desktop btw). The problem is that since I first ran wine, when ever I close my laptop the backlight stays off. Normally it turns back on when I open it, but now it stays dark. Also (I believe a related problem) wine leaves my display in a lower-than-usual resolution. What configuration changes does

Can anyone confirm my action plan is the proper way to do this? The reason I''m doing this is I want to create 2xraidz2 pools instead of expanding my current 2xraidz1 pool. So I''ll create a 1xraidz2 vdev, migrate my current 2xraidz1 pool over, destroy that pool and then add it as a 1xraidz2 vdev to the new pool. I''m running b130, sharing both with CIFS and ISCSI (not

does anybody in the list has succesfully installed centos in dell b130? Im planning to use it for this laptop. thanks tad -- sometimes truth is stranger than fiction -bad religion- http://www.bloglines.com/blog/mailist -------------- next part -------------- An HTML attachment was scrubbed... URL:

Just the output of one of the viridian enabled windows hvm machines: Florian virsh dumpxml titan <domain type=''xen'' id=''40''> <name>titan</name> <uuid>cedb6201-82d6-3c96-4da3-e0bfad6a7501</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>2</vcpu> <os>

hi everyone, .. one of the Sambas fails to authenticate users. I have four virtually identical Samba systems which are configured as AD members. All servers seem fine, I can $ net ads lookup | status | dn | user | testjoin .. and so on. But, problem is that all servers except one can successfully: smbclient -L $(hostname) -UDOM\\user here that one server fails: SPNEGO login failed: Logon

On 05/10/2019 13:01, Pascal Christen via dovecot wrote: > > Hi > > > We tried to update our Dovecot Director-Ring to 2.3 (latest version) > and had one problem/bug. When we try to deliver an email from Exim to > a receiving Dovecot (2.3 latest) via the LMTP-Proxy the LMTP process > stays open forever and never closes. So after a few hours, we hit the > LMPT-Process

On 06/12/2019 11:08, Pascal Christen via dovecot wrote: > Hi > > I tried to get some logs: https://pastebin.com/Z8xVzpzW > > As you can see the process isn't shutdown and still in transaction as > long dovecot is running. It destroyed the transaction when I stopped > Dovecot. And this behavior only happens when the mailbox of user is full... > > Any Ideas how to

On 23/06/2020 16:01, Pascal Christen wrote: > Hi Stephan > > We tried it again last week with the latest dovecot version and still > having the same issue. The whole setup works perfectly fine with the > latest version of dovecot 2.2 > > The problem only exists if the quota of the user is full, every other > message gets delivered without a problem, and the lmtp process