FreeBSD Shutdown problem

[dswartz]

forgive me, i've never used git before. i assume i need to discard everything after a certain point, except for the irq9 change? if so, how far back am i supposed to go?

 

[Equand]

http://stackoverflow.com/questions/...t-repository-with-specific-revision-changeset

there are two ways,
please post the results here after testing

 

[dswartz]

Yeah, I just realized there are two ways to approach this: 1) take the current code and back out the irq9 fix, and 2) take a snapshot as of the timeframe that qemu shipped with proxmox had, and add the irq9 fix to that. #1 seems much easier (and more reliable.) if that fixes it, that is the issue, otherwise some other change is. i will let you know...

 

[dswartz]

well that didn't work. i seem to have mismerged something (and/or a subsequent commit to that file is the issue.) anyway, i just noticed that there is a tag just for that one cherry-picked change. i will try that later...

 

[Equand]

might be... the seabios in current proxmox pack is ancient, so you'll have to go down a lot i think... find the qemu version then look which seabios was bundled, or easier, check the bios on startup of a container

 

[dswartz]

Sigh. Apologies for the wasted bandwidth here. I forgot that I had violated a cardinal rule by not only updating the BIOS but switching to ext4. I think what was killing me was the write barrier in ext4. I switched back to ext3 with your BIOS and the performance is fine. Sorry again

 

[Equand]

no problem, stuff happens
cheers

 

[dswartz]

I've been encountering something annoying (I can't swear it only started with the bios with the above fix, but it definitely happens 100% of the time for me.) If I do some kind of reboot (either via the reboot button in proxmox, or typing 'reboot' in the linux host), the VM shuts down - it does NOT reboot. I would be glad to track down whatever diagnostic info you think might be helpful...

 

[Equand]

Same here but with BSD vm's, seems like this fix plays bad with something else in acpi... I wonder what? Maybe we should post an issue to their tracker? I can't find it though

 

[dswartz]

Oh, sorry. I didn't mean to imply it was only linux. I see this with ANY OS I have tried. BSD, linux and windows XP Unfortunately, reverting to the old bios is not an option, since I lose the ACPI shutdown

 

[tom]

look like you talk about containers (OpenVZ), this thread is about KVM - don´t mix this - pls open new thread for new topic but before use the search function of the forum - this question is discussed several times already.

 

[dswartz]

What did I post talking about containers? I *was* talking about KVM!

 

[tom]

Because the description of your problem sounds like an OpenVZ issue to me.

 

[dswartz]

I thought I had replied to this post, but I don't see it. Anyway, if you re-read the thread, I refer to bios and acpi several times. Neither of those concepts has anything to do with openvz.