Re: Xen and Windows 2003 HVM

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Fri, Jun 27, 2008 at 10:33:28AM +0200, Hauke Fath wrote:
> At 22:16 Uhr +0200 26.06.2008, Manuel Bouyer wrote:
> >On Thu, Jun 26, 2008 at 05:26:19PM +0200, Hauke Fath wrote:
> >>
> >> Several times, the win2003 DomU has managed to lock up the entire
> >> machine by filling the (admittedly tight) space in the Dom0 file
> >> system by logging > 100 MB to /var/log/xen/qemu-dm.${PID}.log. What
> >> it logs is large amount of whitespace with a few dots and form feeds
> >> - it looks like a repeated attempt at an ascii screenshot from the
> >> Windows screen.
> >>
> >> Since these logfiles are created per-process, management is
> >> difficult, especially for long-running sessions which don't seem to
> >> let go of their files.
> >>
> >> Does anyone know of a way not to let a DomU log to those files?
> >
> >I don't know a way to avoid it, but my files are definitively small.
> >Most are less than 512 bytes.
> 
> Well, most of them are too, here, but:
> 
> # ls -lS qemu* | head
> -rw-r--r--  1 root  wheel  5966301 Jun 26 18:17 qemu-dm.11084.log
> -rw-r--r--  1 root  wheel  1441752 Jun 27 10:28 qemu-dm.14072.log
> -rw-r--r--  1 root  wheel    97851 Feb 18 09:57 qemu-dm.27244.log
> -rw-r--r--  1 root  wheel      812 Jun 26 15:38 qemu-dm.11902.log
> -rw-r--r--  1 root  wheel      809 Mar  3 17:06 qemu-dm.1186.log
> -rw-r--r--  1 root  wheel      809 Mar  4 12:04 qemu-dm.7018.log
> -rw-r--r--  1 root  wheel      808 Jan 29 11:49 qemu-dm.16404.log
> -rw-r--r--  1 root  wheel      808 Jan 23 11:27 qemu-dm.5942.log
> -rw-r--r--  1 root  wheel      738 Jan 22 14:19 qemu-dm.4434.log
> -rw-r--r--  1 root  wheel      650 Mar  4 12:00 qemu-dm.6634.log
> #
> 
> The file qemu-dm.14072.log e.g. starts with
> 
> domid: 32
> qemu: the number of cpus is 1
> Watching /local/domain/32/logdirty/next-active
> qemu_map_cache_init nr_buckets = 4000 size 196608
> shared page at pfn 1ffff
> buffered io page at pfn 1fffd
> Time offset set 0
> xs_read(): vncpasswd get error. 
> /vm/c5373a67-005c-a474-b081-05b77dd34895/vncpasswd.
> Warning: Unable to initialize AAlib mouseUsing AAlib driver: Standard 
> output driver (stdout)
> 
> and then tons of whitespace.

I have:
domid: 3
qemu: the number of cpus is 1
Watching /local/domain/3/logdirty/next-active
qemu_map_cache_init nr_buckets = 10000 size 3145728
shared page at pfn 1ffff
buffered io page at pfn 1fffd
Time offset set 0
Register xen platform.
Done register platform.
register acpi io
Triggered log-dirty buffer switch
xs_write(/vm/d199930f-9d56-6d30-8c83-cc227a9226ea/rtc/timeoffset, 
rtc/timeoffse): write error
xs_write(/vm/d199930f-9d56-6d30-8c83-cc227a9226ea/rtc/timeoffset, 
rtc/timeoffse): write error

And that's all. 

> 
> >What does ps axuww |grep qemu shows are parameters?
> 
> # ps axuww | grep qemu
> root  14072  0.0  0.0 21700 309656 ?       IWa  10:25AM   1:00.02 
> /usr/pkg/libexec/qemu-dm -d 32 -vcpus 1 -boot c -localtime -acpi -usb 
> -usbdevice tablet -domain-name Brocken -net 
> nic,vlan=1,macaddr=00:16:3e:00:48:11,model=rtl8139 -net 
> tap,vlan=1,bridge=bridge0

Mine is:
root     872  9.7  4.0 6260 26092 ?        Rl   12:15PM 0:51.74 
/usr/pkg/libexec/qemu-dm -d 3 -vcpus 1 -boot d -acpi -usb -usbdevice tablet 
-domain-name redmond -net nic,vlan=1,macaddr=00:16:3e:00:05:00,model=rtl8139 
-net tap,vlan=1,bridge=bridge614 -vncunused -vnclisten localhost 

Looks quite similar. I wonder if the error about vncpasswd in your
case can't cause it to switch to some other kind of output ...

Also note that I almost never connect to the vnc console; I use rdesktop.

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--